How ZPZ Coin Works: Follow One Token Through Six Jobs

What is ZPZ Coin actually for? ZPZ is the utility token of the EZPZ ecosystem, an ERC-20 on Polygon, designed for six jobs: access, payments, burns, fee routing, governance and on-chain proof. This post follows one token through each job and shows the whitepaper rule behind it.

Most token pages list their uses in a line each. Here you follow the token itself: where it's designed to go when someone uses the ecosystem, what happens to it there, and which rule in the whitepaper governs each step. While ZPZ is launching, every one of these uses is planned, not live.

ZPZ's six jobs at a glance

Follow the token, job by job

1. Hold ZPZ for access Planned

The first job doesn't move the token at all. The whitepaper sets access tiers in fixed ZPZ amounts, not dollar values: hold a set number of ZPZ and a tier opens. Access is designed around holding, so the tokens stay in your wallet.

The tiers cover token-gated data feeds, premium indicators, mentorship and elite tiers. If market conditions ever make a tier impractical for new users, the DAO can adjust its threshold. Read section 3.1.

2. Pay for tools in ZPZ Planned

The second job is the first time the token moves. The whitepaper lists subscriptions, AI tools, alerts and mentorships as things ZPZ is designed to pay for, with you approving each payment from your own wallet. Read section 3.

The tools themselves are real today. EZRA, the AI research analyst, and AiPe, the analyst built into EZPZ Trading's tool pages, are live on EZPZ Trading plans, and anyone can try EZRA free with 5 questions a day. Paying for them in ZPZ is planned.

3. Spent ZPZ can be burned Planned

Here's what is designed to happen to ZPZ after it's spent. The token contract has a platform burn function: authorized platform contracts may burn ZPZ a user approves when it's spent on ecosystem services. Read section 3.2.

Every protocol burn passes a check first. No protocol burn can take supply below 5,000,000,000 ZPZ, and a burn that would cross that floor is rejected in full, never partly filled. Read section 5.2.

Burned ZPZ is gone for good. MAX_SUPPLY is 10,000,000,000 ZPZ, counted against every token ever minted, so a burn never makes room to mint more. Read section 5.1.

4. Ecosystem fees split three ways Planned

Using the ecosystem also creates fees, and part of them is designed to come back to ZPZ. At the end of each quarter, eligible ecosystem fees are designed to be split 70% to the treasury, 20% to development and 10% to a buyback contract.

The buyback share buys ZPZ through an approved Polygon DEX router and burns it, sized so the burn stays within the capacity left above the 5B floor. Eligible fees are the ones kept from completed use of ecosystem services, after refunds, chargebacks, taxes and pass-through costs. Token price and treasury performance don't change the allocation. Read section 3.2.1.

Two details the whitepaper states plainly: 70% / 20% / 10% is the initial split, which the contract owner can change, with every change logged on-chain. And the quarterly timing is an operating commitment, not something the contract enforces.

5. Vote with staked ZPZ Planned

The fifth job sends ZPZ into staking, because only staked ZPZ votes. Unstaked balances, including the treasury and development wallets, carry no voting power.

Voting is quadratic: your voting credits are the square root of your staked ZPZ, so a holder with 100 times the stake gets 10 times the votes, not 100 times. Voting power is fixed by a snapshot one hour before voting opens, so ZPZ staked after that can't swing the proposal. Proposers can't vote on their own proposals, every vote stays open at least 3 days, and passing needs more than 50% of the votes cast plus a minimum turnout. Read section 10.1.

Those votes decide real things. Treasury spending from $25,000 to $250,000 goes to a DAO vote, and larger amounts need a higher quorum and a timelock. Read section 10.2.

6. Check it on-chain Planned

The last job is proof. Fee routing, buyback funding and burns are designed to leave on-chain transactions and events, and each quarterly report is designed to list the fee base, the 70% / 20% / 10% amounts, the transaction hashes, the ZPZ burned, the supply after the burn and the burn capacity left. Read section 3.2.1.

Designated project wallet addresses are published so anyone can follow their balances, staking and votes (section 10.3). Every contract address, for the token, staking, the DAO and the buyback, will be published and source-verified on Polygonscan before DEX launch (section 11). Only trust addresses published on the official ZPZ Coin website.

What the six jobs add up to for supply

Put the six paths together and you get one supply rule: use can take ZPZ out of supply, down to a floor, and nothing puts burned ZPZ back.

• The cap is fixed. 10,000,000,000 ZPZ can ever be minted, and burning never resets that count.
• Two paths burn ZPZ. ZPZ spent on ecosystem services, and ZPZ bought with the 10% buyback share.
• Both stop at 5B. The protocol can reduce supply from the 10B maximum toward 5B, but never below it. The floor has no ordinary setting that can lower it.
• Issuance is gradual. 1,000,000,000 ZPZ was minted at the start, and the rest is minted in phases. While live supply is at or below 5B, every protocol burn stays off and the buyback share keeps building up.

These are rules about how many tokens exist. They say nothing about what a token is worth, and the whitepaper states that this mechanism doesn't guarantee any price or return.

The ecosystem ZPZ is designed for

ZPZ wasn't made first and handed a use later. It's designed for products that already exist, and most of them are live:

The statuses are the products'. ZPZ's connections to all of them are planned. For a tour of each product, read Not a Meme Coin.

Honest limits

The whitepaper is direct about what ZPZ and its contracts can't do. So are we:

• ZPZ isn't connected to any EZPZ product yet. Today the products run on their own plans.
• Protocol burns are off while live supply is at or below 5B. Because issuance starts at 1B and grows in phases, burns may not run until later allocations are minted.
• The 70% / 20% / 10% split can be changed by the owner, and the quarterly schedule is an operating policy, not a contract rule.
• Quadratic voting can, in theory, be diluted by splitting a stake across many wallets, and open voting means the contract can't stop it. Read section 10.3.
• The 5B level is a burn floor, not a price guarantee.

FAQ

What is ZPZ Coin used for?

ZPZ is the utility token of the EZPZ ecosystem, on Polygon. It's designed for access tiers, payments for tools and subscriptions, governance votes, community programs, and burns tied to ecosystem use. All of these are planned while ZPZ is launching.

Does holding ZPZ give access to EZPZ tools?

That's the design. Access tiers are set in fixed ZPZ amounts and open by holding, not spending. It isn't live yet.

What happens to ZPZ when it's spent?

Authorized platform contracts may burn ZPZ a user approves when it's spent on ecosystem services. No protocol burn can take supply below 5,000,000,000 ZPZ.

Is the 70/20/10 fee split fixed?

It's the initial split. The contract owner can change it, every change is logged on-chain, and each quarterly report lists the amounts.

Who can vote in the ZPZ DAO?

Anyone with staked ZPZ above the published minimum. There's no allowlist or identity check for voting, and votes are quadratic, so voting power grows with the square root of the stake.

Can I use ZPZ in EZPZ tools today?

Not yet. ZPZ is launching, and its access, payment and governance links are planned.

When is the presale?

The target dates are on the roadmap, and the terms are in the presale section of the whitepaper. Dates are targets and can move.

Start here

Read section 3 of the whitepaper for every planned use, then the tokenomics for supply and allocation, and check the targets on the roadmap. To see the tools ZPZ is designed for, ask EZRA 5 free questions.