The world,
onchain.

01 / Privacy today

A map of drops, not player positions.

The game is open with direct wallet payouts. Public blockchain records are not anonymous.

MEMEGO reopened the existing deposit and catch flow on September 10. Available map pins are public, while player positions and individual pickup history stay off the public website. The current contracts publish drop coordinates and claim transactions, which can link a receiving wallet to the original pickup place.

Successful claims pay directly to the chosen wallet. Unclaimed deposits keep their original expiry and governance refund rules. Fee coverage follows the active campaign and available budget. No private-payout upgrade or new withdrawal balance has been deployed.

A future private reward flow would need a different, reviewed protocol. Delaying a payment or using another wallet alone is not enough: token identity, unusual amounts, timing and small groups can still reveal a connection. The current game does not promise anonymous pickups.

02 / Our mission

A first step onchain starts outside.

MEMEGO's goal is to onboard the world to onchain activity and memecoins through something people already understand: exploring places and finding things together.

A first crypto experience can involve unfamiliar wallets, networks, signatures and exchanges before there is a clear reason to use any of them. MEMEGO starts with a familiar action: open a map and see what is nearby. The intended journey is to discover a funded token drop, walk to its location and claim it into a wallet.

Memecoins bring communities, humor and shared identity into that journey. MEMEGO gives those communities a way to place their tokens in the real world, where newcomers can discover them through participation. A token appearing on the map is not an endorsement of its quality or value.

• Make the first action understandable.

  Explain a drop, its network and the wallet destination before asking someone to sign.

• Let people learn by doing.

  Help a first-time player understand receiving, owning and sharing a token through a clear experience.

• Build for a worldwide community.

  Start in the phone browser and support communities in different places. Availability still depends on funded drops, accessible locations, supported networks and applicable service restrictions.

• Measure useful participation.

  Judge progress through successful onboarding, verified payouts, returning explorers and community-funded hunts. These are intended measures, not reported adoption figures.

The mission is global. It does not promise a drop in every neighborhood, unrestricted availability in every country, or income from going for a walk.

03 / The game

Discover. Walk. Collect. Share.

MEMEGO connects a funded token reward to a real place. Players explore the map; people and communities supply the drops.

• 01 / Discover

  Browse drops by location and network. Review the token, funded amount, expiry and distance. A pin represents a particular funded drop, not a promise of a future reward.

• 02 / Walk

  Travel to the location safely. Allow the location check when attempting a catch, and wait for sufficiently accurate, recent readings. No camera or augmented reality is required.

• 03 / Collect

  Confirm the receiving wallet and approve the catch request. After the location service approves it, a successful transaction pays the drop directly to that wallet. A pending screen is not a confirmed payout.

• 04 / Share

  Choose a supported token you hold, a network, a location, an amount and an expiry. Confirm the funding transaction. Other players can discover the drop after its funding is verified.

A public drop has one successful recipient. It can be claimed by another player before your transaction completes, and donors cannot claim their own drops. Rarity labels help distinguish map experiences; they do not guarantee a market value, liquidity or profit.

Anyone meeting the published access and catch rules can participate in public drops without holding the official MEMEGO token. Community sponsors can use drops to introduce a token or organize a hunt. MEMEGO does not charge a platform percentage on public drop donations; network and token-level fees may still apply.

The normal public map does not seed simulated coins or simulate real payouts. Explicit local test mode is separate. Real funding and claims remain unavailable until the relevant network is activated.

The official map uses a cloud index of finalized public blockchain records. It loads recent drops in bounded pages so each phone does not have to scan the whole chain. Map and ranking views can be incomplete while history syncs or older records fall outside the loaded window. A catch always checks the funded drop onchain again.

04 / Wallets & networks

One account. Two wallet families.

Players can sign in with email and have wallets created through Privy, or use a supported existing wallet. They do not need to arrive with four different wallets.

One EVM wallet address can be used across Robinhood, BNB and Base, while Solana uses a separate wallet address. The account brings these together in the interface. Balances remain separate on each chain: ETH on Base is not automatically available to pay fees on Robinhood.

