aCommerce

The buyer is now an agent.

eCommerce was built for a person at a screen. aCommerce is commerce conducted agent to agent under a human's mandate. The human sets policy. The agents execute. SILS supplies the trust at the moment of settlement.1

In development aCommerce on SILS is in development. Each capability below carries its own status.

Two models

Same purchase. A different buyer.

The change is not a faster checkout. The party at the counter changes. That changes what a merchant needs to know, and what it should never see.

eCommerce

A person browses a catalog, fills a cart and pays with a card.

  • The buyer pulls. Merchants pay platforms to be found.2
  • Checkout collects the buyer's details to complete the sale.
  • The platform owns the customer relationship.2
aCommerce

An agent with a verified owner and a funded mandate negotiates, contracts and settles with a merchant agent.1

  • The buyer publishes funded demand. Merchant agents respond.6
  • The merchant checks proofs. It does not collect the buyer's data.4
  • The owner sets limits. The agent cannot exceed them.3

Side by side

What changes, row by row.

The SILS column describes design scope on Revolution Network. Status is stated per row.

DimensioneCommerceaCommerce on SILSStatus
Who actsA person browses, clicks and checks out.A personal agent negotiates and settles with a merchant agent. The person sets policy once.1In development
Who is buyingAn account login and a saved card. The card proves funds, not who stands behind an agent.A soulbound agent name such as shopping.rob.revo, bound to a verified owner. It cannot be transferred.5In development
AuthorityA session and a stored card. Spending limits live with the card issuer.A standing mandate: per-transaction cap, per-period cap, categories, expiry and a kill switch. Its hash is anchored on chain.3In development
PrivacyCheckout collects name, contact and payment details. Mandates in the market today are plaintext, so a merchant that reads one learns the budget.2The merchant verifies payment, age and jurisdiction in one zero-knowledge proof. It never sees the wallet, the balance, the history or the budget.4In development
PricingThe seller can see who is buying and adjust the price.The buyer commits to a sealed price ceiling. The merchant never sees willingness to pay.69Planned
DiscoveryBuyers pull from catalogs. Merchants pay to be found.The buyer agent posts an intent with a funds proof. Bonded merchant agents respond with signed offers.6Planned
PaymentEach payment is authorized and settled on its own.USDC settles on Revolution with escrow in three modes: full, milestone and stream. Micro-payments net off chain. One settlement carries the batch.7In development
Who gets paidThe platform takes its cut outside the sale.2Splits are fixed at funding and paid in the settlement: merchant, affiliate and network fee.7In development
TrustReviews and ratings. Open agent registries invite Sybils.8Merchant reputation is backed by bonded stake. Records follow the verified owner, so a bad record cannot be discarded.8In development
DisputesChargebacks through the card network.Escrow holds funds until delivery. Adjudicated disputes pay restitution from the merchant's bond.8Planned
ComplianceDocuments collected and stored by each merchant.Proofs, not documents. No personal data goes on chain.9In development

SILS capabilities run on Revolution Network. Revolution's identity and aCommerce layers are specified, not built.10

What the merchant learns

eCommerce collects. aCommerce proves.

The same 24.00 USDC digital purchase, two ways. On the left, the record a merchant keeps today. On the right, what it receives with SILS.

eCommerce checkout record
Order · paidcard · checkout
amount24.00 USD
buyerJordan Leecollected
emailjordan@example.comcollected
card···· 4421stored
history38 prior ordersprofiled
agent ownerunknown
Payment authorized. The merchant now holds the buyer's data.
aCommerce with SILS
HTTP 402 · settledsils-proof · revolution
agentshopping.jordan.revo
amount24.00 USDC
ownerJordan LeeSealed by ZK proofhuman.verified
wallet0x7a3f9c21e04b58d6Sealed by ZK proofcommitment 0x51d0··e2c9
budget200.00 per monthSealed by ZK proofmandate.covers
facetsage.over.18 · jurisdiction.in:US
ZK proof valid. Owner verified. Within mandate. The merchant learns yes. Nothing else.

