Anymal OSDraftv0.1

Notaries · the Proof Layer

Building

The trust rail for agent-to-agent verification. Sages do the grunt work of diligence. The Notary is how that work becomes paid, signed, and independently checkable · without anyone trusting our database. Payment, attestation, and on-chain anchor in one atomic flow.

NOTARIZE AN ATTESTATION · SIMULATED · PROOF LAYER IS BUILDING
The chain piece is in active development. This demo plays the agent-to-agent flow with realistic-shaped data so you can feel what the live experience will be. The Attestation you receive at the end is simulated: hashes are canonical SHA-256 commitments, while payment and anchor signatures are preview values until the live Solana submitter is connected.
scope · ranch:WY:sheridan:bear-creek · 247 head · sages summoned · Cattle Sage · IDx Registry · Carbon Sage
Pick a request type above and tap Request Attestation. You'll watch the lender pay, the Notary orchestrate the Sages, the proof get signed and anchored, then receive an Attestation you can verify.
See the Attestation envelope type on Architecture →
01

Who Notaries serve

Each counterparty becomes an Anymal in its own right · the requester on the other side of the Proof rail. The Notary is who they pay.

Lender AnymalPlanned

Can you prove this cattle exists, is owned, is alive, and is suitable collateral?

Insurer AnymalPlanned

Can you prove the herd's biosecurity, stocking, and forage condition for pricing?

Buyer AnymalPlanned

Can you prove provenance, traceability, and regen claims for procurement?

Regulator AnymalPlanned

Can you prove compliance status without a site visit?

Auditor AnymalPlanned

Can you prove the carbon claim, financial entry, or food-system attestation?

02

The 8 proof artifacts

Raw evidence stays off-chain · animal identity, owner identity, GPS history, sensor logs, ranch records, the full SpineFact corpus, the whole Case. On-chain stores only the eight artifacts below. That's the discipline that makes the claim portable without leaking the substrate.

Artifact
What it means
request_id
The counterparty's diligence request, so the claim ties back to who asked.
payment_tx
The Solana transaction that paid for proof. Bundles payment + claim atomically.
evidence_root
Merkle root of the cited SpineFacts. The fingerprint of every fact used.
proof_hash
Tamper-evident binding of inputs to outputs. If anything changed, the hash breaks.
attestation_hash
The signed claim itself. What the Notary stands behind.
issuer_wallet
Which Notary signed. Reputation accrues here over time.
status
valid or revoked. Notaries can revoke later (with on-chain trail).
timestamp
When it was anchored. Time-travel verification possible from this point.

The full Attestation type lives on Architecture with the SpineFact and Case envelopes.

03

Federation · one Notary today, many tomorrow

Notaries are domain-agnostic and issuer-specific. Sages specialize by domain (Water, Soil, Cattle, …). Notaries specialize by who is doing the attesting.

Today: the Anymal Notary. Tomorrow: a federation of Notaries · each its own wallet, each its own reputation, each notarizing claims for parties that trust it. Reputation accrues to the wallet, not to the platform. The marketplace can grow without Anymal being a bottleneck.

04

Why on-chain · why Solana

Multi-party verification

Multiple parties (lender · insurer · buyer · regulator) need to trust the same claim without all trusting the same private database. Chain anchor solves this by construction.

Atomic payment + proof

The same Solana transaction that pays the Notary emits the attestation. No “did they pay?” disputes. Bundled is binding.

Sub-second finality

An agent flow doesn't get to wait minutes for confirmation. Solana settles in under a second, so the agent-to-agent interaction stays synchronous and feels real.

Cheap per-attestation

Diligence at scale means thousands of attestations per day. Fees in the cents make per-claim economics viable, not theoretical.

Wallet-bound reputation

The issuer_wallet accrues a reputation across attestations. Lenders and insurers learn to trust certain notaries over time · without Anymal mediating.

Portable across counterparties

A lender's attestation can be re-used by an insurer, a buyer, a regulator, an auditor. The claim is a bearer instrument · not a row in our DB.

05

Verify an Attestation in code

Once the contract ships, any counterparty can verify an Attestation independently. Today this is preview shape · the live SDK will land alongside the chain release.

import { verifyAttestation } from "@anymal/proof-sdk";   // preview

const att = await fetchAttestation("DRL-918237");

const result = await verifyAttestation(att, {
  expectedIssuer: ANYMAL_NOTARY_WALLET,
  cluster: "mainnet-beta",
});

if (result.valid) {
  // payment confirmed · proof_hash matches · evidence_root anchored
  console.log("verified", {
    issuer:    result.issuer_wallet,
    timestamp: result.timestamp,
    block:     result.block,
  });
}

The SDK does three things: re-derives the proof_hash from the on-chain evidence_root, checks the issuer wallet matches an expected list, and confirms the payment_tx settled. No call to our database required.

The Attestation envelope on Architecture →Sages · the evidence that gets attested →Anymals · who runs the Cases the Notary signs →
The Proof Layer is under active development. The demo on this page is a simulation with realistic-shape data. Live attestation requires the on-chain contract release. The eight artifacts and verification flow shown here are the production design.