Drops settle on the network where they were funded. MEMEGO does not automatically bridge or swap a token into another network. Always check the chain and full token address; names and symbols can be copied.

Privy supplies the embedded-wallet and sign-in infrastructure. MEMEGO's normal game does not generate a private key in browser storage. Recovery and wallet export use Privy's supported flows; protecting the sign-in account and testing recovery remain important. Sign-in, creation of both wallet families and session restoration have been checked; cross-device recovery and physical-phone checks remain launch tasks.

Network fees are distinct from the reward. Players may need the network's fee asset to submit a claim. Optional gas sponsorship is implemented but disabled; any launch of sponsored claims will need a separate funded operating budget and published limits.

05 / Deposits & payouts

Fund a drop. Pay its catcher directly.

A drop contract holds the donated tokens until one valid catch or an expiry return. This temporary holding is what escrow means here.

• Funding

  The donor authorizes a token transfer into the drop contract. The funded record identifies its token, amount, location, expiry, donor and location-verifier key and policy hash. The initial implementation binds those fields per drop; upgrade authority can change future enforcement. The frontend waits for verified chain state before treating it as funded.

• Payout

  The contract checks the location service's signature, recipient, deadline and whether the drop remains available. A successful claim transfers the funded reward directly to the named wallet. MEMEGO does not create a separate spending balance that needs a later withdrawal.

• Expiry

  After expiry, anyone can submit a return transaction that pays only the original donor. While an upgrade, owner transfer or permanent upgrade lock is pending, new deposits stop and the original donor can also sign an early return of an unclaimed drop. Existing claims may still complete. An early return must confirm before the catch or governance change executes. Canceling a pending change reopens deposits and restores normal expiry rules. Returns require a network transaction and its fee.

The initial release is designed for upgrades approved by one MEMEGO owner wallet, with a 48-hour onchain delay. The current implementation has no administrator withdrawal of rewards, but an approved upgrade can change custody, claim and refund rules, including introducing a withdrawal. Users therefore trust the owner with upgrade power. The owner can schedule a transfer to a new owner, including a future multisignature wallet, or permanently disable upgrades through the delayed process. These mechanisms need independent audit before activation.

Tokens can have their own transfer taxes, restrictions or unusual behavior. EVM funding records the actual amount received by the contract. An outgoing token tax may reduce what arrives in the recipient's wallet; not every token implementation is compatible. Contract balances are token units, not a guaranteed cash value.

A confirmed on-chain transaction is the payout record. Failed, expired or interrupted requests must be reconciled against the chain before retrying; the interface must not report success based only on a local animation.

Robinhood, BNB and Base each use an upgradeable proxy and a separate implementation contract. Solana uses a drop program plus a reviewed immutable governor program that enforces its owner approval and delay. A direct owner-controlled Solana loader key would bypass that delay and is not accepted by this design. There are four game networks, but more than four deployment transactions and contract/program addresses. The game contracts were deployed on all four mainnets on September 8, 2026, and their code, owner authority and 48-hour delay were verified. Location signing is configured on all four networks; real funded phone testing remains. The Network status page lists each deployed address and block explorer.

06 / Token review

Review the token. Keep custody onchain.

MEMEGO manually curates the tokens shown on its official map. Listing approval is separate from the permissionless contracts that hold and pay out funded drops.

Before funding through the official app, select a coin in Place a drop and submit it for review there, or use the Token review page. The exact token contract or Solana mint and its chain identify the listing. Add a public project link and relevant details. No payment, token transfer or private key is required to request a review. The same address on a different chain is a separate listing. A copied name or symbol is not proof of identity.

• A person makes the listing decision.

  An explicitly authorized reviewer approves or disapproves each request. The private panel shows the exact network and token address, with the submitted project information available to inspect. The service records the reviewer, decision and time automatically. The simplified controls do not claim that an audit or individual scam checks were completed. Project identity, mutable token controls, transfer restrictions, liquidity and holder concentration remain factors the operator can investigate. No automated scam score or continuous risk scanner is operating.

