PARNASA TRANSPARENCY CENTER

Every important claim needs a source.

This page intentionally shows the difference between design intent, connected data and verified blockchain facts. Nothing is presented as on-chain until a real network and deployed contract are connected.

Maximum supply77,777,777DESIGN LOCK
Additional mintingDisabled targetPRE-DEPLOYMENT
Token contractNot deployedNOT VERIFIED
Treasury walletsPending publicationNOT CONNECTED
Vesting contractsPending deploymentNOT CONNECTED
Blockchain networkNot selectedCONFIGURATION REQUIRED
SUPPLY POLICY

77,777,777 maximum.

The design target is a fixed-cap token with additional minting disabled. That statement becomes independently verifiable only after the final smart contract is deployed and its authority model can be inspected on-chain.

TokenPARNASA
TickerPARNSA
Decimals18
Mint targetNo additional minting
NetworkNot selected
ContractNot deployed
ALLOCATION LEDGER — DRAFT

Exact integer allocation model.

AllocationTarget %UnitsStatus
Ecosystem + Utility28%21,777,778DRAFT
Community + User Rewards20%15,555,555DRAFT
Treasury15%11,666,667DRAFT
Liquidity12%9,333,333DRAFT
Core Team / Contributors10%7,777,778DRAFT
Strategic Partnerships8%6,222,222DRAFT
Security / R&D / Reserve7%5,444,444DRAFT
TOTAL100%77,777,777EXACT
VERIFICATION STANDARD

Design targets are not observations.

DESIGN TARGET

A defined product rule, not a verified live capability.

ON-CHAIN VERIFIED

Directly derived from deployed blockchain state.

SYSTEM VERIFIED

Signed or authenticated Project ONE backend evidence.

THIRD-PARTY VERIFIED

Independent registry, auditor or provider evidence.

NOT YET VERIFIED

Missing, unavailable or not independently verified evidence.

Current supply does not prove a permanent minting cap. Database audit rows are not immutable against their administrator. Token holdings do not grant rights to patents or exit proceeds.

Inspect the wallet evidence workflow →
← Return to PARNASA