80% of a verified creator GLD claim is allocated to eligible holders. The remaining 20% stays with the creator treasury.
PUBLIC REFERENCE / VERSION 2
Rules. Records.
Responsibilities.
How PYRMD holder rewards and community features work, which records are live, and which production inputs activate the remaining programs.
of claimed creator GLD fees funded into holder rewards
before a token balance can qualify
10, 30 or 60 minutes remain available if volume and cost demand it
Gold Points never multiply financial GLD rewards
Actual fees.
Published allocation.
Rewards depend on GLD that Pons creator fees actually produce and the team funds into the rewards contract.
Each eligible holder receives a share proportional to their eligible PYRMD balance multiplied by how long it has been held. Holding more earns more, and holding longer earns more, up to a 7-day age cap.
Every received token lot ages separately. A balance becomes eligible after it has been held for at least 15 minutes.
Rewards are prepared in 15-minute rounds. The operator also supports 10, 30 and 60-minute windows if volume and transaction costs demand a change.
Creator, project, curve, rewards, liquidity-system and configured operational wallets do not receive holder allocations.
No collected or funded GLD means no payout. A scheduling window also cannot guarantee when a public transaction reaches finality.
Community status,
measured in public.
Gold Points are nonfinancial utility. They can support future community access or a separately disclosed team-supply program.
per 100,000 PYRMD for each completed 15-minute period after the 15-minute requirement.
per 0.001 GLD of verified Pons curve trading volume.
The project owner publishes eligible LP minutes and a proof hash. Completed eligible units add points to the wallet.
A referral counts only when both wallets hold PYRMD. The contract records the relationship once and the separate marketing reserve funds any referral program.
Built, public,
and verifiable.
The dashboard reads finalized chain activity. Contract-backed programs appear as soon as the launch wallet completes community setup.
The live pyramid, public wallet ranks, Gold Points, Vault, graphical achievements, leaderboard, Pharaoh Circle and recent trades read finalized Robinhood Chain data.
The monitored operator checks a fresh Robinhood-backed market-cap estimate. The contract uses fixed cumulative supply targets at $25k, $50k, $100k and $250k, and burns funded milestones to the public dead address.
Referral registration and eligible LP minutes are recorded onchain and feed the public Gold Points calculation.
All Pharaoh wallets appear together. A separate reserve and published Merkle rounds support the approved 2% supply pool.
Longest Holder, Most Referrals, Volume Leader and Golden Pharaoh of the Day are calculated from the live leaderboard. They are visual records, not tokens.
Two wallets.
Separated by permission.
The launch wallet owns community administration and never goes on the worker host. A separate operator wallet can only report market-cap checkpoints for funded burns. One guided funding operation activates both required reserves, while later program actions remain independently reviewable.
The guided activation funds the full cumulative 2% burn target. At the launch supply, that equals 20,000,000 PYRMD. The contract cannot burn more than this dedicated reserve holds.
Fund the separate reserve with the approved pool amount. At the launch supply, 2% equals 20,000,000 PYRMD.
The operator publishes eligible minutes and a proof hash. The dashboard converts completed units into Gold Points.
The operator downloads a deterministic eligibility plan, publishes its Merkle root and shares individual claim links.
Every contest, treasury, marketing and burn transfer emits an onchain record that the public dashboard exposes.
The leaderboard calculates and displays the current achievement holders from finalized public records.
Verify it
yourself.
These are the PYRMD contracts on Robinhood Chain mainnet. Every address below is read from the deployment, so what you see here is what the site uses.
Need the technical packet?
The repository contains the contract trust boundaries, testing status, operating limits, evidence reports and source-hash manifest. GitHub access is required because the repository is private.