HYBRID-CHAINWallets ↗

NETWORK-SCOPED WALLET AUTHORITY

One wallet model.
Three trust boundaries.

A customer ceremony belongs to exactly one network, one authorization plane, one address namespace, and one evidence history. Availability is published only after every required gate passes.
01 · DEVNETGATES PENDING

CUSTOMER DEVNET

Customer-controlled development wallets exercise the complete authorization, DKG, activation, signing, and public-proof lifecycle without production value.

NETWORK
hybrid-devnet
NATIVE ASSET
DHYBRID
ADDRESS PREFIX
dhyb
ACTIVE WALLETS
0
FRESH SIGNING
0
VALUE AUTHORITY
NOT GRANTED
ENROLLMENT GATESBLOCKED

BLOCKEDREGISTRY UNAVAILABLE

ENROLLMENT REMAINS FAIL-CLOSEDNO NETWORK AUTHORIZATION COMMITMENT
02 · TESTNETGATES PENDING

CUSTOMER TESTNET

Release-candidate wallets will use independent Testnet roots, thyb addresses, THYBRID, and a separately admitted ceremony protocol.

NETWORK
hybrid-testnet
NATIVE ASSET
THYBRID
ADDRESS PREFIX
thyb
ACTIVE WALLETS
0
FRESH SIGNING
0
VALUE AUTHORITY
NOT GRANTED
ENROLLMENT GATESBLOCKED

BLOCKEDREGISTRY UNAVAILABLE

03 · MAINNETSEPARATE PRODUCTION CEREMONY

CUSTOMER MAINNET

Production wallets require a distinct Mainnet launch ceremony and can never be activated by a pre-production feature flag or trust root.

NETWORK
hybrid-mainnet
NATIVE ASSET
HYBRID
ADDRESS PREFIX
hyb
ACTIVE WALLETS
0
FRESH SIGNING
0
VALUE AUTHORITY
NOT GRANTED
ENROLLMENT GATESPROHIBITED
NO PRE-PRODUCTION ENROLLMENT ROUTENO NETWORK AUTHORIZATION COMMITMENT

PROMOTION IS A CEREMONY

Software can advance. Authority cannot leak.

DEVNETEngineering proof

Fast iteration, valueless activation, and reproducible failure paths.

TESTNETRelease proof

Independent roots and operator evidence before release-candidate wallets exist.

MAINNETProduction authority

Separate governance, signer admission, operational acceptance, and value policy.

A network label is never sufficient authorization.PROFILE + ROOTS + PROTOCOL + ACCEPTANCE