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

Sahyadri Resources

Every protocol claim has a source. This page indexes the documents, specifications, and code that together define Sahyadri — with honest state markers for what is published and what is still being written.

01 · Documentation Index

Seven Reference Documents

The Sahyadri protocol is documented in seven distinct references. Each serves a different purpose: the specification is the formal definition, the whitepaper is the mathematical justification, the source is the ground truth. Read them together — no single one is complete on its own.

I

Protocol Specification

Published

The formal specification of the Sahyadri protocol: state transition function, Account + Crest state model, Ashwa Consensus ordering algorithm, and the exact rules that every node evaluates.

Open →
II

Whitepaper

Published

The complete mathematical description of the protocol with formal security arguments: emission series, ML-DSA signature bounds, deterministic ordering proof, and finality threshold derivation.

Open →
III

Node Source Code

Public

The reference implementation. Every claim in the protocol spec corresponds to code that runs on every node. When the spec and the source disagree, the source is ground truth.

Open →
IV

Vocabulary

Published

A precise glossary of every term used across the protocol, whitepaper, and documentation. Each definition gives the specific meaning the term carries in Sahyadri, not its generic blockchain meaning.

Open →
V

Architecture Documentation

In Progress

Deep dives into specific subsystems: Sync-Wave state synchronization, state-proof construction, SMT commitment scheme, and SahyadriX memory-hard PoW internals.

VI

Security Model

In Progress

Formal treatment of the adversarial bounds: reorg probability as a function of depth, forgery probability under MLWE, and the reduction from protocol security to standard cryptographic assumptions.

VII

Research Notes

Living Document

Open problems and design explorations: recursive proof compaction optimizations, alternative parameterizations of SahyadriX, and analyses of decentralization metrics over time.

02 · How to Read These

Three Reading Paths

Different readers come with different questions. The three paths below cover the three ways this documentation set is meant to be used. There is no required order — but each path uses the documents differently.

The Verifier

For users who want to check rather than trust

Vocabulary → Protocol → Node Source

Start with the glossary to fix terms, then read the specification, then audit the implementation. Any disagreement between spec and source is a bug.

The Builder

For developers integrating the protocol

Protocol → Architecture → Node Source

Understand the state transition function first, then the RPC surface, then the specific subsystems you will call.

The Mathematician

For those evaluating the security arguments

Whitepaper → Security Model → Research Notes

The whitepaper provides the proofs; the security model formalizes the bounds; the research notes identify open problems.

03 · The Verification Principle

Documentation That Can Be Checked

Every claim in this documentation set is falsifiable. A protocol spec claim is falsifiable by an implementation that disagrees. A security claim is falsifiable by a proof of the underlying hardness assumption. A performance claim is falsifiable by a benchmark run on public data. There is no claim in these documents that requires believing an author — the claims are checkable, and the checkability is the point.

spec_claim ⟺ impl_behavior   (or the spec is wrong)

When a claim in the specification disagrees with the source code, there is exactly one correct resolution: the source is correct and the specification must be updated, because the source is what runs and the specification is what describes. This is not a concession to pragmatism — it is the definition of what a specification is for.

authoritative = source_code   >   specification   >   whitepaper

A whitepaper that disagrees with the specification is a whitepaper that needs revision. A specification that disagrees with the source code is a specification that needs revision. The source code is the only artifact that cannot be wrong about what the network does — because it is what the network does.

04 · What is Not Here

A Documentation Set is Defined by Its Absences

What is not in these documents is as important as what is. The following categories are intentionally absent — not because they are not useful, but because they would contradict the nature of the protocol.

No roadmap with dates

The protocol is not developed on a schedule. It is developed correctly, and released when it works. Timelines published by other projects are marketing artifacts, not engineering ones.

No team page with faces

The protocol does not depend on any team. Names are provided for attribution, not for trust. You are not asked to trust a person — you are asked to read the mathematics.

No token allocation table

There is no allocation to publish. No premine, no founder reserve, no foundation treasury, no advisor pool. The emission is entirely through mining.

No list of investors

There are no investors. There is nothing to invest in. The protocol has no equity, no token sale, no ownership structure that could accept investment.

No partnership announcements

A partnership with a company is a promise made by a company. Sahyadri is not a company, so it cannot make such promises. Every interaction is a cryptographic interaction, not a business relationship.

Resources are not documentation of authority. They are documentation of mathematics — and mathematics does not require interpretation, only verification.
— Sahyadri