Whitepaper - Mainnet edition
PR3DICT Protocol
A programmed redistribution system on BNB Smart Chain Mainnet. PR3DICT combines eligible-supply based Holder Drops, Time Vault accumulation, automated liquidity logic, and public on-chain status tools.
1. Abstract
PR3DICT is designed as a tokenized redistribution protocol where on-chain activity, reserves, liquidity, and reward eligibility are exposed through transparent contract reads. The interface does not custody user assets. It reads the contract, helps users inspect protocol state, and routes signed transactions through their own wallet.
The protocol centers on three ideas: eligible supply, Holder Drops, and Time Vaults. Eligible supply defines which PR3D balance participates in reward distribution. Holder Drops distribute programmed reward capacity to holders. Time Vaults collect and process value accumulated by the protocol.
2. Mainnet Deployment
PR3DICT runs on BNB Smart Chain Mainnet. The official contract address is:
0xAF89873640418D13304902A3112052577477eF67The public site reads mainnet state directly from the contract, including eligibleSupply(), currentDayIndex(), launchTimestamp(), packetPendingNative(), pendingPacketSwapTokens(), and reserve balances. The launch date displayed by the site is derived from launchTimestamp(), not from a hardcoded text value.
3. Tokenomics
The fixed supply is 101,000,000 PR3D. The allocation model is intended to separate initial liquidity, operating support, airdrop capacity, early Holder Drops, and long-term reserve functions.
| Allocation | Share | Amount | Purpose |
|---|---|---|---|
| Initial PancakeSwap pool | 0.15% | 151,500 PR3D | Initial liquidity; LP permanently locked. |
| Operating support | 2% | 2,020,000 PR3D | Operations, infrastructure, communication, and partnerships. |
| Airdrop | 8% | 8,080,000 PR3D | External campaigns and dedicated distributions. |
| Holder Drops Year 0-1 | 10% | 10,100,000 PR3D | Initial period distribution capacity. |
| PR3D reserve | 79.85% | 80,648,500 PR3D | Reserve for controlled release, liquidity, pairing, and later phases. |
4. Eligible supply for rewards distribution
Eligible supply is the live contract value used by the interface to describe how many PR3D are currently eligible for reward participation. The site reads this through eligibleSupply() on mainnet.
This value is not the same as total supply. It excludes balances that the contract marks as ineligible, such as protocol reserves, locked liquidity, and exempt addresses. For this reason the interface must not subtract reserve amounts a second time. The displayed metric should preserve the contract's own eligible-supply reading.
5. Holder Drops
Holder Drops are programmed distributions based on the relationship between a wallet balance and eligible supply. The model is intended to reward holders without requiring the site to custody funds or run an off-chain accounting ledger.
During the first year, the protocol exposes the Year 0-1 Holder Drop reserve through on-chain readings such as year1RewardRemaining(). The interface estimates a wallet's share using live balances and eligible supply, while actual claims remain governed by the contract.
6. Time Vaults
Time Vaults represent the protocol's accumulated value layer. The site reads native BNB and queued PR3D components through packetPendingNative() and pendingPacketSwapTokens(). These values are shown as total Time Vault value and as PR3D equivalent when a liquidity price is available.
The Time Vault concept gives the protocol a visible state: users can inspect what is ready, what is queued, and how it compares with the eligible supply for rewards distribution.
7. Reward Cycle Update
PR3DICT uses a public operational trigger called Reward Cycle Update. The interface checks whether the current day has advanced beyond the last processed package day. When useful, a user can call the update flow from the site and sign the transaction in their own wallet.
The site shows user-friendly launch-relative days while preserving the raw blockchain day as a technical note. This keeps the interface readable without hiding the underlying on-chain date index.
8. Liquidity and market data
The initial PancakeSwap pool is a permanent liquidity allocation. The interface reads the current LP pair through the contract and derives spot price from reserves when the pair is available. Market display values are informational and may change with liquidity depth, swaps, volatility, and RPC availability.
Non-custodial interface
Wallet connection is used to identify the address and read on-chain data. Transactions are always signed by the user's wallet.
Mainnet-first reads
The production interface is configured for BNB Smart Chain Mainnet and the official contract address listed above.
9. Governance and autonomy
The contract includes owner, configuration freeze, and autonomy paths. The long-term direction is to reduce discretionary control and leave public protocol functions available for users and keepers. Interface tools are designed to surface the relevant state without obscuring contract behavior.
10. Risk notice
No financial advice. This whitepaper is informational only. It is not investment advice, legal advice, tax advice, or a promise of returns.
Digital assets are volatile and can lose value. Smart contracts, liquidity pools, RPC providers, wallet software, and user transactions carry technical and market risks. Users are responsible for verifying the contract address, reading transaction prompts, and understanding the risks before interacting with PR3DICT.