feat: handle Summon wallets with capability-based metadata#208
feat: handle Summon wallets with capability-based metadata#208kanyuku wants to merge 1 commit intoMeshJS:mainfrom
Conversation
|
@pierrepeach is attempting to deploy a commit to the MeshJS Team on Vercel. A member of the Team first needs to authorize it. |
- Update Wallet type to include capabilities\n- Modify buildWallet to compute capabilities for Summon, SDK, and Legacy wallets\n- Update hooks (useAppWallet, useMultisigWallet, useWalletBalances) to leverage capabilities\n- Update UI components (CardWallet, ShowInfo) to use capability-driven rendering\n- Add unit tests for Summon wallet capabilities
kanyuku
force-pushed
the
feature/issue-205-summon-hook-ui-updates
branch
from
2f131b8 to
3eb3fb2
Compare
There was a problem hiding this comment.
@kanyuku does your approach still cover all the edge cases ?
There was a problem hiding this comment.
Hi @kanyuku from the brief overview it looks good.
Just wanted to check with you if you checked if our edge cases still work.
In the very beginning we created our wallets with unordered cbor lists and have to keep that compatibility.
Regradless happy to see your contrbution : )
Can I find you on twitter?
|
2 participants
This PR introduces a capability-based metadata system to properly support Summon wallets and fix incorrect address display and staking/governance feature exposure.
Summary of Changes
Wallettype with a newcapabilitiesfield to standardize wallet metadata.buildWalletto compute and assign capabilities for Summon, SDK, and Legacy wallets.Overall, this ensures accurate address handling and feature visibility while creating a consistent, extensible foundation for supporting multiple wallet types.