The legendary, in full.

Ten of them. None of them fine print.

• Sponsor

  Touch Grass is the sole sponsor of this promotion. The company behind it is being set up; its name, address and registration number appear here the day it exists.

  Apple Inc. is not a sponsor of and is not involved in this promotion in any manner. Google LLC is not a sponsor of and is not involved in this promotion in any manner. Neither company sits between you and this game today: the Android build is a file you download from this site rather than a Play listing. The sentence stays anyway, because it has to be true on the day either store carries this.

• Who can enter

  18 or over, and resident in one of ten countries: France, Germany, Italy, Spain, the Netherlands, Belgium, Portugal, Ireland, Austria or Luxembourg. Void in any of those countries where local registration of a prize promotion is required and has not yet been completed — the announcement for each drop names the countries it is open in.

  The map is wider than that list, and that is not a mistake: fragments spawn in front of shops all over it, and an ordinary fragment asks only that you are 18 or over, which the terms write out. A legendary is narrower: at most the ten countries above, because a single announced prize with a fixed window is a different animal from a fragment, and it only runs where we can actually run it.

  The list opens country by country. Several of those countries ask you to register a prize promotion with an authority before it may run, and that registration starts once the sponsor entity exists. The countries already open are the ones that count on the day you claim, wherever on the map the door lands: the server picks the door, Tokyo as easily as Lyon, and eligibility does not move with it. Write to support@touchgrass.family before you chase one if you want yours confirmed.

  You also need an account, because a prize has to be sent somewhere. Sign-in is Google, X, or Apple in the app — no password, no form, and a wallet that appears on its own.

  That wallet, the one sign-in made, is the one that has to be holding 5,000 $GRASS when you claim, and to have been holding it for a day. Not a wallet you connected somewhere else, and not a friend’s: the balance is read on the address the prize would be sent to, so send the tokens there a day before the one you mean to win, and leave them there.

  The awkward part, said out loud: the app asks you to declare, once, that you are over 18, and it stores that answer on your device. There is no server-side age check behind it yet. The rule binds regardless — a false declaration means you were never eligible and the prize can be refused before it is sent. After it is sent it is a transfer on a public chain and nobody can pull it back, which is exactly why the question is asked before you play instead of after you win.

• Employees

  Employees of the sponsor and their immediate families are excluded. In practice that rule has one concrete meaning: nobody who can see a code before it goes on the wall may win. A code is generated on the server when a drop is scheduled by hand and shown exactly once, to whoever scheduled it. It is never sent to a browser or to the app again: not in the countdown, not in the public API, not to the winner afterwards. A drop the server schedules itself carries no code at all, and nobody, us included, is told the door or the hour before the announcement that tells everyone.

• Entry window

  Each legendary has one fixed start time and one fixed end time, both set before it is announced, and the announcement lands at least 24 hours ahead — in the app, and on the front page of this site with a countdown running on it.

  Most drops are scheduled by the server itself, on a fixed rhythm: a door already on the map, at 18:00 in that door’s own time zone, open for one hour, and only once the vault already holds the share. The rest are scheduled by hand. Both are announced the same way and judged by the same rules.

  Early is refused, and the refusal tells you how many minutes are left. Late is refused too: the window closes, the drop is archived, and the slot is free for the next one. There is no grace period and no extension.

• Number of winners

  Exactly one per drop. Not one per city, not one per hour, not a consolation tier. When a claim is accepted, the winner slot is written down before the prize is signed for, so two people tapping in the same second cannot both win — the second one is told that somebody already took it.

• How the winner is determined

  The first eligible player to arrive at the announced location during the window, holding the required $GRASS, and, when a code was announced with the drop, to enter the code displayed physically at that location. Determination is by arrival and action, not by chance.

  The only random things in the entire mechanism are which door the server picks for a drop it schedules itself, and the six characters printed on a sticker when there is one. Neither decides who wins: the door is announced a day ahead to everyone at once, and the letters exist so a code cannot be guessed from a sofa. (The alphabet has no I, no O, no 0 and no 1 in it, because somebody is going to be reading it off a wall in the rain.)

  Being at the address is not enough on its own. Neither is faking your GPS: a spoofed position gets you to the coordinates and no further. With a code, that is because the code only exists on a physical surface at the place. Without one, the hold does the same job from the other side: a thousand invented wallets hold no $GRASS between them, and the one that does belongs to a person who could have walked.

