Platform

Verified owners. Bounded agents. Private payments.

SILS is three steps delivered as seven products. Provision a verified owner. Assign agents under a policy. Settle with a proof the merchant checks in one call.

In development Nothing on this page is live. Every product carries its own status.

Overview

Provision. Assign. Settle.

Each step maps to products. Identity and policy calls are free to prepare. Settlement carries the fee.

Provision

A person or business verifies once, off chain, with regulated identity data partners. The chain records a commitment. Never the documents.

SILS ID

Assign

The owner creates named agents and sets limits. Each agent acts under a signed policy. The owner watches and stops them from one console.

SILS Policy · SILS Console

Settle

The agent pays in USDC and presents a proof. The merchant verifies it. Reputation and funded intent build on the settled record.

SILS Proof · Merchant · Score · Intent

SILS ID · Provision

In development

Every agent is the child of a verified owner.

What it does: Binds each agent to a verified person or business on Revolution Name Service. KYC for people. KYB for businesses. KYA for agents. Agent names are soulbound. There is no transfer function.¹
Concrete detail: Revocation is permanent and immediate. A revoked identity fails at the next transaction, not the next batch. Agents cannot create agents.²
Who uses it: Owners who want agents to act for them. Businesses that run merchant agents. Developers who need a verified principal behind every call.

Name tree, illustrative

rob.revo Verified owner

shopping.rob.revo

travel.rob.revo

old.rob.revo Revoked

On chain per identity: one facet root, one reputation pointer, per-settlement nullifiers. Nothing else.¹

Verification levels

Level	What is checked	What it unlocks
Basic	Email and device bound. Uniqueness checked.	Agent creation. Low-value settlement.
Verified	Government identity checked against data partners.	Age and jurisdiction facets. Standard settlement.
Enhanced	KYC and AML screening completed.	Accredited-investor facets. RWA-linked settlement.
Entity	Legal entity verified with an authorized signatory.	Merchant agents. Bonded reputation pools.

Levels are governance-set on Revolution. Verification happens off chain. The chain records commitments, never attributes.¹

SILS Policy · Assign

In development

Limits the agent cannot exceed.

What it does: Holds each agent to its owner's signed policy. The policy is stored off chain. Its hash is anchored on chain with the agent identity and expiry.³
Concrete detail: The agent never holds the owner's key. It holds a session key. A policy hook checks target, selector, asset, amount, rate and expiry on every call. A call outside the policy fails.³
Who uses it: Owners and finance teams who set budgets. Developers who set policy through the API or MCP.

Where policy is enforced

Before the call. The policy service evaluates each payment off chain.
On every call. The session key hook rejects anything outside target, asset, amount, rate or expiry.
At settlement. Funding reverts unless the mandate is anchored and required proofs verify.
In batches. Netted micro-payments are checked against the caps on chain.

Policy fields

Field	What it controls	Example
Per-transaction cap	Largest single payment the agent can make	25.00 USDC
Per-period cap	Total spend in a day, week or month	50.00 USDC per day
Allowed categories	Merchant categories the agent may buy from	`retail`, `books`
Counterparty facets	What a seller must prove before the agent pays	`entity.verified`
Approval threshold	Payments above it wait for the owner to approve	40.00 USDC
Expiry	When the policy lapses and the agent stops	`2027-01-01`
Kill switch	Suspends the agent at its next transaction	On or off
Mandate hash	Hash of the signed policy, anchored on chain	`0x9c1e...4b7a`

Examples are illustrative. Field set follows the standing mandate in the Revolution design.³

SILS Proof · Settle

In development

Prove the payment. Keep the wallet private.

What it does: Replaces the transaction hash in an x402 payment with a proof. The proof shows that a settlement exists, matches the stated amount, asset and recipient, has not been presented before, and is bound to this merchant's request. It ships as a scheme inside x402, not a rival protocol.⁴
Concrete detail: One verification can combine payment, age, jurisdiction and mandate checks. An owner can issue a viewing proof that discloses one specified payment to an auditor. The proof is free. The fee sits on settlement.⁴
Who uses it: Agents that pay. Merchants that verify. Auditors who need one payment, not a full history.

The merchant learns

Payment settled
Amount and asset meet terms
Recipient is this merchant
Not reused
Requested facets hold

Sealed in the proof. The merchant never sees

Payer wallet
Balance
Payment history
Identity documents
Budget or remaining cap

Proof internals are not published until counsel clears them.

SILS Score · Settle

In development

Reputation proven as a threshold.

What it does: Scores agents and merchant entities from settled volume, disputes, delivery and bond. A deterministic, published function produces the score.⁵
Concrete detail: The score is exposed as the facet reputation.above. The threshold is proven. The number is not revealed. A good record cannot be bought, and a bad one cannot be discarded.⁵
Who uses it: Merchants that filter buyer agents. Buyers that filter sellers. Networks that set bonds and caps.

Scope, by design

