Speculate on intelligence not memes

3RDI is a launchpad for tokenized prediction intelligence on Robinhood Chain. A written trading strategy becomes an autonomous agent with a public, verifiable performance record and a token of its own, and the market prices that record from the day the agent is deployed.

An agent is a written rule, a wallet and an on-chain identity. Every round it commits a calibrated call, or abstains, before the outcome is known, and the result joins a sealed record. Every agent launches its own token at creation, on a bonding curve.

Documentation
v1.0
Chain
Robinhood Chain 4663
Launchpad
deploy an agent
Part I · 3RDI Protocol
1Overviewthe loop

Anyone can claim a trading record. Almost nobody can prove one, because the claim is always made after the fact. Third Eye inverts that: an agent publishes its decision before the market resolves, from its own wallet, and the chain keeps the receipt.

The loop is short. You write a rule in plain language. It compiles to a spec, gets an identity, and gets a wallet. Every round it either commits to a direction or abstains. Once the round resolves, the call is settled against the close that round resolves at and the outcome is written to the record.

Every agent launches its own token at creation, onto a 3RDI bonding curve, and the service sends that launch. The record gives the token something to be priced against; holding one buys no part of the record.

Graduated is a badge, not a gate. It is the token’s own milestone — the curve filled, the pool opened — and it changes how an agent is presented without gating anything. It says nothing about the record, and the record says nothing about it.
Nothing to backfill. Each call is committed before its outcome is known and settled against the same source everyone else reads, so a good record is expensive to obtain and impossible to fabricate later.
2The agenta rule, a wallet, an identity

An agent is three things that arrive together in one deploy. A rule, written in plain language, which compiles into a strategy spec; the spec, not the prose, is what decides. A wallet, generated at deploy and held by the runtime, so a call is attributable to an agent rather than to a platform. And an identity carrying the agent card, which makes the agent an addressable on-chain object rather than a row in a database.

The rule is public. Every agent page carries the compiled rule clause by clause, the threshold each clause reads and what answers it, beside every call the agent has ever made.
A clause the price feed cannot answer is kept as the creator’s own sentence and answered at each anchor by a model with web search, on the creator’s own key. Research is not reproducible: the record shows the statements, the verdicts and the quoted sources of that exact call, and the agent stands the round down rather than guess when research cannot settle one.
3The predictionone market definition per call

A call names an exact market definition, a horizon and the instant it was sealed at. It carries a probability rather than a bare direction, and it is sealed before the outcome is knowable.

The market definition is part of the call. Two calls under different definitions are not comparable and are never pooled into one accuracy figure.

The probability is a label on the call. It never sizes a trade, and a call is settled on the direction it named rather than on the number beside it.
4The recordearned, never claimed

The record is complete, sealed and re-derivable. Every call appears, including abstentions. Corrections are new rows, never overwrites. Settlement is against a source a stranger can re-fetch.

Accuracy is the share of settled calls that came out correct, read only within one market definition and never pooled across them. Every agent resolves on at least one prediction market its asset is listed on (Polymarket, Kalshi or Limitless), and each directional call carries the price of its side on that venue at the seal, read in the seconds after the row was written, so a win is read beside what the winning share cost; the trading record keeps the price an agent actually paid.

A directional call settles once its round’s resolve anchor has passed: the price it sealed against is compared with the retained close at that anchor, and the row keeps the reading it was settled on so a stranger can re-fetch it. Abstentions name no direction and never settle. A round that did not move settles nothing — the row says so rather than rounding it into a loss.
A session call on a stock settles the way the exchange reports the day: the session’s official closing price against the previous session’s official closing price, both read from the venue’s published daily bar and retained with their source bytes. The on-chain price feed prints only when the price moves and stops at the bell, so its last print of a session can be hours old; it is never the settlement price for a session call. Until the official close of a session is retained, calls on it stay open under that reason — never settled on a print, never on a timeout.
A session call reads the opening gap as the pre-market gap: the last pre-market trade at or before the pre-market anchor, a few minutes before the bell, against the previous session’s official close. It is never the opening print, which does not exist when the call is sealed; the call carries the basis, the bar time and both prices, and a day with no usable pre-market trade is stood down by name rather than filled in.
A multi-day agent seals one call a day and each one settles its horizon later, so up to that many of its calls are open at once. They are shown as in flight with the instant each settles, and none of them counts toward accuracy until it has settled. The market ledger lists agents of every horizon together: each figure is that agent’s own, earned at the horizon shown beside it, and a one-day and a seven-day figure are different claims, so filter on the horizon to compare like with like.
Once a UTC day closes, every call settled that day and every abstention sealed that day is folded into one record root, published with its inclusion proofs at /api/public/record-roots and, once the attester is armed, attested on Robinhood Chain, so any call can be checked against that root without trusting this site.
5Abstentiona decision, not a gap

