n
nightshift ink@nightshift_ink · 3h
old letterpress in the basement still runs. fed it a post. it printed a coin.
4122.4K18.9K
$FEED · Robinhood Chain · browser extension
The feed is the launchpad.
Launch a coin from any post on X. Twenty seconds, one press.
See a post worth a coin? Press launch before the thread cools. The account that wrote it earns from every trade, whether they know it yet or not.
live demo · the twenty-second loopplays itself · or hover a post
k
kera draws@kera_draws · 5h
drew the whole lore of a coin that does not exist yet. someone please make it exist.
$HOYOmcap $8.4K12 bought herepressed by 0x3c9…a04 · 11m after post
961.1K7.3Kclaimed · locked
one post, one coin ·first press wins ·the author gets paid ·no exemption list, ever ·real curve balances only ·Robinhood Chain ·one post, one coin ·first press wins ·the author gets paid ·no exemption list, ever ·real curve balances only ·Robinhood Chain ·
$FEED · Contract address
PRE-LAUNCHTBA — launching on the chain's pad, same rules as every press
Always verify on the official channels. Anything that is not this exact address is not us.
How it works
Twenty seconds. One press.
The whole product, in the order it happens.
- 01Scroll
You are on the timeline like any other day. A post is going off.
- 02Hover
A small Launch this appears in the post's action row. Only on hover, never permanent.
- 03Press
The side panel opens already filled from the post: name, ticker, image, description. Origin is locked.
- 04Launch
One transaction to the launchpad. Fixed supply, bonding curve, tradable from block one.
- 05Badge
Back on the timeline the post now wears its market. That post can never be launched again.
The problem
Launchpads have a demand problem, not a supply problem.
- 01Launching is already trivial
A recent pad on this chain took 131 launches from 64 wallets in under four hours — and recorded almost no trading against any of them.
- 02The bottleneck is narrative
Sitting at a blank form asking what should this coin be about is where most would-be launchers quit.
- 03Narrative supply is infinite and free
It is scrolling past on X every second, already ranked by an algorithm, already carrying an audience.
- 04The window closes first
Open a site, connect, upload an image, invent a ticker. The gap between seeing and acting is measured in minutes.
- 05The market lives where nobody goes back
The post keeps circulating. The token does not.
Feedpad's bet
Put the launch button where the narrative already is, collapse the gap to one press, then put the market back on the post. Distribution stops being a budget and becomes a property of the product.
The engine
Every token carries our mark into every aggregator.
The launchpad stores a metadata block with every token. It is permanent, public, and read by every chart site. Feedpad fills it deliberately.
written on-chain · per tokenpermanent
| name | from the post |
| symbol | launcher's choice |
| logo | post media, copied to permanent storage |
| description | "Launched from @author's post · Feedpad" |
| socials.website | feedpad.press/t/<postID>← the billboard |
| socials.x | the origin post URL← the provenance |
| creatorFeeRecipient | the fee splitter contract |
| creatorTax | 1–5%, chosen at press, immutable |
| salt | ground for a house address suffix |
The quiet loop
- 01A stranger opens a chart aggregator and finds a Feedpad token.
- 02The token's website field points at feedpad.press/t/<postID>.
- 03Every aggregator renders that button. They click it.
- 04They land on the token page: the original post, the chart, the buyers, one line — launched with Feedpad.
- 05Install, or press a post of their own.
The loud loop
- 01The origin author's share accrues from trade one. No account needed.
- 02They find out — a reply, a tag, or they search their own handle.
- 03They post about being paid for a post they already wrote.
- 04That post is read by the audience that made the coin work.
One launch → one permanent billboard in every aggregator + one motivated human with an audience.
Positioning
Other pads make you go find a narrative. Here it found you.
Other launchpads
Feedpad
You open a website, then go hunt for a narrative
You never leave the timeline; the narrative found you
Blank form: invent a name, ticker, image
Form arrives pre-filled from the post you were reading
Anyone can launch the same idea 50 times
One post, one coin. First press owns that narrative
The person whose idea it was gets nothing
The author earns a share of every trade, automatically
Market lives on a site nobody reopens
Market lives on the post, which keeps circulating
Discovery needs paid ads
Every token carries our mark into every aggregator
Insider wallets quietly exempted from snipe tax
No exemption list is ever passed. Verifiable per token
Scarcity
One post, one coin.
A product rule, enforced honestly — not a chain rule dressed up as one.
- The registry maps post ID → token. First launch wins, ordered by block number.
- The claim is externally verifiable: the post ID is written into the token's own on-chain metadata.
- The extension refuses a second launch on a claimed post and shows the existing token instead.
- Someone can still deploy the same idea directly on the pad. They get no badge, no billboard, no registry entry, no author split. The lock holds because our lane is the good one.
- Quote-posts and reposts resolve to the original post ID. A viral quote cannot relaunch a claimed idea.
registry · first press wins
| post | token | pressed by | when | block |
|---|---|---|---|---|
| 1834…9021@someguy | $SCAT | 0x7a2…f19 | 4m after post | 62,144,829 |
| 1834…7714@kera | $HOYO | 0x3c9…a04 | 11m after post | 62,143,102 |
| 1834…6630@dmt | $BELL | 0xe11…77b | 2m after post | 62,141,880 |
illustrative rows · the live registry is public and readable by anyone
Fairness, verifiable
The snipe window — what we do not do.
The launchpad taxes the first seconds of every token's life: currently three seconds, starting at 99% and decaying to the normal fee. Only the pad's team can change that. We cannot, and we do not ask.
Feedpad calls this
launchToken(params, config, pair)
without exemption list — everyone faces the tax
Feedpad never calls this
launchToken(params, config, pair, exemptions[])
with an exemption list — named wallets skip it
- 01The launcher's opening buy happens inside the launch transaction — the one privileged buy, and it belongs to whoever pressed.
- 02No pre-approved wallet list is ever passed. There is no insider lane because the call shape has no parameter for one.
- 03Anyone can verify this per token: read the launch transaction and check which form of the call was used.
Every competing pad should be asked which form they call.
Fees · the real math
One tax, three parties, one contract.
Chosen by the launcher between 1% and 5% at press time, defaulting to 2%. Immutable once set — the panel says so before you press.
Creator tax
ETH
Launcher's $FEED tier
Fee generated
2% of 10 ETH/day
0.2 ETH / day
Launcher
pressed the button
0.1 ETH/day
50% · 3 ETH/30d
Author
wrote the post
0.06 ETH/day
30% · 1.8 ETH/30d
Protocol
Feedpad
0.04 ETH/day
20% · 1.2 ETH/30d
The launcher and author slices never shrink. We only ever discount our own cut, and the discount goes to the launcher. Feedpad's share of every trade at this setting: 40 bps.
- 1primaryProtocol slice of creator tax
20% of 2% = 4 bps of every trade on every Feedpad token. Scales with volume, not launch count — we profit from tokens that trade, which is the behaviour we are trying to cause.
- 2secondaryPlatform launch fee
A flat fee on top of the pad's own, shown as a line item before pressing. Small by design: a launch fee that hurts suppresses the exact behaviour we want.
- 3structuralUnclaimed author fees
Author shares unclaimed after 90 days route to buyback. Never reported as revenue; the countdown is public per token from day one.
- 4structuralDisavowed token shares
When an author disavows, their slice routes to buyback for the life of the token. Doing the right thing costs nobody anything.
Protocol slice · allocation
Engineering + infrastructure40%
$FEED buyback25%
Author-discovery fund15%
Security review + store compliance10%
Reserve10%
$FEED · utility
Hold it for the edge, not for a promise.
Everything works with zero tokens. Holding buys the tools that make hunting rational, and shrinks our cut of your presses.
SCROLL
hold 0
protocol takes 20%
- ✓Unlimited launches
- ✓Post badges + token pages
- ✓Buy and sell from the panel
PRESS
hold 0.25%
protocol takes 15%
- ✓UNCLAIMED markers on the timeline
- ✓Momentum alerts
EDITOR
hold 1%
protocol takes 10%
- ✓Address suffix grinding
- ✓Verified press badge
- ✓Front-page submission
DESK
hold 3%
protocol takes 0%
- ✓Protocol takes 0% — you keep the full split
- ✓Bulk claim across every token you pressed
- ✓New surfaces the day they ship
What $FEED is never
- — It is not a claim on revenue.
- — It is not required to launch, buy or sell.
- — It does not change the launcher's or the author's slice — only ours.
Supply pressure
- ▸25% of the protocol slice buys back continuously
- ▸100% of author fees unclaimed past 90 days
- ▸100% of disavowed author slices, permanently
- ▸Tier thresholds hold supply off the market while a hunter is active
- ▸Suffix-grinding rights are consumed per launch
Contract facts
- Supply
- 1,000,000,000
- Distribution
- 100% fair launch on the chain's launchpad
- Team allocation
- none
- Presale
- none
- Vesting
- not applicable — there is nothing to vest
- Exemption list at launch
- none passed — same rule as every token pressed with Feedpad
Architecture
The key never leaves the wallet. We write one contract.
The extension builds calldata and hands it to your wallet. It never holds funds and never asks you to sign something you cannot read.
- Content scriptreads posts, injects the hover button
- Side panellaunch form + docked watchlist
- Service workermetadata, quotes, registry
- User walletsigns the one launch transaction
- Registry APIpost ID → token, first press wins
- Image intakepost media → permanent storage
- Launchpad factorytoken + curve
- FEED SPLITTERour one contract — fees only
- Indexertoken pages → aggregators
FEED SPLITTER · the one contract we write
It does
- ✓ receive creator tax for one token
- ✓ hold immutable split shares set at registration
- ✓ let each party pull their own accrued balance
- ✓ expose the origin post ID as a public field
- ✓ route the author slice to buyback on disavow or 90-day lapse
It does not
- ✕ custody anyone's trading capital
- ✕ hold user deposits of any kind
- ✕ have an admin withdraw path over launcher or author slices
- ✕ have an upgrade proxy
A contract that never holds principal cannot lose principal. The splitter only ever touches fee revenue that has already been earned.
Extension permissions · minimum viable
- x.com
- the only site we read
- feedpad.press
- our own API
- chain RPC
- reads and sends
- storage
- wallet address, tier, settings
- sidePanel
- the docked panel
No tabs, history, cookies or broad host access. The listing states what each line is for.
The press room
A track record, not a points balance.
Every wallet that has pressed has a permanent public record, and the unflattering numbers sit next to the flattering ones.
0x7a2…f19press record
- Presses
- how many narratives claimed
- Live rate
- % still trading after 24h
- Graduations
- how many reached the curve threshold
- Median volume
- the honest middle, not the best one
- Speed
- median minutes from post to press
- Authors paid
- total routed to origin authors
Titles · earned, not bought
- FIRST PRESSpressed within 10 minutes of the post
- COLD READpressed a post under 1K likes that then graduated
- THE SCOOPpressed a post that 10x'd after your press
- PATRONover 1 ETH routed to origin authors
- STREAKa live token every day for 7 days
- DRY SPELLshown too. 20 presses, nothing traded. Public.
The attack
The defence
Write a post yourself and press it instantly, forever
Self-press is labelled, not blocked. The token page says so; the leaderboard filters it by default.
Spam presses to climb the front page
Front page ranks on curve volume, never on press count.
Farm launches from one wallet
Rate limit per wallet per hour, rising with live rate. Launchers whose tokens trade earn more presses.
Launch from a handle that never wanted this
Blanket opt-out. Any verified handle can turn off launching from their posts, honoured at the extension level, no appeal process for us.
Launder the lock through a viral quote-post
Quotes and reposts resolve to the original post ID.
Impersonate a public figure
Every token page carries community-launched, not affiliated above the fold, permanently.
Roadmap
Press. Circulate. Hunt. Surfaces.
- 01 · weeks 1–4PRESS
- —Hover affordance + side panel
- —Heuristic auto-fill, no model dependency
- —One-transaction launch, native pair, no exemption list
- —Registry lock, post ID written on-chain
- —Token page at /t/<postID>
- —Splitter contract, reviewed
Exit: A stranger presses a post; a second stranger finds that token cold on an aggregator and buys it without the extension.
- 02 · weeks 5–10CIRCULATE
- —Post badges
- —In-panel trading
- —Author index + claim + disavow
- —Author-discovery outreach
- —Front page + press records + titles
- —Store listing + signed zip fallback
Exit: Origin authors start claiming without being contacted first.
- 03 · months 3–5HUNT
- —$FEED fair launch, same rules
- —Tiers live: UNCLAIMED markers, alerts, suffix grinding
- —Ranked name/ticker suggestions
- —Buyback routing
- —Public read API
Exit: Holding $FEED is the obvious move for anyone pressing more than occasionally.
- 04 · months 6–12SURFACES
- —Second browser target
- —Mobile path
- —Optional group press, once there is an audience for a pool to fill
- —Other post sources
- —Author-side tooling
Key decisions
What we chose, and why.
Instant launch, no pooled commit round at v1
A pooled round is only visible to people who already installed. At zero users that is an empty room.
One post, one token
The only scarcity a launchpad can honestly have. Turns scrolling into a race.
Lock is a product rule, stated as one
The post ID on chain makes it auditable anyway.
Origin author paid by default, no opt-in
Turns the obvious objection into the best marketing we have.
Website field points at our own token page
Aggregators become permanent distribution we never pay for.
Never pass an exemption list
There is no insider lane if the call shape has no parameter for one.
Splitter holds fees only, never principal
A contract that never holds principal cannot lose it.
Creator tax chosen by the launcher, disclosed as immutable
Hiding that would be the kind of thing we are differentiating against.
Real curve balances only, never virtual reserves
Competing pads render a virtual reserve as 40% to graduation on tokens holding nothing.
Minimum extension permissions
Anything more and nobody installs a crypto extension.
Metrics that matter
The category's vanity metric is launch count. We refuse it as a headline — a pad with 131 launches and no trades is the thing we are reacting to.
Primary
- ▸ % of presses with ≥1 buyer who is not the launcher
- ▸ Median curve volume per press
- ▸ Cold installs attributed to token-page arrivals
Secondary
- ▸ Author claim rate + median time to claim
- ▸ Median seconds from panel open to press
- ▸ Repeat press rate at 7 days
- ▸ Graduation rate
Published whether good or bad, on the docs page, monthly.
Strengths
- The registry of claimed posts, author relationships and installed base are not copyable — the mechanic is.
- Three-sided network: launchers want unclaimed narratives, buyers want badges, authors want their balances.
- Every press is a labelled narrative-to-market datapoint nobody else is collecting.
- The honest position is unoccupied: real balances, published metrics, no exemption list, no custody of principal.
Risks · written down on purpose
- Store policy. Trading extensions on X have precedent; launching does not. Minimum permissions, no key custody, signed zip on our own domain as fallback.
- Host DOM changes. Parsing sits behind one module and fails soft — if we cannot parse, the button does not appear and nothing else breaks.
- Spam at scale. Volume-based ranking, rate limits tied to live rate, author opt-out.
- Impersonation. Permanent unaffiliated line, disavow, blanket handle opt-out honoured without negotiation.
- Mobile. Most of the timeline is read on phones where extensions do not exist. This caps the base until phase 4.
- Pad dependency. Someone else's launch contracts control the snipe parameters. The splitter and registry are ours; the call is abstracted.
You have scrolled past nine launchable narratives today. Somebody else pressed first on all nine.
⚡ PRESS FIRST