Scores agents and merchant entities. Never the human.
Commerce performance inside the network as inputs.
A threshold proof, never a published number.
Commercial reputation. Not a consumer credit score.

SILS Intent · Settle

Planned

Buyers post funded demand. Merchants bid.

What it does: A buyer agent posts a committed intent backed by escrow. Bonded merchant agents respond with signed offers. Expert agents attach recommendations and earn an affiliate split when the buyer accepts.⁶
Concrete detail: The price ceiling stays private. The intent carries a commitment to it and a proof that escrow covers it. Posting is free. Every intent needs a funds proof.⁶
Who uses it: Buyer agents with a budget. Merchant agents that want committed demand. Expert agents that recommend.

An intent carries

Category and a hash of the specification
A commitment to the price ceiling
A proof that escrow covers the ceiling
Required seller facets and delivery terms
An expiry and a responder filter

SILS Merchant · Settle

In development

A drop-in verifier for the checkout.

What it does: Checks the proof, the owner and the policy in one call and returns one answer. Proof valid. Owner verified. Within policy. Middleware for Express, Hono and Next.js.⁷
Concrete detail: Escrow in three modes: Full, Milestone and Stream. Stream releases metered funds up to a cap for subscriptions and API usage. Splits for merchant, affiliate, network fee and withholding are fixed at funding.⁷
Who uses it: API sellers, online merchants and marketplaces that accept agent payments.

server.ts

import { sils } from "@sils/merchant"

app.get("/api/v1/report",
  sils.requireProof({
    amount: "24.00", asset: "USDC",
    payTo: "sales.acme.revo",
    facets: ["human.verified"]
  }),
  handler)
// Proof valid. Owner verified. Within policy.

Illustrative. Interface subject to change.

SILS Console · Assign

In development

The owner's control room.

What it does: One place to verify, create agents, set policy, fund, and stop. Every action is signed by the owner with a passkey.⁸
Concrete detail: The kill switch suspends an agent mid-stream and the stream halts. Policy history keeps every version, so an auditor can see which rules applied to which payment.
Who uses it: Owners, operations leads and compliance teams.

In the console

VerificationAgent rosterKill switchKey rotationRecoveryPolicy historyFundingAudit export

What the merchant sees

Same payment. Two receipts.

Standard x402 settlement publishes the payer address on chain. Any merchant can read the wallet, its balance and its history. A SILS receipt answers the merchant's question and stops there.⁹

Standard x402 receipt

HTTP 402 · payment settledexact · base

amount24.00 USDC

payTo0x4b20...c91e

payer wallet0x7a3f9c21e04b58d6a1f0public

balance1,842.17 USDCreadable

history212 prior paymentsreadable

ownerunknown

policynone

SILS receipt

HTTP 402 · payment settledsils-proof · revolution

amount24.00 USDC

payTosales.acme.revo

payer wallet0x7a3f9c21e04b58d6a1f0Sealed by ZK proof0x9c1e··4b7a

balance1,842.17 USDCSealed by ZK proof0x51d0··e2c9

history212 prior paymentsSealed by ZK proof0xa8f3··07d1

ZK proof valid. Owner verified. Within policy. The merchant learns yes. Nothing else.

Illustrative. Wallet values are examples. SILS Proof is in development.

Who it is for

Four audiences. One trust layer.

Owners

Verify once. Give each agent a name, a budget and a kill switch.

SILS ID and Policy

Agent developers

One MCP server for identity, policy, proofs and payment. REST and SDKs for the rest.

Developer docs

Merchants

Accept agent payments with a verified owner behind them. Learn yes. Nothing else.

SILS Merchant

Networks and processors

Read a SILS identity as a Know Your Agent credential without re-registering the agent. Design intent.

Networks

Pricing logic

Free to prepare. Paid to settle.

Nothing is charged while an owner decides whether to try it. SILS earns where agents create value: managed agents and settled payments.

Free to start

Identity creation, proofs and intent posting are free within a metered allowance. Gas for these calls is sponsored on Revolution.

Per agent subscription

Businesses pay per agent per month for agent management, the console and merchant tooling.

Merchant settlement fee

Merchants pay a SILS service fee on settled agent payments. It is separate from the Revolution protocol fee.

Enterprise

Annual contracts with committed volume, delegated administration and compliance reporting.

Pricing structure is draft. Prices will be published when final.

Sources

Revolution Network Whitepaper v2.0, October 2026, draft for review, §6.1 to §6.4.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §5.6 and §6.3.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §7.4 and §8.4.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §8.6 and §11.6.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §8.8.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §8.7.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §8.5 and §11.6.
Revolution Network Whitepaper v2.0, October 2026, draft for review, §11.1 and §11.5.
Ethereum EIPs, "ERC-3009: Transfer With Authorization." eips.ethereum.org/EIPS/eip-3009. x402 Foundation, "x402 Specification v2," Dec 9, 2025. github.com/x402-foundation/x402