Integrate
We will help you plug this in
Everything on this site is built to be used by other products: an open standard, signed documents a verifier can check without trusting us, a data feed, badges, a widget, and a registry with a two-call enrolment flow. If you run a wallet, an exchange, a custody desk, a fund, a data platform or an audit practice, we will do the integration work with you. Most take an afternoon. Write to hello@latticescan.com or use the contact form and say what you run.
Access. The website is open to anyone, one query at a time. Programmatic access to the JSON, CSV and PDF endpoints is by API key, issued to partners by hand and free to start. Ask for one in your first message and say roughly what volume you expect.
Wallets
Your users hold keys that will one day be recoverable from their public halves. The wallet is the only place a commitment can be made automatically, at the moment the key exists.
- Registry commitment at address creation: generate an ML-DSA-65 key next to the classical one, sign the statement, submit it. One call to get the statement, one to record it.
- Exposure indicator per address: hash-protected and never spent, or already revealed. Same data as the Exposure tool, read through the API.
- Canary hook: an event when an address the wallet manages first reveals its key, so the wallet can nudge the user to sweep.
Effort. Two API calls and a key-generation step. An afternoon for a wallet team that already has message signing.
Exchanges and custodians
Proof of Reserves shows the coins exist. Users, auditors and the SEC are starting to ask the next question: how much of the reserve is behind an already-revealed key.
- A quantum solvency score computed from your own published address set, signed and anchored in Bitcoin, on the index and on a badge for your Proof of Reserves page.
- A reserve attestation: a policy you choose (per-key cap, hash-protected only), checked on a schedule, with a signed report each time.
- An evidence pack mapped to DORA, FINMA, MAS and FCA control language, so the number lands in the format your compliance team already files.
- Registry commitments for treasury addresses, so your ownership claim predates any dispute.
Effort. Publishing the address set is the only prerequisite. Scoring is ours to run. Adding the badge is one image tag.
Data platforms and analytics
Your users compare exchanges on reserves, fees and volume. Quantum solvency is the next column, and it is derived from data you already index.
- The feed: one versioned JSON document with every scored reserve, the market number, and links to the signed snapshots. CSV too.
- Per-reserve and market badges, and an embeddable widget with no scripts.
- A stable slug per reserve, and on request an extra id field that matches your own identifiers so you can join without a mapping table.
Effort. One HTTP GET every five minutes. We issue the key and adapt the shape to what your pipeline wants.
Funds, treasuries and ETF issuers
Your filings already say quantum computers could compromise the wallets holding the assets. The next filing can say how much, and what you did about it.
- Exposure measurement of your holdings or your custodian’s, signed, with the OpenTimestamps proof that fixes the date.
- A repeatable attestation against a policy you set with your custodian.
- Registry commitments for every address, filed before any migration debate starts.
Effort. Send the address set, or have your custodian send it. The first report is the same day.
Auditors and regulators
A number is only useful if a second party can recompute it. Everything here is built so that you can.
- The open specification, Proof of Quantum Solvency v1, with exact classification rules and arithmetic.
- The reference verifier: one file, no dependencies beyond Node.js, checks signature, anchor and arithmetic of any document we issue.
- Assessor status: any firm may assess against the standard. We will help you stand up an independent implementation and cross-check results.
Effort. Run the verifier on any document you are handed. Nothing to install.
What we bring to the table
- The specification and the verifier, both open. Nothing about the method is proprietary, only the work of running it well.
- A signing key already published and a Bitcoin anchoring pipeline already running. Your documents inherit both on day one.
- Engineers who built every endpoint on this site and will sit with yours until the integration is live. No ticket queue.
- Primary sources only. Every claim we make in your materials cites NIST, CISA, the White House, the IETF, the chain’s own proposals, or the company’s own filings.