ZeckyChainZeckyChain
Phase 1 — Live buildSolana MainnetOP Stack · op-gethEST. 2026

The Zcash
Layer 2.

ZEC, finally in motion. $Zeck launches on Solana, every trading fee feeds a public ZEC reserve, and wrapped ZEC will settle on ZeckyChain — an OP Stack L2 anchored to Zcash.

70 / 10 / 20
fee split, hard-coded
Solana
launch network
OP Stack
op-geth execution
Zcash
state anchoring

The system

01 / 05

Three components. One direction: ZEC on ZeckyChain.

A

$Zeck — launch token

Issued on Solana (Mainnet), traded in SOL. Funds the launch and routes protocol fees. Not the L2 gas token; no claim on the reserve.
B

Public ZEC reserve

70% of protocol fees buy wrapped ZEC, converted to native ZEC in a public Zcash transparent address. Every execution is recorded with a transaction hash.
C

Wrapped ZEC (yZEC)

Redeemable wrapped ZEC on Solana. Trade it on-chain; redeem to native ZEC for shielded privacy; deposit into ZeckyChain at mainnet.

Fee mechanics

02 / 05

Every fee,
split the same way.
Forever.

0
% reserve
0
% burn
0
% ops

The ratio is a constant in the FeeSplitter contract — there is no function to change it. Recipients move only through a public 7-day timelock. Execution is permissionless: anyone can pull the trigger once the threshold is met.

FEES · SOLFEESPLITTER70 / 10 / 20ZEC RESERVEpublic t-addressBUYBACK → BURNincineratorOPERATIONSmultisig70%10%20%

Fig. 01 — live wiring of the FeeSplitter contract

Architecture

03 / 05

OP Stack execution, Zcash anchoring.

01

Execution layer

The OP Stack sequencer and op-geth execution client batch transactions, run contracts, and produce blocks. Fully compatible with existing Solidity tooling, wallets, and explorers.

02

Settlement & assets

ZEC used on ZeckyChain originates from wrapped ZEC locked on Solana. The official bridge handles locking and release.

03

Data availability

Transaction data lives on a data availability network or committee — raw batches are not written to Zcash.

04

Zcash connection

At intervals, the state root, on-chain ZEC supply, and data location are committed into a Zcash transparent transaction for public verification.

Security model, mainnet year one: the bridge is operated by a multisig or threshold signature scheme, with state digests written to Zcash. If Zcash later adds in-protocol proof verification, the bridge will be evaluated for proof-based release.

Rollout

04 / 05

Live in three steps.

01In progress

Now — token & reserve

$Zeck issues on Solana. Fees flow through the 70/10/20 splitter. Reserve data published on this site.

02

Next — wrap & redeem

Redeemable wrapped ZEC: wrap native ZEC into yZEC, redeem back. Issued yZEC never exceeds confirmed reserves.

03

Then — ZeckyChain mainnet

OP Stack mainnet with the official bridge. Deposit wrapped ZEC in, withdraw back out. Balances reconcile on both sides.

Full roadmap & completion criteria →

In plain terms

05 / 05

ZeckyChain is a Zcash Layer 2 built on the OP Stack.

$Zeck is issued on Solana as the project launch token. It is not the L2 gas token and cannot withdraw the reserve.

Trading fees are split 70% / 10% / 20%: 70% buys ZEC into a public reserve, 10% buys back and burns $Zeck, 20% funds operations.

Reserve addresses and execution records are publicly verifiable.

Wrapped ZEC trades on Solana; for privacy, redeem to native ZEC and use shielded transactions.

Once mainnet is live, users can deposit wrapped ZEC into ZeckyChain.

Don't trust.
Verify.

Reserve & recordsContract listEvery address public · every execution hashed