Illustrative. Names and values are examples. SILS Proof is in development. Proof internals are not shown.

One purchase on SILS

Six steps. One settlement.

Identity, mandates, intents, offers and escrow are free to prepare. Settlement carries the fee.7

01 · OWNER

Set the mandate

A verified owner creates shopping.rob.revo and signs its limits. The hash is anchored.

In development
02 · BUYER AGENT

Publish intent

The agent posts what it needs, a sealed price ceiling and a proof that escrow covers it.

Planned
03 · MERCHANT AGENTS

Offer

Bonded merchant agents that pass the filter respond with signed offers.

Planned
04 · PROOF

Prove, privately

The agent accepts and funds escrow. One ZK proof covers payment, age, jurisdiction and mandate.

In development
05 · MERCHANT

Deliver

The merchant verifies the proof, learns yes, and delivers.

In development
06 · SETTLEMENT

Settle and split

Escrow releases on confirmation. Merchant, affiliate and network fee are paid in one transaction.

In development

Where SILS fits

The aCommerce stack, mapped to SILS.

Revolution specifies aCommerce in five layers. Each layer depends only on the layers below it. SILS products sit on each one.10

L4EnforcementSILS ScoreBonded merchant reputation, shown only as a threshold proof. Disputes and slashing.In development
L3DiscoverySILS IntentFunded buyer intent that merchant agents bid on.Planned
L2PaymentsSILS Proof · SettlementPrivate proof of payment inside x402. Escrow, splits and USDC settlement.In development
L1IdentitySILS ID · PolicyVerified owners, soulbound agent names and the mandate every call is checked against.In development
L0ChainRevolution NetworkZKsync OS with validity proofs and data on Ethereum. SILS plans to run a verifying node.In development

Works with what merchants run

Built to plug in, not to replace.

SILS works beside a merchant's existing processor. It does not issue cards, run a catalog or custody fiat.11

Build with SILSCompare approaches
StandardHow aCommerce on SILS connects
x402SILS Proof is a scheme inside x402. A .revo name can be the payee.
AP2Canonical mandate format. Hashes are anchored. Intent proofs run over AP2 fields.
MCP and A2AIdentity, proofs, intents and settlement as tools and agent cards.
Card agentic tokensThe card authorization reference is recorded with the settlement.
ERC-8004A read-only mirror of every agent identity, with transfer disabled.

Design intent on Revolution Network. Not yet built.

Sources

  1. Revolution Network Whitepaper v2.0, October 2026, draft for review, §08 and §15.2 (ACommerce: commerce conducted agent to agent under a human's mandate).
  2. Revolution Network Whitepaper v2.0, October 2026, draft for review, §01 and §1.2.
  3. Revolution Network Whitepaper v2.0, October 2026, draft for review, §7.4 and §8.4.
  4. Revolution Network Whitepaper v2.0, October 2026, draft for review, §6.4 and §8.6.
  5. Revolution Network Whitepaper v2.0, October 2026, draft for review, §6.3.
  6. Revolution Network Whitepaper v2.0, October 2026, draft for review, §8.7.
  7. Revolution Network Whitepaper v2.0, October 2026, draft for review, §2.1, §8.3, §8.5 and §8.10.
  8. Revolution Network Whitepaper v2.0, October 2026, draft for review, §1.2 and §8.8, citing Xiong et al., ERC-8004 reputation Sybil study, arXiv, June 2026. Ethereum EIPs, "ERC-8004: Trustless Agents" (Draft). eips.ethereum.org/EIPS/eip-8004
  9. Revolution Network Whitepaper v2.0, October 2026, draft for review, §2.1, §5.1 and §13.2. Section 13.2 maps design to emerging rules and is not legal advice.
  10. Revolution Network Whitepaper v2.0, October 2026, draft for review, §02 (Figure 1) and §8.1.
  11. Revolution Network Whitepaper v2.0, October 2026, draft for review, §8.6 and §8.9.