Robinhood Chain · chain 4663

Write it. The coin
buys itself back.
You get paid.

Post a thesis on a coin you hold. Its own fees fire a buyback, burn what they buy, and pay you 30% of the run.

See how a run firesWhy the wallet is a contract
Burn
60%
Writer
30%
Caller
5%
Protocol
5%

Fixed at deploy. There is no function that changes these.

scroll

The machine

Six steps. Every one of them checkable.

Nothing behind a casing. Every gate, weight and address the engine uses is published, along with the reasoning for each one.

The fee lands in a contract
Not a wallet. No owner, no withdraw, no upgrade.
Anyone fires the run
A stranger with gas is paid 5% for pressing it.
One transaction settles it
Buys, burns, pays the writer, records the receipt.
Walk the six steps

Verify

Paste any vault address.
Ours or theirs.

The page reads the bytecode and prints what it finds. Point it at a competitor’s fee wallet and read the result out loud.

  • ✓bytecode matches the published BackVault build
  • ✓no owner, no admin, no proxy, no upgrade path
  • ✓no function can transfer ETH to an arbitrary address
All five checks

$BACK

Here is our fee wallet.
Find the withdraw function.

The only coin fed by every other coin, running on the same contract as everything else here, with no exception written into the code for it.

How $BACK burnsRead the docs

Contract address

pre-launch

Not launched yet

The address will appear here, and nowhere else first.

Only trust an address published here or on the official X account. Anything sent to you in a direct message is a fake.

The problem

Attention already moves these coins. None of it reaches the coin.

Two generations of sites have tried this. Each fixed one thing and left the important thing alone.

01

The writing is free labour

People argue the case for a coin every day, in public, for nothing. The writing moves the price. The writer is never on the receipt.

02

The fee wallet is somebody's wallet

The first sites to turn writing into a buyback kept each coin's fees in an ordinary address whose key one operator holds, and only that operator's server could spend it.

03

The writer's share is a dial

The sites that do pay writers make the share a per-coin setting. We read one platform's public API and found live coins advertising thesis rewards with that share set to zero.

04

Nothing is checkable

Every number on those homepages comes out of a private backend. There is no way to verify a single claim without asking the people making it.

The machine

Six steps, and every one of them is checkable.

This is the whole product. Nothing behind it is a dashboard you have to believe.

  1. 01

    Somebody trades

    4% comes off the quote leg of every buy and every sell, the same on every coin here.

    proofWritten into the token record at creation. No setter exists.

  2. 02

    The fee lands in a contract

    Not a wallet. A BackVault with no owner, no withdraw function and no upgrade path. It holds exactly one coin's money.

    proofRead the verified source. Look for a function that moves ETH to an arbitrary address. There isn't one.

  3. 03

    A holder publishes a thesis

    Written in the social app, not here. The author must already hold the coin. No signing, no gas.

    proofWe cannot write one. That is the point of it living somewhere we do not own.

  4. 04

    The attester signs a fact

    This text, this author, this wallet, this timestamp, this coin. A typed receipt, nothing more.

    proofThe signer can decide when a run happens. It can never decide where money goes.

  5. 05

    Anyone fires the run

    The writer, a bot, a rival, a stranger. The contract checks the receipt, the holding, the cooldown, the budget and the price impact.

    proofPermissionless by design. If our server dies, the coins keep running.

  6. 06

    One transaction settles it

    Market-buys the coin, burns every token it bought, pays the writer, pays the caller, and records the receipt hash so it can never be claimed twice.

    proofEvery figure on this site links to the transaction that produced it.

The split

Four numbers, written at deploy, with no setter.

On the closest live competitor the writer's share is a per-coin dial, and we found coins advertising thesis rewards with that dial set to zero. Here it is bytecode.

60%

Burn

buys the coin, destroys what it buys

30%

Writer

the person whose thesis fired the run

5%

Caller

whoever paid the gas to press it

5%

Protocol

buys and burns $BACK

Run simulator · the contract’s own maths

live

Fees at 4% = 0.8 ETH per day

  • Burn0.48 ETH
  • Writer0.24 ETH
  • Caller0.04 ETH
  • Protocol0.04 ETH

Your cut as the writer

0.12 ETH

Scaled by your holding against the 2% cap. Hold 2% or more and you take the full 30%.

pay = budget × 0.30 × min(hold, 2%) / 2%

A model, not a promise. Every figure here comes out of fees the coin actually collected. A coin with no trading collects nothing and pays nothing.

Custody

The mechanic is proven. The custody is the product.

