[CHROME_DAO_INITIATIVE] / SMART-SSI

Smart-SSI: self-sovereign identity on Solana

Smart-SSI is an open-source self-sovereign identity protocol by Chrome DAO. Your runs, your missions, your reputation already exist, locked inside platforms. Smart-SSI turns them into proofs anyone can verify, without exposing your data and without depending on a platform.

RAW DATA ON-CHAIN
0
RAW DATA ON-CHAIN
LAYERS: PROVE, INTERPRET, ATTEST
3
LAYERS: PROVE, INTERPRET, ATTEST
TOKEN. FUNDED BY THE DAO
NO
TOKEN. FUNDED BY THE DAO
GET /athlete/activities · TLS 1.3RECEIVING_TLS_RESPONSE
{
  "athlete": "camille.r",  "email": "c.r***@mail.com",  "session_token": "eyJhbGciOiJIUzI1...",  "activities_total": 312,  "first_activity": "2024-09-03",  "avg_runs_per_week": 3.0,  "home_lat": 48.8566,  "home_lng": 2.3522,  "heart_rate_avg": 152,  "last_route": "Parc des Buttes...",}

ATTESTATION · SOLANA

REGULAR RUNNER

3× / WEEK · SINCE 2024-09

VALID
SUBJECT
did:sol:7xKX…q9Fd
SOURCE
strava
PROOF_REF
0x9f3c…e21a
RAW_DATA
NOT STORED
01RESPONSE
02PROOF
03REDACT
04ATTEST

01 // THE_PROBLEM

Today you either declare or expose.

Proving who you are online forces a choice between not being believed and showing everything. Pick a mode and watch what the landlord gets.

VERIFIER_QUERY: "DO YOU EARN MORE THAN €3,000 A MONTH?"

CAMILLE R.FR76 3000 4000 0312 4567 8901 23412 RUE DES LILAS, PARIS
07/07SALARY · ACME SAS+3 412,00
26/07DONATION-77,50
11/07RENT-106,69
28/07SUPERMARKET-12,25
13/07CINEMA-67,75
22/07BAKERY-76,60
14/07BAR-54,17
14/07INSURANCE-47,50
24/07SUPERMARKET-93,90
28/07BOOKSHOP-25,46
04/08SALARY · ACME SAS+3 412,00
04/08TRANSFER TO MUM-58,76
22/08PHARMACY-78,59
26/08SUPERMARKET-76,67

Illustrative scenario.

TRUST96%
PRIVACY4%

DATA POINTS HANDED OVER

93

THE LANDLORD NOW KNOWS WHERE YOU SHOP, EAT AND HEAL.

01

SILOED IDENTITIES

Years of runs, hundreds of freelance jobs, a reputation: locked in each service, gone if the account closes.

02

DECLARING IS NOT ENOUGH

With generative AI a credible fake profile costs almost nothing. One actor can pass for hundreds.

03

VERIFYING COSTS PRIVACY

To prove an income you send three full bank statements. The verifier keeps far more than it needs.

04

EXISTING ANSWERS ARE PARTIAL

DIDs and Verifiable Credentials need an issuer. Strava, Spotify or your bank will never issue one.

02 // THE_PROTOCOL

Three layers.
Data in, proof out.

Smart-SSI builds a bridge between the data that already exists and attestations anyone can verify: a zkTLS proof, a public rule, then an attestation on Solana.

01

LAYER_1 · PROOF

The data really comes from the source

You log in to the service as usual. With zkTLS, an attestor run by the DAO on open-source code watches the encrypted exchange without seeing its content, and you generate a proof that the server’s response contains the data. Nobody gets your credentials. Only the useful fact is revealed.

PHASE_4SEES: ▓▓▓▓
DAO_ATTESTORSEES: ▓▓▓▓
PHASE_4SEES: ▓▓▓▓
YOUDEVICE
9f3c 0a71 e2b8 44d0 c19e 7f02 b3aa 58e6 21cf 9d04 6be1 f3a7 0c58 e912 47bd a0f6 9f3c 0a71 e2b8 44d0 c19e 7f02 b3aa 58e6 21cf 9d04 6be1 f3a7 0c58 e912 47bd a0f6 9f3c 0a71 e2b8 44d0 c19e 7f02 b3aa 58e6 21cf 9d04 6be1 f3a7 0c58 e912 47bd a0f6 9f3c 0a71 e2b8 44d0 c19e 7f02 b3aa 58e6 21cf 9d04 6be1 f3a7 0c58 e912 47bd a0f6 9f3c 0a71 e2b8 44d0 c19e 7f02 b3aa 58e6 21cf 9d04 6be1 f3a7 0c58 e912 47bd a0f6 9f3c 0a71 e2b8 44d0 c19e 7f02 b3aa 58e6 21cf 9d04 6be1 f3a7 0c58 e912 47bd a0f6
TLS 1.3 · ENCRYPTED
STRAVASERVER

NEVER SHARED

login · password · session token

OUTPUT

π = proof(response contains activities_total)

02

LAYER_2 · INTERPRET

The data becomes a useful claim

“312 recorded activities” tells a verifier little. An AI model turns proven data into a readable, dated claim. It produces derived facts, never personality traits: every claim traces back to the proven data it rests on.

PROVEN DATA · STRAVA · 2024-09 → 2026-090 RUNS

activities_total = 312

weeks = 104

avg = 3.0 / week

DERIVED CLAIM

REGULAR RUNNER · 3×/WEEK · 2 YEARS

✓ derived fact   ✗ “disciplined person”   ✗ “health profile”

03

LAYER_3 · ATTEST

The claim is bound to your identity

The claim is signed and recorded on Solana, attached to your decentralized identifier. Only the claim goes on-chain, never the data. Any service can verify it in milliseconds, without contacting you or the source.

SOLANA · ATTESTATION SERVICE LIVE SLOTS
#80120tx…
#80121tx…
#80122tx…
#80123tx…
#80124tx…
#80125tx…

ON-CHAIN

claim · date · source · signature · expiry

bound to did:sol:7xKX…q9Fd

ANY VERIFIER

verify(attestation) → PENDING…

no call to you, no call to Strava

03 // PRIVACY_&_TRUST

Your device is
the perimeter.

Credentials, raw data and history never leave the phone. Only the claim crosses the line, and you can take it back.

YOUR DEVICE

NEVER LEAVES

LOGIN CREDENTIALS
RAW DATA
ACTIVITY HISTORY
DEVICE_PERIMETER

SOLANA

PUBLIC · VERIFIABLE

CLAIM✓
DATE✓
SOURCE“strava”
SIGNATURE✓
STATUSVALID

YOU_STAY_IN_CONTROL

You choose which proofs to generate, approve each claim before it is issued, decide who sees it, and can revoke it at any time. Revoking does not erase the on-chain record; it makes the attestation invalid for every verifier.

TRAIL CLUB · VERIFIER

verify("runner.regular", did:sol:7xKX…q9Fd)

→ VALID

Two trust levels, made explicit

Every attestation rests on two kinds of trust. Each phase of the roadmap shrinks what you still have to take on faith.

LEVEL_1

DATA PROOF

The data really comes from the stated service. Trusted today: zkTLS attestors.

ONE DAO-RUN ATTESTOR

SEVERAL INDEPENDENT ATTESTORS

DAO-SELECTED NETWORK

Bar = trust you still extend (qualitative) →

LEVEL_2

INTERPRETATION

The claim correctly follows from the data. Trusted today: the Smart-SSI issuer.

PUBLIC MODEL + RULES

TRUSTED EXECUTION (TEE)

zkML

Bar = trust you still extend (qualitative) →

GDPR: claims cover activity facts, never psychological traits or sensitive data (health, opinions, religion), and rest on explicit consent at each step. No personal data goes on-chain in clear; the fit with the right to erasure is still to be confirmed with a lawyer.

04 // USER_JOURNEY

The cryptography
stays invisible.

Users only see badges they control, share and can remove from their profile. Here is Camille.

SMART-SSI1/5

NEW IDENTITY

ID

did:sol:7xKX…q9Fd

✓ READY · NO SEED PHRASE

05 // USE_CASES

First the DAO.
Then anyone who needs trust.

Smart-SSI serves the Chrome DAO itself first, then opens to every service that has to know something about you.

DAO · ANTI_SYBIL_VOTING

One person. One voice.

However many wallets someone controls, a verified person votes once. Governance gains legitimacy.

ONE ACTOR · 40 WALLETS

VOTES COUNTED

64

HELD BY ONE ACTOR63%

Illustrative simulation.

DAO · METAVERSE_ACCESS

Doors that open on proof

The 3D hub already gates The Source for Ring holders. Spaces can open on proof: a studio for verified artists, a club for regular athletes.

RING
OPEN
ARTIST
OPEN
ATHLETE
LOCKED

DAO · INITIATIVE_SELECTION

Fund proven talent

Project leads prove their track record (jobs delivered, audience, sporting or artistic consistency) instead of just declaring it.

DECLAREDI have 10k listeners
PROVEN12k monthly listeners · 18 months

Beyond the DAO

Each verifier gets exactly the answer to its question, and nothing more.

AIRDROPS

Web3 projects

ASKS

Unique person, active on 3+ services?

→ TRUE

Never sees: which wallets, which accounts

FREELANCE

Platforms, clients

ASKS

100+ jobs delivered, rated 4.8+?

→ TRUE

Never sees: clients, rates, messages

INCOME

Landlords, lenders

ASKS

Income above 3× the rent?

→ TRUE

Never sees: exact amount, every transaction

COMMUNITIES

Clubs, Discord, events

ASKS

Climbs at least twice a month?

→ TRUE

Never sees: gym, schedule, location

HIRING

Companies

ASKS

Shipped Rust code in the last 12 months?

→ TRUE

Never sees: private repos, employer

Example questions, for illustration.

06 // POSITIONING

Not who you are.
What you did.

Legal identity is getting its standard. Proven reputation does not have one yet. That is the empty corner Smart-SSI fills, as self-sovereign identity for what you did.

THAT YOU EXISTWHAT YOU DID →WHAT IS PROVENRAW DATAREADABLE CLAIM ↑EU WALLET (eIDAS 2.0)WORLD IDHUMAN PASSPORTRECLAIM PROTOCOLSMART-SSI

Chrome DAO's reading of the landscape. Tap or hover a point.

SMART-SSI

PROVES

What you did, as readable claims

HOW

Own open-source zkTLS + AI interpretation + attestations on Solana

ROLE

The layer that turns data proofs into an identity humans and apps can read.

W3C standards (DID, Verifiable Credentials) are followed, keeping the door open to the European wallet.

07 // ECONOMICS_&_GOVERNANCE

A public good.
No token. No raise.

Auctions fund the protocol, the protocol strengthens the DAO’s governance, and verifier revenue feeds the treasury.

VERIFIER FEESFREEFOR USERSCHROME AUCTION1 Chrome at a time · SolanaDAO TREASURYfunds the initiativesSMART-SSIdev · audits · infraGOVERNANCEone person, one vote

CHROME_HOLDERS_VOTE_ON

  1. 01Which data sources come first
  2. 02Issuance rules: thresholds, validity
  3. 03Who joins the attestor network
  4. 04How the initiative’s budget is spent

USERS

FREE

VERIFIERS

PAY PER CHECK OR SUBSCRIBE

REVENUE

BACK TO TREASURY

08 // ROADMAP

Four phases.
Each one voted.

The DAO approves every phase before the next one starts.

  1. 1 NOW

    PHASE_1

    PROOF OF CONCEPT

    • ›DID on Solana
    • ›First source: Strava or GitHub
    • ›DAO-run zkTLS attestor, open source
    • ›First attestations for DAO members
  2. 2GATE · DAO VOTE

    PHASE_2

    INTERNAL USES

    • ›Anti-sybil voting
    • ›Proof-gated Metaverse access
    • ›5 to 10 supported sources
  3. 3GATE · DAO VOTE

    PHASE_3

    OPENING UP

    • ›Public SDK for verifiers
    • ›First paying partners
    • ›Full security audit
  4. 4GATE · DAO VOTE

    PHASE_4

    DECENTRALIZATION

    • ›Network of independent attestors
    • ›Interpretation in a TEE
    • ›Interop with the EU wallet
$ cat KNOWN_LIMITS.md

! SOURCE_DEPENDENCY

If a site changes its interface or blocks access, that source has to be adapted.

! RESIDUAL_TRUST

Until interpretation is proven cryptographically, the issuer stays a trusted party, held in check by transparency and governance.

! ADOPTION

An attestation is only worth something if verifiers accept it. That is why the first uses are inside the DAO.

! LEGAL_FRAMEWORK

The status of attestations and their fit with the GDPR must be validated before opening to third parties.

09 // FOR_BUILDERS

One public schema.
Zero raw data.

Attestations live on the Solana Attestation Service, the shared standard for credentials on Solana. Only the proof hash is kept, for later audits; the data itself is never stored.

sas_attestation.jsonPHASE_1 SCHEMA
{
  "credential": "<Smart-SSI credential>",ISSUER  "schema": "runner.regular v1",WHAT  "nonce": "<user wallet>",WHO  "signer": "<issuer key>",  "expiry": "2027-10-05",EXPIRES  "data": {    "since": "2024-09",    "frequency_per_week": 3,    "source": "strava",FROM    "proof_ref": "<hash of the zkTLS proof>",AUDIT    "model_version": "<hash of the rules>",TRACE    "issued_at": "2026-10-05"  }}

VERIFY_ON_SOLANA

  • The zkTLS proof is checked off-chain by the issuer. Only its hash goes on-chain.
  • Verifiers check the account, the Smart-SSI credential, the schema, the signer and the expiry.
  • Revoking closes the account. The DAO pays the accounts, so users need no SOL.
  • Same standard as other Solana issuers (KYC, work, gaming): verifiers can combine them.
Solana Attestation Servicedid:solTLSNotary (self-hosted)RustNo custom on-chain program

10 // FAQ

Smart-SSI,
questions answered.

What Smart-SSI is, how zkTLS proofs become attestations on Solana, and how to verify a badge.

What is Smart-SSI?

Smart-SSI (The Smart Self-Sovereign Identity) is an open-source self-sovereign identity protocol by Chrome DAO. It lets you prove facts about your online activity, such as how long you have been coding on GitHub, without exposing your data and without depending on a platform. Proofs become attestations on Solana that anyone can verify and that you can revoke at any time.

How does Smart-SSI work?

Smart-SSI works in three layers. Proof: with zkTLS, your phone shows that data really comes from a real service, without handing over any password or token. Interpretation: a public, versioned rule turns the proven facts into a simple, dated claim, always derived facts, never personality traits. Attestation: the claim is signed and recorded on the Solana Attestation Service, where any app can check it.

What is zkTLS, and which implementation does Smart-SSI use?

zkTLS lets you prove that a response really came from a website over its normal encrypted (TLS) connection, while revealing only the part you choose. You log in to the service as usual; an attestor watches the encrypted exchange without seeing its content, and you generate a proof that the server's response contains the data. Smart-SSI uses TLSNotary, self-hosted, with an attestor run by Chrome DAO on open-source code.

Is Smart-SSI built on Solana?

Yes. Attestations are recorded on the Solana Attestation Service, the shared standard for credentials on Solana, and bound to a decentralized identifier (did:sol). Smart-SSI uses no custom on-chain program. The prototype runs today on Solana devnet; mainnet comes only after a security audit and a DAO vote.

What data does Smart-SSI put on-chain?

Only the claim: what it says, its date, its source, the issuer's signature, its expiry and a hash of the zkTLS proof kept for later audits. Login credentials, raw data and activity history never leave your phone, and the raw response never goes on-chain.

What can I prove with Smart-SSI today?

The prototype supports a first source, GitHub: a developer badge showing since when you have been coding, your activity in the last 12 months, the projects you contributed to and your languages. Chrome DAO issues one badge per GitHub account; proving it again on another phone closes the older one. More sources are planned on the roadmap, chosen by DAO vote.

How do I verify a Smart-SSI badge?

The holder shows the badge as a QR code. Scan it with your phone camera and it opens chromedao.xyz/verify, which answers Yes or No in one sentence, with nothing to install. The page reads the record live from Solana in your browser, without asking Chrome DAO's servers, and checks that it is signed by Chrome DAO, not revoked, not expired, and shown from the holder's phone within the last few minutes.

Can I delete or revoke a Smart-SSI attestation?

Yes. You choose which proofs to generate, approve each claim before it is issued, decide who sees it, and can revoke it at any time. Revoking closes the attestation account: the past record is not erased from the chain, but the attestation becomes invalid for every verifier.

How is Smart-SSI different from World ID, Human Passport or Reclaim Protocol?

In Chrome DAO's reading of the landscape: World ID proves human uniqueness with a biometric iris scan, while Smart-SSI uses no biometrics and proves far more than "I am human". Human Passport gives a humanity score from connected accounts; Smart-SSI proves what the activity contains. Reclaim Protocol provides raw Web2 data through hosted zkTLS; Smart-SSI runs its own open-source zkTLS layer and adds interpretation and identity. The EU digital identity wallet (eIDAS 2.0) covers legal identity and is complementary.

Is Smart-SSI free? Is there a token?

Smart-SSI is free for users and has no token and no fundraising. It is a public good funded by Chrome DAO auction proceeds. Chrome DAO pays for the Solana accounts, so users need no SOL. Verifiers are planned to pay per check or by subscription, with that revenue going back to the DAO treasury.

Who runs and governs Smart-SSI?

Smart-SSI is a Chrome DAO initiative, open source and governed by Chrome holders. Holders vote on which data sources come first, the issuance rules, who joins the attestor network and how the budget is spent. Today Chrome DAO runs the single zkTLS attestor; the roadmap moves to several independent attestors, then a DAO-selected network, with each phase approved by a DAO vote.

When did Smart-SSI start, and where can I read the white paper?

Research started in 2023, with early proofs of concept on Reclaim Protocol; the prototype now runs on TLSNotary. The white paper is on GitHub in English and French (github.com/chromedao/smart-ssi-paper), and the prototype code is at github.com/chromedao/smart-ssi.

[END_OF_TRANSMISSION]

Your reputation,
proven. Portable. Yours.

Read the full white paper, follow the build on GitHub, or hold a Chrome to vote on what Smart-SSI proves first.