Last verified 2026-08-26 against the protocol's current economics.

Built to run on any chain

Most of what makes this protocol work was never Solana-specific. The trading engine, the autonomous risk engine, the integrity system that watches for coordinated abuse, and the dozens of scheduled jobs that keep every firm honest — none of them import a Solana library. The only Solana-specific part of DecentralProp is the money layer: five on-chain programs that hold treasuries, price tokens, and settle evaluations. Everything else is chain-shaped software wearing a Solana costume, and a costume can change.

The five programs are a plugin, not the foundation

The protocol's architecture separates "how a firm runs" from "which chain a firm's money lives on." A firm deploys against a chain adapter — one object that knows how to deploy a treasury, price an evaluation, settle a result, and deliver a payout on its specific chain. Solana's adapter is the original five programs, wrapped rather than rewritten. A second chain's adapter is a new implementation of the same contract. Nothing above that line — , the risk engine, the integrity system, the keeper fleet — has to know or care which one it's talking to.

DecentralChain: proven, not promised

DecentralChain is the first chain to run this pattern besides Solana, and the proof is a real one. On DecentralChain's actual mainnet, using real money: a firm deployed, an evaluation was purchased against it, the evaluation settled, and the payout delivered through the same multi-way stakeholder split the protocol runs on Solana. Every step was independently checked against DecentralChain's own chain state afterward, not just read back from the tool that ran it. This is the first time DecentralProp's core loop has ever completed on a chain other than Solana.

The hardest part to port, and what it proved

The interesting test of a chain adapter is not whether transactions go through. It is whether the protocol's guarantees survive the trip.

The load-bearing one is custody: the firm treasuries, escrows and reserves described in On-chain architecture & trust are accounts that hold money and that nobody holds a key to. On Solana that comes from address mathematics, an address built so no private key can produce it. DecentralChain has no such concept, so the same guarantee had to be reached another way: a rule attached to the account itself that refuses every transaction the account tries to sign, permanently. A key exists there, and it is powerless, because the network declines everything it signs. Money moves only through the contract's own logic, which is the property that mattered.

There is a wrinkle that goes in DecentralChain's favour. On Solana a keyless account is still governed by a program, and programs can be upgraded, so permanence takes separate deliberate work. On DecentralChain, changing a contract requires a transaction sent from that contract's own account, and a contract that refuses all its own transactions can therefore never be changed. Keyless and permanent arrive together.

Permanence is a serious commitment, since a mistake in a frozen contract stays frozen too. So the deployment splits the job: the vault that holds funds is deliberately simple and permanently locked, exposing exactly one operation that only the main contract may call, while all the complicated rules live in a separate contract that can still be corrected under a multi-signature approval. Irreversibility applies only to the part small enough to check by reading it.

Two chains with nothing in common, one guarantee, reached two different ways. That is the clearest evidence the line between the protocol and the chain was drawn in the right place.

Why this matters more than one extra chain

The expensive part of running on a new chain is porting the five programs — everything a firm's treasury, rules, and settlement actually depend on. That cost is paid once per chain and never again: the risk engine, the integrity system, and every keeper that already governs a firm on Solana govern a firm on any chain the same way, unmodified, the day that chain's adapter lands. A protocol that has to be rebuilt for every chain it touches is not really portable. One that only has to re-plug its money layer is.

See On-chain architecture & trust for how the five programs work, and What's live today for the protocol's evidence bar and where each chain stands against it.