Ownership is Cryptographic
A Sahyadri account is not a database row. It is a public key, and its balance can be moved only by a transaction signed with the corresponding private key. No institution can move it, freeze it, or recover it. There is no admin override, no court order a node will honor, no "forgot password" flow that can substitute for the key.
The signature scheme is ML-DSA (Dilithium), a post-quantum algorithm. This means the security of your balance does not depend on the assumption that classical computers cannot break discrete logarithms — the assumption that Shor's algorithm falsifies. It depends on the MLWE problem, which no quantum algorithm solves in polynomial time.
The practical consequence: if you lose your key, you lose your funds. There is no recovery authority. This is not a UX flaw — it is the property that makes the system sovereign. Any mechanism that could recover your key could also take it. Sahyadri chooses to have neither.
Either It Happened, or It Didn't
A payment is a state transition. Either the sender's balance decreases and the recipient's increases, or neither does. There is no intermediate state where money is "in transit." This is what "atomic" means — the transaction either commits fully or is rejected entirely, and the choice is made by the same deterministic function on every node.
σ otherwise }
Two additional properties: the balance check and the state update are the same operation, and the transition is verified by every node on every block. There is no "charge pending," no "hold on funds," no "settlement delay." A payment either produced a new state or it did not — and the network agrees on which, deterministically.
Finality is a threshold, not a wait. Once the block containing your transaction has accumulated enough cumulative work, reversal is impossible for any rational adversary. The probability of reversal decays geometrically with depth — a handful of blocks makes it negligible.
A Fee That Doesn't Depend on Amount
The transaction fee is a small, fixed amount expressed in kana (10−8 CSM). It does not depend on the amount being transferred. Sending 1 kana costs the same as sending 1 million CSM. There is no auction, no priority fee market, no bidding war during congestion.
The fee exists for two reasons: to prevent spam (a flood of free transactions would overwhelm the mempool) and to compensate the miner who includes the transaction. It is not a revenue stream for any party — no foundation, no treasury, no governance committee receives a share. The entire fee goes to the miner.
There is no second fee hidden in the protocol. There is no gas, no priority tip, no MEV extraction built into the state transition. What you see in the transaction is what you pay — and the protocol guarantees that no other amount can be deducted by any mechanism the protocol defines.
The Network Never Sleeps
There are no banking hours, no weekend closures, no maintenance windows, no holidays. The network is a distributed set of nodes running the same transition function. As long as at least one honest miner is active, blocks are produced — and as long as at least one honest node is running, anyone can verify them.
Where N is the number of independent nodes and phonest is the probability that any one node is live at a given moment. As N grows, the network's uptime approaches 1 — even if individual nodes fail frequently. This is a structural property of decentralization, not a promise from any operator.
Cross-border payments are the same as local ones. No foreign exchange intermediary, no correspondent banking, no clearing delay. The recipient's address is the only routing information needed, and it works the same way whether the recipient is across the street or across an ocean.
Sovereign by Construction
Two columns. On the left, what the protocol guarantees is yours. On the right, what the protocol removes entirely — because a mechanism that could provide it could also take it.
- ✓Your private keys — never leave your device
- ✓The timing of your transactions
- ✓The amount you send (any fraction, any size)
- ✓Who receives your funds (any valid address)
- ✓Whether to run a node and verify independently
- ×Account recovery (if you lose the key, funds are lost)
- ×Chargebacks (confirmed transactions are final)
- ×Reversal by any third party, ever
- ×Custodial intermediaries (no one holds your funds but you)
- ×Admin keys or emergency overrides
Every item on the right is a consequence of the design, not a limitation the protocol failed to solve. Recovery requires an authority; the network has none. Chargebacks require a trusted arbiter; the network has none. Reversibility requires a governing committee; the network has none. To gain sovereignty, you give up the mechanisms that would also give others sovereignty over you.