Who controls user assets
Responsibilities of the two account types
Section titled “Responsibilities of the two account types”- EOA wallet: an externally owned wallet directly controlled by the user. It confirms deposits, approvals, and operations initiated by the user.
- AA Vault: an ERC-4337 smart account deployed on the Jasper Vault chain. It handles batch transactions, contract permission checks, automated execution, and gas sponsorship.
- Ownership: the AA Vault contract stores an immutable owner. A UserOperation signature must match that owner.
- Address relationship: one EOA can own multiple AA Vaults. Users can independently calculate and verify addresses with VaultFactory.getAddress(owner, salt).
Operation authorization
Section titled “Operation authorization”| Operation | Authorization |
|---|---|
| Initiate a deposit from Base | The user EOA confirms approve, when required, and the transferRemote transaction |
| Initiate a standard UserOperation through an AA Vault | AA Vault owner signature |
| User-initiated cross-chain redemption | The user EOA signs data containing the Vault, asset, amount, destination chain, and expiration |
| Automated liquidation, settlement, limit orders, and risk controls | Authorized contract modules or system execution accounts act according to preconfigured on-chain rules |
Platform permission boundaries
Section titled “Platform permission boundaries”Jasper Vault uses a two-layer structure of user owner permissions and contract module permissions:
- The user’s EOA private key remains in the user’s wallet. Signatures are generated locally by the wallet, and the platform cannot sign with that private key.
- Standard AA Vault UserOperations are authorized by its EOA for deposit and withdrawal operation signatures.
- Automated liquidation, settlement, and cross-chain execution are performed by authorized modules according to contract rules.
- The Diamond owner manages governance configuration and core module upgrades and is a critical governance permission.
This structure lets users retain EOA signature control while supporting the automated execution required by the trading system. All module calls and governance changes leave on-chain records.