Permissions
Wallet-Native Capabilities
In Moss today, core asset abilities are increasingly wallet-native rather than something users should think of as separately installable apps.
3 sectionswallet-native-capabilities
01
Token Abilities
Moss treats common token actions as wallet capabilities rather than something every app should rebuild.
That means apps entering the account context can reuse one shared token approval, transfer, and signing model.
- Token permissions do not need to be redesigned by every app.
- Transfers and batched approvals can share the same account semantics.
- Users understand what their wallet allowed, not a different rule system inside each app.
02
NFT Abilities
NFT abilities follow the same logic. Moss tries to keep NFT permissions and actions tied to the account layer instead of scattering them across isolated app-specific flows.
That makes listings, approvals, delegated execution, and multi-asset flows easier to reason about.
- Useful for NFT markets and signed-listing flows.
- Also useful for delegated execution and delayed execution models.
- The user sees one continuous wallet experience instead of a different NFT rule set per product.
03
What Makes an App Available
- The app should exist in the Store-supported product path.
- The account needs to install it and enable it inside the wallet.
- Specific actions may still require signatures or permission confirmation.
- Users should still be able to disable or withdraw access later.