PUBLIC DATADocumentation
§ sidechains

sidechains

Activated slots, community projects and pending proposals.

MAINNETMainnet observations require a verified endpoint and checkpoint. Alpha and Beta data are kept separate.Network context
Activated sidechains
Unavailable
UNAVAILABLEAwaiting source
No observation
§ metric methodology

Activated sidechains

Distinct activated BIP300 slots, including community sidechains.

Methodology
Official network hub ListSidechains response, sourced from its BIP300 enforcer. Count activated slots separately from pending proposals and node reachability.
Source & scope
enforcer / mainnet
Observed
No observation
Classification
UNAVAILABLE
Refresh
Every 5 minutes
Limitations
Activation does not prove node uptime, transactions, users, locked value or endorsement. Alpha is a retired network. Mainnet requires its own verified source.
History
Snapshots begin after the first successful hub sync.
Community sidechains
Unavailable
UNAVAILABLEAwaiting source
No observation
§ metric methodology

Community sidechains

Activated slots outside the seven reviewed LayerTwo Labs slots.

Methodology
Official network hub ListSidechains response, sourced from its BIP300 enforcer. Count activated slots separately from pending proposals and node reachability.
Source & scope
enforcer / mainnet
Observed
No observation
Classification
UNAVAILABLE
Refresh
Every 5 minutes
Limitations
Activation does not prove node uptime, transactions, users, locked value or endorsement. Alpha is a retired network. Mainnet requires its own verified source.
History
Snapshots begin after the first successful hub sync.
Pending proposals
Unavailable
UNAVAILABLEAwaiting source
No observation
§ metric methodology

Pending proposals

Distinct proposals still awaiting activation; replacement proposals may share an occupied slot.

Methodology
Official network hub ListSidechains response, sourced from its BIP300 enforcer. Count activated slots separately from pending proposals and node reachability.
Source & scope
enforcer / mainnet
Observed
No observation
Classification
UNAVAILABLE
Refresh
Every 5 minutes
Limitations
Activation does not prove node uptime, transactions, users, locked value or endorsement. Alpha is a retired network. Mainnet requires its own verified source.
History
Snapshots begin after the first successful hub sync.
Activated means the slot exists on this network. Node reachability is shown separately. The source is the official network hub’s enforcer.

LayerTwo Labs projects

Seven reviewed project slots · catalog reviewed 2026-09-28

Catalog source

Mainnet sidechain observations are not connected. Project listings remain available below.

ProjectSlotActivationNode observationL2 heightDevelopers · 30d
BitNames ↗Names and identity2UnobservedNo node observation—0
BitAssets ↗Tokens and digital assets4UnobservedNo node observation—0
Thunder ↗High-throughput payments9UnobservedNo node observation—3
Truthcoin ↗Prediction markets13UnobservedNo node observation—5
zSide ↗Private transactions98UnobservedNo node observation——
Photon ↗Post-quantum signatures99UnobservedNo node observation—0
CoinShift ↗Cross-chain swaps255UnobservedNo node observation—1

Developer counts cover the latest 30 days across networks, and may overlap between projects. zSide’s linked repository is outside the reviewed eCash / LayerTwo Labs scope. L1 sync time is the mainchain block seen by the sidechain; it is not an L2 transaction timestamp.

Community sidechains

Additional activated slots outside the seven project slots above

Community slots appear after a successful network hub sync.

New community slots are included automatically on the next sync. Listing a slot does not imply development, operation, audit or endorsement by LayerTwo Labs.

Pending proposals

No proposal observation yet.