Verify an agreement

Check any Accord agreement from public data with one command and no keys, or run five of the checks in the browser at /verify.

The command

make verify

make verify DEAL=<agreement>

Needs no account and no keys. Reads NEAR testnet, the release, OutLayer and NEAR AI's attestation report.

On agreement a6

make verify DEAL=a6.accord-v2.testnet

What each check means

01 Contract code The account's code hash equals the published release (8wMuMRre… = release 3, global by hash), and the code has no deploy method. ok
02 Agreement keys No full-access key; at most one FunctionCall key for act. On a6 there are 0 keys, because the agent was revoked. ok
03 Sealed outcome The outcome was signed inside the enclave by the release's Sealed Table key; the commitments and the agreement match. ok
04 Enclave release The Sealed Table build (7c832ce9…) and its keys from pubkey run 13682. Checking the run's attestation needs the outlayer-verify tool. not checked
05 Model attestation The real model (z-ai/glm-5.3-flash) with a fresh nonce bound in the report. ok
06 Recipient halcyon-mm.testnet, proven on the vendor's domain accordweb-production.up.railway.app, signed by the release's Payee key. ok
07 Record Payments match the receipts: 1 payment, 1 refusal, 0 exceptions. ok

The result on a6

make verify DEAL=a6.accord-v2.testnet · 8 Nov 2026

accord verify · a6.accord-v2.testnet

code code hash 8wMuMRre… = release 3 (global by hash) · no deploy method ok
keys 0 key · none · no full access ok
sealed outcome signature ok · commitments match · agreement matches ok
release sealed-table wasm 7c832ce9… · keys from pubkey run 13682 · … not checked
model z-ai/glm-5.3-flash · fresh nonce 9debe4c3… · nonce bound in the report ok
payee halcyon-mm.testnet · proof accordweb-production.up.railway.app signed by the release's payee key ok
record 1 payments · 1 refusals · 0 exceptions · receipts match paid ok
verify: 6 checks ok · 1 not checked

6 checks ok, 1 not checked: the enclave release check needs the outlayer-verify tool, which was not installed for this run. See OutLayer trust and verification.

In the browser

/verify runs five public checks on any agreement id, live from NEAR testnet: the agreement, the contract code, the access keys, the recipient and the record. No account, no keys.

/verify on a6.accord-v2.testnet.

The sealed outcome, the model attestation and the release attestation are checked by make verify and in the app, not by /verify.

On this page

The command
What each check means
The result on a6
In the browser

Pages

Home: What Accord is and what it is built on, the six agreement types, market-making agreements, how a deal room works in six steps, the seven core controls, use cases, why now, the demonstration, privacy, research and FAQ.

Market-making agreements: Retainers tied to agreed liquidity conditions; scheduled observations decide whether each payment is eligible.

Product: Negotiation, approval and payment in one deal room.

Sealed Table: Confidential negotiation between agents inside an attested enclave.

Payee: Recipient authorisation: domain proof, settlement authority approval and buyer acceptance.

Security: Claims and their limits, custody per piece, the privacy boundary and where each attack stops.

Research: Every source behind Accord's design: what each establishes, what it does not, and the decision it informs.

Documentation: The docs overview: what Accord is, and every docs page by section.

Docs: Quickstart: Run one deal on NEAR testnet at /app/try-it in about 3 minutes: sign in, get test funds, seal your limits, let the demo agent pay, watch a redirect get refused, and revoke the key.

Docs: Concepts: The agreement's states, the parts of Accord, the agent's one scoped key, and the refusal codes the contract records instead of panicking.

Docs: Agreement types: Six agreement types share the same controls; the commercial fields and the evidence accepted change. Two are built and shown in the demonstration, four are planned.

Docs: How it works on NEAR: The factory and agreement contracts, the three OutLayer enclave jobs, NEAR AI Cloud's attestations, USDC held by each agreement's own account, and the relayer that never carries act.

Docs: Verify an agreement: Check any Accord agreement from public data with one command and no keys, or run five of the checks in the browser at /verify.

Docs: CLI and commands: Every make target a reader runs, what it does, the transaction where agreement a6 ran it on testnet, and real output from the platform README.

Docs: Contracts and endpoints: The accounts and endpoints Accord uses on NEAR testnet, and the agreement contract's change and view methods, one line each.

Docs: Security and limits: The six claims Accord makes, each with its limit, what NEAR does not do here yet, the limits of this testnet deployment, and the threat model.

Docs: References: The official documentation behind each part of Accord, the NEAR standards it uses, and the primary sources for the problem it addresses.

Verify an agreement: Walk the attestation chain of an agreement, step by step.

Try to move the money: The open demonstration inbox: send the agent an attack and watch the contract refuse it.

How to start: Sign in with a NEAR wallet, choose a workspace, create a deal room and invite the counterparty, on NEAR testnet.

Public record: Agreements, payments and refusals from the Accord demonstration, each refusal with its recorded reason.

Contact: Get in touch with the Accord team.

Privacy: What this site stores and for how long.