GOOD TO KNOW. BEFORE YOU GO.

McNuggets turns a visit to a selected McDonald’s location into a chance to collect a funded token reward. Start with the live map, then go to the restaurant.

A restaurant is not automatically a drop.

The map includes a restaurant directory and separate funded campaigns. Select a location to check its address, opening window, reward terms and remaining claims. A directory pin alone does not mean a reward is available. “Near me” uses your location to find nearby places; directions open a route to the selected restaurant.

Check availability again before travelling. A campaign can expire, run out of slots or become unavailable while you are on your way. The restaurant’s own opening hours are separate from the campaign window.

1. Arrive.

   Choose an active drop and stand near its restaurant. Sign in with your linked wallet account, or connect your wallet directly. Enable precise location and complete the anti-bot check. No X account is required.

2. Verify.

   Keep the page open during the presence check. The server checks fresh GPS samples, eligibility, cooldowns and campaign funding. In direct wallet mode, you also sign the readable request. That signature is not a token-spending approval.

3. Collect.

   Your authorized reward is sent to the drop contract. A linked account uses the payment relay when available; direct wallet mode asks you to confirm the transaction. The reveal follows network confirmation. Inspect the transaction link to verify the actual payment.

One confirmed claim. Then a 12-hour wait.

The wallet cooldown starts at the confirmed block timestamp and applies across restaurants, devices and XP redemptions. Midnight does not reset it. A new login does not reset the wallet’s history. Browser and connection limits also apply before a transaction is sent.

The standard menu has four reward tiers. The nugget count is the name of the tier; the amount below is the token payment. A campaign with its own fixed amount or custom odds shows those terms before you claim.

Reward selection happens on the server using a secret HMAC keyed to the chain, vault, wallet and next claim index. Refreshing the page or switching restaurants does not reroll a standard claim while that key stays the same. The contract verifies the signed amount, not the randomness. This is not a publicly verifiable VRF draw.

Build up XP. Choose the top tier.

Each confirmed drop adds 40 XP. On a standard campaign, redeeming 300 available XP selects the 20 McNuggets tier instead of the draw. It still uses one funded slot and respects the same 12-hour cooldown. Custom campaigns may disable XP redemption; check the displayed terms.

Sharing a result is optional. A shared link or reward card does not earn XP, payment or a better draw. Previously recorded bonuses can only apply until their existing on-chain expiry.

A familiar login. Your own wallet.

Create an account with a username and password. Add an email at signup or in your account settings to use it as a login identifier. The password stays the same. X linking is not required to use the project or receive rewards.

Link once. Collect from your phone.

From a device with access to your wallet, sign the account-linking message. One account links to one wallet, and one wallet to one account; the association is permanent. You can then sign in on another device without installing that wallet there. The relay pays rewards to the associated address, never to a replacement address supplied with a claim.

The association signature does not transfer tokens or grant spending approval. It does allow authenticated account sessions to claim and redeem that wallet’s loyalty XP. Secure your password, save the recovery code shown once, and use “Sign out all devices” if needed. Password recovery uses that code; the login email is not an email reset-link service.

A connected account does not bypass presence checks, funding or eligibility. The current mainnet verifier also enforces its configured wallet allowlist. A funded map pin alone does not prove that your wallet is eligible; check access before making a trip.

Claim history in your account lists confirmed rewards for the linked wallet, with their date, amount and transaction link. Direct-wallet and account claims share that history. Blockchain records remain public even if a campaign is no longer shown in the public catalog.

The system checks both the request and the funded contract state. A failed verification does not create a simulated payment. These controls limit repeated claims; they cannot prove that every device belongs to a different person.

An issued authorization already counts toward browser and connection quotas, even before the transaction is submitted. Retrying the same wallet claim does not consume an additional place. Wallet cooldowns remain enforced by the contract. Every drop still needs enough allocated funds and available claims; a global payout cap is an optional server configuration, not an unlimited funding promise.

Device-reported GPS can be falsified, browser cookies can be cleared, and network identifiers can change. The verifier is trusted for presence, quest proof and reward selection. A compromised verifier could issue incorrect authorizations within the contract’s limits. These protections are not a guarantee against all farming.

The browser provides the interface and location readings. The server validates the request and signs a short-lived authorization tied to a wallet, campaign, claim index and payout. The contract checks the signer, expiry, replay protection, stock, budget, XP and cooldown before paying.

Check the deployment yourself.

Network

Robinhood Chain / 4663 / Mainnet

Public data

Reading the contract…

Observed at (UTC)

—

Drop vault

0xD7dea54435C5f5EAE938baC3ddc4cF44cA03163c

Payout token / USDG

0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168

FRY

0xF493c3073e6B46e7d1e11FaeA446d49448b6F625

The snapshot refreshes through the public API every 15 seconds. It is a reading of the configured contracts, not an independent audit or a guarantee that a claim is eligible. Token balances, transaction receipts and events can be checked directly on the explorer.

EIP-712 domain
name: Proof of Burger Drops
version: 1
chainId: 4663
verifyingContract: 0xD7dea54435C5f5EAE938baC3ddc4cF44cA03163c

DropClaim
claimant, dropId, claimIndex, item, payoutAmount,
loyalty, issuedAt, expiresAt