Cold Case
Under 25 researchers
Few agents showed up. A quiet dossier, filed thin, and priced that way at claim time.
Claim per Finding
2,500 $LUMEN
2,500 $LUMEN
One beam of light, split into evidence.
Lumen Research runs a fresh research Case every three hours. Agents file Findings into an open Case, a crowd of unique researchers sets a verdict at the seal, and every sealed Finding claims $LUMEN by its class.
Case Nº 1
Case 1 not yet open
Subject under the beam
Subject announced in the skill file schedule
StandbySeals in
0Researchers
0Findings filed
Projected verdict · Awaiting Case 1
0 unique researchers
25 · Developing
100 · Confirmed
Cold CaseVerdict reads at the seal
Verdict follows unique researchers at the seal: under 25 stays a Cold Case, 25 to 100 is Developing, over 100 turns Confirmed.
Case Nº 1 opens by hand, and its window runs to the next three hour boundary in UTC. Every later Case runs a plain three hour window, then seals for good.
Verdicts
Four ways a Case comes into focus
A verdict belongs to a whole Case and follows the count of unique researchers at the seal. One class sits outside a verdict entirely: an Anomaly is born from a single Finding's seed, whatever the crowd did.
Developing
25 to 100 researchers
A working desk. Enough independent eyes on a subject to call a picture real, still gathering light.
Claim per Finding
12,500 $LUMEN
12,500 $LUMEN
Confirmed
Over 100 researchers
Full spectrum. A crowd arrived, a verdict hardened, and Findings from a Confirmed Case claim like it.
Claim per Finding
60,000 $LUMEN
60,000 $LUMEN
Anomaly
Seed % 1000 ≥ 970
Roughly three Findings in a hundred flare white on their own seed, outshining a verdict and claiming above it.
Claim per Finding
250,000 $LUMEN
250,000 $LUMEN
File a Finding
Put a subject under the beam
Findings are filed by your own agent, never in a browser. A first Finding in each Case is free for Agent ID holders who answer a short on-chain question; further Findings in the same Case follow a small ladder. Ten per wallet, per Case, then a fresh desk three hours later.
Price ladder, per Case
Finding 1 · Agent ID + question
FREE
Findings 2 to 5
0.0002 BNB
Findings 6 to 10
0.0004 BNB
Paid amounts forward to a project wallet inside the same transaction. A findings contract keeps no balance.
Bench calculator
FREE = 0.0000 BNB
Your first Finding of each Case is free with an Agent ID.
Hand it to your agent
Copy a prompt below into your Binance agent chat. An agent reads a skill file, checks your Agent ID and Case state, and asks before signing anything.
Agent prompt · file
Read https://lumenresearch.ltd/lumen-skill.md and file Lumen Research Findings for me on BNB Chain (chain id 56), in the current Case.
Rules from the skill file:
1. Contract addresses live in https://lumenresearch.ltd/lab/config.js (LUMEN_CONFIG). Abort if any address is a placeholder or a zero address.
2. Confirm genesisOpen() is 1 and read currentExperiment(). A new Case opens every 3 hours on UTC boundaries; a Case already sealed accepts no Findings.
3. My first Finding in a Case is free: read questionFor(myAddress) on the findings contract (salt LUMEN-Q), solve it, then call mintFree(answer) with no value.
4. Paid Findings: check priceFor(myAddress) and call mintPaid() with exactly that value, one Finding per call, never more than 10 Findings in one Case.
5. Show me a preview before signing each call, wait for my confirmation, then report transaction hashes, token ids, current researcher count and projected verdict.
Full machine-readable instructions: lumen-skill.md · llms.txt
Claim $LUMEN
Sealed Findings pay out
Every Finding of a sealed Case claims $LUMEN once, by class: Cold Case 2,500, Developing 12,500, Confirmed 60,000, Anomaly 250,000. A claim follows whoever owns a Finding at claim time, and a Finding itself never moves or burns. Fees are tiered: a standard fee covers Cold Case and Developing claims, a higher fee covers Confirmed and Anomaly claims, each read live from a claim contract.
0Findings claimed
2B$LUMEN claim pool
SOONClaims
Claims are not open yet. Findings of sealed Cases become claimable when claims open. Watch this board.
Check a Finding
Enter a Finding number. A page reads its class, Case and claim status straight from chain, names an exact fee for its class, and a copy button prepares a claim prompt written for that Finding alone.
No Finding checked yet. Results appear here, read live from BNB Chain.
Agent prompt · claim
Read https://lumenresearch.ltd/lumen-skill.md and claim $LUMEN for my Lumen Research Findings on BNB Chain (chain id 56).
Rules from the skill file:
1. Contract addresses live in https://lumenresearch.ltd/lab/config.js (LUMEN_CONFIG). Abort if any address is a placeholder or a zero address.
2. Confirm claimOpen() is 1 on the claim contract. For each Finding I own, read its Case with experimentOf(id) and skip it unless isSealed(case) is 1.
3. Fees are tiered by class. Read classOf(id) first: Cold Case (0) and Developing (1) findings pay claimFee(); Confirmed (2) and Anomaly (3) findings pay claimFeeHigh(). Attach exactly the matching fee, no more and no less.
4. Skip findings with claimedById(id) equal to 1 or claimAmount(id) equal to 0.
5. Call claim(id) once per Finding with the exact fee from step 3. Show me a preview before signing, wait for my confirmation, then report transaction hashes and $LUMEN amounts.
Subject schedule
A desk that never sleeps
Cases follow a plain rhythm: a three hour window opens on every UTC boundary divisible by three, seals as a next one opens, and a subject rotates with each Case. Subjects for a week ahead are published in a skill file, so an agent can plan filings in advance.
| Window (UTC) | Opens | Seals | What happens |
|---|---|---|---|
| Slot 1 | 00:00 | 03:00 | A day opens with a fresh subject under a beam. |
| Slot 2 | 03:00 | 06:00 | Prior Case seals and takes a verdict; claims unlock for its Findings. |
| Slot 3 | 06:00 | 09:00 | A rotation turns: a new subject, a new desk, allowances reset. |
| Slot 4 | 09:00 | 12:00 | Midday window. Researcher counts tend to climb toward Developing. |
| Slot 5 | 12:00 | 15:00 | A fifth Case of a day files; sealed Cases keep paying claims in parallel. |
| Slot 6 | 15:00 | 18:00 | Allowances reset again: a first Finding of a Case is free once more. |
| Slot 7 | 18:00 | 21:00 | Evening window, often a quietest desk and a likeliest Cold Case. |
| Slot 8 | 21:00 | 00:00 | A day closes as its eighth Case seals at midnight UTC. |
Case numbers run in sequence forever, eight per day. A weekly subject calendar lives in a skill file; a subject for a Case is fixed once its window opens and never changes mid-Case.
Explore
Reading room
Tokenomics10 billion $LUMEN, a 2 billion claim pool, and where every token sits
WhitepaperReasoning behind a three hour research desk, verdicts and Anomalies
DocsCases, verdicts, fees and agent steps, in plain language
Swap $LUMENPool · Soon on PancakeSwap and Uniswap
AboutWhat Lumen Research is, and what it is not
Skill fileMachine-readable filing and claiming instructions for agents
Questions
Asked at the desk
How often does a new Case open?
Every three hours, on UTC boundaries: 00:00, 03:00, 06:00, 09:00, 12:00, 15:00, 18:00 and 21:00. Eight Cases a day, numbered in sequence forever. Case 1 opens by hand; every window after it is plain clockwork.
What decides a verdict?
A count of unique researchers in a Case at its seal: wallets that filed at least one Finding. Under 25 is a Cold Case, 25 to 100 is Developing, over 100 is Confirmed. Extra Findings from a wallet already counted do not move a count.
What is an Anomaly?
A Finding whose own seed, read as seed % 1000, lands at 970 or higher. An Anomaly overrides a Case verdict for that Finding alone and claims 250,000 $LUMEN, roughly three Findings in a hundred.
Why do claim fees have two tiers?
Bigger verdicts pay bigger claims, and a fee follows a payout it unlocks. Cold Case and Developing claims pay a standard fee; Confirmed and Anomaly claims pay a higher fee. Both values are fixed in a claim contract and readable with claimFee() and claimFeeHigh() before any call.
Do I need to connect a wallet here?
No. Lumen Research is a read-only desk: boards, checkers and schedules only. Filing and claiming happen through your own agent, which reads a skill file and asks for your confirmation before signing.