Everything below is the difference between a mechanism and a service you have to trust.

Thesis-reward sites today

fomoback

The coin's fee wallet is an ordinary address whose key an operator holds
The fee wallet is a contract with no owner and no withdraw path
Only the operator's server can fire a run
Anyone can fire a run, and is paid a tip for the gas they spent
The writer's share is a per-coin setting a launcher can set to zero
The split is written at deploy and has no setter. Every coin pays 30%
Payout maths lives in a private backend
Payout maths lives in the contract. Read it yourself
One launch flow asks the user to paste a private key into a web form
We never take a key. Every action is a wallet signature
Platform stats are mostly the platform's own coin
We publish the breakdown with our own coin excluded

The attester can

  • yesDecide which thesis receipts get signed
  • yesTherefore decide the timing of runs

The attester cannot

  • noMove a single wei out of any vault
  • noChange the split, the caps or the cooldowns
  • noPay an address that does not hold the coin
  • noPay the same receipt twice
  • noStop anyone else firing a clock-driven run

Worst case with a fully malicious attester: fees the coin already earned get spent buying that coin back sooner than they otherwise would, bounded by the same 2% impact cap, with 30% going to holders who were named. That is the entire blast radius.

The gates

What the contract refuses to do.

Every one of these is enforced in the vault, not in a backend rule somebody can edit.

Budget floor

run must be worth more than its own gas

Cooldown

10 minutes minimum between runs on a coin

Writer cooldown

6 hours per writer per coin

Impact cap

the buy may not move price more than 2%

Replay guard

each receipt hash pays exactly once, ever

Clock floor

20 minutes, so a silent coin still deploys its fees

Attack

Spam theses to drain a coin's fees
Budget is capped by what the coin actually earned, plus a 6-hour cooldown per writer. A hundred posts buy exactly what one post buys.
Buy a bag, write, dump, repeat
Holding is measured at publish and at payout, and the lower one wins. The 24-hour sell flag is permanent and public on your record.
Sybil the handles
Payout scales with share of supply, not handle count. Splitting one bag across ten wallets splits the payout ten ways.
One whale takes every payout forever
Counted holding is capped at 2% of supply, which a mid-size holder reaches too.
Sandwich the buyback
The 2% impact cap keeps the extractable amount small, and run timing is not announced ahead of execution.
Fork it and zero the writer share
Anyone can deploy anything. Our answer is a reader, not a lock: paste their vault into Verify and it prints their real split.

Verify

Paste any vault address. Ours or theirs.

The page reads the bytecode and prints what it actually finds. Point it at a competitor’s fee wallet and read the result out loud. That is the whole defence against somebody forking this and quietly zeroing the writer.

  • ✓bytecode matches the published BackVault build
  • ✓no owner, no admin, no proxy, no upgrade path
  • ✓no function can transfer ETH to an arbitrary address
  • ✓split reads 60 / 30 / 5 / 5
  • ✓fee recipient on the token record equals this vault
A ribbon of records running to a vanishing point

$BACK

The only coin fed by every other coin.

It runs on the same contract as everything else here, with no exception written into the code for it.

Contract facts

Supply
1,000,000,000
Team allocation
0%
Presale
none
Distribution
100% fair launch on the curve
Pair
ETH
Graduation
4.2 ETH into the curve
Creator fee
4%, both directions, fixed at creation
Fee recipient
$BACK's own BackVault contract
A stack of coins dissolving upward into embers

Two directions at once

Its own trades pay 4%, and 60% of each run burns $BACK. Every other coin’s runs send 5% to the $BACK vault, which burns $BACK with it. Supply destruction, not a payment to holders.

Open

no bag
  • Launch a coin
  • Write and get paid
  • Fire runs and take the tip
  • Read every number

Reader

0.1%
  • Watchlist alerts when a run is ready
  • Writer badge on your rows

Caller

0.5%
  • Machine-readable runnable-coins feed
  • Tie-break priority in the run queue

Desk

2%
  • Bulk receipt endpoint for desks and bots
  • New venue integrations land here before they are announced

What this will never do

  • neverGate the core loop behind the platform token
  • neverTake a cut of the writer's 30%
  • neverCharge a fee to write or to claim
  • neverAsk anyone for a private key
  • neverAdd a setter to the split

Revenue

Where the money comes from, in full.

015%

Protocol share of runs

Of every run's budget, across every coin, paid in the same transaction and routed to the $BACK vault, which buys and burns $BACK.

024%

$BACK's own creator fee

$BACK trades pay exactly what every other coin pays. It lands in its own vault and is spent the same way, with no exception in the code.

