Backr Documentation

Overview#

Backr is a platform where communities can launch tokens connected to campaigns, projects, products, causes, and creators from supported external platforms. Anyone can launch a token for an eligible campaign; the launcher does not need to be the original campaign creator.

The core model

External campaign → community-launched token → Pons V2 bonding curve → community trading → possible Uniswap V4 graduation.

Kickstarter campaign URLs are the first and only currently supported campaign source. Backr is designed for additional fundraising and creator platforms later; those integrations are not live today.

How Backr Works#

From campaign to market

1. Enter an eligible URL from a currently supported campaign platform.
2. Choose token details and, optionally, an atomic dev buy.
3. Backr submits the launch to Pons V2 on Robinhood Chain.
4. Backr verifies the confirmed onchain receipt, then indexes the token.
5. The indexed token appears in Explore and on its Backr trading page.
6. Use Trade coin after launch to open that page.

Who Can Launch a Token?#

Anyone can launch a token for an eligible campaign from a currently supported platform. The launcher does not need to own the campaign, be its creator, or represent the project.

Two separate roles

Token launcher: the wallet that submits the Pons V2 launch.

Campaign creator: the person or entity that controls the external campaign.

Launching does not establish creator identity, authorization, or endorsement.

Launching a Token#

Campaign and token details

The current integration accepts a canonical Kickstarter campaign URL; Kickstarter is the first supported source, not Backr's permanent or exclusive focus. URL-derived campaign metadata is pending/unverified and is not proof that the launcher controls the campaign.

New launches use Pons V2 launch configuration 0 and the native ETH pair. Backr reads the current launch fee and economics from the Pons factory immediately before submission rather than presenting legacy Backr V4 constants as active Pons economics.

Launching and indexing are separate

Launching is the onchain transaction that creates the token. Indexing adds that confirmed token to Backr's database and Explore. A token can be live onchain even if indexing temporarily fails.

Backr verifies direct factory receipts and atomic router receipts. If indexing fails, it preserves the original transaction and shows Retry indexing. Retrying indexes the same launch; it does not launch again, submit another purchase, or repeat the dev buy. Never submit another launch after the original transaction succeeded.

Atomic Dev Buy#

The launcher may optionally enter an ETH dev-buy amount. Leaving the field empty or entering zero performs a normal launch. A positive amount creates the token and executes the launcher's purchase inside one atomic Pons transaction.

Execution properties

• Another public trade cannot be inserted between creation and the atomic buy.
• The launch fee and buy amount are sent together to the Pons router.
• Backr derives a non-zero minimum output from current Pons economics.
• Purchased tokens go directly to the launcher's selected wallet.
• If any part fails, both launch and buy fail; no launched token is left without its atomic buy.

Atomic execution does not promise profit, a future price, or protection from every possible form of MEV.

Token Economics#

Bonding Curve#

Tokens begin trading on a Pons constant-product bonding curve. As tokens are bought or sold, execution follows the live quote and token reserves. A larger trade therefore cannot be calculated by simply multiplying the current spot price by the amount.

Phantom quote reserve

Pons uses a phantom quote reserve to shape initial pricing. Backr reads it from Pons when quoting an atomic dev buy. It is distinct from the curve's real ETH reserve.

Token page and chart

Every successfully indexed Pons token receives a Backr page with Pons buy and sell controls, market price and cap, real liquidity, tokens remaining, curve or graduation status, recent activity, campaign and token information, explorer links, and connected-wallet data where available. The live chart displays ETH per token, reconstructed from Pons reserve activity, and refreshes periodically.

Buying#

On a Pons token page, buyers enter an ETH amount. Backr quotes the trade from the curve's current quote reserve, token reserve, sellable tokens, and onchain fee settings.

Submitting a buy

Buying needs no token approval. The Pons curve call includes a minimum token output and sends purchased tokens to the connected wallet. The displayed quote can move before confirmation, and gas is separate.

If a buy reaches the curve's remaining sellable amount, Pons can consume the required quote and return the remainder. Quotes separately identify the Pons protocol fee, Backr creator tax, and any Pons snipe tax.

Selling#

Sellers enter a token amount or choose a percentage of the connected wallet's position. Expected ETH comes from the live Pons curve.

