ZXOXO

DOCS / LAYERZERO / LIVE ON FIVE CHAINS

Every chain to the Zero.

Send one packet. From every chain you mine on, LayerZero carries your mZXO into one omnichain record. Nothing to trade and nothing moves: a record, verified twice, locked until 30 Nov.

Chains wired5/5
Verifiers per packet2 of 2
Packet size128 bytes
Tokens created0
MessagingLayerZero V2
HubBase
Your mZXOStays put
RecordOnly up

In one minute

Think of five receipts sent to one ledger. The receipts never move your mZXO. They prove it.

  1. 01You mine on five chainsYour mZXO is claimed chain by chain. Arbitrum only knows your Arbitrum part, Base only your Base part, and so on.
  2. 02Each chain sends one packetA LayerZero message carrying the mZXO you hold on that chain. You pay a small fee there; whatever is not used comes back.
  3. 03One record, one totalThe ZXOXO hub on Base adds them up: your omnichain mZXO, confirmed by two independent verifiers before it counts.

The map

Four chains send packets through LayerZero. Base, where the hub lives, records directly.

LAYERZERO V2Endpointtakes the packet and the fee2 of 2 verifiersLayerZero Labs · HorizenExecutordelivers it to the hubArbitrumgateway · eid 30110Optimismgateway · eid 30111BNB Chaingateway · eid 30102Avalanchegateway · eid 301060ZXOXO hubBase · eid 30184Baserecord hereDots are packets. Each one carries one wallet's mZXO on one chain, checked by both verifiers before the hub counts it.

Life of a packet

One click on the mining page, eight steps on-chain. Usually a few minutes end to end.

Youyour walletGatewaythe chain you send fromLayerZeroverify and deliverHubon Base1 · send() + LayerZero fee2 · reads your mZXO: balanceOf(you)3 · 128-byte packet4 · unused fee back to you, same transaction5 · both verifiers confirm it6 · lzReceive(packet)7 · keeps the highest per chain8 · Delivered: your omnichain total, on /mine
  • Steps 1 to 4 happen in your one transaction on the chain you send from. If it fails, nothing is sent and the fee stays with you.
  • Step 5 waits for the source chain to finalize, then both verifiers check the packet independently. One is not enough.
  • Steps 6 to 8 happen on Base. You can close the page while it travels: the packet does not need you anymore.

Inside a packet

Four fixed fields, 32 bytes each. Every packet is the same size, so every packet costs the same.

bytes 0-31version1
bytes 32-63accountthe wallet that sent it
bytes 64-95balanceits mZXO on that chain
bytes 96-127sentAtsource block time
ZxoPacketCodecabi.encode(
  uint8   version,   // 1
  address account,   // msg.sender on the source chain
  uint256 balance,   // ZxoMined.balanceOf(account) there
  uint64  sentAt     // block.timestamp there
)                    // always 4 words = 128 bytes
  • The balance is read, never typed. The gateway asks ZxoMined for the sender's own balance. Nobody can pick the number or report for someone else.
  • Anything else is refused. A payload of the wrong size, version or range is logged and skipped by the hub, never counted.

How the hub counts

One rule: per wallet and per chain, the hub keeps the highest balance it has seen. Your total is the sum over chains. mZXO only grows, so the highest is always the latest.

EventARBBNBBASETotal
01 Packet from Arbitrum carrying 120.00120.000.000.00120.00+120.00
02 Packet from BNB Chain carrying 80.00120.0080.000.00200.00+80.00
03 You claim more on Arbitrum, then send an update carrying 150.00150.0080.000.00230.00+30.00
04 An older Arbitrum packet carrying 120.00 arrives late150.0080.000.00230.00no change
05 Record here on Base: 40.00150.0080.0040.00270.00+40.00
Arbitrum 150.00BNB 80.00Base 40.00

Example numbers. Step 4 shows why late or out-of-order delivery can never lower or double a record.

Use it

