On this page
One system. Composable layers.

Choose the evidence for your decision

Paxeer X gives each activity a canonical signed receipt. A merchant verifies payment facts before releasing a resource; an auditor preserves the exact signed outcome; an account owner proves committed state to settlement workflows. Each workflow uses a different evidence boundary.

EvidenceEstablishesUse
Portable receipt (v2)Canonical outcome authenticated by a pinned receipt keyOffline receipt validation and outcome accounting
Native state witnessA canonical account or module fact is included in a composite state rootBalance and module-state verification
Custody state proofCustody state at verified heights under a pinned chain identityPaxeer custody verification
Mirror archiveA receipt obtained from an untrusted archive belongs to an authenticated batchIndependent receipt verification from Ethereum or Solana mirrors

Portable receipt format

The current format is layerx-receipt-proof-v2. The wire identifiers retain the LayerX name for interoperability. The earlier v1 format (layerx-receipt-proof-v1) is not accepted by the current crate; there is no v1 parser in layerx-portable. Verification runs offline once you supply your own pinned receipt-key list.

MemberValue
formatlayerx-receipt-proof-v2
verificationLevelreceipted
signedReceiptExact signed canonical receipt bytes; lowercase 0x hex
receiptDigest32-byte receipt digest; lowercase 0x hex
receiptKeyObject with keyId and publicKey (32 bytes each, 0x hex) and firstHeight / lastHeight (0x quantities): the inclusive height window in which that key signs
inclusionHeight0x quantity; must not precede the signed receipt height
rawTransactionOptional; raw transaction bytes as 0x hex, bound to the receipt activity ID

Byte strings are lowercase 0x hex and heights are 0x quantities. Unknown JSON members are refused. The JSON input limit is 1,500,000 bytes; the signed receipt must contain between 1 and 1,048,576 bytes.

Establish the trust root first

The trust root is your pinned ReceiptKeys list of ReceiptKeyEntry values (key ID, Ed25519 public key, first and last signing height). The receiptKey carried in the JSON names the entry that signed; it is trusted only after it equals the entry selected from your own pinned list. Copying the key out of the incoming JSON does not authorize it.

// Rust: json_bytes and receipt_keys (your pinned list) are supplied by your application.
let verified = layerx_portable::PortableReceiptV2::verify_json(
    &json_bytes,
    &receipt_keys,
)?;

from_json parses the bounded representation without establishing trust; verify_json parses and verifies it against your pinned keys. Export uses PortableReceiptV2::export(signed_receipt, receipt_key, inclusion_height), or export_with_transaction to also bind raw transaction bytes. Export verifies the signed receipt before producing its JSON representation. from_sequencer_receipt exports the signed receipt of a receipted or committed RPC answer and refuses submitted answers.

What verification checks

  1. Parse the bounded JSON and decode every field in its canonical 0x form.
  2. Strictly verify the sequencer Ed25519 signature on the signed receipt against the pinned key list.
  3. Select the pinned entry by the receipt key ID and require the carried receiptKey to equal it exactly.
  4. Require inclusionHeight to be at or after the signed receipt height.
  5. Recompute the receipt digest and require it to equal receiptDigest.
  6. When rawTransaction is present, require its Keccak-256 hash to equal the receipt activity ID.
receipt_digest domain: "LXP/v1/receipt\0"

A cryptographically verified rejected outcome remains rejected. The portable proof establishes sequencer authentication of the signed receipt; batch inclusion and checkpoint settlement require their own evidence.

Source: services/interop/crates/layerx-portable/src/receipt.rs — PortableReceiptV2, verify_json, export.

Native state witnesses

Native witnesses prove a canonical key/value leaf through its module subtree into the composite state root. Account leaves (module 0) include a separate positional account-registry path, followed by the module-zero account-tree binding and the module wrapper. The Rust and Go verifiers share this encoding.

Lengths, indices, leaf counts, path depths and trailing bytes are checked. Odd-width Merkle levels duplicate the final node and require that exact sibling. The native leaf hash places both lengths before the key and value:

SHA256("LXP/v1/state-leaf\0" || key_len:u32be || value_len:u32be || key || value)
SHA256("LXP/v1/state-node\0" || left[32] || right[32])
Source: services/agent/crates/layerx-proof/src/state_witness.rs.

Custody state proofs

The Go custodyproof package verifies custody state bundles under the format version paxeer-custody-state-v3. Verify(request, now) checks a decoded request against an Expected pin set by the caller: genesis hash, Comet chain ID, EVM chain ID, custody identity, module hash, asset ID and confirmation count. It verifies the light-block history from genesis and the state membership proofs at the requested heights before returning a result. Decode parses the bounded JSON input.

Pin the expected values from your own configuration. Values copied out of the incoming bundle do not authorize themselves.

Source: custodyproof/verify.go, custodyproof/decode.go.

Archive and mirror verification

Ethereum and Solana mirrors publish batch archives for independent receipt verification. layerx-mirror-verify validates an untrusted archive, authenticates its batch header against configured trust, verifies receipt inclusion and reports freshness. Preserve trust configuration alongside the archive: a valid historical receipt does not alone establish that it is current.

For long-term evidence, retain signed receipts, your pinned receipt-key list, signed headers, inclusion proofs and publication references. Preserve exact bytes rather than reconstructed display JSON. See Data Availability for availability verification and Finality for commitment policies.

Verification failures

Handle typed refusals explicitly. Portable-receipt failures are distinct: JSON bounds or shape, receipt bounds, unsupported format or verification level, invalid hex, length or quantity, receipt verification failure, receipt-key mismatch, missing or mismatched digest, raw-transaction mismatch, a not-yet-receipted transaction, and an inclusion height preceding the signed height. Preserve the original activity ID for recovery and never upgrade a weaker evidence level to a stronger success.

Paxeer X · System documentationBack to top ↑

Ask Paxeer X Docs

Answers from the documentation.

What would you like to know?

Ask a question, find a guide, or get help with your next step.

Enter to send · Shift+Enter for a new line