Approval and settlement

Selling requires token approval for the Pons curve. The sell call uses a minimum ETH output and sends proceeds to the connected wallet.

Trading Fees#

Separate fee layers

The Backr creator tax is not the Pons protocol fee. Backr configures a 100-basis-point creator tax and routes all of it to the treasury address shown in Technical Reference. Pons reports protocol fees and tax amounts separately in curve events. Slippage protection and gas are not fees.

Campaign Creator Fees#

A Backr market can be launched before the underlying creator ever interacts with Backr. A future creator-fee system may let the creator verify control, connect a wallet, and participate.

Intended future flow

1. A market exists and its 1% Backr creator tax accrues to the treasury.
2. The campaign creator visits Backr.
3. The creator verifies campaign control and connects a wallet.
4. A future distribution system may make eligible fees claimable.

Campaign creators cannot claim these fees through Backr today. No verification method, authentication integration, distribution formula, or creator claim flow is represented as available.

Crowdfunding Platforms#

Backr is designed as a cross-platform campaign-token layer, rather than a product tied to one fundraising or creator platform.

Current support

Kickstarter is the only current campaign URL integration and is Backr's first supported campaign source. The application normalizes a campaign's canonical URL and can derive metadata, but that URL-derived metadata is pending/unverified and does not authenticate the campaign creator.

Future platforms

Additional fundraising and creator platforms, campaign-creator verification, creator fee claiming and distribution, and cross-platform campaign discovery are planned. They are not currently available.

Graduation#

Tokens begin on the Pons bonding curve. Pons exposes live graduation readiness and graduated status; when its configured mechanics are met, the token can graduate to Uniswap V4.

What happens

1. The curve reports progress using its live sellable-token and reserve state.
2. Pons determines readiness from its configured graduation threshold.
3. After graduation, the token's market moves to Uniswap V4 under Pons mechanics.

Backr displays Pons state; it does not replace Pons execution or promise a graduation time, price, or outcome.

Robinhood Chain#

Pons V2 launch and trading support documented here is configured for Robinhood Chain mainnet. The launch UI enforces chain ID 4663.

Contracts#

These addresses come from Backr's committed Pons V2 configuration.

Configuration

• Native pair: 0x0000000000000000000000000000000000000000
• Default launch config ID: 0
• Creator tax: 100 bps (1%)

Relevant environment variables

• NEXT_PUBLIC_ROBINHOOD_NETWORK — must be mainnet for Pons V2.
• NEXT_PUBLIC_ROBINHOOD_MAINNET_RPC_URL — optional mainnet RPC override.
• NEXT_PUBLIC_ROBINHOOD_MAINNET_EXPLORER_URL — optional explorer override.
• NEXT_PUBLIC_BACKR_FEE_WALLET — optional valid-address treasury override.

Security / Trust Model#

Verified design properties

• Backr verifies successful direct factory and atomic router receipts before indexing.
• It checks the token, curve, launcher, native pair, bytecode, name, symbol, treasury recipient, and 1% tax.
• Atomic router receipts must also match token, curve, launcher, recipient, quote spent, and tokens received.
• Launches and trades execute through Pons smart contracts; Backr provides discovery, indexing, and the interface.

Campaign identity and duplicates

Backr normalizes the supported campaign URL and deterministically derives a campaign key. Pre-launch lookup, a unique database constraint, and idempotent transaction indexing prevent a second token from becoming the canonical indexed Backr token for the same campaign.

This is not an absolute onchain duplicate guarantee: Pons does not enforce Backr campaign keys, so two wallets can submit launches before either is indexed. In that narrow race, more than one token may exist onchain; the first successfully indexed token is canonical in Backr.

Risks#

• Token prices can be highly volatile; bonding-curve assets are speculative.
• Trading a campaign token does not mean a platform or campaign creator endorses it.
• A token is not equity or ownership in the campaign unless explicitly structured otherwise.
• Smart contracts, wallets, integrations, and networks carry technical risk.
• Quotes, liquidity, and execution can change before confirmation.

Trading is not crowdfunding

Buying a Backr token is an onchain market trade through Pons. It is separate from contributing to the external campaign on its platform.

FAQ#