NEAR memecoin · Testnet prototypeThe meme runson rituals.
A meme with a memory. Show up once a day on NEAR Testnet. The contract records the ritual; a successful day opens eligible reward claims, while a missed day burns a slice of the ritual treasury.
The memecoin where showing up
sets the supply.
One check-in is a small act. Together, they decide the day. Meet the target and eligible participants can claim a reward after finalization. Miss it and the contract burns a fixed share of the ritual treasury. The numbers have no admin setters.
- check-ins needed
for a successful day - 50
- fixed epoch length
set by the contract - 24h
- minted per participant
after a successful epoch - 1,000GEMBULL
- of the ritual treasury
burned on a missed day - 0.05%
Proposed genesis values
GemBullRitual / Day —Testnet
Not connectedToday’s ritual
no live dataeligible accounts checked in
Minimum 1,000 GEMBULL at check-in. One check-in per account per epoch. Ritual writes attach 0.05 Testnet NEAR for contract storage; excess remains with the contract.
Consecutive successful epochs. A miss resets it.
The best run so far, separate from the current one.
Claimed after finalization. No bulk mint.
No finalized epochs yet. Bars appear once the contract finalizes its first day.
Waiting for the first finalized epoch.
A simple act. A shared outcome.
Show up, reach the mark, let the contract settle the day. The ritual is simple enough to feel; its rules are public enough to verify.
CHECK IN
One day. One check-in.
Any NEAR account holding at least 1,000 GEMBULL checks in once per 24-hour epoch. One transaction, recorded on-chain.
HIT THE TARGET
Reach 50. Together.
If 50 accounts check in before the epoch closes, the day succeeds and the community streak goes up by one.
MINT OR BURN
The outcome leaves a mark.
On success every participant can claim 1,000 GEMBULL after finalization, minted by the contract. On a miss the ritual treasury burns 0.05%. Neither number has an admin setter.
- Connect a NEAR wallet A Testnet account holding the minimum GEMBULL.
- Check in once One transaction per epoch, recorded on-chain.
- Claim after finalization Rewards are minted only after a successful epoch.
What if we all showed up?
Move the slider to explore a possible day. The illustration follows the contract rules; it does not predict real participation.
The target was missed. After finalization the contract records the configured treasury burn and resets the streak.
Illustration of the contract rules, not a prediction. Proposed genesis values. Burn is computed on a 150,000,000 GEMBULL proposed genesis treasury.
One ritual. Many ways
to show up.
Whether you hold, gather, inspect, or build, the same public rules give every role a place in the story.
- ROLE
Holder
A single check-in joins a larger count. Hold the minimum, show up once, and claim if the day succeeds.
Minimum holdingOne per epochEnter the ritual - ROLE
Community
The streak is written together, one eligible account at a time. Its history stays open to everyone.
Shared streakPublic historySee the history - ROLE
Judge
Follow every parameter, claim and burn to the contract. The ritual is meant to be checked, not taken on faith.
get_rules()Event logsRead the rules - ROLE
Builder
Read the contract views, run the 60-day simulation, and build on the mechanic.
Open viewsSimulationSee the supply
Every number leaves a trace.
The contract reports the supply on the left. The separate 60-day simulation on the right shows how these rules could move it.
- Genesis supplyProposed launch amount
- 1,000,000,000GEMBULL
- Total supplyGEMBULL in circulation
- —
- Ritual treasuryGEMBULL held by the contract
- —
- Rewards mintedGEMBULL claimed by participants
- —
- Treasury burnedGEMBULL removed after misses
- —
- Max supplyHard emission cap · proposed
- 1,050,000,000GEMBULL
- Reserved for claimsHeld back for today’s check-ins
- —
- Free mint capacityRoom left under the cap
- —
Deterministic participation patterns from docs/simulation, run on the displayed rules from a 150,000,000 GEMBULL treasury. Every eligible participant is assumed to claim. This is supply movement, not a price chart or a forecast.
The 3D campaign coin represents the ritual narrative. On-chain token metadata at gembull-core.testnet is verified NEP-141 / NEP-148 GemBull (18 decimals).
Every day leaves a record.
Finalized epochs come from contract views. Eligible claims appear beside the day that made them possible.
| Day | Outcome | Check-ins | Burned | Your reward |
|---|---|---|---|---|
| Loading finalized epochs… | ||||
Ritual event log
Mint, burn, check-in and settlement logs emitted by the GemBull contract. Each link opens its NEAR transaction.
Loading verified Testnet receipts…
The rules live in the open.
Read from get_rules() when a contract is configured. These parameters have no admin setters; code upgrade authority is disclosed below.
No admin function changes these parameters, and no one can mint outside a successful epoch claim.
A deployer with code upgrade access could still replace the contract code, so upgrade authority has to be reviewed separately before anyone calls this immutable.
Minimum holding and one check-in per account add friction. They do not prove one human per account.
- Epoch lengthFixed 24-hour cadence
- 24 hours
- Daily targetCheck-ins needed for a successful day
- 50 accounts
- Max participantsCap on accepted check-ins per epoch
- 200 accounts
- Minimum holdingRequired at the moment of check-in
- 1,000 GEMBULL
- Missed-day burn0.05% of the remaining ritual treasury
- 5 bps
- Reward per claimMinted only after a successful epoch
- 1,000 GEMBULL
Where could a future reserve come from?
Try two proposed sources: purchases through a future GemBull app router and a one-time graduation surplus. Move the sliders to see each calculation and its path into the 3D vault. No router, graduation flow, purchase, or custody is live.
× proposed 1% = $50 / day
× 60 days = $3,000
× proposed 5% = $0
After protected obligations; zero surplus means zero input.
Only hypothetical purchases through a future GemBull app router count here. Ordinary transfers and unrelated DEX trades do not.
A one-time hypothetical amount left after refunds, LP seed, settlement costs, and minimum reserve obligations.
- From app purchases / 60 days
- $3,000
- From protected surplus / once
- $0
- Total hypothetical contribution
- $3,000
The next stock choice belongs to the community.
The proposed ballot would live on NEAR. The team can host the conversation; the contract would count votes and set the result.
- 01Nominate
Eligible wallets propose a stock candidate.
- 02Vote on NEAR
Wallet-signed choices become public ballots.
- 03Finalize
Anyone closes the round. No admin picks the winner.
Active wallets only, using a fixed snapshot and verified Ritual Points.
No ballot or recipient ledger is live. A vote does not buy shares or grant stock ownership.
Arithmetic only, not actual reserve performance. No real shares, broker execution, custody, dividends, redemption, or equity ownership. Costs and market movements are excluded.
Proposed Ritual Points and active-holder allocations are a separate, unimplemented simulation. This example never changes on-chain GEMBULL supply or the ritual treasury.
What ships next.
Ride with GemBull from the live contract to a public ritual demo, then onward to a simulated idea. Select a flag or a stop to see what each milestone really means.
The rules are on-chain.
GemBull is deployed on NEAR Testnet. Token metadata and genesis balances were verified. The contract enforces daily check-ins, claims after successful days, and ritual treasury burns after misses.
Milestones describe implementation status, not launch dates or returns. The stock reserve remains SIMULATED.
Give the ritual a face.
Four little marks for the days you show up. Download a transparent PNG and share the moment with your community.
Show up today. Come back tomorrow.
A daily act becomes a shared history. Sign one check-in, watch the community reach for its mark, and let the chain tell the rest.
Testnet only · No price promises · Stock layer is a simulation