COSMOS AUTHORITY
Keplr
Signs the Cosmos Hub state change that records the canonical V2.0.2 binding.
Not connected
Xeteria · coming soon
TWIX BIND · CANONICAL V2.0.2 CEREMONY
Two wallets.
One on-chain identity.
MetaMask proves control of the H160. Your Cosmos wallet separately authorizes the state change. The canonical runtime permanently records the one-to-one relationship when public binding is enabled.
1. Connect both sides
TWIX never asks MetaMask to send an Ethereum transaction. MetaMask is used only for the H160 proof.
EVM IDENTITY
MetaMask
Signs the EIP-191 ownership proof for the H160 identity.
Not connected
2. Eligibility & canonical challenge
Both mappings must be free, the H160 must not be reserved, and the runtime must accept public writes before signing.
BINDING STATE
AWAITING WALLETS
Connect a Cosmos wallet and MetaMask to inspect the one-to-one binding state.
PROTOCOL NOTE
The deployed V2.0.2 contract verifies a fixed canonical EIP-191 message domain. Twix Chain branding does not alter those signed bytes.
01Cosmos signerNot connected
02MetaMask H160Not connected
03ChallengeNot built
04EIP-191 proofNot signed
05Cosmos bindNot submitted
3. Build, sign, submit
The proof is generated in memory only. Account changes or expiry changes invalidate it immediately.
CANONICAL SIGNABLE PAYLOAD
Connect both wallets, confirm eligibility, then build the canonical challenge.
Runtime status is unknown. Signing stays locked until the canonical manager can be queried.
Bound by the runtime maximum. A fresh height is read before challenge creation.
MetaMask signatureNot signed
Cosmos transactionNot submitted
TWIX ID · VERIFIED ON-CHAIN
Identity binding established
Cosmos—
↔
H160—
Canonical runtime identity
This UI points at one fixed Cosmos Hub deployment. A different deployment requires a different signable payload.
Network
cosmoshub-4
Canonical manager
—
Browser client
Not loaded