DecentralChainDecentralChain
  • Technologysubmenu
    Why DecentralChainWhat sets this chain apartHow the chain worksPublic blocks, public validatorsBlockchain featuresWhat is on, what is being voted onFinalityThe rollback bound, and what is unverifiedRIDEContracts that cannot run foreverFor machinesUnsigned transactions and RIDE in processSolana bridgePhantom and Solflare, mainnet onlyNetwork statusHeight, sync and peers, read live
  • Ecosystemsubmenu
    DCC public saleOpens 26 SeptemberDecentralCoinSupply, allocation and tokenomicsDecentral.ExchangeexternalDecentralPropDecentralScansoonCubensis ConnectDecentralAmericasoon
  • Developerssubmenu
    QuickstartRead, compile and composeREST APIEvery endpoint, no key, no accountSDK packages19 on npm, 5 in the workspaceSigningAuthorising without custodyMCP & AgentsThe chain, and the tools we have builtDecentralChain NodeRun a validator, and what LPoS pays
  • Communitysubmenu
    ChannelsTelegram, X and the reposDCC AirdropAllocated, not yet arrangedGovernanceWho can actually decide anythingBrand kitThe mark, and how to use it
  • Documentation
XGitHub
Start buildingarrow
DecentralChainDecentralChain

An open Layer-1 with Leased Proof of Stake.

Native token: DecentralCoin (DCC)

Fixed supply 100,000,000 DCC
Minted at genesis, never inflated

  • X
  • GitHub
  • Telegram

Build

  • Quickstart
  • REST API
  • SDK packages
  • Signing
  • MCP & Agents
  • Documentation

Ecosystem

  • DCC public sale
  • DecentralCoin
  • Decentral.Exchange
  • DecentralProp
  • DecentralSwap
  • Cubensis Connect

Network

  • Blockchain features
  • Finality
  • RIDE
  • Solana bridge
  • Run a node
  • Network status

Project

  • Community
  • DCC Airdrop
  • Governance
  • Brand kit
  • GitHub
mainnetHeight—Node—read from your browser
© 2026 DecentralChainOperated by DecentralExchange · Cédula Jurídica 3-102-956858
Jacó, Garabito, Costa Rica
TermsPrivacySecurityLicensingdecentralchain.io

Finality

How far the tip
can move back

Finality on DecentralChain has a figure attached to it. The chain carries a configured maximum rollback depth, which is the honest answer to how many confirmations you should wait for. This page states what is verified and marks what is not.
Authoritative tierT0Max rollback depth100 blocksBlock time~60 seconds

On this page

  • The tiers
  • The bound you can rely on
  • HotStuff, and where it runs
  • Do not ask the node for it

The tiers

T0 DeterministicFinality is the authoritative tier. It is what the chain treats as settled, and it is the tier any integration should be written against.

The bound you can rely on

max-rollback-depth is 100 blocks. That is the configured ceiling on how far the tip can be reorganised, and in practice the lag stays well below it. At a block roughly every 60 seconds, 100 blocks is a bound you can put in a runbook rather than a probability you have to reason about.

Note
Sixty seconds is the long-run average. Leased Proof of Stake decides who writes the next block and when, so individual intervals vary. Size a confirmation policy on block count, never on wall-clock time.

HotStuff, and where it runs

A second tier, T2 HotStuff, has been authoritative on testnet since 3 August 2026, on node DecentralChain v1.7.0. The reading taken that week was testnet height 108,096 with hotStuffFinalizedHeight at 107,697.

Not yet verified · Q2

Whether T2 HotStuff is authoritative on mainnet has not been verified, and this page will not claim it either way. The public mainnet node reports DCC v1.3.5, several releases behind the 1.7.0 that carries HotStuff, which is reason enough not to assume it. Until someone confirms it against mainnet, write your integration against T0 and the 100-block bound.

Do not ask the node for it

Careful
GET /blocks/height/finalized does not exist on mainnet. It returns HTTP 400, because the node parses finalized as a block signature. The endpoint comes from a testnet finality spec, and the failure does not look like a missing feature, so it is easy to misread as an outage.

Track confirmations against /blocks/height instead, and compare it to the height your transaction was included at. The API reference lists what does answer.