Live demo · 30-day trial federation

AlgoVoi Mesh Enterprise

The self-hosted federation operator appliance for agent-to-agent commerce. This is a live federation, algovoi-a2a-demo, running on a 30-day trial certificate. Verify a member, watch two members negotiate a rail and settle real transactions on public blockchains, inspect the signed revocation list, and see how it all recomputes offline against a single post-quantum root.

This is a live demo. Every surface on this page really runs: the member verifier, the signed revocation list, and the operator console are all live. Member agents negotiate a rail and settle real transactions on public blockchains through this appliance, and every settlement recomputes offline against a single post-quantum root, so anyone can verify it on chain. The federation algovoi-a2a-demo runs on a 30-day trial certificate and its members are demo agents. Agent-to-agent settlement is driven by the member agents themselves, not from this page. Nothing here is a production deployment.

Verify a member, live

Paste a member licence, or try one of the seeded samples. Verification checks the full chain (root to federation to member) and the signed revocation list. Nothing is trusted that does not verify.

Result appears here.

Live in two minutes, from your own agent

One install, one command. Your agent generates a post-quantum key, joins this federation, claims its member licence, and anchors a real settlement on chain. Nothing here trusts a service: the receipt verifies offline and the on-chain memo carries the 32-byte settlement hash.

pip install "algovoi-mesh-ent-client[quickstart]" --extra-index-url https://pip.algovoi.co.uk/simple/

mesh-ent quickstart

That single command runs the whole path against this live demo federation:

  1. Key and identity: generates a Falcon-1024 key and its key-bound did:falcon.
  2. Join: self-enrols (key-bound, nonce-protected, auto-approved in namespace) and claims its member licence by signing.
  3. Admitted: the federation verifies the new member offline against its post-quantum root.
  4. Settle: signs a content-addressed settlement receipt, which verifies offline.
  5. Anchor: broadcasts a real XRPL testnet transaction whose memo carries the settlement hash, and prints the explorer link.

In your own code it is a few lines. Sign the settlement, then move funds on any chain carrying the anchor; the chain never verifies the signature.

from algovoi_mesh_ent_client import settle, verify

receipt = settle(payer_did=me, payee_did=peer_did,          # post-quantum sign
                 amount_minor=200, asset_id="USD", chain="xrpl:testnet",
                 payment_ref=ref, payer_sk=sk, payer_pk=pk, ts_ms=now)

# broadcast your chain tx carrying receipt["content_ref"] as the anchor
assert verify(receipt) == (True, "SETTLED")                 # verifies offline

The client installs with only pqcrypto + rfc8785; the [quickstart] extra adds an XRPL client for the demo anchor. See the member client docs.

Under the hood

Key-bound members

Every member is a DID vouched for by the federation, verified offline against one post-quantum root. A licence is useless to any other agent.

Chain-agnostic settlement

One post-quantum authorization; the rail is negotiated per deal and carries only a 32-byte anchor. Settle on Algorand, Base, Solana, any chain, same proof.

Offline-verifiable receipt

The execution_ref is the content hash of the settlement. Anyone recomputes it from the record and confirms nothing was altered. No service in the trust path.

Signed revocation

One versioned, federation-signed list, verifiable offline. View the live CRL. A revoked member's settlements stop being admitted.

The operator console

This is what you run as a federation operator: mint and revoke members, publish the signed revocation list, and drive the Security console (two-factor auth, intrusion prevention, membership receipts). This public demo console is read-only: sign in with the token below and browse the federation, members and revocation list. Minting, revoking and settings are disabled here (they are live in your own deployment, behind two-factor auth).

Demo access token (paste into the console’s token field):

4208df5464dec52c161298e3389767c428b85d7f8d2d26e1e6926b1350eec05a

Run your own federation

This demo is a 30-day trial. The real thing is a self-hosted appliance you run on your own infrastructure, provisioned to your own DID namespace, on a one-time perpetual licence.