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

Integration Requirements

No exchange listing is currently active. This page documents what an exchange would need to integrate Sahyadri — the API surface, the verification model, and the specific difference between Sahyadri and UTXO-based chains that most exchange backends assume.

01 · The Model Differs

Account + Crest, Not UTXO

Most exchange backends are built for UTXO chains — Bitcoin, Litecoin, and their derivatives. Those systems track coins as discrete objects, and "balance" is the sum of unspent outputs. Sahyadri does not work this way. Balances are per-address state, updated atomically by transactions. There are no outputs to enumerate.

σAccount : Addr → ℕ   (balance per address, not per coin)

The implication for exchange integration: deposit detection is a state query, not a UTXO scan. Withdrawal construction produces a transaction with exactly one input semantic — a signed balance adjustment — not a set of inputs to be selected and signed individually.

deposit(addr, amt)  →  query state at block B  →  check bal[addr]
02 · Finality Before Credit

An Exchange Should Never Credit on Inclusion

A transaction being included in a block does not make it final. It makes it a candidate. Finality requires cumulative work beyond the block. Any exchange that credits a deposit on inclusion alone is exposed to reorg risk. The safe rule: credit only when the block containing the deposit has crossed the exchange's own finality threshold.

credit(deposit) ⟺ final(Bdeposit)   ∧   Verify(path, leaf, Bdeposit.state_root) = ⊤

The two conditions are independent. The first checks that the block cannot be reversed. The second checks that the deposit is actually in the block. Both must hold. An exchange that skips either — credits on inclusion, or credits on a node's word — has no cryptographic guarantee of anything.

How Many Confirmations?

There is no protocol-defined answer. The threshold depends on the exchange's own risk tolerance and the value of the deposit. For small amounts, a shallow threshold suffices. For large amounts, a deeper threshold is rational — because the cost to reverse at that depth exceeds the extractable value by orders of magnitude. Exchanges should compute this threshold themselves rather than copy a number from Bitcoin.

03 · Withdrawals

The Withdrawal is a FlashTransaction

A withdrawal is not a set of inputs to select and sign. It is a single FlashTransaction — a signed intent to move a specific amount to a specific address. The exchange constructs the payload, signs it with the hot wallet key, and broadcasts it. There is no coin selection, no change output, no UTXO bookkeeping.

payload = FLASH_V1 ‖ version ‖ pubkey ‖ recipient ‖ amount ‖ fee ‖ expiry ‖ salt ‖ signature

The salt field is the replay protection. It must be unique per transaction — a repeated salt with the same fields produces an identical transaction ID, which is rejected as duplicate. The expiry field bounds the time window; a withdrawal that is not included before expiry must be re-signed. Exchanges should generate a fresh salt per withdrawal and set expiry conservatively.

salt ~ random(2128)   ∧   expiry > current_daa_score + buffer
04 · What to Monitor

Four Events, Nothing Else

An exchange needs to observe four event types on the network. Anything else is internal to the exchange, not to the protocol. This is smaller than most exchange integration surfaces — because the protocol is smaller.

I

Block Finalization

A block crosses the exchange’s finality threshold. Triggers reconciliation of all deposits in that block.

event: W(B) ≥ threshold
II

Deposit Detection

A transaction to a monitored address appears in a finalized block. Query state at that block, verify the balance delta.

event: Δbal[addr] > 0 ∧ final(B)
III

Withdrawal Inclusion

A broadcast withdrawal appears in any block. Mark as pending inclusion; do not mark as sent until finalization.

event: tx_id ∈ B   (any B)
IV

Chain Tip Update

The canonical tip advances. Used to maintain the local view of the DAG and to detect potential forks.

event: tip_n ≠ tip_{n−1}
05 · Current State

No Listings Currently Active

Sahyadri is not currently listed on any exchange. There is no CSM trading pair, no fiat on-ramp, and no market maker arrangement. Any claim otherwise — from any source — is false. When listings occur, they will be announced through the official Sahyadri channels linked below.

For exchanges and market makers interested in integrating Sahyadri, contact through the official channels. Integration support, node documentation, and technical due diligence materials are available on request. There is no listing fee, no foundation treasury, and no allocation set aside for exchange incentives — any arrangement would be a commercial agreement between the exchange and the network, not a protocol feature.

Official Channels

Warning: Any listing announcement, token sale, or CSM offering that does not originate from the channels above is fraudulent. There is no Sahyadri foundation, no treasury, and no authorized agent who can sell CSM on behalf of the network.

No listing is a security. No announcement is a promise. Verify only what is signed by a key you trust, and trust only keys you have verified.
— Sahyadri