The economic layer is proposed, not launched
PZRO does not currently exist as a publicly offered token. The numbers in Permission Zero Litepaper v0.1 are design targets for a future network-economic layer, not a sale, a guaranteed airdrop or an investment offer. The distinction is important because token economics should be allowed to change while the underlying network is still being researched and tested.
The current proposal uses a maximum supply target of 1,000,000,000 PZRO. That number is large enough to support fine-grained community distribution without creating an unnecessarily huge headline supply. Supply count by itself does not create value; what matters is the percentage ownership, release schedule, utility, governance and credibility of the network.
Why target 90 percent for the public ecosystem?
Permission Zero is being designed around a simple ownership philosophy: if the network is meant to protect human authority on the autonomous internet, the company should not begin with majority economic control. The proposed split therefore places 90 percent of supply in public and community-oriented buckets and limits company plus strategic allocations to 10 percent.
The 90 percent is broader than an airdrop. It includes a Genesis Community allocation, long-term community rewards, a community treasury, builder and security grants, and protocol liquidity. Each bucket serves a different function, so publishing only one headline percentage without explaining those functions would be misleading.
The proposed allocation
Litepaper v0.1 currently models 50 percent for Genesis Community, 20 percent for long-term community and network rewards, 10 percent for a community treasury and ecosystem, 5 percent for builders, security and research grants, 5 percent for protocol liquidity, 8 percent for the company and core contributors, and 2 percent as a future strategic reserve.
The strategic reserve is intentionally small. If it is never required, the project could later propose redirecting or retiring it through the final governance framework. If it is used, the intended policy is disclosure of the purpose, recipient class, lock and vesting conditions rather than a hidden private sale.
Why not distribute 90 percent on launch day?
Because public ownership and immediate liquidity are not the same thing. Releasing 900 million transferable PZRO at genesis would create a large free float before the network had enough utility or demand to absorb it. It would also concentrate distribution in whoever is fastest at farming the claim process rather than whoever contributes over time.
The proposed model therefore uses staged release. Only a limited Genesis portion would be claimable near network launch. Long-term rewards would stream over years. Community treasury assets would remain under governance and timelocks. Grants would be milestone-based. Company tokens would use a long cliff and vesting schedule. Protocol liquidity would be deployed for market infrastructure rather than handed to insiders.
No presale changes the incentive structure
A public presale can finance development, but it also turns the earliest project relationship into buyer versus issuer. Permission Zero’s current preference is to avoid that structure and build the first year around research, community and prototypes instead.
No presale does not mean no future funding. The company can seek ordinary corporate financing, grants, partnerships or other legally appropriate capital without selling a large discounted token allocation to the public. The proposed two percent strategic reserve exists only as a future option and remains subject to the final legal and governance model.
Community distribution needs anti-Sybil design
Any free or community distribution attracts automation. That is particularly relevant to Permission Zero because the project is explicitly trying to distinguish genuine human participation from machine-scale farming. A future claim methodology should therefore use multiple signals rather than raw follower counts or referral totals.
Possible inputs include historical participation, proof-of-human or equivalent eligibility evidence where appropriate, contribution quality, testnet or Swarm League activity, account age, graph analysis and rate controls. The exact method should be published close enough to distribution for transparency but not so early that it becomes a year-long farming recipe.
Immutability should protect supply, not freeze mistakes
The strongest long-term monetary commitment is a token contract that cannot create more supply after final deployment. Permission Zero currently prefers a non-upgradeable fixed-supply core token with no post-genesis mint function. Separate vesting, treasury and distribution contracts can then control how already-created supply moves over time.
Those surrounding contracts still need testing, audits and carefully designed administration. Timelocks and role-based controls can make changes visible before they execute. Only after the system is proven should unnecessary privileges be removed or governance transferred.
Why one billion is a unit choice, not a valuation claim
A one-billion maximum supply is intended as a practical denomination, not a statement about economic value. A network with one billion units can represent exactly the same aggregate value as a network with one hundred million or ten billion units if ownership percentages and market value adjust accordingly. The useful question is therefore whether the denomination supports intuitive grants, community allocations and application-level uses without relying on excessively small decimals.
The proposal also avoids the visual extremes common in speculative launches. A very small supply can encourage misleading comparisons based on unit price, while an enormous trillions-style supply can be chosen primarily for marketing psychology. Permission Zero should communicate percentages, circulating supply and unlocks more prominently than nominal token price.
If the final economic design discovers that a different denomination is technically or operationally better, v0.1 should not prevent that change. What matters more is the intended fixed maximum after deployment, the absence of hidden minting, transparent allocation and the separation between allocation and circulation.
Transparency should continue after genesis
A community-first launch needs ongoing disclosure. The public should be able to identify the major allocation wallets or vaults, understand which portions are locked, see when scheduled releases can occur, and distinguish protocol liquidity from company holdings. Treasury decisions should be recorded in a way that makes the movement of large balances explainable.
This does not require publishing personal information about every holder. It requires the project to make its own controlled allocations legible. If the company, strategic reserve, treasury or liquidity program moves a material amount, the reason should not be left to rumor. Transparent operational communication is especially important when the project asks the community to trust a long release schedule.
The same standard should apply to changes. If the 1B target, 90/10 philosophy, vesting schedule or launch timing changes, the project should publish the new version and a concise rationale. A versioned Litepaper and later formal issuance documents can make that history visible instead of silently rewriting old commitments.
A community-first model remains conditional
The proposed allocation, one-billion supply and 2027 target are not permanent commitments. Regulation, tax treatment, security findings, chain selection, community behavior or market structure may require changes. If the final token design differs materially from Litepaper v0.1, Permission Zero should publish a changelog explaining what changed and why.
The principle that should survive those changes is more important than any individual number: build the network before asking the token to carry value, keep insider ownership small, avoid a public presale, make supply policy transparent, and give genuine community participation a meaningful role if and when the economic layer launches.