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.ExchangeexternalDecentralNode OneThe hardware node, with DecentralOSDecentralPropDecentralScansoonCubensis ConnectDecentralAmericaexternal
  • 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 paysDecentralNode OnePlug-in hardware, preloaded with DecentralOS
  • Communitysubmenu
    ChannelsTelegram, X and the reposDCC AirdropAllocated, not yet arrangedGovernanceWho can actually decide anythingBrand kitThe mark, and how to use it
  • Documentation
  • Blog
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
  • DecentralAmerica

Network

  • Blockchain features
  • Finality
  • RIDE
  • Solana bridge
  • Run a node
  • DecentralNode One
  • 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
Blog

Why this blog exists

2 September 2026·DecentralChain·1 min read

DecentralChain has a manual and a set of reference pages that read live from the network. Between them they answer what the protocol does and what the network is doing right now. Neither answers why we changed something, and that is the gap this blog fills.

What goes here

Release notes with reasoning attached. Protocol changes and the argument for them. Post-mortems when something breaks. Occasionally a walkthrough of a part of the system that the manual documents correctly but tersely.

What does not

Price talk, partnership announcements with no shipped code behind them, and roadmap dates we have not earned the right to promise.

Every number here is sourced

The site build runs a check over published copy: any figure that reads like a factual claim has to appear in SOURCE-OF-TRUTH.md with a provenance tag, or the build fails. That check covers these posts too.

It is a crude rule. It cannot tell a sourced fact from an editorial one, only whether a number ever passed through the register. That turns out to be enough, because the failure it exists to catch is a figure reaching a public page without anyone checking where it came from.

If you find a claim here you cannot trace, that is a bug. Tell us and we will fix it or remove it.

  • meta