Skip to content

Conversation

havan
Copy link
Member

@havan havan commented Feb 3, 2023

Documentation for Platform API Methods

@havan havan requested review from c4t-ag and evlekht February 3, 2023 20:32
```

- `networkID`: the ID of the Network
- `assetID`: the fee assed ID
Copy link
Member

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
Copy link
Member

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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants