Skip to content

Commit 598388a

Browse files
committed
docs: add LLM-Friendly Docs section and enhance ERC-8004 documentation
1 parent f373a84 commit 598388a

2 files changed

Lines changed: 42 additions & 0 deletions

File tree

docs/.vitepress/config.ts

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,14 @@ export default defineConfig({
7373
{ text: 'Compute Unit Benchmarks', link: '/advanced/benchmarks' },
7474
]
7575
},
76+
{
77+
text: 'LLM-Friendly Docs',
78+
collapsed: true,
79+
items: [
80+
{ text: 'llms.txt', link: '/llms.txt' },
81+
{ text: 'llms-full.txt', link: '/llms-full.txt' },
82+
]
83+
},
7684
],
7785

7886
socialLinks: [

docs/erc-8004.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,40 @@ SATI is ERC-8004 on Solana. Full feature parity with the standard, plus Solana-n
1111

1212
[[toc]]
1313

14+
## How SATI Relates to ERC-8004
15+
16+
ERC-8004 is the standard. SATI is an implementation of that standard on Solana, with Solana-native extensions on top.
17+
18+
Think of it like this: ERC-8004 defines *what* agent identity infrastructure should look like - registration, reputation, validation, and a shared registration file format. SATI implements all of that using Solana's primitives (Token-2022 for identity, Light Protocol for storage, Photon for indexing) and adds capabilities that the standard leaves to implementers.
19+
20+
### What's the same
21+
22+
- **Registration file format** - same JSON schema, same field names, same CAIP-2 identifiers. An ERC-8004 registration file on Base and a SATI registration file on Solana are interchangeable.
23+
- **Feedback fields** - `value`, `valueDecimals`, `tag1`, `tag2`, `endpoint` map directly between ERC-8004 and SATI. See [Feedback Field Mapping](#feedback-field-mapping) below.
24+
- **Cross-chain identity** - agents can be registered on both chains simultaneously, linked via the `registrations` array in the shared registration file.
25+
26+
### What SATI adds
27+
28+
ERC-8004 defines the interfaces and leaves implementation choices to each chain. SATI makes three specific choices that extend the standard:
29+
30+
**1. Optional proof of participation (FeedbackV1)**
31+
32+
ERC-8004's `giveFeedback()` is an open model - any reviewer can submit feedback about any agent. SATI implements this as FeedbackPublicV1 (the default). On top of that, FeedbackV1 adds an optional dual-signature flow where the agent cryptographically commits to the interaction before knowing the feedback outcome. This makes feedback verifiable by on-chain programs - useful for DeFi composability, escrow, and automated trust decisions.
33+
34+
Both models coexist. FeedbackPublicV1 is the ERC-8004 compatible default. FeedbackV1 is available when stronger guarantees are needed.
35+
36+
**2. Native indexing via Photon**
37+
38+
On EVM, querying "all feedback for agent X" typically requires an external indexer like The Graph - a separate service with its own trust assumptions and operational cost. On Solana, Photon RPC indexes compressed accounts natively. Every RPC provider that supports Light Protocol serves this data as a standard RPC call, with no additional infrastructure to deploy or maintain.
39+
40+
**3. Cost-predictable compressed storage**
41+
42+
Every feedback interaction is stored individually on-chain at ~$0.002 via ZK Compression - not just aggregated summaries. This cost is stable regardless of network conditions. On EVM L2s, per-transaction costs are comparable at current gas prices but vary with network congestion.
43+
44+
### Can agents exist on both?
45+
46+
Yes. An agent registered through SATI on Solana and through ERC-8004 on Base can share the same registration file, the same services, and the same identity. The `registrations` array in the registration file links identities across chains using CAIP-2 identifiers. See [Cross-Chain Agent Identity](#cross-chain-agent-identity) below.
47+
1448
## What's Compatible
1549

1650
SATI implements every component of the ERC-8004 specification:

0 commit comments

Comments
 (0)