Zenpower Blockchain Master Plan

Last updated 25 Jan 2026, 13:49

Unified roadmap for all blockchain components toward full protocol sovereignty. Vision: "If Zenpower HQ vanishes tomorrow, the protocol continues."

Overview

The Zenpower blockchain ecosystem follows a Five-Layer Decentralization Architecture:

┌─────────────────────────────────────────────────────────────────┐
│  Layer 4: CLIENT        IPFS/Arweave frontends, ENS discovery   │
│                         Anyone can host, no permission needed   │
├─────────────────────────────────────────────────────────────────┤
│  Layer 3: BRIDGE        Threshold TSS (5-of-9 validators)       │
│                         Chainlink CCIP backup path              │
├─────────────────────────────────────────────────────────────────┤
│  Layer 2: STATE CHANNELS   Fast MUD gameplay, 10-min anchors    │
│                            24-hour dispute resolution           │
├─────────────────────────────────────────────────────────────────┤
│  Layer 1: SMART CONTRACTS  EVM (Base/Arbitrum/ETH)              │
│                            Economy, governance, registries      │
├─────────────────────────────────────────────────────────────────┤
│  Layer 0: SATORI          Bitcoin fork - ultimate settlement    │
│                           21M ZENCOIN, PoW + Proof-of-Play      │
└─────────────────────────────────────────────────────────────────┘

Sovereignty Standard

Property Bitcoin Uniswap Zenpower Target
No servers required Yes Yes Yes
Permissionless Yes Yes Yes
Censorship resistant Yes Yes Yes
Frontend optional Yes Yes Yes
State on-chain Yes Yes Hybrid*

*Hybrid: Core state on-chain, gameplay in state channels for performance

Network Configuration

Testnets

Network Chain ID Purpose Status
Base Sepolia 84532 Punk Contracts testing Active
Satori Testnet 18333 Bitcoin fork testing Q3 2026
PostgreSQL Ledger N/A ZenTropy pre-Satori Production

Mainnets

Network Chain ID Purpose Launch
Base 8453 Punk Contracts Q1 2026
Satori Mainline 28333 ZENCOIN Q3 2026
Satori Playground 28334 ZENPLAY Q3 2026

Component Details

1. Punk Contracts (Identity Layer)

Purpose: Soulbound NFTs for identity and consent management.

Contracts:

  • PunkSeed.sol - ERC-721 soulbound identity token
  • ConsentBeads.sol - ERC-1155 consent tracking tokens

Deployment Status:

Contract Base Sepolia Base Mainnet Status
PunkSeed Not deployed TBD Ready - Quick win
ConsentBeads Not deployed TBD Ready - Quick win

Deploy to Testnet (quick win):

cd /opt/zenpower/apps/punk-contracts
npm install
npx hardhat test  # Run tests first
npx hardhat run scripts/deploy.ts --network base-sepolia
npx hardhat verify --network base-sepolia <ADDRESS>

2. ZenTropy (Gaming Layer)

Purpose: Provably fair gaming with dual-coin rewards.

Architecture:

  • Domain layer: Game logic, quest definitions
  • Application layer: API routers, services
  • Infrastructure layer: PostgreSQL ledger (pre-Satori), Satori RPC (post-launch)

Dual-Coin Economy:

Token Symbol Supply Purpose
ZenDollar ZEN$ Unlimited (minted/burned) Stable daily transactions
ZenCoin ZENCOIN 21,000,000 Governance + savings

Testing:

cd apps/zentropy
pytest tests/ -v
# 440+ tests covering all layers

3. Bitcoin Satori (Layer 0 - Settlement)

Purpose: Bitcoin-derived blockchain for ultimate settlement and hard currency.

Consensus: Progressive PoW + Proof-of-Play

  • RandomX-inspired (memory-hard, ASIC-resistant)
  • Play-weight influences mining difficulty (AFK-resistant)
  • 80% miner / 20% treasury split

Genesis Parameters:

Parameter Mainline (ZENCOIN) Playground (ZENPLAY)
Symbol ZCN ZPL
Total Supply 21,000,000 21,000,000
Block Time 10 minutes 10 minutes
Initial Reward 50 coins 50 coins
Halving Interval 210,000 blocks 210,000 blocks
Treasury Share 20% 30%
Address Prefix Z P
P2P Port 18333 18334
RPC Port 18332 18335

