yaps.fun

Overview

The launch and trade side of yaps.fun runs on the live pons V2 contracts, which pons owns and operates. Every launch, buy, and sell is a call into pons’s factory, curve, and router. On top of that, yaps.fun deploys and runs two contracts of its own — the talker registry and the contributor reward pot — which are what turn a launch’s fees into a payout for the people talking about it. See Contracts.

How a launch lives here:

1. Launch — a token is created on pons’s factory, priced in ETH or an approved pair asset. Its creator fee recipient is fixed to the yaps.fun reward pot, so the launch can be listed here. See How launches work.
2. Trade — the token trades on a bonding curve, then in a locked Uniswap v4 pool after graduation. Every trade pays a fee, part of which is the creator’s share.
3. Yap — anyone links an X account once, then registers on a token’s board by burning 10,000 of that token. See Yappers and registration.
4. Earn — a launch’s creator fees pool in the reward pot, and registered yappers claim a share of them, weighted by mindshare. See Contributor reward.

How launches work

Launching a token costs 0.0005 ETH, paid to pons’s factory contract. The launch mints a fixed supply of 1,000,000,000 tokens, all of which go to that token’s bonding curve — nothing is minted to the creator’s wallet directly. You can include a developer buy in the same transaction.

Paired asset

A launch is priced in ETH or in any ERC-20 pair asset pons has approved — including tokenised stocks. Trading, graduation, and the creator’s payout all happen in that asset, and pons never converts between assets. The create form lists the pair assets pons currently approves.

Creator fee recipient (fixed to the pot)

The creator fee recipient for a launch here is the yaps.fun reward pot, not the launcher. The form fixes it, and a launch is only listed on this site when its recipient is that pot. This is the whole point of the product: the creator’s fees become the contributor reward, paid to the launch’s yappers rather than to one wallet.

Contributor reward rate

At launch you set the launch’s creator tax between 1% and 10%. Together with the base trade fee’s creator share, that is what pools in the reward pot. A launch with no creator tax is not listed here.

Anti-snipe exemptions

Every new launch has an anti-snipe tax for its first few seconds of trading. At launch you can declare wallets that are exempt from it. Your own wallet and the reward pot are exempt automatically; the wallet that receives the developer buy is exempt too.

Yappers and registration

A yapper is an X account registered on a launch’s board. Only yappers earn from the contributor reward.

Link your X account (once)

On your profile you link an X account: you post a short line that carries a code yaps.fun issued and your wallet address, and the site verifies the post through X’s public embed. The link is keyed on the X user id, never the handle, so renaming the account does not lose it. You do this once, for every token.

Register on a token (per token)

On a token’s page you register by burning 10,000 of that token (0.001% of supply). The registry records your X user id as a yapper for that launch. A slot is permanent and the fee is not refunded. The burn is the only thing that differs between tokens; the X proof is shared.

Registrations are recorded by the YapsTalkerRegistry contract and only accepted for launches this site lists (see What makes a launch appear here).

Mindshare scoring

Each launch’s board ranks its yappers by mindshare: how much attention they created for that launch on X. Only posts from registered yappers, made after they registered, count.

The score for one post is built from six factors:

S = W × G × F × E × D × K

• W — author trust, from 0 to 1, from a pagerank over the accounts a yapper is quoted, mentioned, or reposted by, seeded by a curated list of trusted accounts. An unknown account starts at a small floor and is discounted further if it looks automated.
• G — quality gate. Spam, bait, and copies score zero; original content passes. The first poster of a repeated line keeps the score.
• F — split across tokens. A post that mentions many tokens divides its score across them.
• E — engagement. Likes, reposts, replies, quotes, and bookmarks, weighted by type and capped so one post cannot dominate. Engagement from fellow yappers of the same token is limited.
• D — time decay. Fresh posts count more. Boards use a 24-hour and a 7-day window.
• K — diminishing returns. A yapper’s later posts about the same token count for less, up to a daily cap.

A post counts toward a token when it references it — by cashtag, name, contract address, or a yaps.fun link. The contract address and link are the strongest signals, since memecoin names repeat.

A board turns these scores into shares: each yapper’s share is their total score divided by everyone’s total score for that token. Scoring runs off-chain; the chain only settles the result (see Contributor reward).

The exact factor weights, the seed list and its scores, the engagement constants, the caps, and the abuse thresholds are calibrated internally and are deliberately not published, so the ranking cannot be reverse-engineered and farmed.

Contributor reward

The creator fee recipient for every launch here is the YapsContributorReward pot. When a launch’s curve or pool sweeps fees, pons credits the pot in the launch’s own asset. That pooled fee is the reward, and it is paid out like this:

1. The team takes a fixed cut off the top of every round. The rate is set when the pot is deployed and cannot be changed afterwards. The default is 10%.
2. The keeper publishes a round. When a launch’s accrued reward reaches a threshold — by default 10% of the launch’s own on-chain graduation threshold, so about 0.42 ETH for a 4.2 ETH launch — the keeper commits a Merkle root over each yapper’s share. The keeper chooses the board, once; it cannot set an amount per yapper, because the contract derives each payout from the committed share.
3. Yappers claim. On the token page, a yapper claims their share with a Merkle proof. The contract pays amount × shareBps / 10000 in the round’s asset, once.

