Post-quantum attestation for any transaction.

PQ Attest writes a fingerprint of a confirmed transaction from any chain onto Algorand’s quantum-secure ledger and returns a proof you can verify independently. A new attestation costs the published price, paid through x402 on any chain the service accepts. Agents and clients start at the remote MCP. The API is the source behind it. Checking a proof is free.

Ledger
Algorand MainNet
On-chain signature
Falcon-1024
Proof signature
ML-DSA-65
Fingerprint
SHA-256
Payment
x402

Five steps, from an id to a proof.

  1. Submit

    Send the id of a transaction that has already confirmed. The id can be from any supported chain.

  2. Pay

    Pay the published price through x402, on any chain the service accepts. The first request returns the payment terms. Complete them and send the same id again.

  3. Fingerprint

    The full confirmed record is fingerprinted, including inner transactions and confirmation details. Nothing is dropped.

  4. Record

    A post-quantum account writes that fingerprint into the ledger. Once confirmed, it is part of Algorand’s history, not something we store for you.

  5. Prove

    You receive a signed bundle. Check it on the chain, or offline, with a published key. The proof still holds if this service goes away.

  • Algorand
  • Base

A record that does not depend on today’s signatures.

Falcon, on the ledger

Algorand checks the attestation with Falcon, a post-quantum signature. The on-chain record does not rest on a key a large quantum computer is expected to forge.

A fingerprint that stays

The attestation carries a SHA-256 fingerprint of the confirmed transaction. Anyone can fetch the original, recompute the fingerprint, and compare.

Yours to verify

The bundle is signed with ML-DSA over the fingerprint, the ledger entry, and the attestor. You need the bundle and a public key. You do not need to trust us forever.

What you receive.

One document. It names the transaction, its fingerprint, the ledger entry that records it, and a signature over all of that. There is no extra state proof. The chain is the record.

proof-bundle.jsonSample · shortened
{
  "version": 1,
  "network": "algorand-mainnet",
  "source": {
    "txnId": "J6GYUX7M22Z65EEV6U4QTKM6QD6D5XHWRXRBU6BM7O3STNI7S7JA",
    "hashSha256": "61b62b38c65ec66ea2638d49926dbd16b0b344c1fc3ee30a69f8ade02a2a2cd3"
  },
  "attest": {
    "txnId": "F732JQ5WWC3IXEPVNEEEBOE2LBWBS6EMZM5G2XCXTBGIFFT37CJA",
    "round": 65330479,
    "note": "fingerprint of the source transaction"
  },
  "attestor": {
    "algorandAddress": "EVG4CYNYGIDNDIDJTUDJU7ELJQJBNAJA6UZAQJO54XCL5SKKM6IR33PQJE",
    "pqPublicKey": "3rO9EVFuGb9iUL1kiE9f6eF/5bGu22e3qNn5PSj2tkCvfQPH…"
  },
  "signature": {
    "alg": "ML-DSA-65",
    "sigBase64": "hgUwnwK1srDBLPJQGiWNm6g5oQmGC0AyR6iOoYANEN71I4xq…"
  }
}
Fingerprint
A SHA-256 hash of the confirmed transaction. Recompute it from the bytes in the bundle.
Ledger entry
A confirmed transaction whose note carries that fingerprint.
Signature
ML-DSA-65, checked with the attestor’s published public key.

Start at the MCP.

Remote MCP

This is the first door for agents and for clients. Connect to https://mcp.pqattest.com/mcp. Call pq_attest for a proof, or pq_verify to check one. The server forwards both to the API. It does not sign, settle, or hold keys.

The API

The API is the source behind the MCP. Call it directly when you speak HTTP, or run the reference implementation against your own node. A new attestation costs the published price, paid through x402. USDC can be paid on any supported chain, all attestations take place on Algorand. Contact us about an integration.

  • Request an attestationA confirmed transaction id in, paid through x402. A signed proof out.x402
  • Check a proofConfirm the fingerprint and the signature. Optionally, re-check the chain.Free
  • Read the descriptionx402 payment terms, for the MCP and for the API.Free

MCP address: https://mcp.pqattest.com/mcp

API address: https://api.pqattest.com