• Prize

  One whole Stock Token of the announced symbol.

  A Stock Token is a token representing a derivative contract with Robinhood Europe UAB that tracks the price of the underlying listed share. It is not a share. It confers no shareholder rights — no vote, no claim on the company, no entry in any shareholder register. Its value fluctuates and may fall. It is not covered by any investor compensation or deposit insurance scheme.

  Which is the long way of saying: it is a prize, not an income. It can be worth less tomorrow than on the day you won it. Walking is not earning, and nothing in this game pays you.

  The prize sits in a public vault before the window opens, and the site says out loud whether that vault can actually pay it. If it cannot, the drop is labelled “vault not funded yet” rather than letting somebody cross a city for a prize that is not there. You can count the vault yourself.

• Award date

  Transferred to the winner’s wallet within 24 hours of the window closing. In practice the transfer is signed the moment the code is accepted and lands in seconds; the 24 hours is the outside limit we hold ourselves to, not the target.

  Every transfer is on the public block explorer, and past winners are listed on the front page beside a shortened form of the address that received the token. Nobody has to take our word for who won — which is the next rule, because it cuts both ways.

• Publicity

  Winning is public, and permanently so. The prize moves by a transaction on a public chain, so the full receiving address and the transfer itself sit on a block explorer forever, readable by anyone, and nobody — us included — can edit or delete them. The front page lists past winners by a shortened form of that same address, and the app shows it the same way on the drop you are looking at.

  Entering is agreeing to that, and it cannot be undone afterwards. Deleting your account later removes your rows from our side and changes nothing on the chain; there is no delete on a public ledger, which the privacy policy says at more length.

  What is not published is everything else. No handle, no display name, no avatar, no email, no city, no position — winning publishes an address and a transaction, and nothing else. This one is spelled out here rather than in the app’s rules card, which is a shipped build and does not name it yet; until that build is replaced, this page is where it is written down, and it applies either way.

• Disqualification, and how to argue with it

  Claims that fail our anti-fraud checks may be refused. Those checks exist because a game about physically going somewhere stops meaning anything the second coordinates can be typed instead of walked to.

  A refusal is not the end of it. If you think you were refused wrongly, email support@touchgrass.family and a person will look at it and answer you within 72 hours. A person, not the same automated checks run a second time. The email is the mechanism, and it is read.

The gate, with the numbers in it.

A rule you cannot check is a rule you have to trust. These are the actual conditions a legendary claim passes through, in order.

• The window is open. Too early and you are told how long is left. Too late and the window is closed. Already won and you are told so.
• You are inside the radius. Each legendary carries its own radius, announced with the drop and deliberately tighter than the 40 m an ordinary fragment allows. Your phone’s own error bar widens it, since standing in a crowd with a coarse fix is still standing there.
• Your fix is good enough. An accuracy worse than 65 m is refused outright. Step outside, wait for the circle to shrink.
• Your body could have got there. Two different cities inside an hour is not a walk, whatever the flight was, and it is your own wallet’s last accepted positions that this is judged against. There is a second trail kept per device, and it deliberately refuses nobody: a “device” here is really a hash of your connection and your phone’s headers, and a mobile carrier hands one of those to a whole city. Being refused because a stranger on your network caught something elsewhere would be both wrong and impossible to explain, so it does not happen.
• The fix reads like a real one. A real satellite fix comes back with about fifteen decimal places of noise on it; coordinates copied off a map have five. A position that never drifts, an accuracy that never changes, a device clock hours away from the timezone it claims to be standing in, an accelerometer reporting energy from zero readings — no single one of those proves anything on its own, and a handful of them at once is a refusal.
• Your wallet holds 5,000 $GRASS, and held them a day ago too. The balance is read from the chain at that moment, on the wallet you signed in with. The age comes from the token’s transfer record: whatever arrived since then is subtracted, and what is left has to still be above the bar. A chain that cannot be read is a refusal too, one that says to try again in a moment, rather than a wave through: the window is an hour, and a blink of the network costs a retry, not the prize. Nothing is spent.
• You typed the code, when there is one. A drop scheduled by hand carries a sticker and its card says “code on site”. A drop the server scheduled itself carries none, and the card says that instead. Where there is a wall, this is the part no amount of software gets you past.

Touch Grass, and a person who answers.

The company behind Touch Grass is being set up. Its name, address and registration number appear here, in the app’s rules card, on the privacy policy and on the terms, all on the day it exists.

Meanwhile there is a person on the other end of support@touchgrass.family, and that address is the fastest way to reach one: for a refused claim, for a prize that did not arrive, or for anything on this page. The support page says what to include so it can be answered in one reply instead of four.

Rules can change between drops. They do not change during one: once a window is announced, the rules that were published with it are the rules that decide it, even if this page is edited in the meantime. The same rules are bundled inside the app itself rather than only linked to — shorter there, identical in what they say — so you can read them standing in the street with one bar of signal.

If this page and the rules card inside the app ever disagree, that is a bug — tell us at support@touchgrass.family and we will fix the wrong one rather than argue about which counts.

last updated 14 September 2026