Everything happens in the "Send one packet" card on the mining page, with your linked wallet.

  1. MineKeep your device mining. Rigs and blocks add mZXO on each chain.
  2. Claim on a chainClaim your mZXO on that chain first. A packet carries what you hold there, so an unclaimed chain has nothing to send.
  3. Send packetPress Send packet on that chain's row. Your wallet switches chain and shows the fee. Confirm.
  4. Watch it landThe row shows In flight with a LayerZero Scan link, then Delivered. Your hub total updates.
  5. Base: Record hereThe hub lives on Base, so Base needs no packet: Record here reads your Base mZXO directly. Gas only.
  6. Claim more, updateClaimed again? The row turns into Send update. Only the increase is added.
Open the mining page

What you see

Each chain's row is in one of four states.

Claim here firstNo mZXO claimed on this chain yet. Nothing to send, nothing to pay.
Send packetYou hold more here than the hub has recorded. One click, one fee. After a first packet it reads Send update.
In flightSigned and on its way. Kept through a page reload, so the same packet is never paid for twice.
DeliveredThe hub holds everything you hold on this chain. On Base it reads Recorded.

What it costs

One LayerZero fee per packet, paid in the coin of the chain you send from, plus that chain's network fee. Quoted live from the contracts:

ARBI0.000139ETH · about $0.25
OPTI0.000139ETH · about $0.25
BNB0.000416BNB · about $0.24
AVAX0.0370AVAX · about $0.26
BASE0no LayerZero fee · gas only

The button sends a small margin on top of the quote. LayerZero takes the exact fee and returns the rest to your wallet in the same transaction.

Security

2 of 2 verifiersEvery packet is confirmed by LayerZero Labs and Horizen. Both must agree, or it is not delivered.
Pinned librariesThe send and receive libraries are fixed per pathway, so a later change to LayerZero defaults cannot touch them.
Only from our gatewaysThe hub accepts packets only from the LayerZero endpoint, and only from the ZXOXO gateway on each chain.
Only your own numberA packet carries the balance of the wallet that sends it, read on-chain. Nobody can report for anyone else.
Only upHighest per chain wins. Late, repeated or out-of-order packets cannot lower or double a record.
Never stuckThe hub never rejects a delivery. Anything malformed is logged and skipped, so nothing jams the pathway.
Fixed packetSame 128 bytes every time, with delivery gas set by the contract. Callers cannot attach value or options.
Holds no fundsThe fee goes straight to LayerZero and the rest returns to you. The contracts keep nothing.
Final freezeAt the snapshot the record freezes for good. After that no number can change, not even by ZXOXO.

No proxy, no upgrade path, no self-destruct. Source verified on every chain, 174 contract tests, and every pathway rehearsed end to end before mainnet.

Not a token

The hub is a record. It was built so that nothing in it can ever be traded.

It cannot

  • be transferred, traded, sold or bridged
  • be listed by a wallet or an exchange: it has no balanceOf, totalSupply, symbol or transfer
  • move your mZXO: the gateways only read it
  • hold or take your funds
  • change after the freeze

It does

  • count your mZXO from every chain in one place
  • prove each number with LayerZero verification
  • show your record on the mining page, live
  • stay open for anyone to read on Base

Timeline

  1. 17 NovemberHub and five gateways live on mainnet. Every pathway tested with real packets.
  2. NowSend your packets. Update them as you claim.
  3. SnapshotThe record freezes. Nothing changes after.
  4. 30 NovemberEvery chain to the Zero.

Contracts and code

Source verified. Read them yourself, or check your record straight from Base.

ChainRoleAddressEndpoint id
BaseHub0x9760…d40030184
ArbitrumGateway0x9760…d40030110
OptimismGateway0x9760…d40030111
BNB ChainGateway0x3C2b…692430102
AvalancheGateway0x9760…d40030106

mZXO (read only): 0x61A9…3c4C on every chain. LayerZero EndpointV2: 0x1a44…728c.

