Documentation

A campaign routes a Pons token's creator fees into a dedicated vault on Robinhood Chain.

Eligible X posts earn scores each round. New fees split 10% to the platform and 90% to participants by score, then are committed on-chain and paid out.

A campaign needs a fee source. When you launch through BUZZCUT, the new Pons token is created with the campaign vault as its creator-fee recipient. When you connect an existing token, you transfer the creator-fee recipient to the vault (or the operator's dev wallet claims fees and deposits them).

Every campaign is reviewed against the participation policy before it goes live. You choose the round length; the holding threshold and scoring version are published on the campaign's Rules tab.

• Vault recipient: Pons pays creator fees to the campaign vault; an operator role can only call allowlisted Pons claim functions.
• Dev wallet: the wallet that launched the token claims creator fees and deposits them into the vault with a reference.
• Fees are rewards only after they reach the vault. Unclassified transfers are never counted as fees.

You prove that you control both a wallet and an X account. No passwords, cookies, seed phrases or private keys are ever asked for.

• Connect your wallet and sign in with Ethereum (a signature, not a transaction).
• Enter your X username and sign a message that consents to publicly linking that X account to your wallet for this campaign.
• Post the one-time code tweet we show you (it expires after a few minutes), then paste the tweet link.
• We verify the tweet by your permanent X user id — renaming your account doesn't break the link.
• One wallet ↔ one X account per campaign. Posts made before you joined never count.

We search X for posts that mention the campaign token and match them to participants by X user id. Metrics we can't read stay unknown — they are never counted as zero.

• Mentioning the full token address (or a Pons/explorer link containing it) is a strong match.
• A ticker alone needs another signal (token name, campaign links, Pons URL, chain keyword) and a ticker that is unique among active campaigns.
• Ambiguous matches go to a manual review queue and are never rewarded automatically.
• Retweets, your verification tweet and posts made before you joined are excluded.

Scores are deterministic integer points computed after the round freezes, from final metrics. Each campaign publishes its scoring version; the defaults below are scoring version x-v1.

Your score for a round is the sum of your counted posts after multipliers. You can open a per-post explanation (factors, exclusions, reasons) for every frozen round on the token page.

Rounds have fixed UTC boundaries: a round of length L starts at every multiple of L since the Unix epoch. A post belongs to the round in which it was created and never moves to another round.

After a round ends we wait a settle delay, then freeze it: final metrics are fetched and scores become immutable. If more than 5% of posts are missing metrics, or a search window is incomplete, the round is deferred and retried — it is never paid on partial data.

Every round, token balances are read for all participants at one block. The block is chosen pseudo-randomly inside the round's block range from a seed nobody controls in advance (the round's end block hash, the campaign and the round index), so moving tokens around for one moment doesn't help.

Participants below the campaign's holding threshold score zero for that round. Above it, the holding multiplier grows linearly up to its cap. Because each wallet can back only one X account per campaign, one balance can back one participant.

Only new fees count: the vault keeps on-chain counters of fees received and fees processed. Each round commit takes the difference, sends the platform share to the treasury, and allocates the rest by score. All math is integer, in the asset's smallest unit.

Rewards are paid in the asset that was actually received (ETH or a supported token). Different assets are never converted or added together.

• New fees = fees received − fees already processed.
• Platform fee = floor(new fees × 10%) — fixed in the vault at deployment, capped at 10%.
• Your allocation = floor(available × your score ÷ total score).
• Rounding remainders and rounds with no eligible score stay in the pool for the next round.

Each round commit publishes a Merkle root of cumulative entitlements (what each wallet has earned in total). The distributor pays the difference between that amount and what was already paid.

• An executor pushes payouts automatically after commit; gas is paid by the platform, never deducted from rewards.
• Small amounts wait until they reach the asset's minimum payout; they stay committed and claimable meanwhile.
• Anyone can trigger a claim for a committed amount — it only ever goes to the committed wallet.
• A new root only becomes payable after an activation delay, so a bad root can be revoked before it pays.
• Paying the same amount twice is impossible on-chain; the round manifest and proofs are public.

Risk signals are combined into a score per participant. Warnings reduce the round score (by 25% or 50%); a high score disqualifies the participant for the round. Every flag is shown in your explanation.

• Second wallets and shared funding sources.
• New or very young X accounts and very low follower counts.
• Posting bursts and unusually high posting rates.
• Copy-pasted or near-duplicate text.
• Engagement that doesn't fit the audience (likes vs views, engagement ratio).
• Ambiguous matches, deleted posts and posts with unknown metrics don't score.

Collecting posts, matching them and scoring them happens off-chain and is operated by the platform. The contracts can't judge post quality. What they do guarantee:

• The platform fee is fixed per vault and can never exceed 10%.
• Allocations can never exceed the funds available to a campaign.
• Campaigns and assets are isolated from each other.
• No double payment: the distributor tracks what each wallet was paid.
• Payouts only go to committed addresses; operators can't withdraw committed rewards.
• Contracts are not audited. Social data comes from a third-party provider and can be incomplete.