One handbook.
The complete TWIX build.

What TWIX is.

TWIX Mainnet is an independent Cosmos SDK network with native Ethereum-compatible execution. Cosmos-facing and EVM-facing tools operate against the same chain state. The production chain ID is twix-1; the EVM chain ID is 1415006552 / 0x54574958.

Four layers, one public identity.

Wallet / dApp
     │ HTTPS / WSS
     ▼
TWIX public edge ──────► Explorer / Docs / Apps
     │ restricted proxy
     ▼
TWIX node services
     │
     ├─ Cosmos consensus + staking + governance
     └─ Native EVM execution

Where everything lives.

Canonical constants.

Genesis SHA-256: 9ef3c22a4820d0c32ad3418f4c848382e88064f8083db373375d0b3f4978d8b0. Block 1 hash: 8AE55F99837AFB6836DE279A1914B9828C2E70A5D23CACC2AE873F3856BBBE8A.

TWIX is native chain currency.

The display unit is TWIX. The base denomination is atwix with 18 decimals:

1 TWIX = 1,000,000,000,000,000,000 atwix

Native TWIX pays gas and participates in Cosmos staking. It is not an ERC-20 contract. Any future wrapped representation must be treated as a representation of native supply, not additional native issuance.

The public validator set.

Consensus validators produce and attest blocks under the Cosmos staking/consensus model. Public validator information includes operator address, moniker, staking status, bonded tokens, commission and jail state.

Canonical network access.

curl -s https://rpc.twixchain.com/status

curl -s https://evm.twixchain.com \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Raw backend services and unsafe administrative namespaces are intentionally not part of the public interface.

MetaMask and Keplr.

MetaMask / EIP-1193

{
  "chainId": "0x54574958",
  "chainName": "TWIX Mainnet",
  "rpcUrls": ["https://evm.twixchain.com"],
  "nativeCurrency": {"name":"TWIX","symbol":"TWIX","decimals":18}
}

Keplr

Keplr uses twix-1, coin type 60, TWIX Bech32 prefixes, atwix with 18 decimals, and the EVM-signing feature flags published in /keplr-chain.json.

Indexed visibility across both execution worlds.

The Explorer indexes TWIX Mainnet into protected SQLite storage outside the public webroot. Public pages cover blocks, transactions, contracts, addresses, validators, governance proposals, tokenomics and charts.

Explorer installation and diagnostics endpoints remain operational/admin surfaces and are protected separately from normal public browsing.

On-chain policy, not marketing copy.

TWIX uses Cosmos governance for network parameter changes. The website queries chain state and deliberately distinguishes proposal intent from executed configuration.

Live state and policy are labeled separately.

The Explorer tokenomics dashboard reports native supply, bonded stake, community-pool state and supply snapshots. The tokenomics policy file contains a seven-bucket economic model, security-release schedule, fee-policy target and representation rules. Policy values are not represented as deployed controls unless the chain enforces them.

Cosmos and Ethereum tooling against the same mainnet.

Use standard Cosmos RPC/REST clients on the Cosmos side and Ethereum JSON-RPC tooling such as ethers, web3 or Foundry on the EVM side. The public interface intentionally omits dangerous administrative namespaces.

# EVM chain identity
cast chain-id --rpc-url https://evm.twixchain.com

# Cosmos node status
curl -s https://rpc.twixchain.com/status

# Bonded validators
curl -s 'https://api.twixchain.com/cosmos/staking/v1beta1/validators?status=BOND_STATUS_BONDED'

One source of truth for integrations.

Signed physical records anchored to TWIX.

validator.twixchain.com hosts the TWIX Data Attestation Protocol application. Devices or gateways create Ed25519 identities locally, canonicalize readings, sign record commitments, and submit them to the Device API. Records can be batched into SHA-256 Merkle roots and optionally anchored through an EVM transaction.

Analysis without custody or execution.

The toolkit contains seven public calculators and labs. The live-market tools use a same-origin whitelisted proxy with direct public-provider fallbacks; no private trading API key is required.

Wallet integration direction.

The Xeteria page documents the intended TWIX-aware wallet integration path across Cosmos and EVM interfaces. It is deliberately labeled as an integration direction where functionality has not yet been claimed as fully shipped.

Expose what users need. Keep privileged surfaces private.

Public HTTPS/WSS reverse proxies front the intended interfaces. Raw backend ports, unsafe Comet RPC and EVM administrative/debug namespaces are not part of the public launch surface. Consensus validator metadata is public; consensus signing material is not.

Static-first public site with dynamic read-only helpers.

The main site is predominantly static HTML/CSS/JavaScript for resilience and straightforward hosting. A service worker caches stable pages/assets but deliberately bypasses PHP, Explorer and Data Attestation runtime routes so live status and market data are not frozen into stale PWA responses.

Public code and protected state are separated.

public_html/
├── assets/                  shared site CSS / JS
├── downloads/research/      preserved research packages
├── explorer/                Explorer application code
├── validator/               Data Attestation application code
├── .well-known/             canonical network manifest
├── docs.html                complete handbook
├── validators.html          consensus validator directory
├── validators-data.php      read-only staking data adapter
├── status.php               read-only network status adapter
└── network / wallet manifests

../explorer-data/             protected Explorer DB/config (not public)
../validator-data/            protected TDAP DB/keys/config (not public)

The /explorer/ and /validator/ directories remain compatible deployment sources while the root .htaccess redirects those paths to their dedicated public subdomains.

Read-only public checks; protected admin diagnostics.

The public adapters default to the canonical TWIX TLS endpoints. Server administrators can override upstreams without editing public code by setting TWIX_RPC_URL, TWIX_REST_URL and TWIX_EVM_URL; the validator directory uses TWIX_REST_URL.

The Cosmos Hub work remains evidence, not current configuration.

The archive preserves Meta Account, EIP-191 binding, CosmWasm runtime, security and peer-review material from the earlier Cosmos Hub research line. Archive pages use their own navigation and explicit warnings so users do not confuse ATOM/Cosmos Hub experiments with TWIX Mainnet.

Names used across the platform.

TWIX Mainnet

The production twix-1 Cosmos/EVM network.

Consensus Validator

A Cosmos validator participating in staking/consensus and block production.

TWIX Data Attestation

The application at validator.twixchain.com for signed physical-data records. Not a consensus validator.

TWIX Explorer

The indexed public chain-history application at explorer.twixchain.com.

atwix

The 18-decimal base denomination of native TWIX.

Research Archive

Historical Cosmos Hub Meta Account and binding experiments preserved for review.