402Signal records commitments to its routing evidence in an append-only transparency log. Signed checkpoints are periodically anchored to Algorand TestNet using native Falcon-1024 authorization.
Routing never waits for blockchain confirmation.
Why this matters
Imagine your shopping agent spends $3 checking whether a used car is a good buy. Months later, you want to know which services it relied on.
402Signal’s transparency log creates a timestamped, tamper-evident record of the routing evidence it produced. The blockchain anchor makes it much harder for that historical record to be silently rewritten after the fact.
It doesn’t reveal your wallet or raw request, and it doesn’t prove an endpoint was truthful. It gives you a way to verify the history of the decision infrastructure your agent relied on.
The same idea applies when an agent compares paid news, buys a report, selects an API, purchases data, or pays for compute.
What did my agent rely on when it spent my money?
LOG SIZE
13
LAST ANCHORED
13
SINCE ANCHOR
Caught up
ANCHORS CONFIRMED
3
LATEST ANCHOR
ROUTING EVIDENCE
Commitments
Commitments to what 402Signal observed and selected.
APPEND-ONLY LOG
Merkle history
A growing Merkle history that exposes later rewriting.
SIGNED CHECKPOINT
Ed25519 identity
402Signal signs the current Merkle root with its Ed25519 log identity.
ALGORAND TESTNET
Falcon-1024 / f1
The checkpoint is anchored using Falcon-1024 / f1 authorization.
Proof chain: routing evidence is committed to an append-only log; 402Signal signs a checkpoint of that log; the checkpoint is authorized on Algorand TestNet with Falcon-1024 (f1).
View Falcon account on Pera (Pera Explorer, TestNet). This is the configured Falcon-1024 account. Not every transaction on that account is a valid 402Signal checkpoint without PQ1 verification. First-party confirmed history is listed below.
Current vs anchored
Current tree 13 · confirmed tree 13 · unanchored growth 0.
This anchor commits a specific log state to TestNet. Anyone can compare the signed checkpoint, Merkle root, and confirmed txn to detect later rewriting.
What this does not prove
It does not prove an endpoint claim was true. It is not a merchant payment.
402Signal recommends the route. The agent retains the wallet, signing, and seller payment.
It does not: let the blockchain prove endpoint correctness; make Base or Solana payments PQ-safe via Falcon; identify or authenticate a seller; or guarantee future endpoint behavior.