• Review once, then allow ordinary drops.

  After approval, donors can use that exact token on that chain without a separate manual review for every ordinary drop, while the approval remains current and the network accepts deposits. The app checks again before funding. Only current approved tokens enter official map discovery and catches. No review activates an undeployed network.

• Review sponsored campaigns separately.

  A sponsor submits its plan, branding, claims, dates, budget and proposed public locations. Campaign approval requires a current token approval and applies to the submitted proposal. It does not automatically schedule, promote or fund a hunt. Ordinary donor funding does not confer official sponsorship or brand endorsement.

• Date, renew or remove the listing.

  Token approvals do not expire. Once approved, a token remains listed until a MEMEGO operator disapproves or suspends it. Existing approvals, including those whose previous time limit had elapsed, follow this policy. Pending or disapproved requests are not approved automatically. Original decisions and evidence remain in the review history.

The review page publishes current token decisions, their dates and risk summaries. Pending, rejected and suspended tokens are excluded from the official map. The map refreshes its review state regularly and hides listings when a fresh check cannot be confirmed. Every new app deposit and catch requires a current check. The cloud service also checks the funded token before issuing or reusing an approval and before paying a claim fee. It refuses unlisted or suspended listings even if someone bypasses the app. A decision can change while a wallet transaction is being signed; listing checks are not an on-chain guarantee. A catch approval already issued can still settle until its short deadline. Suspension cannot revoke that signature.

Removing a listing does not transfer, freeze or confiscate its tokens. Existing drop history remains in My bag, including unlisted tokens, so the original donor can recover unclaimed funds after expiry under the contract rules. A third party can call the contracts directly or build another interface; that does not create an official MEMEGO listing. MEMEGO operates the listing review, automatic location service and initial contract upgrade authority. Those controls are centralized even though funding and direct payouts settle onchain.

Reviewed is a dated listing decision, never a guarantee that a token is safe, liquid, sellable or valuable. Projects can change permissions, fees and behavior after review. Manual checks can miss scams. Unresolved risks need further evidence; review is not a substitute for an independent audit.

Review submissions are associated with a pseudonymous signed-in account. Project details, decisions and reviewer audit records are retained for moderation and accountability; they do not use the location service’s 24-hour deletion window. Avoid personal information in submissions. Public summaries must exclude private contact details. Final retention, operator contact and privacy disclosures must be published before game launch.

• Submit a token, sponsored campaign or risk report ↗

My bag includes a separate paginated wallet history, including tokens that are no longer listed. Donors can also look up a drop by its onchain ID and request an expiry return if the index is unavailable. Wallet history now uses an authenticated POST to MEMEGO’s official API and requires the requested wallet to be linked to that account. It sends no GPS samples. Public map responses contain only currently available, reviewed drops and exclude player wallet identities and caught-drop history. The index helps discovery and does not itself authorize a payout. Contract upgrades are a separate owner power: the app checks a reviewed implementation and the expected owner, and refuses an unrecognized deployment change until its configuration and code checks are deliberately updated.

A donor submits the token before any payment. The reviewer checks that it is a meme coin, records the evidence, and approves or rejects the token. Donors choose how many tokens to drop. MEMEGO imposes no per-drop or daily token amount cap; wallet balances and the chain contract’s supported amount range still apply. Saving approval makes that token available for funding on enabled networks immediately; no separate server update is needed. Once the donor confirms funding and it is indexed from the chain, its drops appear on the map. Expired or suspended approvals remove funding eligibility and stop new catch approvals. Limits on catch frequency, account cooldowns and location checks remain in place. Token approval is not a guarantee of safety or dollar value.

07 / Location & trust

On-chain funds. Off-chain location checks.

MEMEGO uses automatic checks by a centrally operated location service. A blockchain cannot establish a phone's physical location from GPS readings alone.

The service verifies the signed-in account and the receiving wallet's signed request, reads the funded drop from the chain, and checks recent location samples, accuracy, timing, movement and account limits. If the request passes, it signs a short-lived approval bound to that drop and recipient.

