The authoring surface for the LORE Network. Draft a legend, place its coordinates on the same satellite map players see, attach illustrations, and submit it for review — the identical pipeline the app uses, without typing a thousand words of story on a phone.
Both required. They are how legends get grouped and found later — by who they are about, and when.
How hard is this hunt to finish? Judge the walk and the puzzle together. Players filter on this.
Locations must be somewhere the public may lawfully and safely go. No private property, no hazards, no trespass. A person reads every legend before anyone else sees it.
Everything you have submitted, and what a reviewer said about it.
Waiting on a decision, most-reported first. Click a legend to review it as players will see it. A written reason is required for every outcome — approvals included, because the log exists to show who let something onto the map.
Players' extra history on Collectibles. Approving publishes it under the legend and pays the author the same GLC as an approved legend. Check it is fact, not a clue or a pointer to the coin. Hold and reject need a reason, which the author is shown.
Saving keeps a draft that only admins can see. Publishing is what players read — and it is permanent in the record: every published version is kept, because which text somebody agreed to on a given date is the whole question if it is ever disputed.
Loading…
Publishing queues an audited, retried in-app push notice for every user. After signing in, each player must review and accept the current published Terms and Privacy Policy before continuing in the app. Email is not required or sent.
Every receipt a player creates by checking the box and tapping Agree in the app. Receipts are permanent and are never edited.
Everyone who can open the console. Reviewing and appointing are separate: a reviewer works the queue, a manager can also add and remove people. Every change here is written to a permanent record.
They must have signed in to LCL at least once — access is granted to an account that exists, not to an address. If they used Apple’s Hide My Email, the address on their account is the private relay, not this one.
Gives every Trading Post item to any account without console access, so it stays an ordinary player. Staff pass every paywall, so test paywalls from accounts like this one.
When on, Collector and Lore Mode need Digital, and the field needs Physical — paid in the App Store, or given by an access code. Staff and the App Review account always pass. Takes effect within 15 seconds.
Checking…
Make codes that grant exactly what you choose — to test past a paywall, or as promotional gifts. Each code works once per person, up to its number of uses. Codes are shown once, then stored only as a hash: copy them before you leave this page. Players redeem them under Profile → Subscriptions → Redeem a code.
Every code, newest first: when it was made and by whom, what it gives, who it was issued to, and each use.
Type the email from the mailed form, then the expedition, and click the one it suggests. The code is emailed from inquiries@ and lasts 30 days for that expedition only. One request per email, per expedition, per day.
A find that pays only GLC needs no approval: it pays the moment it is verified on arrival. It comes here only when it looks wrong — its risk score reaches the line (a failed App Attest check, a simulated or teleporting approach, no recorded walk-in). A find with cash or a physical prize always waits under Finds awaiting review for a person before anything is paid or shipped.
Loading…
Finds refused for going over a daily limit in the last 30 days. The phone keeps a refused find and resends it, so one attempt can show several tries; days over counts separate days the player hit a limit. A legitimate player is simply told to wait. Several days over, or many tries, is worth a look — suspend from above if it is a pattern.
Loading…
Every five minutes the server looks across recent claims for patterns a single claim cannot show — failed App Attest checks, a device key shared between accounts, injected GPS, claims landing on the exact answer. When an account crosses the line it lands here and every staff manager gets a push. Nothing is suspended until you approve it.
Loading…
Suspended automatically, with an email to inquiries@ each time: a modified app (App Attest failed), a simulator, the third or later account on one phone, an ID document reused after a warning (every account on it), or a third refused walk-in in a day. Faked GPS is not suspended — the account is flagged and emailed, and a find (not an XP checkpoint) is held under "Finds held for review". Suspensions you approved above are listed here too. Lifting one lets the player claim again; a new attempt suspends them again. Each rule can be switched off in the app's Developer Menu → Zero tolerance.
Loading…
Raised automatically for a person to look at, without suspending anyone: for example a subscription presented by a second account, or faked GPS. An open flag holds that winner's payouts until it is resolved; resolving one records your note and releases them within 30 minutes.
Loading…
Accounts that share one device key (App Attest) or one paid subscription. Informative, never proof: families share phones and people reinstall. Revoking a device key makes that device prove itself again before it can claim; use it on a device you have caught cheating, with a reason (recorded).
Loading…
XP checkpoints decide themselves: inside the radius they are accepted, whatever the risk score, and outside it they are rejected and the player can walk back to claim again. Their risk still feeds automatic review above. Only a final checkpoint (a find) is held, when its risk score reaches the line: two or more things look wrong, such as a failed App Attest check, a simulated or teleporting approach, or no recorded walk-in. Accepting one here awards its XP and the find's GLC, the leaderboards follow, and the player gets a push that opens their outcome. Your note is shown to the player if you reject. Disqualify removes the player from that expedition and from every leaderboard.
Loading…
A find verifies itself on arrival — GLC, cash and prizes alike — once its final checkpoint is accepted. It waits here, and inquiries@ is emailed, only when the legend has an open report or the finder's account an open flag, or when its final checkpoint is still held. Cash places settle when the 8-hour upload window closes. Verify needs the player's final checkpoint claim to be accepted (accept it above first if it is held) and a find time inside the evidence window: after the entry and the time seal, before the find arrived. The field is pre-filled with the phone's time when it falls inside. Verifying records the find and pushes the player their place; a cash payout still needs the settlement window and identity verification. Reject voids the claim, frees its slot, and shows your note to the player.
Loading…
Everything below the first section comes straight from our own database, so it matches what actually happened. The vendor sections need their own logins connected before they show anything — and they say “not connected” rather than showing a zero, because a zero you believe is worse than a blank.
Winners of a place, newest first. Two kinds of money pay a place: sponsor cash, held by Stripe and sent to the winner's own Stripe account with Send Stripe payout; and LCL's pot, the money Lost Coin Legends selected the legend for, which you pay from LCL's own account and then record here. Both need the find approved as paid. A Stripe payout can be approved before the winner is ready: it is held, the winner is told to verify their identity and set up payouts (Stripe takes their tax details), and it is sent the moment they finish (reminders at 3 and 10 days; inquiries@ is emailed at 14). LCL's own payment still needs the winner verified first. Only staff managers can move or record money.
Loading…
When a winner deletes their account, what they were owed goes back to the pool and the expedition is held: no next winner is awarded until a person checks it. Release a hold once you have looked (your note is recorded); the next finder in line is then given the place.
Loading…
Expeditions holding sponsor or creator money in Stripe. Refund returns every payment on the expedition to whoever paid it, minus nothing (Stripe keeps its card fee). It is refused once a winner's payout has been approved from it. An expedition holding money cannot be erased until it is refunded. Staff managers only.
Loading…
Physical prizes on their way to the first verified finder. The winner adds an address in the app; it is encrypted and the creator never sees it. The creator chose a USPS Flat Rate box and paid its postage in Lore Mode (LCL never pays a creator's shipping); when the winner's address arrives the label is bought on that postage, a USPS price rise is charged to the creator's saved card, and the creator gets the QR code by email and in the app to show at a Post Office. Nothing is ticked by hand: carrier tracking alone marks it shipped and delivered. inquiries@ is emailed if the carrier hasn't scanned it 48 hours after the address, hasn't delivered it 7 days after the first scan, or returns it — and for any prize a label can't be bought for. Official expeditions are LCL's to ship: buy the label here, or ship another way and enter the tracking number. Addresses are shown to staff managers only. After delivery the winner has 14 days to confirm it is the item promised, in the condition promised, or report a problem with photos (required); silence counts as received as promised. A report emails inquiries@, flags the creator, and waits here with its photos for you to mark it settled (the winner is told how).
Loading…
Once a day the server compares the Stripe balance with what is held for prizes and not yet paid out, and emails inquiries@ and pushes staff managers if Stripe holds less. Don't send a payout while this shows a shortfall.
Loading…
The two checks on GLC: drift (the treasury's running totals against the ledger; must be zero) and the chain (every ledger row's hash links to the one before it; a break means a row was edited). Below them, the newest ledger rows.
Loading…
Two kinds of winnings. Cash goes through Stripe, which collects each winner's tax details in payout onboarding and files their 1099s — keep 1099 reporting on in Stripe → Settings → Connect, and LCL reports none of it (shown here for reference). Prizes — physical rewards from LCL, sponsors and other players — are LCL's to report, at the value the creator stated, in the year they were delivered (box 3, "Other income"). A 1099-MISC is due by January 31 for a winner whose prize value reaches the year's threshold ($600 for 2025, $2,000 for 2026 — set each year below). That winner signs a new W-9 in the app each such year before the prize ships, so the address is current. "View W-9" opens the signed form to print; the CSV holds full Social Security numbers and addresses for the filing service or IRS IRIS. Every opening of a full number is logged.
Loading…
Where players live, from the home postal code they give on their profile. Pots are funded from subscription net profit where subscribers are — judge by city first, then state, then country, then continent. Totals only; no individual is ever listed.
Loading…
LCL funds expeditions near its subscribers (Terms §9). Postal codes ranked by active subscriptions — players who live there and hold an active subscription — optionally within one state; beside each, the open expeditions nearest it (distance to the public zone centre), with ♥ fondness as the measure of how exciting players find them and what the pot holds now. Type an amount beside an expedition and "Fund with Stripe" opens a Checkout to pay it into that expedition's pot. Stripe funding is taken only before an expedition opens. Counts only; no player is listed.
Loading…
Loading…