Ref Node Live| VIEW RUST CORE ON GITHUB →
INTRODUCTION
CHAIN
RESOURCES
INNOVATION
CONNECT

Web5.

For three decades, identity has been rented from institutions. Every login is a permission slip. Every account can be revoked. Sahyadri removes the intermediary from the definition of identity itself. Your account is a public key. Your authority is the matching private key. Nothing else is required to prove who you are.

What Web5 Requires

Web5 is not a protocol. It is a property: identity that no third party can revoke, silence, or monetize. That property is not obtained by declaration. It is obtained when authentication reduces to a cryptographic equation the user alone can satisfy, and when verification of that equation does not depend on trusting any specific server, committee, or vendor.

The identity is the key

A Sahyadri account is an ML-DSA-65 public key. There is no username, no password, no recovery email. Possession of the private key is the only authenticator. No server issues the account, and no server can revoke it.

Verification is O(1)

A full chain state commits to a single proof of bounded size — ~200 KB serialized, measured, growing sublinearly with tree depth (O(log N)) — regardless of how many transactions the chain has settled. Verification time is 1.5 ms and does not grow with history. Any device that can verify one proof can verify the entire chain.

Why the Architecture Matters

Most systems compromise one of three properties: they trust a coordinator, they leak identity metadata, or their verification cost scales with adoption. Sahyadri was designed so that none of these is a tradeoff.

PoW-DAG consensus

Blocks are produced in parallel and ordered deterministically. There is no leader and no validator committee, so there is no single party who can censor a transaction or exclude a key. Target block time is one second.

Proof-native state

Every state transition is committed to a succinct proof. Light clients do not replay history. A 1.5 ms verification attests to the chain, not a summary of it.

Post-quantum from genesis

Signatures are ML-DSA-65 from block one. There is no migration roadmap because there is nothing to migrate. Keys issued today remain valid under a quantum adversary.

ASIC-resistant PoW

Memory-loop proof-of-work with a 16 MB working set. Mining advantage comes from memory bandwidth, not from custom silicon. The cost of a mining attack scales with general-purpose hardware, not with the size of a fab order.

Decentralized Identifiers

A DID on Sahyadri is not a registration. It is a stable reference to an ML-DSA-65 public key. Resolution returns the key material and its revocation status. Nothing about the identifier requires permission from any authority to exist.

Cryptographic rootdid:sahyadri:csm1s9n2x4f8h3k7m1p6q9r5t2w7y0v3a6b8d1e4g7j0l3n5p8r2s5t8u1v4

No authority issues it. No authority revokes it. There is no password to reset because there is no password. The chain records public keys, not identity documents.

Authentication, Step by Step

The flow below is the actual protocol. None of it requires a third party to be online, honest, or even present.

Step 1
Application Requests Authentication

The application generates a random challenge. It does not ask for a password. There is no password to ask for.

The Architecture of Trust

Deterministic order

Parallel block production, a single total order. No coordinator, no finality gadget layered on top of consensus.

Succinct chain proof

~200 KB. 1.5 ms. Verifiable by any device with reasonable bandwidth. The chain is not summarized — it is proven.

Local-first privacy

Identity keys live on your device. The chain commits to public keys only. Personal data never enters consensus.

What the World Wants

Read any privacy policy. Read the terms of service nobody reads. The demands are always the same, and they are always denied.

01

To own what they create

An account balance is not an IOU from a company. It is a number the user can verify, spend, or withhold without a permission slip.

02

To prove without revealing

To verify age without a birth certificate. To prove a balance without a statement. To demonstrate a credential without submitting the original.

03

To speak without a gate

An identity that cannot be de-platformed, blacklisted, or suspended by a moderator acting under a policy update no one voted for.

04

To leave without losing

The freedom to walk away from a service without abandoning a reputation, a balance, a contact graph, or a history built over a decade.

What the World Does Not Want

✕

Custody dressed as convenience

"Not your keys, not your coins" was correct in 2009 and remains correct. Convenience obtained by surrendering custody is not convenience; it is dependency.

✕

A committee of validators

Twenty nodes selected by a foundation is not decentralization. It is a distributed database with better branding.

✕

Permission as a business model

If an API key can silence a user, the platform is the product and the user is the inventory.

✕

Reset buttons they control

A recovery mechanism that bypasses the private key is a backdoor. It will be used, and it will be used against the person who most needs protection.

On First Principles

Identity is a key.

Not a record. Not a row in a database. Not a claim granted by an authority. A key you generate, and only you can use.

Trust is verified, not granted.

Any claim a system makes about itself is worthless unless it can be checked by someone who does not trust the system. This is the entire argument.

Succinctness is not optional.

A proof that grows with history is a proof that cannot be run on a phone. A chain that cannot be verified by a phone is a chain that cannot be trusted by a person.

Cryptography beats jurisdiction.

A protocol is not a company. It has no headquarters, no employees, no server to subpoena. A user who holds a key is not a user that can be locked out.

Finality is a property, not a promise.

An asset is not "yours" if a reorg, a freeze, or a fork can take it. Ownership ends the moment a third party retains the ability to reverse.

The system must work without its authors.

Any mechanism that requires a specific team, foundation, or developer to remain alive is not a system. It is a service with extra steps.

After Web5

A user creates a key on a device with no network connection. They sign a transaction, prove ownership of a credential, and interact with three services that have never met each other and never will. None of the three asks who they are. All three know they are authorised.

The user moves to a new country. They copy twenty-four words. They continue. No account to migrate, no KYC to repeat, no history to rebuild.

The state they interact with cannot freeze their balance. The service they use cannot delete their identity. The chain they settle on cannot be replayed on another chain, and cannot be reverted by a committee of validators who woke up one morning with a different opinion.

None of this requires a new user to "believe" in anything. It requires only that the equations be true, the proofs be short, and the keys be held by the people whose names are not in any database.

Sahyadri — proof-native layer 1