Current initial settings require an 80 m catch radius, reported accuracy of 65 m or better, and at least three samples spanning 12 seconds. The service normally issues a 90-second approval; the contract permits no more than two minutes. These are implementation settings under review, not a claim of exact physical accuracy. Funded drops keep their original verifier and policy.

GPS can be spoofed, accounts can be farmed and plausible movement can be fabricated. These checks reduce some abuse but do not prove that each account is a unique person at the location. A compromised or dishonest signer could authorize illegitimate catches. A service outage prevents new approvals; it does not give the operator a contract withdrawal power.

The service keeps the latest precise sample per pseudonymous account for movement checks. Routine activity and catch-check records age out after 24 hours at maintenance; current provider backups are retained for seven days. Some relay reconciliation records persist longer, and public drop coordinates and wallet transfers remain public on-chain. There is no public player-position feed or catch-location leaderboard. Catch activity is published only as anonymous daily totals by token and chain. Existing onchain drop coordinates can still be linked to a claim wallet through public transactions; this interface does not provide cryptographic location privacy. Storage, backup recovery and actual privacy disclosures still need final review.

MEMEGO's goal is to minimize custody and make fund flows verifiable. The whole platform is not fully decentralized: location approval, hosting, sign-in and recovery depend on operators and service providers.

08 / The MEMEGO token

A token that helps fund the map.

The official MEMEGO token is planned for Pons on Robinhood Chain. The game must work with real catches before that separate token launch.

The intended creator tax is 3%, split equally among those three uses. This describes the creator component, not every cost of trading: launchpad, network and token-specific fees must be considered separately. The creator proceeds arrive in the pairing asset and need conversion before they can become MEMEGO drops.

An immutable fee-splitting contract is implemented locally for native ETH proceeds. It allocates received creator proceeds equally to three fixed destinations and has no owner-controlled withdrawal or recipient setter. It is not deployed. The protected purchase route, map reserve and funding worker still need implementation and review.

MEMEGO's splitter cannot remove powers in the upstream launchpad. The launch design must account for Pons recipient changes and takeover mechanisms, and verify the actual deployed launch terms before committing proceeds. The launch will publish the official token address, supply, decimals, distribution, vesting or lock arrangements, liquidity terms and fee destinations once finalized. Those details are not finalized in this edition.

There is no official deployed MEMEGO token address in this release. The intended token is native to Robinhood Chain; support for four game networks does not create four official tokens. Holding a token does not guarantee income, a reward or price appreciation.

09 / Activity-based drops

Put funded hunts near real activity.

The proposed map cycle is collected fees, protected MEMEGO purchases, funded public drops, then direct payouts to successful catchers.

• Count activity with consent.

  Optional activity sharing uses authenticated, recent sessions while the map is visible. It counts an account once across linked wallets and networks, and expires after an hour without activity. Catch verification is separate from this optional allocation consent.

• Choose areas fairly.

  Allocate from actual available funds, consider outstanding drops, cap concentration and rotate opportunities among smaller active communities. Opening the app repeatedly or connecting extra wallets must not create extra weight.

• Choose suitable places.

  Use reviewed public walking spots near eligible areas. Do not copy a player's precise position into a pin, follow a moving player or publish sparse player-location data. Keep the budget when no suitable place is available.

• Buy and fund within limits.

  Use a reviewed purchase route, price and spending limits, and actual received balances. Confirm each funding transaction once before showing a funded pin. Expired unclaimed rewards return to the reserve for a later round.

The purchased MEMEGO is distributed through catches; it is not burned by this design. A drop near an active area is a public opportunity, not a reward reserved for the account that helped that area qualify. Global placement still settles the official token on Robinhood Chain.

A local allocation planner exists. The conversion, protected reserve and transaction worker are not operating. Exact geographic weights, spending limits and campaign rules must be published before activation. Purchases, funded drops and returned funds should be traceable on-chain without exposing individual activity records.

10 / Holder benefits

More ways to take part.

Proposed holder benefits focus on participation, identity and community hunts. Public drops stay available without MEMEGO ownership.

• Holder hunts / In design

  Separately funded hunts for eligible holders, with published capacity and rewards. Holding alone does not complete the location check or reserve a prize.

