You move a bridged denom in against at least the configured threshold of attestor signatures, and out by burning it for attestors to countersign. Governance registers each external chain with its vault, finality depth, attestor set and per-asset caps, so no path is open until you open it. Publish chunked batch archives to Ethereum and Solana, where the mirror contracts hold no custody, and send ICS-20 transfers through the IBC precompile.

What it does

Paxeer X reaches other chains through three separate paths. An attested bridge mints and burns a bridged denom against signatures from a governance-registered attestor set, archive mirrors publish retrievable Paxeer X batch archives to Ethereum and Solana, and a vendored IBC stack carries ICS-20 token transfers over Tendermint light clients. Settlement stays on Paxeer X in every case: the mirrors hold no custody and the bridge mints only against a registered remote vault.

Key capabilities

• bridgeIn mints a bridged denom against at least threshold attestor signatures over the vault deposit digest.
• bridgeOut burns the caller's bridged denom and emits BridgeOut for attestors to countersign.
• Governance registers each external chain, its vault, finality depth, attestor set and per-asset caps.
• layerx-bridge-relayer journals observed Ethereum events and collects attestor signatures before broadcast.
• Mirror publisher writes chunked batch archives to Ethereum and Solana; a verifier checks them offline.
• IBC precompile 0x…1009 exposes transfer and transferWithDefaultTimeout, accepting a 0x receiver.

Differentiators

Mirror contracts have no custody, withdrawal, payable or token surface, so an archive cannot become a settlement venue. Mirror verification is rooted only in a finalised archive, and the sequencer public key and batch range are configured independently and never read from an archive payload. Each relayer instance holds exactly one attestor key behind a remote signer, so no chain private key enters the process.

Outcomes

• Assets enter and leave against an explicit attestor threshold and caps
• Anyone verifies a Paxeer X batch from an Ethereum or Solana archive
• The bridge stays dormant until governance registers a chain

Technical notes

• The attested bridge is modules/layerxbridge behind the LayerXBridge precompile 0x0000000000000000000000000000000000001016. It is distinct from the LayerX kernel bridge module (module 8), which is the LayerX-to-Paxeer custody path.
• Attestors sign keccak256 over an abi.encodePacked preimage with no EIP-191 prefix and no EIP-712 domain: PAXEERX_BRIDGE_IN_V1 at 196 bytes, PAXEERX_BRIDGE_OUT_V1 at 185 bytes. Signatures are 65 bytes r || s || v with v in {27, 28}, low s, and strictly ascending recovered signer.
• Governance messages are MsgRegisterChain, MsgSetAttestors, MsgSetCap, MsgPause and MsgUnpause, authorised by the gov module account. At most 64 attestors; threshold must be 1..set size; max_per_tx may not exceed max_in_flight, and a zero cap refuses every bridgeIn.
• Each inbound event is nullified once by (chain id, tx hash, log index); each release is nullified by keccak256(paxeerTxHash || paxeerNonce). The minted denom is factory/{bridge module address}/lxb….
• Default genesis registers no chain, sets no attestors and no caps: the bridge ships dormant and only a governance registration brings a chain up.
• Mirrors are interop/crates/layerx-mirror with layerx-mirror-publisher and layerx-mirror-verify, over interop/contracts/ethereum-mirror/LayerXMirrorArchive.sol and interop/contracts/solana-mirror. Archive limits: 64 MiB per archive, 24 KiB per chunk, 65,536 chunks. The beta plan runs the mirrors on the Ethereum and Solana test networks.
• IBC is a vendored ibc-go fork under interchain/, with core, ICS-20 transfer and the 06-solomachine, 07-tendermint and 09-localhost light clients. The transfer keeper is built with an EVM address handler, so a receiver may be given as a 0x address. The precompile rejects staticcall and delegatecall and is non-payable.
• Not yet implemented: interchain accounts are vendored under interchain/modules/apps/27-interchain-accounts but not wired into the application, and there is no fee middleware, interchain queries, 08-wasm client or packet-forward middleware. No repository document describes an operating IBC connection or relayer for hyperpax_125-1.

interface ILayerXBridge {
    function bridgeIn(
        uint64 chain, address vault, bytes32 txHash, uint64 logIndex,
        bytes32 recipient, address asset, uint256 amount, bytes[] calldata signatures
    ) external returns (string memory denom);

    function bridgeOut(uint64 chain, address asset, uint256 amount, address recipient)
        external returns (uint64 nonce);
}

More in Network