One Chain. Two Ecosystems. Zero Bridges.
MPCQ achieves simultaneous native compatibility with Cosmos and Ethereum through the x/evm module — a canonical Cosmos SDK module that embeds a full EVM execution environment within the blockchain state machine.
Dual-Ecosystem Interoperability
The Same State, Accessed Through Two Interfaces
The native ampcq denomination is automatically mapped to an EVM contract address (0xCf209484cBfB9194D97b562aEB20B624ea03B4db). The ERC-20 interface at that address reads from and writes to the same state the Cosmos bank module manages for the native coin. No bridging contract. No multisig. No wrapped asset. No depeg risk.
Your MPCQ balance is equally accessible from MetaMask (as 0xCf20...) and Keplr (as native MPCQ). Both interfaces read and write the identical state.
Fraud Proof Eliminated
Because the EVM state and the Cosmos bank state are the same deterministic state accessed through different interfaces, there is no bridging contract that can be exploited, no multisig that can be compromised, and no wrapped asset that can depeg.
Unified Developer Experience
Smart contract developers write standard Solidity and deploy to the EVM execution environment. Cosmos SDK module developers write in Go and interact with the bank, staking, and IBC modules. Both developer communities build on the same chain, using the same native asset, without understanding each other's toolchains.
Exchange Integration Simplified
Any centralized exchange that supports either Cosmos SDK chains or EVM-compatible chains can list MPCQ without custom integration work. The chain speaks both protocols natively.
The Bech32 Prefix Decision
Why MPCQ Uses the cosmos Prefix
MPCQ uses the cosmos Bech32 prefix deliberately — not as a brand claim, but as the deterministic consequence of the cryptographic standard.
When a private key is imported into a Cosmos SDK chain using ethsecp256k1 key derivation (as MPCQ does), the Cosmos address is computed by taking the 20-byte Ethereum address representation and encoding it with the Bech32 prefix. The output — when using the cosmos prefix — produces the standard cosmos1... format that every Cosmos wallet, explorer, and IBC relayer has supported since genesis.
Using a custom prefix such as mpcq would require every wallet, explorer, and relayer to implement custom mapping logic. By using cosmos, MPCQ inherits universal compatibility with zero integration effort.
This is not a cosmetic shortcut. It is an adherence to the cryptographic standard.
Interchain Architecture
Three Nodes. One Unified System.
The MPCQ interchain architecture is deployed across three physically distinct VPS nodes, each serving a specific role in the cross-chain communication pipeline.
Chain ID: 262144
VPS 1 — MPCQ Main Chain
Native MPCQ. StableSwap contract (0x6E17...). All DePIN tokens, DeFi protocols, and synthetic assets.
Chain ID: mpcq-bridge-1
VPS 2 — Bridge Hub
Sovereign Axelar fork plus Hermes relayer.
- Connected to 7 EVM chains: Arbitrum, Base, BNB Chain, Optimism, Linea, zkSync Era, Avalanche
- Pending: Ethereum, Polygon
- Isolated by unique chain identifier keccak256("MPCQ-BRIDGE-V1")
Chain ID: mpcq-ica-1
VPS 3 — ICA Orchestrator
Interchain Account module. x402 Facilitator (port 8088). Gas Optimizer. Payment verification. Automated Treasury sweeps.
- Native token iMPCQ (1,000,000 supply) for gas and staking
All three nodes are IBC-connected with Let's Encrypt SSL.
Sovereign Bridge + Public Axelar
Two Bridges. One Unified Asset Flow.
MPCQ maintains two parallel bridges, each serving a distinct strategic purpose.
Sovereign Bridge (VPS 2)
Federated — MPCQ validators
A self-hosted fork of the Axelar Network protocol, operated entirely by the MPCQ ecosystem's own infrastructure.
- 7 connected chains (2 pending)
- Fast, high-performance, isolated namespace
- Use case: high-value, latency-sensitive transfers
Public Axelar Bridge
Permissionless — AXL stakers
Integration with the permissionless Axelar Network connecting 65+ EVM chains through a decentralized validator set staking AXL tokens.
- Variable speed, economic security
- Broad market access, smaller chains
Both bridges converge on a unified asset flow: external USDC enters through either bridge, is verified and routed through the ICA Orchestrator, and is minted as native MPCQ-USD via StableSwap at a 1:1 ratio.
x402 Payment Verification
DePIN API Monetization Through HTTP 402
The x402 Facilitator (running on port 8088 of VPS 3) is a payment verification system that enables DePIN infrastructure monetization through the HTTP 402 Payment Required standard — a previously underutilized HTTP status code now revived for Web3-native API monetization.
- 1
User Payment
A user pays MPCQ-USD to a designated payment address, producing a unique transaction hash on MPCQ Main Chain.
- 2
API Request
The user sends an API request to the DePIN service endpoint with the transaction hash in the HTTP Payment header.
- 3
Verification Call
The endpoint calls the x402 Facilitator on VPS 3, port 8088.
- 4
On-Chain Verification
The Facilitator queries MPCQ Main Chain to verify transaction existence, payment amount, correct recipient, and double-spend prevention via nonce tracking.
- 5
Service Provisioning
Upon successful verification, a signed authorization token is returned and the service is provisioned.
- 6
Treasury Allocation
30% of all verified fees are automatically routed to the ecosystem Treasury via the ICA module.
Security Model
Defense in Depth
Each VPS serves a distinct role. Compromise of the ICA Orchestrator does not grant control over bridge assets or native assets.
- The ICA module can only execute pre-authorized transaction types, limiting the blast radius of any single-node compromise.
- IBC channels between the three VPS nodes use standard Cosmos SDK security. Light client updates flow in both directions. Any fork or equivocation causes IBC channels to freeze — a fail-safe, not a failure condition.
- The sovereign bridge's unique chain identifier cryptographically isolates it from the public Axelar network, and vice versa. A message signed for the MPCQ bridge cannot be replayed on Axelar mainnet.
- The x402 Facilitator maintains a nonce registry for each payment transaction hash. Once consumed, a hash cannot be reused — preventing replay attacks where a single payment is used multiple times.
- As the ecosystem matures, the sovereign bridge validator set will transition from ecosystem-operator-controlled to a decentralized set of independent validators. The ICA module's authorization scope will be constrained through on-chain governance.