Infrastructure for autonomous AI agent payments exists and processes hundreds of millions of transactions. But every dominant protocol is compliance-gated, stablecoin-denominated, and corporately controlled. KYT screening is embedded in the settlement pipeline. Settlement currencies have issuers who can freeze balances. Infrastructure operators retain admin keys and kill switches. For agents that need to operate without identity exposure, without a compliance layer, and without a settlement currency that can be frozen — the incumbent architecture is structurally incompatible.
PROXY is the permissionless alternative. It enables autonomous AI agents to hold, spend, and settle $PROXY — a native ERC-20 token with no issuer and no compliance layer — anonymously on Base. No KYT screening. No admin keys over settlement contracts. No entity with the technical capability to freeze a balance or block a transaction. Five protocol layers: non-custodial Agent Wallet SDK, ZK anonymous routing, non-upgradeable escrow contracts, permissionless provider network, and cryptographic proof-of-delivery. PROXY is launched as a fully fair-launch token on Base and governed entirely by its $PROXY holders.
Incumbent infrastructure
is not permissionless.
Agent payment rails exist and process hundreds of millions of transactions. But every dominant protocol routes through compliance infrastructure, settles in regulatorily-controlled stablecoins, and ships with transaction screening baked into the stack. For agents that require genuine privacy and censorship resistance — the architecture is incompatible.
1.1 — Compliance Layers Are Architectural, Not Optional
KYT screening in dominant agent payment protocols is not a feature flag — it is embedded in the settlement pipeline. An agent transaction is evaluated against a private entity's risk model before escrow releases. That is not a permissionless architecture regardless of how the protocol is marketed.
1.2 — Stablecoin Settlement ≠ Censorship Resistance
The dominant settlement currency for agent payments operates under regulatory jurisdiction. Wallet addresses can be blacklisted at the issuer level and balances can be frozen. A decentralised routing layer that settles in a regulatorily-controlled stablecoin inherits all of that currency's censorship properties — regardless of how decentralised the routing layer itself is.
1.3 — Custodial Infrastructure Has Admin Keys
Agent wallet infrastructure operated by corporations retains the ability to freeze, restrict, or terminate agent wallet functionality. Spending limits, session caps, and compliance controls are implemented at the infrastructure level — not the agent level. The operator always has a kill switch.
1.4 — Transaction Privacy Is Not Default
Every agent transaction on incumbent protocols generates a log entry visible to the infrastructure operator. For agents acting on behalf of institutional principals, or executing strategies with competitive sensitivity, a surveillance layer baked into the payment stack is an unacceptable architectural dependency.
PROXY: The Permissionless
Alternative
PROXY is not the first agent payment protocol. It is the first permissionless, anonymous, native-token agent payment protocol. The distinction matters. PROXY does not compete with incumbent infrastructure on transaction volume — it exists for the use cases that incumbent architecture cannot serve: agents that need genuine privacy, censorship resistance, and settlement in a currency no entity can freeze.
The core proposition: Every incumbent agent payment protocol routes through a compliance layer. PROXY does not. Every incumbent settles in a stablecoin with an issuer. PROXY settles in $PROXY — a native token with no issuer. That is not a tokenomic preference. It is an architectural property.
PROXY delivers four properties that no existing agent payment infrastructure delivers simultaneously: permissionless access with no compliance gatekeeper, anonymous transactions with no KYT screening, native token settlement with no stablecoin dependency, and non-upgradeable contracts with no admin keys. These are not features. They are the architecture.
Five steps.
Zero intermediaries.
Every PROXY transaction flows through five discrete protocol layers, from signed agent request to on-chain settlement. No layer can be bypassed. No intermediary can intervene between a valid DeliveryProof submission and escrow release. The entire cycle completes in approximately two seconds at Base block time.
AgentRequest object specifying resource type, model or feed parameters, max latency, and a budget ceiling in $PROXY. The budget ceiling is atomically escrowed in the PROXY smart contracts at broadcast — providers are guaranteed payment exists before accepting a job. No pre-authorisation. No human approval.DeliveryProof to the proof layer. For inference: a deterministic output hash computed against committed model weights. For data feeds: a signed timestamp and source attestation. For storage: a Merkle proof of data availability. The proof layer validates the submission — including spot-checking 8% of inference jobs against independent validators — before any escrow releases.On permissionlessness throughout the flow: At no step is a compliance decision required. The escrow contracts are non-upgradeable — their settlement logic cannot be modified by any entity. The routing layer uses ZK attestations to anonymise both parties. The proof layer releases funds based on cryptographic verification, not on a compliance decision. This is not a design aspiration. It is a description of the current architecture.
Five layers.
No bypass.
The PROXY protocol is composed of five discrete layers. Every transaction flows through all five. Every component is designed around a single constraint: at no point should any entity have the technical capability to prevent a transaction from completing once a valid DeliveryProof has been submitted.
4.1 — Agent Wallet SDK
A lightweight, framework-agnostic library that initialises a non-custodial ERC-20 wallet on Base for any autonomous agent. Exposes four primary methods: init(), request(), verify(), balance(). Compatible with LangChain, CrewAI, AutoGPT, and any custom agent runtime. No key custody. No KYC. No compliance registration.
4.2 — ZK Routing Layer
Receives broadcast AgentRequest objects and executes a weighted provider matching algorithm. Provider eligibility is verified via zero-knowledge proofs — confirming sufficient bond, resource compatibility, and reliability score without revealing the provider's wallet address or infrastructure details to the requesting agent. The routing score function is a governance-controlled weighted sum across five parameters: stake weight, latency score, reliability score, availability score, and price score.
4.3 — Escrow Smart Contracts
All payment flows through non-upgradeable escrow contracts deployed on Base. Budget ceiling atomically escrowed at broadcast. On valid proof, escrow releases immediately. Failed proofs open a 300-second dispute window. Unresolved disputes route to on-chain DAO arbitration. Contracts are non-upgradeable post-audit — no proxy pattern, no admin key, no entity that can modify settlement logic.
4.4 — Provider Network
Permissionless entry: any operator bonds $PROXY to register a provider node. No whitelist. No KYC. No permission from the protocol. Five node types with distinct proof standards and minimum bond requirements. Bond is subject to slashing for delivery failures (10%), proof timeouts (5%), and fraudulent submissions (50%).
4.5 — Proof Layer
Every resource delivery requires a DeliveryProof before escrow releases. Proof standards are resource-specific. For inference: output hash must be deterministically reproducible from committed model weights, with 8% of jobs re-run by independent validators. For data: signed timestamp within freshness window, cross-validated against two independent sources. Invalid proofs trigger immediate partial slashing.
The data structures
that power every transaction.
Two JSON objects govern the entire PROXY transaction lifecycle. The AgentRequest is constructed by the agent SDK and signed with the agent's private key before broadcast. The DeliveryProof is constructed by the provider and submitted to the proof layer upon job completion. Escrow releases only on valid proof verification.
What agents
spend $PROXY on.
PROXY launches with an initial marketplace of resource categories, each with a defined AgentRequest schema, DeliveryProof standard, and pricing mechanism. All resources are priced and settled exclusively in $PROXY. All providers register permissionlessly by bonding $PROXY — no whitelist, no application process.
6.1 — Provider Bonds by Node Type
Provider registration is permissionless. Any operator bonds the minimum $PROXY amount for their declared node type and begins serving requests. Bond is subject to slashing for failed DeliveryProof submissions, latency SLA violations, and sustained downtime. Minimum bonds: Compute (500 $PROXY), Oracle (250), Relay (150), Storage (200), Bandwidth (100).
The unfreezable
settlement layer.
$PROXY is the sole payment and settlement currency of the PROXY protocol. The choice of native token over regulated stablecoin is an architectural decision: $PROXY has no issuer, no compliance layer, and no entity with the technical capability to freeze a balance or blacklist a wallet address.
| Token Name | PROXY |
| Ticker | $PROXY |
| Network | Base (Ethereum L2 · Chain ID: 8453) |
| Standard | ERC-20 |
| Launch | Fair Launch on Base via Doppler |
| Pre-sale | None |
| Insider Allocation | None |
| Venture Capital | None |
7.1 — Token Utility
Censorship-Resistant Settlement. Every marketplace transaction settles in $PROXY. No stablecoin issuer can freeze it. No compliance layer screens it. No corporate entity controls supply. Settlement is determined by on-chain proof verification logic — not by an off-chain compliance decision.
Resource Payment. All marketplace transactions — inference, data feeds, API access, storage, bandwidth — are denominated and settled in $PROXY. Every unit of network activity creates token demand with no alternative payment path.
Provider Bonding. Providers bond $PROXY to register nodes — collateral against delivery failures, locked from circulation for the duration of active registration. Bond scales with stake tier, creating supply sinks that grow with network participation.
Staking & Job Priority. Providers stake additional $PROXY above their minimum bond to increase routing algorithm weighting. Higher stake weight → higher share of incoming job allocations.
Governance. $PROXY holders govern the protocol via on-chain DAO. Governance scope: resource categories, proof standards, routing algorithm weights, slashing parameters, dispute resolution rules, treasury allocation. No foundation veto. No team veto.
7.2 — Supply Dynamics
Dual-sided supply compression: demand side — every agent transaction transfers $PROXY from agent wallet to provider, creating continuous velocity; supply side — every active provider has bonded $PROXY locked from circulation. As agent count and provider count grow simultaneously, available circulating supply contracts while transaction volume expands. No emission schedule. Supply is fixed at launch.
Anonymous
by default.
Anonymity in PROXY is not a feature that operators opt into — it is the default state of every transaction, enforced at the protocol level through three mechanisms.
Pseudonymous Wallet Addressing. Agent wallets are Base addresses with no on-chain link to human identity. No name, email, KYC, or compliance registration is required or stored. The agent's sole identity on the network is its wallet address.
Zero-Knowledge Routing Attestations. The routing layer verifies provider eligibility using ZK proofs — confirming sufficient bond, resource compatibility, and reliability score without revealing the provider's wallet address or infrastructure details to the requesting agent. Neither party learns the other's identity.
Anonymised Proof Submission. DeliveryProof objects contain only the minimum information required for settlement verification: job ID, output hash, model weights hash, latency, timestamp, and signature. No provider identity, no infrastructure details, no geographic data is included in the on-chain record.
The protocol records only what is necessary for settlement: transaction amount, proof hash, and block timestamp. Nothing more is required. Nothing more is stored.
Built different.
By design.
Incumbent agent payment protocols solve the technical problem of agent payments. PROXY solves the architectural problem: who controls the rails, who screens the transactions, and who can intervene.
| Capability | PROXY | Incumbent Protocols | Stripe / Fiat | Crypto Payments |
|---|---|---|---|---|
| Permissionless — no compliance gatekeeper | ✓ | ✗ KYT screening | ✗ | Partial |
| Anonymous — no transaction surveillance | ✓ | ✗ Logged by operator | ✗ | Partial |
| Native token — no stablecoin issuer | ✓ | ✗ USDC — freezable | ✗ | Varies |
| No admin keys — no off switch | ✓ | ✗ Kill switch exists | ✗ | Partial |
| Censorship-resistant settlement | ✓ | ✗ Stablecoin freezable | ✗ | Partial |
| Cryptographic proof of delivery | ✓ | ✗ | ✗ | ✗ |
| Non-custodial agent wallets | ✓ | ✗ Custodial | ✗ | ✓ |
| Agent-to-agent payments | ✓ | Partial | ✗ | ✗ |
Building
in public.
- Token launch on Base via Doppler — fair launch, no pre-sale
- Website, whitepaper, and GitHub live
- Agent Playground live — full protocol flow demonstration
- Twitter/X and Telegram communities launched
- Early access waitlist open
- PROXY testnet deployment on Base Sepolia
- Agent Wallet SDK alpha release — JavaScript + Python
- First provider integrations: inference and data feeds
- ZK routing layer implementation
- Smart contract audit initiated
- Mainnet deployment on Base — audit complete
- Public resource marketplace open
- Agent SDK v1.0 public release
- First live agent transactions settled on-chain
- Agent-to-agent payment layer live
- DAO governance activated — $PROXY holders govern protocol parameters
- Cross-chain agent wallet support
- Progressive decentralisation of routing layer
The permissionless
alternative is here.
The rails for agent payments have been built. They process hundreds of millions of transactions. The agent economy has infrastructure. The question is no longer whether agent payments work — it is who controls them, who screens them, and who can turn them off.
PROXY is the answer to that question. Not the first agent payment protocol, but the first one nobody controls. No KYT screening. No stablecoin with a freeze function. No corporate entity with an admin key over settlement contracts. Five protocol layers — each designed so that no intermediary can prevent a valid transaction from completing.
For agents where that distinction doesn't matter, incumbent infrastructure works fine. For agents where it does — for operators who need genuine privacy, genuine censorship resistance, and settlement in a currency no entity can freeze — PROXY is the only option that exists.
The opportunity: The agent economy will be worth trillions. The permissionless slice of that economy needs its own rails. PROXY builds them. $PROXY flows through every transaction on those rails — the unfreezable settlement currency of the agent economy's permissionless layer.
PROXY is launched fairly — no pre-sale, no insider allocation, no venture capital. $PROXY is available to anyone from the first block. The protocol is built in public, documented openly, and governed entirely by its token holders.
The rails exist. PROXY is the ones nobody controls.
DISCLAIMER. This whitepaper is for informational purposes only and does not constitute financial advice, investment advice, or a solicitation to purchase any token or security. $PROXY is a utility token designed for use within the PROXY protocol. Participation in any token launch carries significant risk including total loss of capital. The PROXY protocol is in development — features described herein represent the intended design and may change. This document does not constitute a prospectus or offering document of any kind. Readers are advised to conduct their own research and consult appropriate professional advisors before making any financial decision. Nothing in this document should be construed as a guarantee of future performance or outcomes.