Rubix Protocol

The Rubix Protocol

Rubix is a token-based distributed graph ledger designed for direct settlement, parallel execution and scalable multi-asset transactions. Instead of recording every transaction in a single global blockchain, Rubix maintains independent token chains that connect to form a directed acyclic graph.

Technical whitepaper (opens in a new tab)Build on Rubix

A

Architecture

01

Directed Acyclic Graph

Independent Chains. Connected History.

Every token in Rubix maintains its own chain of transactions. When tokens interact, their individual chains establish verifiable relationships, collectively forming a directed acyclic graph.

This structure removes the need for every transaction to be added to a single global block. Independent token chains can progress concurrently while preserving an immutable record of ownership, movement and interaction.

TIMEFORWARD ONLY

02

Token-Based Ledger

Every Asset Maintains Its Own History.

Rubix uses a token-based ledger rather than an account-based ledger. Value is represented through individually identifiable tokens, each carrying its complete transaction history.

A transaction updates the chains of the participating tokens instead of changing balances in a shared global account state. This makes every unit of value independently traceable and verifiable.

ACCOUNT LEDGERONE BALANCE, OVERWRITTENTOKEN LEDGEREVERY STATE KEPT

03

Multi-Asset Transactions

Multiple Assets. One Transaction.

Rubix transactions can involve multiple tokens and asset types within a single execution.

Assets can be executed together without depending on separate settlement processes. The transaction is completed only when all participating token chains are successfully validated and updated.

ONE TRANSACTION

04

Proof-of-Pledge Consensus

Distributed Validation Without Competitive Mining.

Rubix uses Proof-of-Pledge to validate transactions. For every transaction, an independently selected group of validators pledges RBT equal in value to the transaction being verified, giving them a direct economic interest in its correctness. This independent pledging model creates economic security: validators risk losing value comparable to the transaction they validate, making dishonest behaviour economically irrational through the threat of slashing

Because consensus is formed independently at the transaction level, unrelated transactions can be validated simultaneously by different validator groups without waiting for global block production.

TRANSACTIONEACH PLEDGE, EQUAL IN VALUE TO THE TRANSACTIONINDEPENDENTLY SELECTED

05

Subnetworks

Independent Networks Built on Rubix.

Rubix subnetworks allow organisations, ecosystems and applications to operate dedicated networks while retaining the core protocol’s token-chain architecture.

Each subnetwork can define its own participation rules, asset models, governance policies and validator requirements. Subnetworks can remain operationally independent while interacting with the wider Rubix ecosystem when required.

SUBNETWORK ASUBNETWORK BSUBNETWORK CRUBIX PROTOCOLOWN RULES, OWN VALIDATORS

06

WASM Smart Contracts

Familiar Languages. Faster to Ship.

Rubix supports WebAssembly-based smart contracts, enabling developers to build applications using languages such as Rust, Go, C and C++. Contracts execute within controlled environments and interact directly with Rubix tokens and token chains.

This helps devlopement teams to ship and patch faster, draw from a wider contributor community and transform existing Web2 codebases into Web3 applications more easily.

RUSTGOCC++WASMEXECUTES AGAINST TOKEN CHAINSFAMILIAR LANGUAGES

B

Economics

01

Fixed-Cap RBT Supply

A Finite Native Asset.

RBT is the native token of the Rubix network. Its total supply is permanently capped at 51.4 million RBT.

RBT is used for transferring value, pledging by validators and participating in the network economy. The fixed supply establishes predictable scarcity without continuous inflation through unrestricted token issuance.

51.4MCAPTOTAL SUPPLYNO FURTHER ISSUANCE

02

Mining and Network Participation

Earn Through Useful Network Work.

Rubix mining is based on network participation rather than computational competition. Participants contribute by validating transactions and supporting network operation. Validators pledge RBT, maintain the required network infrastructure and receive mining opportunities based on the protocol’s eligibility and selection rules. This model replaces energy-intensive hash competition with useful transaction validation.

As the network grows, validators must contribute more validation work to mine a full RBT. The number of RBT available at each mining level, along with the validator credits earned for participation, reduces over time. This creates a progressively more demanding mining model in which rewards are tied to useful network activity, replacing energy-intensive hash competition with sustained transaction validation.

VALIDATION WORK REQUIREDMINES 1 RBTLEVEL 1LEVEL 2LEVEL 3LEVEL 4LEVEL 5

C

Benefits

01

Instant Finality

Transactions settle as soon as transaction-level consensus is reached, without waiting for global block confirmations.

02

Zero Gas Fees

Rubix removes gas bidding and transaction fees, keeping network usage predictable.

03

Infinite Software Throughput

Independent token chains process transactions in parallel, allowing throughput to scale with network participation.

04

Fixed CAPEX and OPEX

Infrastructure and operating costs remain predictable as transaction volumes grow.

05

Advanced Security

Value-backed pledging, slashing, formally proved smart contract languages to protect your assets.

The network today

What we can show, rather than assert.

51.4MMax token supply
2,847,171Transactions processed
18,422Active identities
1,204Validators
4Named implementations
UnavailableNetwork availability

Demonstration values. No approved Explorer data contract yet.