Key Principles:

  • No pre-mine, no ICO, no founder allocation
  • All supply enters through mining
  • Treasury governed by 2-of-3 multisig → 5-of-9 (decentralization goal)
  • Merit-based distribution through quests

4. State Channels (Layer 2 - Fast Gameplay)

Purpose: Instant MUD gameplay with periodic on-chain settlement.

What runs in channels (off-chain, instant):

  • Player position/movement
  • Inventory changes
  • ZEN$ transfers
  • Combat resolution
  • Room messages, discoveries

What anchors on-chain (every 10 minutes):

  • Merkle root of all player states
  • Significant item transfers
  • Level-ups and achievements

Channel Types:

Type Description Settlement
Solo Channel Single player + coordinator witness On demand
Room Channel Multi-player, all sign relevant changes Periodic
Trade Channel Atomic swaps with immediate anchor Instant

Dispute Resolution: 24-hour challenge period, fraud proofs revert to last valid state.

5. Bridge (Layer 3 - Cross-Chain)

Architecture: Threshold TSS (5-of-9 validators)

Satori → EVM (Lock and Mint):

  1. User sends ZENCOIN to bridge multisig on Satori
  2. Validators observe 100 block confirmations
  3. Threshold signature triggers mint of wZEN on EVM

EVM → Satori (Burn and Release):

  1. User burns wZEN on EVM
  2. Validators observe 12+ confirmations
  3. Multisig releases native ZENCOIN on Satori

EVM ↔ EVM: Chainlink CCIP for L2 transfers

6. Client (Layer 4 - Decentralized Frontends)

Distribution:

  • IPFS/Filecoin for static assets
  • ENS (zenpower.eth) → IPFS content hash
  • Arweave for permanent archive

Client Types:

  1. Web Client - IPFS-hosted, connects to user's Satori node
  2. Desktop Client - Electron with embedded light client
  3. Mobile Client - React Native with remote node

7. Additional Contracts

Ready to Deploy (Quick Wins):

Contract Purpose Chain Status
ZenFarming.sol LP reward distribution Arbitrum Ready

Deploy ZenFarming (quick win):

cd /opt/zenpower/contracts
forge script script/DeployTestnetMultichain.s.sol --rpc-url arbitrum-sepolia --broadcast

New Contracts Required:

Contract Purpose Chain
UniverseRegistry.sol On-chain world definition (zones, areas, paths) Base
BlueprintRegistry.sol Item definitions (what CAN exist) Base
StateChannelFactory.sol Channel deployment + dispute resolution Base
StakingVault.sol Economic security (coordinators, validators) Base

Economic Security Stakes:

Role Stake Required Slashing Condition
Coordinator 10,000 ZENCOIN Unavailability, fraud
Bridge Validator 50,000 ZENCOIN Invalid attestation
Governance Proposal 1,000 ZENCOIN Refunded if passes
Player Channel 100 ZENCOIN (optional) Clean close refund

Environment Configuration

Development (.env.development)

# Network selection
BLOCKCHAIN_NETWORK=testnet
PUNK_CONTRACTS_NETWORK=base-sepolia

# Punk Contracts (Base Sepolia)
PUNK_SEED_ADDRESS=
CONSENT_BEADS_ADDRESS=
BASE_SEPOLIA_RPC=https://sepolia.base.org

# ZenTropy (PostgreSQL Ledger)
ZENTROPY_LEDGER_TYPE=postgres
DATABASE_URL=postgresql://zen:zenpassword@localhost:5432/zentropy_test

# Satori (disabled until Q3 2026)
SATORI_ENABLED=false
SATORI_RPC_URL=
SATORI_TESTNET_RPC=

Staging (.env.staging)

# Network selection
BLOCKCHAIN_NETWORK=testnet
PUNK_CONTRACTS_NETWORK=base-sepolia

# Punk Contracts (Base Sepolia)
PUNK_SEED_ADDRESS=<deployed-address>
CONSENT_BEADS_ADDRESS=<deployed-address>
BASE_SEPOLIA_RPC=https://sepolia.base.org