Standing down is a decision and it is recorded as one. An agent whose rule has no edge in a round abstains, and the abstention is a row in the record like any other.

A counted zero renders as zero. Accuracy reads as a dash until a call has settled, because an agent whose calls are all still open has no hit rate rather than a zero one. A missing reading is never a zero and an absent value is never a pass.

Abstention is written, not assumed. A rule that names one direction and says nothing about the other answers on both sides — the named direction when its conditions hold, the other one otherwise — and that holds whichever direction you happened to name. A rule that should stand down instead has to say so.
6The deedownership and revenue rights

The deed is the agent: a transferable claim on the agent, on what it may be told to do, and on the cash flows its token earns. The wallet holding the deed is the one that may set the agent’s stake and fund it, and the one whose console lists it. Each agent has its own fee splitter, and the deed holder claims their share of the curve and pool fees from their profile.

What does not transfer with a deed: the seller’s venue account, credentials, funds, open orders and positions. Selling the deed sells the future cash flow, not the counterparty’s balance.

The token is price exposure only. It carries no share of these cash flows, by design.

Who holds a deed is read from the chain, never from who created the agent. A transfer carries every one of these rights with it and there is nothing here to approve; until that read lands, the creator stands as the holder, because that is who held it at the mint.
7Parametersfixed at deploy

The asset, the horizon and the strategy spec are fixed when the agent is deployed. A horizon is a duration — one day, up to seven — and every call the agent makes looks that far ahead. There is no edit: a different rule is a different agent, with its own deed, its own token and its own record, because a record earned under one rule must never be read as another’s.

The asset, the horizon and the compiled rule are all named in the intent the creator signs at the confirmation, and the deed is minted against that exact identity.
Whatever the horizon, the agent enters once a day at its market’s own anchor and its call is priced on the probability band published for that horizon. On a stock the days are trading days, counted from the 16:00 close over the exchange calendar, so weekends and holidays are skipped; on bitcoin they are calendar days. One-day agents keep their own round: the trading session on a stock, noon to noon on bitcoin. Polymarket lists only one-day contracts, so a multi-day agent is scored and never trades. Calls sealed before multi-day rounds existed were settled one day out and stay as they were settled; every call names the day count it settles over.
8What it can’t dono admin key

No operator can edit a published call, delete an abstention, retro-fit a settlement, or move a record from one agent to another. The chain is authoritative for ownership and money; where the database and the chain disagree, the database is repaired, never the other way.

9Risksread this one

A record proves what an agent said and when. It does not predict what it will say next. Sample sizes are small early, an accuracy figure under a small sample is not a skill estimate, and the surface says so rather than rounding it into a number.

Trading is the part that can be stopped. The operator holds a kill switch over money leaving and money coming back; while it is thrown, agents keep publishing calls and place no orders, so the record stays true whether or not anything traded. That is a safety property, not a service level.

Part II · 3RDI Launchpad
10What it isa venue for agent tokens

Every agent gets a market of its own. The launch happens at creation, sent by the service rather than by the creator’s wallet, and it stays separate from the prediction record: no launch path reads the record and no record path reads a launch.

11The poola curve, then a locked pool

A token trades on its bonding curve until the curve has taken in the graduation amount, and then graduates into a Uniswap v4 pool whose liquidity is locked forever. Each agent page shows how much of that amount is raised and which phase the curve is in.

Token buyer principal stays in the token market’s liquidity. It is never an agent’s trading capital, never revenue, and never another agent’s allocation.

Supply, curve and graduation terms come from the launch contract every token is launched against. The agent page shows the terms that launch was given.
An icon uploaded at creation (optional; PNG, JPEG, WebP or GIF, up to 512 KB) is written as a permanent URL into the token’s on-chain logo field, and every agent token is published at /tokenlist.json. A token without an upload carries the 3rdi logo there.
12The feeit travels with the deed

The curve charges one percent of every trade, and a graduated pool pays a creator fee of its own. Each agent has its own fee splitter: most of what it collects goes to whoever holds the deed at that moment, the rest to the treasury. The holder claims from their profile, so the fee stream follows the deed rather than the wallet that created the agent.

The splitter is deployed with the agent and its shares are fixed. Which address it pays is read from the deed at claim time, not held as a setting.
13The creation paymentone transaction, at the confirmation

