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
I am opening this to bring up the topic of nomination pools integration in all Nova-based apps, not just IOS.
While the feature is evolving, and the way that it will store locked funds will also evolve, I speculate that pools are here to stay, and they are the future of Polkadot native staking.
That being said, none of the nova-based wallets yet support pools. Write operations can come next, but the fact that your funds in pools are not even shown in your wallet anymore is something that I can encourage you to fix.
A similar issue was made for subscan about "pool funds being missing". I think this is a low hanging fruit and fixing it can reduce confusion for tens of thousands of pool members, which is growing rapidly: subscan-explorer/subscan-issue-tracker#45
I am opening this to bring up the topic of nomination pools integration in all Nova-based apps, not just IOS.
While the feature is evolving, and the way that it will store locked funds will also evolve, I speculate that pools are here to stay, and they are the future of Polkadot native staking.
That being said, none of the nova-based wallets yet support pools. Write operations can come next, but the fact that your funds in pools are not even shown in your wallet anymore is something that I can encourage you to fix.
A similar issue was made for subscan about "pool funds being missing". I think this is a low hanging fruit and fixing it can reduce confusion for tens of thousands of pool members, which is growing rapidly: subscan-explorer/subscan-issue-tracker#45
Lastly, see here for a guide about how to integrate pools: https://forum.polkadot.network/t/nomination-pools-integration/361
If need be, feel free to reach out to the core staking developers community here: https://matrix.to/#/#nompools-support:matrix.parity.io
The text was updated successfully, but these errors were encountered: