Seal every stripe.
Hash- and lattice-based signatures form the proposed proof layer for coin launches and treasury records.
Explore the seal ↗
BLACK. WHITE. SHIELDED.
Built different.
By nature.
Quantum-sealed coins. A Zcash bunker.
A whole herd behind you.
QZ / 001 PRIVACY IS AN INSTINCT.
ONE HERD.
THREE LAYERS.
THREE LAYERS.
SLH-DSA + ML-DSAthe quantum seal
ZEC FLOOR + HOLDthe holder bunker
BURN → REDEEMthe exit, on your terms
Ƶ[ THE THESIS ]
Strength in stripes.
Power in the herd.
A launchpad concept built around three instincts: protect the record, grow the bunker, put holders at the heart of it.
Build the bunker.
A share of creator fees flows toward ZEC. One pool for the floor. Another for holders who stay.
Inside the bunker ↗Your herd. Your move.
Stay for the journey, or explore a proportional floor redemption. The proposed exit gives back to the herd.
Follow the flow ↗[ FOLLOW THE STRIPES ]
From first coin.
To shared conviction.
Every layer has a purpose. See how the proposed protocol connects a launch to its ZEC bunker.
Explore the architecture →- 01CREATEYour coin. Your identity.↘
- 02SEALA record of every stripe.↘
- 03BUNKERCreator fees → ZEC reserves.↘
- 04THE HERDHold together. Exit on your terms.Ƶ
Bunker intelligence.
A preview of the protocol dashboard. Explore exposure, treasury mechanics and the layers behind the herd. Figures below are illustrative.
| scheme | rests on | status |
|---|---|---|
| ECDSA | elliptic curve | elliptic curve |
| Ed25519 | elliptic curve | Solana signature |
| Zcash Orchard | elliptic curve | privacy layer |
| SLH-DSA | hash | launch seals |
| lattice seals | lattice | our launch seals |
| ML-KEM | lattice | envelopes |
What guards whathonest FAQ →
[ KNOW YOUR STRIPES ]
The herd has a handbook.
Seals, splits, vaults and exits. Everything behind the interface, explained.
Open the docs ↗tools / exposure checker
Are your stripes showing?
Explore how different address formats expose public keys. This demonstration recognizes formats locally; it does not inspect balances or transaction history.
> scan <address> --demo
Local format demonstration. No address leaves your browser.
> how the stripes work
- Solana: addresses represent public keys.
- Bitcoin: exposure depends on the address type and spending history.
- Ethereum: outgoing signatures can reveal a public key.
- Zcash: shielded transactions are a different privacy model. This demo does not analyze them.
tools / bunker sim
How fast does the bunker fill?
Adjust the assumptions and watch a hypothetical ZEC floor grow. All prices and volumes are illustrative; this is a simulator.
> bunker --inputs
> bunker --project
Assumes constant MC and volume, 60% of fees to the bunker, 0.3% swap cost and 70% eligible supply. Scenario, not a prediction.
launchpad / the herd
Your coin. Your stripes.
The same sealed-coin stack, made for your herd. Set your identity and configure the ZEC bunker. Preview the launch experience below.
> your coin
> preview
DEMO
> the seal behind your stripes
- Made for your herd. Your name, ticker and artwork, in one shareable draft.
- The split stays visible. Explore how the bunker, creator and herd fit together.
- Saved in this browser. Come back to your coin on the board.
- A demo, clearly marked. The receipt is a local checksum, not a cryptographic signature or token.
demo receipt (json)
Your launch preview will appear here.
launchpad / board
Meet the herd.
The home of coins deployed through QZEBRA. No coins have been deployed yet.
tools / seal verifier
Check the stripes.
Paste a QZEBRA demo receipt to check its local checksum. This illustrates the verification flow; it is not a post-quantum seal or proof of ownership.
> verify receipt.json --demo
tools / redeem floor
Leave with your stripes.
Explore a hypothetical burn-to-redeem flow: tokens ÷ supply × ZEC floor, less a 2% fee. No tokens are burned and no funds are transferred.
> redeem --simulation
> vault · illustrative
- supply
- 1,000,000,000
- redemption fee
- 2%
- network
- none — local demo
- wallet connection
- not needed
> waiting for a simulation…
project / token
$QZEBRA. Earn your stripes.
The working token concept for The Herd. A black-and-white identity with Zcash at its heart. The proposed tokenomics connect launch activity to the ZEC bunker. No token has been issued.
> concept parameters
- ticker
- $QZEBRA
- illustrative supply
- 1,000,000,000
- contract address
- not deployed
- network
- concept only
- identity
- zebra / Zcash inspired
> a floor for the herd
Concept creator fees flow into three buckets. Move the split in the launch form to see the effect.
- coin bunker
- 60%
- creator
- 20%
- The Herd
- 20%
project / receipts
Follow the stripes.
A small reading list behind the visual concept. These links provide context; they do not demonstrate a deployed QZEBRA product.
project / demo pipeline
Every step. Every seal.
An interactive preview of the coin-creation journey. The stages below run locally and do not submit any transaction to a blockchain.
> pipeline --dry-run
01Design your coinready
02Capture the conceptwaiting
03Create demo receiptwaiting
04Preview on the boardwaiting
protocol / how it works
Coin in. ZEC bunker out.
The same core thesis: launch seals, a holder-owned floor, and privacy-minded payouts. This is the proposed protocol architecture; the site demonstrates the interface.
01 launch in The Herd
A proposed standard SPL coin on Solana, with its identity, artwork and fee split captured in a launch receipt. SLH-DSA (SPHINCS+) and ML-DSA form the planned post-quantum seal layer.
02 every trade fills the bunker
Creator fees split between the coin's ZEC bunker, its creator, and The Herd. The concept allocates at least 50% to the bunker, up to 30% to the creator, and 20% to The Herd.
03 SOL becomes ZEC
The proposed keeper routes SOL fees to ZEC through NEAR Intents, divides them between the Floor Vault and Hold Pool, and seals each treasury epoch. Holder rewards follow the hold-time model.
04 hold or redeem
The proposed burn-to-redeem flow pays a proportional share of the floor in SOL or ZEC, with 2% retained for remaining holders. X-Wing (ML-KEM-768 + X25519) is the proposed encrypted destination envelope.
> what guards what
| layer | proposed technology | purpose |
|---|---|---|
| Coin | Solana SPL / Ed25519 | Standard token ownership |
| Launch seal | SLH-DSA + ML-DSA | Post-quantum receipt signatures |
| Redeem envelope | X-Wing / ML-KEM-768 + X25519 | Encrypted payout destination |
| Bunker | ZEC / Floor Vault + Hold Pool | Floor allocation and holder rewards |
| Settlement | NEAR Intents | Proposed SOL ↔ ZEC routing |
Post-quantum seals do not make the underlying Solana token or Zcash network quantum-proof. Cryptographic and settlement services are not connected in this preview.
project / faq
Ask the Zebra.
Is this a working launchpad?
This is an interactive visual prototype. It creates local coin concepts and demo receipts, but does not mint tokens, connect wallets, collect funds or send blockchain transactions.
Why a zebra?
The zebra gives The Herd a distinct black-and-white identity that fits the requested Zcash theme. Gold accents point back to ZEC, while the terminal layout keeps the reference site’s feel.
Is QZEBRA affiliated with Zcash?
QZEBRA is an independent design concept inspired by Zcash. It is not an official Zcash product or an issued token.
Are the seals post-quantum?
No. Receipts in this prototype use a simple local checksum to demonstrate the interaction. They provide no authenticity, ownership or security guarantee.
Where are my demo coins saved?
In local storage in this browser. They are not uploaded. Clearing site data removes them. You can download each coin’s receipt to keep a copy.
Are the floor numbers live?
No. The dashboard uses sample data and the bunker calculator uses your assumptions. It is a mathematical illustration, not a prediction or a promised return.
Do I need a wallet?
No. Every available flow is a demo and requires no wallet, payment or seed phrase.
QZEBRA / FIELD MANUALEDITION 01 · WEB PREVIEW
FIELD NOTES / 01
Welcome to the herd
A field guide to QZEBRA.
QZEBRA brings three ideas together: post-quantum launch records, a ZEC-denominated bunker, and a community of coin holders. This documentation explains the proposed architecture and the interactive experience available today.
What is live?
The website and its browser-based previews are live. You can design a coin, model a bunker, inspect a demo receipt, browse the herd and calculate a hypothetical redemption.
Current stage · interface preview
There is no deployed token, wallet connection, treasury, payment collection or blockchain settlement. “Live” describes the available web experience. Protocol mechanics described here are proposed.
The three layers
- Seals: a proposed signed record of launch configuration and treasury epochs.
- Bunker: a proposed ZEC reserve divided into a Floor Vault and Hold Pool.
- The Herd: the coin communities that hold, create and explore redemption.
Start exploring
Use Launchpad to create a local draft, Bunker simulator to change assumptions, or Seal verifier to inspect a sample receipt. No wallet is required.
FIELD NOTES / 02
One coin. Four layers.
How the proposed system fits together.
01 · Coin and configuration
The proposed coin layer uses standard Solana SPL tokens. A launch configuration records identity, supply and fee allocations. A separate seal would bind that configuration to a signed record.
02 · Launch and treasury seals
SLH-DSA and ML-DSA are the proposed signature families for launch records and treasury epochs. Their role is to authenticate specific records; they do not replace the signature systems of the underlying chains.
03 · Settlement and reserves
A proposed keeper routes creator fees from SOL to ZEC through NEAR Intents. ZEC is allocated between the Floor Vault and Hold Pool. Routing, custody, reconciliation and settlement would require an implemented and reviewed backend.
04 · Holder flows
The planned holder experience includes time-based rewards and proportional burn-to-redeem withdrawals. An encrypted destination envelope is proposed for payout instructions, using the X-Wing hybrid construction with ML-KEM-768 and X25519.
Separate layers, separate guarantees
Post-quantum record signatures would not make a Solana token or the Zcash network quantum-proof. Privacy and security claims require an implemented system and review.
Further reading
FIELD NOTES / 03
A record of every stripe.
The seal concept and the verifier available today.
The proposed seal
A seal would bind a canonical launch configuration or treasury record to verifiable signatures. The architecture names SLH-DSA, a stateless hash-based signature standard derived from SPHINCS+, and ML-DSA, a module-lattice-based signature standard.
What this verifier checks
The current website uses a small local checksum over the receipt payload. It demonstrates the workflow: generate a receipt, inspect it, change a value and see the mismatch. It is not a cryptographic signature and cannot prove who created a record.
- Open Seal verifier and load the sample receipt.
- Select Check receipt to compare the stored and recomputed checksums.
- Select Tamper with ticker, then check again to see the mismatch.
Checksums are not authentication
Anyone can change the payload and recompute this checksum. A match is a local consistency check, not a security or ownership guarantee.
Standards behind the proposal
FIELD NOTES / 04
Build a floor for the herd.
Fee splits, reserves and simulator assumptions.
Where the fees go
The launch preview allocates creator fees across three buckets. The default split is 60% to the coin bunker, 20% to the creator and 20% to The Herd. The bunker slider ranges from 50% to 80%; the creator receives the remainder after the fixed 20% herd allocation.
Floor Vault and Hold Pool
The bunker is split again. The Floor Vault is the proposed redemption reserve; the Hold Pool is intended for holder rewards. The preview defaults to 50 / 50 and allows a floor allocation between 20% and 80%.
How the simulator calculates growth
The standalone calculator assumes a 0.95% creator fee, a fixed 60% bunker share and a 0.3% swap cost. It uses your chosen volume, ZEC price, duration and floor allocation.
daily ZEC = daily USD volume × 0.0095
× 0.60 × 0.997 ÷ ZEC price
floor ZEC = daily ZEC × days × floor shareThe illustrative holder-share figure divides the floor allocation for your bag by an assumed 70% eligible supply. This is a scenario calculation, not an available balance or payout quote.
Inputs are assumptions
Volume, prices and market cap are constant in this model. It excludes changing prices, liquidity constraints, transaction costs beyond the stated swap assumption, and operational failures. No funds are deposited.
FIELD NOTES / 05
An exit, on your terms.
The proposed burn-to-redeem model.
How a proportional redemption works
The concept exchanges a burned share of token supply for the same share of the Floor Vault. A 2% deduction stays with the remaining holders under the proposed model.
gross ZEC = tokens burned ÷ supply × floor ZEC net ZEC = gross ZEC × 0.98
For example, burning 1 million tokens from a 1 billion supply against a 100 ZEC floor gives a hypothetical gross amount of 0.1 ZEC and a net amount of 0.098 ZEC.
The proposed payout path
A production implementation would need to validate the burn, prevent duplicate redemption, reconcile reserves and settle the payout. SOL or ZEC payout routing and encrypted destination handling are architecture concepts, not connected services on this website.
Try the flow
Choose a sample coin, enter an amount and run the redemption simulation. It calculates a result locally without burning tokens or moving money. Changing the display currency does not execute a swap.
No redeemable balance
The sample coins and reserves are illustrative. The website provides no claim on assets and does not accept deposits.
FIELD NOTES / 06
Give your coin its stripes.
Creating drafts and understanding local storage.
Create a launch preview
- Open Launchpad and enter a name and ticker.
- Add a description and optional artwork. PNG, JPG and WEBP images up to 4 MB are accepted.
- Choose the bunker allocation, floor split and illustrative supply.
- Select Preview launch. Your draft appears on the board with a demo receipt.
What gets saved?
Up to 30 drafts are stored in this browser’s local storage, including uploaded artwork when storage capacity allows. They are not uploaded to a server. Clearing site data removes them, and another browser or domain has a separate collection.
The Netlify address and qzebra.live use separate browser storage. Drafts created on one address will not automatically appear on the other.
Keep a receipt
Use Download .json after creating a preview to save the receipt. It includes the coin configuration and local checksum, but does not include the uploaded artwork or create a token. The verifier can inspect that receipt; it does not import a draft into the board.
Privacy and connections
No wallet, seed phrase or payment is required. Address checks recognize formats locally and do not retrieve chain history. The dashboard uses sample data. External reading links open the named third-party websites.