PoB is not alone in concluding that payments need a purpose-built chain. In the last two years, several serious — and in some cases far better funded — projects have launched around the same observations: checkout needs deterministic finality, fees must be predictable, transparency is a liability for businesses, and autonomous agents are the next payer. This page places PoB among them rather than pretending they do not exist.
| Technology | Settlement | Privacy | Fees | AI agents | Governance & status |
|---|---|---|---|---|---|
| TempoStripe / Paradigm | deterministic, ~0.6 s, no reorgs | opt-in confidential transfers, designed with regulated issuers | gas in USD stablecoins; dedicated payment lanes | stablecoin rails usable by agent protocols | permissioned validators; fintech consortium; mainnet 2026 |
| ArcCircle | deterministic, sub-second (BFT) | opt-in selective shielding of balances and transfers | USDC as gas; predictable dollar fees | stablecoin-finance focus; agents secondary | permissioned validators; mainnet beta 2026 |
| CantonDigital Asset | deterministic (BFT synchronizer) | sub-transaction privacy by construction | application-defined | not a focus | permissioned super validators (incl. Visa); institutional production at very large scale |
| AztecEthereum L2 | rollup — inherits Ethereum finality (minutes) | fully private smart contracts, client-side ZK | sender-paid L2 fees | not a focus | permissionless; alpha mainnet 2026, early |
| KiteKite AI | fast EVM L1 plus payment channels | transparent ledger | gas token; micropayment channels | agent-native: x402 built in, agent identity, spending rules | public PoS L1 with token; early |
| SolanaSolana Foundation | confirmation under 1 s; finalization in seconds | transparent | very low per-tx fees; priority fees under load | carries the largest x402 agent-payment volume today | permissionless PoS; production at scale |
| BaseledgerUnibright / Provide | Tendermint BFT, seconds | business data kept off-chain; only proofs on chain | low fixed fees (UBT) | not a focus | council-governed PoS; process baselining, not consumer payments |
| PoBzkLoop Labs | deterministic certificate, sub-second | encrypted balances by default; unlinkable transactions; private chains | no gas at all; merchant-side % fee and rewards | policy-bound tokens, native escrow, MCP tools, gas-free | operator-composed Byzantine quorum; in development |
Each of these projects is good at what it set out to do, and several validate our thesis better than we could ourselves: Tempo and Arc — backed by Stripe/Paradigm and Circle — demonstrate that “payments need deterministic sub-second finality and predictable dollar fees” is now industry consensus, not a fringe view. Canton proves privacy-by-construction can run institutional workflows at enormous scale. Aztec is advancing general-purpose private computation further than anyone. Kite and the x402 traffic on Solana show real demand for agent-native payment rails.
Tempo and Arc treat confidentiality as opt-in shielding on an otherwise transparent ledger; Kite and Solana are transparent; Canton has privacy by construction but is built for regulated financial institutions, not merchant commerce. PoB encrypts every balance and unlinks every transaction as the base case, then adds per-chain read control on top.
Stablecoin-denominated gas removes volatility, but it still prices every transaction to the sender — and still leaves the “who funds the agent's gas?” question open. PoB has no sender-side fee of any kind; abuse is prevented by a zero-knowledge minimum-balance check, and economics live in merchant-side contract configuration.
Every other entry is a shared network that a business connects to on the network's terms. PoB is closest in spirit to Canton but aimed at operators and merchants rather than global banks: the operator composes its own validator quorum, owns its loop, and can still interoperate — one balance across contracts and chains.
Tempo, Canton, and Solana operate in production at meaningful scale; Arc and Aztec are in public test and alpha phases; PoB is in active development with demonstration deployments — the earliest-stage system in this table, without the ecosystems or balance sheets behind several of its neighbors. The comparison above is therefore one of architecture and intent. On that level we believe the combination PoB occupies — default privacy, deterministic settlement, zero gas, operator custody, and agent policy in one stack — is one no other project currently claims.