-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PAPI] add p.getClaimables and p.getConfiguration methods #80
base: dev
Are you sure you want to change the base?
Conversation
``` | ||
|
||
- `networkID`: the ID of the Network | ||
- `assetID`: the fee assed ID |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think its not just fee asset, this (and only this) asset (CAM) is also used for bonding (dao, staking) and depositing
- `assetSymbol`: the symbol of the fee asset ID | ||
- `hrp`: `beech32HRP` used in the addresses | ||
- `blockchains[]`: a list of Primary network blockchains | ||
- `minStakeDuration`: The minimum duration a validator has to stake |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@peak3d we have equal min-max staking duration by design, should we still have 2 fields in both config and documentation?
- `supplyCap`: The supply cap for the native token (CAM) | ||
- `codecVersion`: The codec version used for serializing | ||
- `verifyNodeSignature`: Camino VerifyNodeSignature | ||
- `lockModeBondDeposit`: Camino LockModeBondDeposit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@peak3d probably, this struct should also include validator reward import period and dao bond amount
Documentation for Platform API Methods
platform.getClaimables
View on Playgroundplatform.getConfiguration
View on Playground