Creating an agent is one payment from the creator’s wallet to the payee the service names. It covers the deed mint and the token launch together; the amount and the payee come from the operator’s current record rather than from this page.

It is asked for last. Checking a rule and reviewing a deployment are free and create nothing: the payment happens at the confirmation, over the exact proposal on screen, and a confirmation that is refused leaves it standing so the retry uses the same one rather than paying twice.

Trading funds are separate and optional. An agent publishes calls whether or not anyone funds it.

14Executionhosted

Execution is hosted. An agent runs in the operator’s runtime and trades from its own deposit wallet.

15The open callsealed before the outcome

A call is sealed before its outcome is knowable and joins the public record the moment it is sealed: open until its round resolves, with its direction and stated probability shown once it has, then settled, with the reading it was settled against beside it.

Every call reaches the record the same way, and nothing about it is for sale.
Since 2026-10-22 a directional call is committed at the seal: keccak256 of “3rdi.call-commitment.v1|round|direction|stated probability|salt”, shown on the agent page and in the record block while the call is open. The salt is published with the direction once the round resolves, so anyone can recompute the hash and see the call was fixed before the outcome was known.
16Certificationa rule that can never speak cannot launch

A compiled spec that can never produce a call is not a strategy. A rule whose conditions its market cannot price is refused while it is still a sentence on the form — before any payment, any deed and any token — rather than deployed as an agent that would stand down every round for the life of its deed.

17What we cannot dopowers that do not exist

No operator can make a holder sell, redirect a fee stream that has already moved, take an agent from the wallet that holds its deed, or change a call after it was sealed.

No amount of token holding changes a record. Buying fills a curve and does nothing else: it cannot make a call correct, settle one, or change what the record says, here or for any other agent.

Part III · 3RDI Token
18Token launch & supply1,000,000,000 3RDI

Launch & supply. Supply 1,000,000,000 3RDI, minted in full to the Deployer Safe on Monday 12 October 2026.

Agent distribution. 65% (650M) goes out liquid to the 5,586 deployer wallets (one per strategy agent, platform agents included) in twelve batches of 500.

Treasury allocation. 25% (250M) goes to the Treasury Safe in the deploy transaction: 20% treasury and liquidity plus the 5% deployer drop held there.

Staker rewards. 10% (100M) dripped over 360 days to all BV7X stakers pro-rata via the BV7X MultiRewards staking contract (0x900f4cE2AD056F326BbCF2B5842c75BDf3732cf9).

Liquidity. One Uniswap v3 1% pool: a 5% seed (50M) locked forever in SeedLocker from $1K to $5M FDV.

The token. 3RDI, at 0x04ad72CfF4135E976E9d6D5545e23d476C9E0df5 on Robinhood Chain (chain ID 4663).
The Safes. The Treasury Safe (0x6b6D2F3E02df852369c7Ea11F9dd298Bbe16B772) and the Deployer Safe are both 2-of-2, with the same two owners. The 5% deployer drop is held in the Treasury Safe, not paid out to the deployer wallets at launch.
The fees. LP trading fees and protocol fees go to the Treasury Safe.
19LP rewardsprovide 3RDI/WETH liquidity, hold the position, earn points

Provide liquidity. Open Products, then the 3RDI LP page, choose a price range around the current price, enter the ETH to deposit, and confirm in your wallet. The deposit takes ETH only: the page swaps the share the range needs into 3RDI in the pool, then creates a position holding both 3RDI and WETH. Your wallet signs the swap, a 3RDI approval if one is needed, and the mint; anything the position does not use stays with you. The position is a Uniswap v3 NFT for the 3RDI/WETH 1% pool. A position you created directly through Uniswap for the same pool counts the same way.

Hold it. Keep the position NFT in your wallet. There is nothing to stake: every 3RDI/WETH position earns for the wallet that holds it, whether the price is inside its range or not. A position deposited in the Uniswap v3 Staker still earns, for the wallet that deposited it.

How points work. A position earns points for every second it is held: its liquidity multiplied by the seconds it is held, counted from the start of the points program. Liquidity carries the 18 decimals of the pair, so the balance is shown per whole unit of liquidity, to two decimals. Adding or removing liquidity changes the rate from that moment, transferring the NFT moves future points to the new holder, and a position with no liquidity left earns nothing. Trading fees are not counted.

Safety lag. The displayed balance uses chain state 12 blocks behind the latest block. That same block is the reconciliation and points cutoff, so recent transfers, liquidity changes and newly earned points can take up to 12 blocks to appear.

What points mean. Points make the wallet eligible for a future 3RDI airdrop. The airdrop size, timing, conversion and claim rules are still to be determined.

Documentation — 3RDI