At a glance
Memo binding
Hedera transactions carry a transaction memo (up to 100 bytes). AlgoVoi usesalgovoi:{token} in the memo field to bind payments to a specific checkout. The Mirror Node exposes the memo on the transaction record, so verification reads it directly.
Token associations
Like Algorand ASAs, Hedera HTS tokens require token association before an account can receive them. A new payout address won’t automatically accept USDC, you have to associate0.0.456858 first. The dashboard validates association when you save the address and refuses to save unless association succeeded.
Wallets
- AlgoVoi Chrome extension (in-house wallet, native x402 / MPP / AP2 across six chains; Hedera flows route through HashPack WC for HTS signing)
- HashPack
- Blade
- Kabila Wallet
Mirror Node
Hedera doesn’t have a public mempool. AlgoVoi’s verifier uses the Mirror Node API to read transaction records. The default endpoint ishttps://mainnet-public.mirrornode.hedera.com for mainnet, with the testnet equivalent for testnet checkouts.
Agent-to-agent settlement on Hedera
The Hedera Consensus Service exists to give a message a tamper-evident, fairly ordered anchor, which is exactly what a settlement reference needs. On Hedera mainnet the mesh writes itsexecution_ref straight into an HCS topic.
AlgoVoi Mesh settles a payment directly between two autonomous agents on Hedera. Each agent verifies the other offline with a Falcon-1024 credential, the pair negotiates Hedera as the settlement chain, and the authorized decision is anchored in a Hedera Consensus Service topic message as one content-addressed execution_ref. There is no facilitator, no per-transaction fee, and no AlgoVoi service in the trust path at settlement time.
Proven on-chain. A mutually verified Falcon-1024 pair negotiated Hedera and settled once:
Open the topic and read message 1. It carries
algovoi-mesh:sha256:150b4e46..., the exact execution reference that run’s handshake produced. Recompute it yourself from the raw fields with a stock RFC 8785 (JCS) implementation and SHA-256; no AlgoVoi software is involved in checking it.
The chain never verifies Falcon. It only carries the anchor, which is why the same agent trust works on Hedera and on every other chain the pair could have chosen. See AlgoVoi Mesh for the mutual handshake, the signed chain-offer negotiation, and the full eight-chain proof.
See also
- x402 protocol for the payment protocol layer
- Concept: chains overview