ZxoPacketGateway · sendfunction send() external payable
  whenNotPaused returns (MessagingReceipt memory r)
{
  // only ever the sender's own balance
  uint256 balance = mined.balanceOf(msg.sender);
  bytes memory packet = ZxoPacketCodec.encode(
    msg.sender, balance, uint64(block.timestamp));
  // fee to the endpoint, the rest refunded to you
  r = _lzSend(hubEid, packet, _sendOptions(hubEid),
    MessagingFee(msg.value, 0), msg.sender);
}
ZxoPacketHub · recorduint256 previous = chainBalanceOf[account][eid];
if (balance > previous) {        // only ever up
  uint256 increase = balance - previous;
  chainBalanceOf[account][eid] = balance;
  record.total  += uint128(increase);
  totalRecorded += increase;
}                                // older or equal:
                                 // nothing changes
emit PacketRecorded(eid, account,
  balance, record.total, guid);
Pathway config · every chain to Baserequired DVNs   LayerZero Labs
                Horizen          (2 of 2)
optional DVNs   none
libraries       SendUln302 / ReceiveUln302
                pinned per pathway
lzReceive gas   300,000          (enforced)
hub             Base, eid 30184
  • Required DVNs are the verifiers. Both must confirm a packet before it can be delivered; there is no optional shortcut.
  • Pinned libraries mean the rules a packet is checked by are set by ZXOXO for this pathway, not inherited from defaults.
  • Enforced gas is fixed by the gateway, so every packet arrives with enough gas to be recorded.
Check your record yourself# your omnichain total on the hub
cast call 0x9760c50dd855f5E2C22313211a5fE7a97b47d400 \
  "totalOf(address)(uint256)" 0xYOUR_WALLET --rpc-url https://mainnet.base.org

# what the hub holds for one chain (Arbitrum = 30110)
cast call 0x9760c50dd855f5E2C22313211a5fE7a97b47d400 \
  "chainBalanceOf(address,uint32)(uint256)" 0xYOUR_WALLET 30110 --rpc-url https://mainnet.base.org

# the LayerZero fee for one packet from Avalanche, right now
cast call 0x9760c50dd855f5E2C22313211a5fE7a97b47d400 \
  "quote(address)(uint256)" 0xYOUR_WALLET --rpc-url https://api.avax.network/ext/bc/C/rpc

Questions

Does sending a packet move my mZXO?

No. The packet carries a copy of the number. Your mZXO stays on its chain, soulbound and untouched. The gateway can only read your balance.

Which chains should I send from?

Every chain where you have claimed mZXO. A chain with nothing claimed shows Claim here first and has no button: there is nothing to carry yet.

I sent a packet before claiming. What happened?

It carried 0 mZXO, so it recorded nothing for that chain. Claim on that chain, then send again: the new packet carries your real balance.

I claimed more after sending. Do I lose it?

No. The row turns into Send update. The hub raises that chain's record to your new balance and adds only the increase to your total.

What does it cost?

The LayerZero fee shown on the button, paid in that chain's coin, plus the normal network fee. The unused part of the fee comes back in the same transaction. On Base there is no LayerZero fee: Record here costs gas only.

How long does delivery take?

Usually a few minutes: the source chain finalizes, both verifiers confirm, then the packet is executed on Base. Follow it on LayerZero Scan from the In flight link. You can close the page while it travels.

Can someone change my record?

No. A packet always carries the balance of the wallet that sends it, and the hub only ever raises a record. Nobody can lower yours or write to it.

Is there a token?

No. The hub has no balanceOf, transfer or totalSupply. Nothing can be listed, traded, sold or moved. It is locked until 30 Nov.

What happens at the snapshot?

The record freezes. After that no number in the hub can change, not even by ZXOXO. Packets that arrive later are logged and ignored.

Is it safe to sign?

You sign one transaction to the ZXOXO gateway, shown in your own wallet. It asks for no approval and cannot touch your coins or tokens beyond the fee you see. ZXOXO never asks for a seed phrase.

Send your packet