TWIX META · ARCHITECTURE

Your MetaMask.
Your Cosmos account.

TWIX Meta is a CosmWasm smart-account authorization layer. An ordinary Ethereum EOA signs domain-separated EIP-191 intents; the smart account recovers the controller, validates the full envelope, and emits native Cosmos messages only when every security condition passes.

MAINNET PROOF COMPLETEHARDENING IN PROGRESSNO SNAP REQUIRED FOR PROVEN PATH
AUTHORIZATION FLOW

The relayer is transport, not custody.

Recipient, amount, relay fee, account, controller, chain, nonce, generation and expiry live inside signed intent boundaries. The relayer cannot silently rewrite them.

MetaMaskcontroller EOA · EIP-191
Permissionless relayKeplr today · Xeteria coming soon
TWIX Metaverify → CosmosMsg
HARDENED CONTROL PLANE

Fail closed by default.

v0.2 expands the original proof into a security model designed to constrain authority instead of making a smart account generically omnipotent.

GENERATION

Controller eras

Controller rotation or recovery increments generation, invalidating signed envelopes from the previous era.

NONCE LANES

Execution is not administration

Execute, admin, recovery and session authorization use independent nonce spaces and signed domains.

SPEND POLICY

Per-denom ceilings

Max-per-transaction and block-window budgets account for native action value plus relay fees.

SESSIONS

Scoped authority

Sessions have their own epoch, nonce, expiry, permission bitmask and native spend budgets.

ROTATION

Two signatures

Current controller authorizes the change; the proposed new controller independently accepts it.

RECOVERY

Guardian + delay

Optional recovery requires guardian authorization, new-controller acceptance and a minimum delay.

RELAYER

Signed economics

Fees are signed, capped and optionally bound to one exact Cosmos relayer.

WASM

Explicit allowlists

Controller Wasm execution requires explicit account permission and an allowlisted target; sessions cannot use generic Wasm in v0.2.

FACTORY

Future templates only

The factory can control future account templates. Existing individual Meta Accounts are instantiated without a Wasm admin.

DEPLOYMENTS

Proven line vs hardened line.

The two deployments are intentionally separate so new security work cannot retroactively change the evidence produced by v0.1.

v0.1 · PROVEN

Mainnet proof line

Account / factory717 / 718
Meta Accountcosmos1qhcf6sr7xtr9zaw6wk7s44209yctdv4ykzf2hy7vuk8vkwjn3z3ssdfyfk
Execution TX04D5F17D8A7CF6D6FA8C30B9E01CFC6435061D15822EB97BB630B841A466E447
v0.2 · HARDENING

Adversarial test line

Account / factory719 / 720
Factorycosmos1xw0rqrjgekrerjrz55n09ezuajcdw2pqp204w2kdsya7szmx55ssug3f89
Hardened accountcosmos14u8hrq7tez3e3pdlhyg4jtgp6jk3jdyzfq9vl3srzclzxl6680qq9np325