Three Facts
Sahyadri can be described in three sentences. Each is a fact about the protocol, not a mission statement.
A state transition system — every block is a deterministic function of the previous state and the current block. Given the same inputs, every node computes the same outputs.
An ordering algorithm — the DAG of blocks is converted into a canonical total order by Ashwa Consensus. Two honest nodes with the same view produce the same order.
A fixed monetary rule — the supply cap is the limit of the emission series, not a policy. No governance, treasury, or committee can change it.
Six Absences
What Sahyadri does not have is as important as what it does. Each absence is a design decision, not an oversight. Adding any of them would require adding an authority — which is the entire thing the protocol exists to remove.
No Governance
There is no voting mechanism. CSM holders do not vote on protocol changes, parameter adjustments, or fund allocations. The rules were fixed at genesis and cannot be changed by any vote.
No Treasury
There is no foundation reserve, no development fund, no ecosystem pool. The protocol has no funds to spend. Any project funded by "the Sahyadri treasury" is not funded by the protocol.
No Team Allocation
The author of the protocol holds no CSM that was not mined. There is no vesting schedule, no advisor pool, no founder reserve, no investor tranche.
No Account Recovery
If you lose your private key, your balance is lost. There is no recovery service, no admin override, no support ticket that can restore access. This is a property, not a bug.
No Reversibility
A confirmed transaction is final. No court order, no service provider, no foundation can reverse it. A blockchain without reversibility is a blockchain without a censor.
No Staking or Yield
CSM cannot be staked. There are no validators, no slashing, no yield. Mining is the only mechanism by which new CSM is produced.
Three Independent Bounds
Security on Sahyadri is not a single mechanism. It is the intersection of three independent mathematical properties, each of which would have to fail for the system to fail. Each is stated as a quantitative bound, not a qualitative claim.
Signature Security
Every transaction is signed with ML-DSA (Dilithium). Forgery requires solving MLWE, which no known classical or quantum algorithm does in polynomial time.
Consensus Security
Reversing a finalized block requires out-mining the honest network. Cost grows linearly with depth; probability decays geometrically.
State Integrity
Every state is a Merkle root. Any change to any leaf changes the root. Verification is deterministic — a proof either checks or it does not.
None of these bounds depends on trusting any party. Each is a mathematical consequence of the design. An adversary would need to break all three simultaneously to compromise the network — and each one is itself at the edge of known cryptographic hardness.
A Cap That Cannot be Lifted
In most monetary systems, the supply cap is a policy. A policy can be changed by whoever has authority over it. In Sahyadri, the cap is a theorem — a mathematical limit of the emission series. There is no authority to change a theorem.
At every block height, the cumulative minted supply is strictly below the cap. No block can mint more than the equation permits. No collection of blocks can mint more than the sum. Any block whose coinbase exceeds the equation is rejected by every honest node, because the transition function evaluates to invalid.
No governance vote, no foundation decision, no emergency resolution can change the emission series. The rules were fixed at genesis, and the only way to change them is to launch a different network. This is why Sahyadri is described as "rule-based" rather than "governance-based" — the rules do not submit to governance, because governance is what the protocol exists to replace.