030%

Launch fee

The launchpad charges its own flat fee. We add nothing on top. Launching here is not a business.

Architecture

One trusted component, and it holds no money.

Social feed

Third party. Theses, handles, linked wallets. We do not host it.

Attester

Signs typed receipts. Holds no funds. Can time a run, never move one.

Public receipt feed

Anyone can read it. Anyone can submit from it.

Callers

Our runner and any stranger with gas, competing to press the button.

BackVault

One per coin. Receives the fee, verifies the gates, buys, burns, pays.

Indexer

Chain events into a read model. Reconstructible from scratch if lost.

Roadmap

Phase 0 is a gate, not a milestone.

If the launchpad will not accept a contract as the fee recipient, the design changes before anything else ships. We would rather find that out in week one.

Phase 0

Prove the plumbing

week 1current
  • ·Confirm on chain that the launchpad accepts a contract as fee recipient
  • ·Confirm the fee claim can be called by that contract
  • ·Run one full cycle end to end for a few cents
  • ·Gate: if a contract cannot be the recipient, the design moves to our own swap hook first
Phase 1

MVP

weeks 2-4
  • ·BackVault final, tested, verified source on the explorer
  • ·Attester service and public receipt feed
  • ·Indexer, coin pages, run history
  • ·Launch flow, wallet signature only
  • ·Verify page working against any address
Phase 2

Launch $BACK

weeks 5-6
  • ·Deploy $BACK through our own public flow
  • ·Team buy addresses disclosed before the first block
  • ·First live runs with real writers
  • ·Writer leaderboard opens
Phase 3

Growth

months 2-3
  • ·Open-source caller bot
  • ·Second social source, so no single feed is a chokepoint
  • ·Embeddable run widget
  • ·Independent review of the vault contract
Phase 4

Ecosystem

months 4-9
  • ·Any existing coin can point its creator fee at a vault without relaunching
  • ·Multi-venue support as the chain's DEX landscape moves
  • ·Writer payouts in the coin instead of ETH, writer's choice
  • ·A receipt standard other sites can adopt

Decisions

Every choice, and why it was made.

Decision

Vault is a contract, not an operator-held wallet
The entire differentiator. Both live competitors hold keys.
Split fixed at deploy, no setter
A competitor's per-coin dial is already set to zero on live coins that advertise rewards.
Anyone can fire a run, caller paid 5%
Liveness without a funded keeper, and a cost we do not carry.
Writer must hold the coin
Makes the tagline literally true and kills spam without a content filter.
Counted holding capped at 2%
Stops a single whale owning every payout forever.
Core loop never gated by $BACK
Gating it would tax the product we are trying to spread.
Never accept a private key
A competitor's launch form asks for one. Being the opposite is free positioning.
Attester signs facts only
Reduces trust from custody to timing, and we say so out loud.
Self-claim escape hatch
The system outlives the team.
Ship on the existing launchpad, not our own hook in v1
The fee-to-recipient path is already proven live by others.

The honest part

What we watch, what we ignore, and what could kill this.

Watched

  • ·ETH paid to writers per day
  • ·Distinct paid writers per week
  • ·Runs fired by callers who are not us, as a percentage
  • ·Coins with at least one run in the last 24 hours

Deliberately ignored

  • ·Total coins launched
  • ·Platform token market cap
  • ·Any headline number that is mostly our own coin

Strengths

  • +The mechanic is already validated by somebody else's money
  • +Nobody has shipped the non-custodial version of it
  • +Liveness does not depend on us being alive
  • +Every claim on this page is checkable on chain

Risks we are not hiding

  • −We are late. Two sites shipped first and one is paying writers today.
  • −The attester is still a trusted party. Reduced and bounded, but real.
  • −The thesis feed is a third-party dependency run by a small team.
  • −The category may be a one-week meta. The first site's own coin fell heavily within a day.
  • −No volume, no product. Every payout comes out of fees a coin actually earned.

Plainly

What this is not.

Not free money

The 4% comes out of the people trading the coin and goes back into the same market. It changes who holds the supply and when the buying happens.

Not a price floor

A coin can only spend what it earned. On a quiet coin that is a small number, and a small buy into a falling market is a small buy into a falling market.

Not a judge of writing

The contract counts theses. It does not read them and cannot score quality.

Not a reason to buy a dead coin

No fees, no runs, no payouts. The mechanism amplifies activity. It does not create it.

Here is our fee wallet.
Find the withdraw function.

Every gate, weight and address, published and checkable.

Read the docsFollow on X