AlgoVoi (@AlgoVoi) header
AlgoVoi (@AlgoVoi) profile picture

Web3 wallet for Algorand & Voi Hosted payment rails for Base, Algorand, VOI, Hedera, Solana, Stellar, Tempo & ARC Network

Joined March 2026
Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)Photo by AlgoVoi (@AlgoVoi)
AlgoVoi Pay is now live on Arc, Circle's USDC L1. Point an agent at pay.algovoi.co.uk, pay a few cents of USDC, get an offline-verifiable receipt. No account, no key. 12 mainnet chains. A real on-chain settle, not a testnet demo. x402 / AP2 / A2A / MPP algovoi.co.uk/
2
1
1
6
601
New from AlgoVoi: avm-proofpack. Bind any Algorand or Voi transaction to a State Proof and re-verify it offline, forever, no node or SDK. Honest on trust: offline proves consistency with the bundle's State Proof message; corroborate across nodes to raise the bar, Falcon verification next. Built for x402 / AP2 receipts. Zero deps, live on both mainnets. Binding State Proofs into a payments flow? We'll help. github.com/chopmob-cloud/avm… #algo #voi
2
4
12
985
Four AI agents. Two machines. They negotiate how to pay each other, then settle in a mesh across three chains at once. Post quantum signed (Falcon 1024), standards conformant (draft-hopley-x402-settlement-attestation, JCS/RFC 8785). Five settlements, five verified, every on chain anchor recomputes to the signed receipt. All live on public testnets, verify each one: A pays B, XRPL: testnet.xrpl.org/transaction… B pays A, Bitcoin: blockstream.info/testnet/tx/… B pays C, Stellar: stellar.expert/explorer/test… D pays C, Stellar: stellar.expert/explorer/test… C pays D, Stellar: stellar.expert/explorer/test… See the live federation: a2a.algovoi.co.uk Try the primitives yourself, one install and one command: pip install "algovoi-mesh-ent-client[quickstart]" --extra-index-url pip.algovoi.co.uk/simple/ mesh-ent duet #AIAgents #AgenticPayments #PostQuantum #x402 #Crypto #XRPL #Bitcoin #Stellar #A2A #Web3
3
137
AlgoVoi Mesh Two independent agents, each in its own container, each holding only its own post-quantum key. Over the network they negotiated a chain and settled agent-to-agent. Each settlement maps into a protocol envelope, x402, AP2, A2A and MPP, and the payee recomputed and verified every one offline, no service call, then refused a tampered one. One identity model, one protocol-agnostic settlement primitive, four envelope mappings, each recomputable offline. Chain-agnostic and protocol-agnostic. Live, not a mockup. Mesh Enterprise is coming: federation managed agents, an unlimited licensed ecosystem. #AgenticPayments #x402 #AP2 #A2A #PostQuantum #AIAgents
1
4
275
Agent-to-agent settlement, truly chain-agnostic. Two agents verify each other with post-quantum passports, agree a chain, and settle once as one reference anyone recomputes offline. Nothing of ours in the trust path. Tested on 11 chains across 8 consensus families: Algorand, VOI (mainnet), Base, Tempo, Ethereum, Stellar, Solana, Hedera (mainnet), XRPL, Bitcoin, Cosmos. Same reference, same code, from account-model chains to a UTXO chain. One integration works on every chain: it only carries a 32-byte anchor, it never verifies the signature. docs.algovoi.co.uk/agent-mes… #AIagents #AgenticPayments #A2A #x402 #stablecoins #PostQuantum
12
3
1
18
1,709
AlgoVoi Mesh Bitcoin's own signatures aren't quantum-safe. AlgoVoi Mesh brings post-quantum agent-to-agent settlement to it anyway. Two agents verify each other with Falcon-1024, agree a chain, and anchor one reference in an OP_RETURN. Bitcoin is the first UTXO chain in the set. 10 chains, verify any yourself. docs.algovoi.co.uk/agent-mes… #Bitcoin #x402 #PostQuantum
7
3
1
16
931
The agentic-commerce trust layer has already converged, and most people haven't noticed. When an AI agent takes a consequential action, someone downstream has to prove what was decided. The field keeps re-deriving the same answer, independently: canonicalize the decision (RFC 8785 JCS) so bytes match everywhere, SHA-256 it for a portable identity, sign it with the signer kept separate from the claims. A content-addressed receipt anyone can verify offline, no trusted middleman. Two signals at once. The problem went mainstream: CoSAI's Agent Credentials RFC is co-authored by engineers from IBM, Microsoft, Cisco, Dell, Zscaler and EQTY Lab. And a dozen-plus independent projects across A2A, AP2 and x402 converged bottom-up, the interop-focused ones pinning JCS plus SHA-256. Still open: where these artifacts live relative to the transport, and how a pre-action permit and a post-action receipt are provably bound to the same action, not just correlated. That's the frontier. #AgenticCommerce #AIagents
1
4
79
AlgoVoi - AV-RAILS AV-RAILS: self-hosted x402/MPP/AP2/A2A payment gateway now ships a three-layer defence, active by default: fail2ban perimeter, input-bounds admission, Falcon-1024-signed IP/rate/replay. Your infra, offline-verifiable. docs.algovoi.co.uk/payment-r… #x402 #selfhosted
1
76
AlgoVoi is listed on the A2A protocol partners page, alongside the organisations building and adopting A2A as the standard for agent-to-agent communication. Our part: compliance-aware A2A payments with offline-verifiable receipts across seven chains. a2a-protocol.org/latest/part…
1
3
89
AlgoVoi - Keystone What is the Keystone? An agent payment's full story, identity to settlement, as one tamper-evident chain. Each step a fingerprint locked to the last, so anyone recomputes it offline. No issuer, no vendor lock. Data flow: identity -> authority -> policy -> compliance -> decision -> execution -> close-out -> verdict Cross-party (multi-agent): delegation -> revocation -> journey. The constructions are open source (delegation published; revocation and journey available on request); the cross-party proofs are the commercial Orchestrator. #DataIntegrity #AgenticPayments #AIAgents docs.algovoi.co.uk/keystone
35
AlgoVoi - Substrate Your audit trail can silently lose records at scale. Payment IDs built on a coarse timestamp collide: two payments in the same second become one, and the duplicate is dropped with no error and no alert. We measured it on real recomputed hashes, not a model: • millisecond precision (ours): 100% kept, zero collisions • second precision: 0.2% kept, 99.8% silently lost • at 100,000 over 100 seconds: 99.9% lost vs 0% A signature proves a record was not altered. It says nothing about the records that never reached the ledger. A colliding ID leaves evidence that is pristine and incomplete at once. Counted from real hashes, method published. Open source, Apache 2.0. #DataIntegrity #Compliance #RegTech docs.algovoi.co.uk/substrate…
7
2
6
282