CAPABILITY MAP

What TWIX does.
And what it does not.

The canonical Runtime and the Meta Account line solve different problems. This page keeps those boundaries explicit.

TWIX META

MetaMask-controlled Cosmos execution.

Experimental mainnet smart-account architecture built on CosmWasm.

IDENTITY

H160 controller

Store an Ethereum-compatible 20-byte controller on a Cosmos-native smart account.

SIGNING

EIP-191 authorization

MetaMask signs canonical domain-separated intent bytes without sending an Ethereum transaction.

EXECUTION

Native Cosmos messages

Validated intents produce Cosmos BankMsg and other explicitly permitted actions.

RELAY

Permissionless transport

A Cosmos wallet relays the transaction and pays outer gas; relaying does not confer controller authority.

POLICY

Spend + action controls

Optional limits can constrain native value and enabled action classes.

SESSIONS

Scoped delegates

Independent session epochs, nonces, expiry, permissions and native budgets.

CANONICAL RUNTIME V2.0.2

Solidity ABI semantics on Cosmos Hub.

Code 681 is the existing deployed line and remains separate from hardened Meta research.

ABI

Solidity-style calls

Recognized selectors execute against supported logical runtime templates.

IDENTITY

One-to-one binding

Existing Cosmos signers can bind one H160 identity through the canonical two-wallet ceremony.

ASSETS

Logical contracts

The runtime models supported token/NFT-style semantics without claiming full EVM equivalence.

SETTLEMENT

Cosmos Hub security

Execution remains CosmWasm state transition logic settled on Cosmos Hub.

SAFETY

Pre-activation gate

Public writes remain controlled by deployed runtime state and governance procedures.

COMPATIBILITY

Fixed signed domain

The deployed binding domain remains CosmosHub Solidity ABI Runtime binding.

NON-CLAIMS

Important limits.