Anything a round promised but nobody claimed is returned to the pot after 90 days, to be paid in a later round. The team cut and the yappers’ reserve can never be withdrawn by the site owner — the owner can only recover a true surplus, never funds already promised.

Rewards are paid in whatever the launch traded against: ETH for a native launch, or the pair token (a stablecoin, a tokenised stock, etc.). The pot accounts for each asset separately.

What makes a launch appear here

A launch is listed on this site only when both are true:

• its creator fee recipient is the yaps.fun reward pot, and
• its creator tax is set above 0%.

A token launched elsewhere, or launched with its reward left at 0%, still exists on-chain and trades normally — it simply will not appear here. Because every launch goes through pons’s shared factory, any token launched here also appears on pons’s own site.

Risk disclosures

This section states what can go wrong and what we cannot promise.

pons controls the protocol, not us

We call pons’s contracts; we do not own or control them. pons’s owner can pause new launches, change the fee policy for future launches, and redirect a launch’s creator fee recipient after a 3-day timelock. If they do, it affects tokens launched through this site the same as any other token in their factory.

Rewards can be small or zero

The contributor reward is exactly a launch’s creator fees. If a launch trades little, the pot earns little. A round can also be worth nothing to some yappers if their share is dust. Nothing here promises a payout.

The pons contracts are not ours

The factory, router, bonding curves, swap hook, fee escrow, buyback vault, and liquidity locker all belong to pons and have not been audited by us. Our own two contracts, the registry and the reward pot, are documented in Contracts.

Paying for posts runs against X’s policy

X’s Developer Policy forbids compensating anyone for posting. The contributor reward is a deliberate, known exception to that, and it is the reason comparable products had to stop. Read that as a real, accepted risk of using this site.

Memecoins routinely go to zero

Most tokens launched through a bonding curve lose most or all of their value. A permanently locked liquidity pool means the pool cannot be drained by its creator — not that the token is worth anything.

Token metadata is not vetted

A token’s name, description, and links are written by whoever launched it. We do not check or endorse any of it.

Network

yaps.fun runs on Robinhood Chain: chain id 4663, native coin ETH, roughly one block every 0.1 seconds. That fast block time is what lets the anti-snipe tax decay in fine steps over its short window instead of dropping all at once.

Explorer: robinhoodchain.blockscout.com. Every launch, trade, registration, round, and claim can be verified there independently of this site.

Contracts

Yaps contracts

These two belong to yaps.fun and run on Robinhood Chain.

pons contracts (the launch and trade layer)

These belong to pons. yaps.fun only calls them.

None of the pons contracts are audited by us. Verify them yourself on the explorer before relying on anything stated here.

Reading state on-chain

Everything this site shows is readable directly from the contracts above, independent of this site.

• Launch terms — pons’s factory getLaunchedToken(token) returns the creator fee recipient, the creator tax, the pair asset, and the graduation phase.
• Registration — the registry’s registrationOf(token, xUserId) and registrantCount(token) say who is on a board.
• Reward — the pot’s rounds(token, roundId), roundCount(token), and hasClaimed(token, roundId, account) are the payout record.

If anything this site displays ever looks wrong, the explorer — not this site — is the source of truth.

Audits

yaps.fun operates two contracts of its own on Robinhood Chain — the talker registry and the contributor reward pot. Both were hardened before they were deployed, under the same adversarial standard we would expect of an external review. This section covers only those two; the rest of the path belongs to pons, which keeps its own audit page at docs.ponsfamily.com/v2#audits.

What our two contracts have been through:

• Adversarial review — a hand review against the risks that matter here: reentrancy, access control, Merkle-claim correctness, round and sweep accounting, and registration signature expiry and replay.
• Foundry fuzzing and stateful invariants — property tests over randomised call sequences rather than fixed cases, held to the pot’s core guarantees.
• Ultrafuzz — agentic, coverage-guided fuzzing, scaffolded against the staging deployment; setup and validation pass, with a full campaign queued.

The review found no critical or high-severity issue. One low-severity issue was found and fixed: a missing reentrancy guard on the registry’s register(), now covered by a test that tries to register through a hostile token. We hold the reward pot to three invariants: reserved, unallocated, and team funds never exceed the pot’s balance per asset; a round’s claims never exceed its amount; and the owner can withdraw only a true surplus, never funds already promised.

Read this before relying on them

• No independent audit has closed. Treat both contracts as unaudited by a third party until an external report is published here.
• The pons contracts are not ours and are not covered here. See docs.ponsfamily.com/v2#audits.
• An audit is not a guarantee. It reduces risk; it does not remove it.

If you find something, report it to us rather than disclosing it publicly, and give us a chance to fix it first.

Support

yaps.fun runs the board, the scorer, and the reward pot, but not the launch and trade protocol — that is pons’s. We cannot pause a launch, reverse a trade, undo a graduation, or move a launch’s fee recipient; only the wallet holding that role, or pons’s owner acting through their timelock, can do that. For a reward that looks wrong, check the pot’s round on the explorer against this page before assuming the interface is right.

Terms

yaps.fun is an interface: a launch and trade frontend on pons’s V2 contracts, plus an attention board and reward pot of our own, on Robinhood Chain. It is not an audit, a guarantee, or an endorsement.

Nothing on this page changes what is written on-chain. The contract addresses in Contracts, and the powers pons’s owner still holds as described in Risk disclosures, govern what actually happens — not this page.

This page is documentation, not financial advice, and not an offer to buy or sell any token.