Account + controller
The intent is tied to one smart-account address and one controller H160.
TWIX treats wallet interoperability as an authorization problem. Signed bytes, domain separation, nonce lanes, generation boundaries and explicit policies matter more than UI convenience.
For controller execution, security-sensitive intent fields are part of the MetaMask-signed canonical message.
The intent is tied to one smart-account address and one controller H160.
Recipient, denomination and amount are signed rather than supplied by the relayer later.
Relay fee and optional exact relayer are included in authorization boundaries.
Chain ID, namespace, generation, nonce and expiry prevent cross-context reuse.
Native action funds and relay fees are aggregated before policy evaluation.
Session keys cannot use generic Wasm in v0.2 because native spend meters cannot reason about arbitrary contract-internal value.
Individual Code-719 Meta Accounts are instantiated with no Wasm admin. The factory manages future templates, not upgrade authority over existing accounts.
When configured, guardian recovery requires both authorization by the guardian and acceptance by the new controller, followed by the enforced delay before permissionless execution.
The full source and observed mainnet test matrix are published for peer review. Pending cases stay labeled pending until they are actually observed.