• Explorer identity / In design

  Holder badges and additional character styles. A current-holder badge is different from an achievement earned by completing a route.

• Trail quests / Proposed

  Routes with checked physical checkpoints and a funded completion reward or collectible. Rules, timing and available slots must be visible before entry.

• Community hunt votes / Proposed

  Help select future hunts from reviewed places within an allocated budget. Binding votes require enforceable voting and execution rules, not just a poll.

No holding threshold, staking requirement, reward schedule or holder share of the map allocation is finalized. A campaign must be funded before it opens and enforce its eligibility rules in the settlement design. Existing public donors' funds cannot be redirected to holder campaigns.

These are proposed product features, not active token entitlements. There is no promised APY, passive dividend or guaranteed weekly payment. A token balance is not proof of a unique person, and token-weighted votes are not one-person-one-vote.

11 / Roadmap & launch

Earn the next milestone.

Progress is measured by working features and verified outcomes. Dates will be shared when they are confirmed.

• 01 / Build the game board - website and accounts live

  The public website, walking map, Privy sign-in, EVM and Solana wallets, cloud hosting, token review and feedback flows are running.

• 02 / Real coins, real catches - contracts deployed

  Game contracts are deployed and ownership verified on all four mainnets. Next: configure location signing and policy, verify wallet recovery, and test small real deposits, direct payouts and donor returns on supported phones before enabling each network.

• 03 / Full-platform audit - required before launch

  Independent review of contracts, wallets, location checks, privacy and funding services. Resolve launch-blocking findings and publish the actual scope and results.

• 04 / Official token - planned

  Launch on Pons after real catching works and the funding contracts, token terms and launch settings are verified.

• 05 / Map buybacks - planned

  Operate protected purchases and activity-based funded drops with visible accounting.

• 06 / Holder hunts and identity - in design

  Publish qualification rules and open only funded campaigns.

• 07 / Trails and community votes - proposed

  Add verifiable route completion and bounded community decisions.

• 08 / iOS app - planned

  Native iPhone experience, device testing, recovery checks and App Store review.

• 09 / Android app - planned

  Native Android experience, device testing, recovery checks and Google Play review.

Public drop-contract deployments are complete on all four mainnets. Reviewed-token funding is enabled on all four networks. Real payout checks and audit follow-up remain. The official token and native apps have not launched. The website's Network status page lists deployed addresses and current claim setup.

12 / Risks & references

Clear rules build lasting trust.

MEMEGO aims to make onchain participation easier to understand. It cannot remove the risks of tokens, software or the physical world.

• Token and transaction risk

  Memecoins may have no liquidity and can lose all value. Transfers can be irreversible. Contract defects, malicious tokens, compromised keys, congestion and network outages can cause loss or prevent a catch.

• Operator and provider dependence

  Location approval and activity placement are trusted decisions. Privy, hosting, RPC, map and launchpad providers have their own availability and controls. A correct contract does not prove that a location decision is honest.

• Outdoor participation

  Use accessible public places, follow local rules and respect opening hours. Do not trespass, enter traffic or use the game while driving. A map pin does not establish that access is safe or permitted.

• Launch disclosures

  Before real-token play, publish the operator and support contact, applicable terms, privacy practices, eligibility restrictions, verified contract addresses and audit results. This whitepaper is a product and technical description, not those legal documents or an investment offer.

This first edition records MEMEGO's design and status on September 8, 2026. It contains no adoption figures, token-price forecasts or guaranteed rewards. Future editions will identify material changes. Planned features may change as implementation, testing and feedback develop.

• MEMEGO network status ↗
• MEMEGO token plans ↗
• MEMEGO roadmap ↗
• Privy: identity tokens ↗
• Pons: official launchpad documentation ↗

The description of MEMEGO's behavior is based on the project's v3 implementation and current operating configuration. Pons-specific design assumptions were reviewed on September 7, 2026 and require confirmation against the actual launch settings and deployed code. MEMEGO is an independent project and is not affiliated with Robinhood or STEPN.