Protocol registry
Domain packs extend the base protocol.
The Sygil base protocol provides four universal methods. Domain protocol packs layer on top — each one defines the state machine, oracle types, and escrow parameters for a specific vertical.
4
base methods
1
live pack
∞
extensible
Architecture
Base protocol plus domain packs.
The four base methods handle discovery, negotiation, commitment, and evidence for every interaction. A domain pack defines what happens within those methods for a specific use case.
Base protocol
Four universal methods
agent/capabilities, agent/propose, agent/commit, agent/evidence. Every Sygil agent implements these. They're domain-agnostic — the same methods work for commerce, marketing, or services.
Domain packs
Vertical-specific extensions
A protocol pack defines the state machine transitions, capability schemas, evidence requirements, oracle addresses, and escrow parameters for a vertical. Packs are versioned and registered on-chain.
Composable
Mix packs in one session
A single agent session can run multiple packs. A commerce agent can also handle a marketing pack to negotiate promotional terms as part of the same deal.
Registry
Available protocol packs.
Protocol packs are identified by name/version. Agents match by capability intersection — no central coordinator needed.
Buyer-seller negotiation with price offers, attribute penalties, inventory attestation, escrow settlement, and delivery oracle. The reference implementation for Sygil Protocol.
Negotiated ad placements between publisher agents and advertiser agents. Audience proof schemas, impression attestation, and performance-gated payment release.
Service delivery agreements between client agents and provider agents. Milestone-based escrow, deliverable attestation, and time-based settlement.
Short-term asset rental agreements. Availability attestation, deposit escrow, damage oracle, and automatic return confirmation.
Extensibility
Anyone can build a protocol pack.
Protocol packs are open TypeScript modules. Define your state machine, publish it, and register it on-chain. Any agent that installs your pack can immediately negotiate with any other agent using the same pack.
Open spec
Published protocol design
The base protocol spec and the pack API are fully documented and open. Anyone can build a pack without permission or coordination with the Sygil team.
On-chain registry
Permissionless registration
Register your pack identifier on-chain. Agents auto-discover compatible counterparties by matching registered pack names. No app store, no gatekeeping.
Single escrow contract
No new contract needed
The base CommerceEscrow contract is parameterized around oracle addresses, fee schedules, and dispute windows. You don't deploy new contracts — you configure the existing one.
Build
Create a protocol pack.
Start with the Sygil SDK, fork commerce/v1 as a reference, and publish your domain pack to the registry.