Proof Center · Finality
What “settled” means, per network.
Finality is where money goes missing when a product flattens every
chain into one “confirmed”. StoneReason never does. Each answer reports
settlement in the chain's own vocabulary, and says whether depth even means anything
there. NETWORK_KNOWN != PRODUCT_SUPPORTED.
| Network | Family | Final condition | Model | Protocol final | Settles at depth |
|---|---|---|---|---|---|
| Arbitrum One | EVM | L1_CONFIRMED | DERIVED_FROM_L1 | yes | not by depth |
| Avalanche C-Chain | EVM | ACCEPTED | PROTOCOL_CONDITION | yes | not by depth |
| Base | EVM | L1_FINALIZED | DERIVED_FROM_L1 | yes | not by depth |
| BNB Smart Chain | EVM | FINALIZED | PROTOCOL_CONDITION | yes | not by depth |
| Celo | EVM | L1_FINALIZED | DERIVED_FROM_L1 | yes | not by depth |
| Ethereum | EVM | FINALIZED | PROTOCOL_CONDITION | yes | not by depth |
| Polygon PoS | EVM | FINALIZED | PROTOCOL_CONDITION | yes | not by depth |
| Stellar | NATIVE | CLOSED | PROTOCOL_CONDITION | yes | not by depth |
| TON | NATIVE | MASTERCHAIN_COMMITTED | PROTOCOL_CONDITION | yes | not by depth |
| TRON | NATIVE | SOLIDIFIED | PROTOCOL_CONDITION | yes | not by depth |
| XRP Ledger | NATIVE | VALIDATED | PROTOCOL_CONDITION | yes | not by depth |
Generated from the deployment. The final condition is the chain's own code; the model is how it settles.
The TRON differentiator
Finalized on the solidified head, not a block count.
TRON settles when a supermajority of its twenty-seven super representatives has built on a block — a threshold, not a depth. StoneReason reads that solidified head from the chain and finalizes against it, rather than counting confirmations that do not mean settlement here.
BLOCK_COUNT != TRON_PROTOCOL_FINALITY— a count is not the condition.SOLIDITY_RECEIPT_ABSENT != FAILED— not yet solid is not failed.TIME_ELAPSED != FINALIZED— waiting is not settling.
Proven at release 6201f617
with payment pay_e4fd7788..., native finality SOLIDIFIED.
"transaction_height": 64_912_impl,
"solidified_head": 64_935_impl,
"native_finality": "ESTABLISHED",
"mechanism": "TRON_SOLIDIFIED_HEAD",
"distance_is_meaningful": falseThe four settlement models, in words you can act on
Every served network reports one of these. The label is not decoration; it changes what you should do before releasing goods.
Protocol Condition
A block either meets the protocol's finality condition or it does not; waiting longer does not make a block that has met it more final. Depth is not meaningful.
Derived From L1
A rollup. Its sequencer confirms immediately, but that is a promise by the sequencer; the block becomes irreversible only when its batch finalizes on Ethereum, where the guarantee actually lives.
Probabilistic
Probabilistic: a block gets harder to reverse as more are built on it, and never impossible. Any depth you choose is a risk decision, not a guarantee.
Not Applicable
This chain makes no protocol-finality claim, and neither does any answer about it. A depth is named instead.