You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A good use case for a runtime API is to fetch a pool's stash and reward address. E.g. poolAddresses(poolId).
In Dapps we are currently using code similar to the following for determining a pool's stash and reward address, which adds complexity and deals with low level binary operations and magic constants - this is not too Dapp developer friendly:
… the pool (#6357)
closes#6358
Adds the following runtime api to pallet-nomination-pools.
`pool_accounts(pool_id)`: Returns `(bonded_account, reward_account)`
associated with the `pool_id`.
cc: @rossbulat
---------
Co-authored-by: command-bot <>
Co-authored-by: Branislav Kontur <[email protected]>
A good use case for a runtime API is to fetch a pool's stash and reward address. E.g.
poolAddresses(poolId)
.In Dapps we are currently using code similar to the following for determining a pool's stash and reward address, which adds complexity and deals with low level binary operations and magic constants - this is not too Dapp developer friendly:
This seems to be a low hanging fruit to improve the developer experience for pools.
The text was updated successfully, but these errors were encountered: