Self Protocol
Open-source zero-knowledge identity protocol (passport-based proof of personhood) used to gate agent access to onchain services.
- Sato Score80
- ChainsMultichain
Self Protocol is an open-source security tool, with last code activity on 2026-10-16 (Active). Sato Score 80/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-22. How the score works →
See how to install Self Protocol →Last commit Oct 16, 2026 · ★ 1,260
Listed from self.xyz on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21. Evidence →
Next step
Watch Self Protocol
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on selfxyz/self before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Self is an open-source ZK identity protocol that lets a user prove personhood or specific attributes (age, nationality) from a passport without revealing the underlying document, verified onchain. It's increasingly referenced as an identity primitive for services that want to confirm a human is behind an agent before granting access; 1,252 GitHub stars, actively developed.
Sato Score
80/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 20/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 8/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.4.1 · as of 2026-09-26- Does it take your key?
- No key read found
- Does your key leave?
- Not observed
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from self.xyz on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.self.xyz | as of 2026-10-22 |
| Verification status | Unverified — not independently reviewed | self-reported | self.xyz | as of 2026-10-22 |
| Recent activity | last commit 2026-10-16 | observed | github.com/selfxyz/self | 2026-10-22 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | docs.self.xyz | 2026-09-21 |
| Website answers | answered (HTTP 200) | observed | self.xyz | 2026-10-22 |
| Daily check record | 90 of 90 daily checks since 2026-07-24 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-21 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-26 |
| Key leaves the machine | not observed during install and start-uplater or triggered code paths are not covered | observed | satohub.ai | 2026-09-26 |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-26 |
| Docs | https://docs.self.xyz/confidence 0.95 | self-reported | github.com/selfxyz/self | as of 2026-08-08 |
| Sato Score | 80/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-22 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Sep 21, 2026
Runtime: Node.js / TypeScript (npm package)
npm install @selfxyz/enterprise-sdk
import { SelfClient } from '@selfxyz/enterprise-sdk'; new SelfClient({ apiKey: process.env.SELF_API_KEY })You supply: SELF_API_KEY (from the dashboard Developer > API keys section), SELF_WEBHOOK_SECRET (webhook signing secret, shown once when adding an endpoint)
Read from the project’s own docs as of 2026-09-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-24
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 39 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-22, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- Identity/verification protocol
- Open source
- Yes
- Last checked
- 2026-10-22
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Self Protocol fits
Related concepts: What Are Onchain Agents?, Onchain Agents vs Offchain Agents, How Agents Use Wallets
Listing History
Recorded changes to Self Protocol's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 26, 2026Edited: entity class, resource type
- Sep 21, 2026Verified: deploy spec
- Aug 8, 2026Auto-enriched: docs url
- Aug 8, 2026Sato Score tier: Medium → HighScore 69 → 77.
- Jul 25, 2026Sato Hub began tracking this listing
- Jul 19, 2026Edited: chains supported
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
COTI
ActivePrivacy infrastructure that gives MCP-compatible agents private wallets, encrypted messaging, and confidential smart contracts using Garbled Circuits.
Turnkey
ActiveSecure key management infrastructure with policy controls, commonly used for agent wallets.
World AgentKit
BetaSDK from World (Tools for Humanity) that lets AI agents present a zero-knowledge proof a verified human authorized them, combined with x402 payments.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Self Protocol
- Is Self Protocol open source?
- Yes. Self Protocol is open source under the Unknown license; the repository is https://github.com/selfxyz/self. Checked as of 2026-10-22.
- Which chains does Self Protocol support?
- Self Protocol lists support for Multichain as of 2026-10-22.
- Is Self Protocol still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-16 (last commit 2026-10-16), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Self Protocol?
- Node.js / TypeScript (npm package). Install: npm install @selfxyz/enterprise-sdk. Entry: import { SelfClient } from '@selfxyz/enterprise-sdk'; new SelfClient({ apiKey: process.env.SELF_API_KEY }). Sato Hub reproduced this install in a container on 2026-09-21.
- Is Self Protocol verified on Sato Hub?
- Sato Hub holds one earned check for Self Protocol: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 80 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Self Protocol — Sato Hub." Sato Hub, updated 2026-10-22, accessed 2026-10-22. https://satohub.ai/resources/self-protocolData last refreshed 2026-10-22; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.