ECX / SIDECHAINS

Sidechains
on eCash

Each sidechain runs its own software and validates its own rules ECX moves between the mainchain and sidechains through the Drivechain protocol

MAINCHAINSIDECHAIN SOFTWAREECXSlots + escrowsBIP300 / 301ThunderzSideBitNamesBitAssetsTruthcoinPhotonCoinShiftEach sidechain validates its own rules
7 projects to explore

01 / PROJECTS

Explore the sidechain projects

Choose a project to inspect what it changes, how it works, and where to find the code

Payments

Thunder

01 / 07

Payments on a sidechain with larger blocks

Thunder explores higher transaction capacity by changing block limits on a separate chain Its users run Thunder's software; other ECX users do not have to validate its full transaction history

Transaction group 1Transaction group 2Transaction group 3BlockSIDECHAIN TRANSACTIONSOWN BLOCK RULES
Purpose
Send and receive payments on the sidechain
What changes
More block space, on a separate chain
Validation
Run this sidechain’s software

02 / NETWORK REGISTRY

Inspect what is registered

Read activation and proposal observations from the selected network, then follow the record to its source

10activated slots
2pending proposals

Activation and node reachability are different observations A slot in the registry does not establish that its software is running

Betanet
OBSERVED IN MAINCHAIN BLOCKS

Follow the commitments

CommitmentAdditional event
Registered sidechain names Last 12 observed ECX betanet blocks, oldest to newest Select a cell to inspect its block
Registered sidechain401340144015401640174018401940204021402240234024
002BitNames
004BitAssets
008Solana
009Thunder
013Truthcoin
024Elements
098zSide
099Photon
130FreeBank
255Coinshift
Oldest → newestBlock height · last four digits
SLOT 2 / BLOCK 974,024

Sidechain block commitment

The mainchain block records this commitment for the slot registered as BitNames

Commitmentf038c99410d75a62…75594160b1097bcbInspect block 974,024
Registration details+
SlotRegistry nameActivation heightNode observationInspect
002BitNames968,998Not reportedInspect
004BitAssets968,998Not reportedInspect
008Solana970,860Not reportedInspect
009Thunder968,998Not reportedInspect
013Truthcoin968,998Not reportedInspect
024Elements970,715Not reportedInspect
098zSide968,998Not reportedInspect
099Photon968,998Not reportedInspect
130FreeBank969,029Not reportedInspect
255Coinshift968,998Not reportedInspect

Betanet observations Registry names identify declarations; commitments do not establish node availability or sidechain block validity

Saved observation 27 Oct · 18:52 SASTOpen data source

03 / BUILD A SIDECHAIN

From local software
to an activated slot

Build and test the software first A proposal then needs miner inclusion and signalling before it becomes an activated sidechain

01 / Local environment

Run the development stack

Select a development network in BitWindow and choose Full node Run the mainchain node, the enforcer and your sidechain together The enforcer tracks Drivechain state; the sidechain node validates its own rules

  • Select the intended development network
  • Let the mainchain node and enforcer synchronise
  • Start the compatible sidechain software
01 / 06

FOUR DISTINCT STATES

01Saved locally

A proposal in your software

02Included in a block

A miner publishes the proposal

03Miner signalling

ACKs counted under network rules

04Activated

The slot is available on-chain

04 / HOW IT CONNECTS

Three different operations

Deposits, block commitments and withdrawals serve different purposes Inspect them separately

BIP300

Deposit into the sidechain escrow

A mainchain transaction locks ECX for a sidechain The sidechain software observes that deposit and applies its own rules for crediting the destination

01MainchainECX transaction
02BIP300 escrowCoins locked
03SidechainDeposit credited

A mainchain confirmation and a credited sidechain balance are different observations

eCash

ECX / a brief explanation

  1. 01Start from Bitcoin’s ledger.
  2. 02Continue on a separate network.
  3. 03Keep new rules on sidechains.

You don’t have to like every experiment.