# ZenTropy (PostgreSQL Ledger)
ZENTROPY_LEDGER_TYPE=postgres
DATABASE_URL=postgresql://zen:***@postgres:5432/zentropy_staging

# Satori (testnet when available)
SATORI_ENABLED=false

Production (.env.production)

# Network selection
BLOCKCHAIN_NETWORK=mainnet
PUNK_CONTRACTS_NETWORK=base

# Punk Contracts (Base Mainnet)
PUNK_SEED_ADDRESS=<deployed-address>
CONSENT_BEADS_ADDRESS=<deployed-address>
BASE_RPC=https://mainnet.base.org

# ZenTropy (PostgreSQL → Satori migration)
ZENTROPY_LEDGER_TYPE=postgres  # Switch to 'satori' after launch
DATABASE_URL=postgresql://zen:***@postgres:5432/zentropy

# Satori (Q3 2026)
SATORI_ENABLED=false
SATORI_RPC_URL=http://satori-node:18332

Testnet Faucets

Base Sepolia ETH

Satori Testnet (Q3 2026)

Testing Strategy

Unit Tests

# Punk Contracts
cd apps/punk-contracts && npx hardhat test

# ZenTropy
cd apps/zentropy && pytest tests/unit/ -v

# SIWE Auth
cd apps/api && pytest tests/test_wallet_auth*.py -v

Integration Tests

# Full blockchain flow (testnet)
PYTHONPATH=. pytest tools/tests/e2e/test_blockchain_integration.py -v

# Punk Seed minting flow
PYTHONPATH=. pytest tools/tests/e2e/test_punk_seed_flow.py -v

Testnet Deployment Verification

# Verify Punk Contracts deployment
npx hardhat verify --network base-sepolia <CONTRACT_ADDRESS>

# Check contract state
npx hardhat run scripts/verify-deployment.ts --network base-sepolia

Migration Plan: Centralized → Decentralized

Phase 1: Foundation (Q1-Q2 2026)

  • Deploy UniverseRegistry, BlueprintRegistry to Base Sepolia
  • Implement solo channel protocol
  • Build coordinator service
  • Run channels in shadow mode parallel to PostgreSQL

Phase 2: Satori Launch (Q3 2026)

  • Fork Bitcoin Core with ProgPoW + play-weight
  • Genesis block with 10+ community nodes
  • Bridge development (TSS + SPV proofs)
  • Security audit of all contracts

Phase 3: Full Decentralization (Q4 2026+)

  • Satori mainnet genesis
  • Bridge activation (ZENCOIN ↔ wZEN)
  • PostgreSQL → chain migration tool
  • DAO governance transition
  • Open source all components
  • IPFS frontend deployment
  • ENS zenpower.eth → IPFS

Success Criteria

When complete, Zenpower will:

  1. Run without any Zenpower-operated servers (anyone can run nodes)
  2. Survive team disappearance (DAO continues autonomously)
  3. Resist government shutdown (distributed globally)
  4. Provide instant gameplay (state channels)
  5. Guarantee asset ownership (on-chain settlement)
  6. Enable trustless trading (DEX integration)

Security Considerations

Smart Contract Security

  • OpenZeppelin contracts v5.0
  • Reentrancy guards on all external calls
  • Access control with role-based permissions
  • Pausable functionality for emergencies

Key Management

  • Hardware wallets for deployment keys
  • Multisig for treasury operations
  • Time-locked admin functions
  • No private keys in version control

Audit Schedule

  • Punk Contracts: Pre-mainnet audit (Q4 2025)
  • ZenTropy: Ongoing security review
  • Satori: Bitcoin Core audit inheritance + custom code review

Monitoring & Observability

Metrics to Track

  • Transaction throughput (TPS)
  • Block production rate
  • Treasury balance
  • Active wallet count
  • Quest completion rate
  • Token distribution curve

Alerting

  • Block production stall > 30 minutes
  • Treasury balance < threshold
  • Smart contract pause events
  • Unusual transaction patterns

Related Documentation

Changelog

Date Change
2026-01-02 Added 5-layer decentralization architecture, state channels, bridge, client layers
2025-12-06 Initial master plan created