Documentation

How YouPaid works

YouPaid connects a token’s creator fees to the permanent YouTube channel behind a public channel, video, or stream.

Channel-ID attributionPump + ponsCreator-controlled claims
01

Overview

A launcher pastes a public YouTube URL or handle. YouPaid resolves the source to a canonical channel ID, uses that channel as the permanent recipient record, and prepares a token launch whose creator-fee path can later be claimed by the verified channel owner.

1Paste source
2Resolve channel
3Create token
4Verify & claim
The channel ID is the anchor.

Handles, names, avatars, and video titles may change. The underlying YouTube channel ID is the recipient identity that should remain stable.

02

Source resolution

YouPaid accepts three public source types. A video or stream resolves to the channel that published it; a channel URL or handle resolves directly.

Channelyoutube.com/@creator

Best when the coin represents the creator’s whole channel.

Videoyoutube.com/watch?v=…

Uses the video thumbnail while assigning fees to its channel.

Streamyoutube.com/live/…

Uses the stream as the token reference and its channel as recipient.

Deleting a source video does not transfer an existing balance to a different channel. The resolved channel ID remains the attribution key.

03

Profiles

A channel’s YouPaid profile is created automatically the first time a coin is launched for it. The channel’s name and picture come straight from YouTube. Coins waiting to launch show as “Launching” on that profile, and appear on Explore once their contract address is linked. A handful of profiles exist before any coin, for channels most likely to get one.

04

Launch venues

The Create screen adapts the wallet, network, and quote asset to the selected venue. YouPaid prepares the creator attribution; the connected wallet approves the venue transaction.

VenueNetworkPairingExecution
PumpSolanaSOL or USDCWallet transaction
ponsRobinhood ChainWETHWallet transaction
Venue terms are independent.

Supply, launch fees, fee splits, graduation rules, and supported pairing assets are controlled by the selected venue and can change. Always review the venue transaction before signing.

05

Fee routing

Each registered token stores a relationship between the token address, the resolved YouTube channel ID, the selected venue, and the fee configuration active at registration.

  1. Trading creates venue fees.The venue calculates and collects fees under its own rules.
  2. Every claimed fee splits 80 / 20.80% belongs to the channel; 20% funds the YouPaid reserve, which pays for claim transactions, swaps and operations.
  3. YouPaid attributes the creator share.The token’s creator-fee recipient points to the attribution route associated with the channel ID.
  4. The creator share is sent or held.If the channel publishes a donate button YouPaid can pay, the share is sent there automatically. Otherwise it is held against the channel ID until the creator verifies and claims. No YouPaid account is needed either way.
  5. The public ledger records settlement.Payments shows the token, channel, amount, payout asset, and status.
06

Channel verification

No YouPaid account is required. The default path: a claimant requests a short one-time phrase such as YP-7K2M, places it in the public channel description, and YouPaid checks that the phrase appears on the expected channel ID. As an optional shortcut, a creator can sign in with Google instead; YouTube then reports the channel ID the account owns, using read-only access.

Verification phraseYP-7K2M
  • The phrase is random, short-lived, and tied to one claim attempt.
  • A matching handle is not enough; verification must resolve to the recorded channel ID.
  • After verification completes, the phrase can be removed from the description.
  • Changing a channel display name does not invalidate the verified channel ID.
07

Creator claims

The verified channel owner chooses where the balance lands. It lands in a wallet they control, paid in USDC, SOL or $YPAID on Solana, with network fees covered by YouPaid. Start a claim

Held

Fees attributed to a channel with no donate button, waiting for the owner to verify and claim. Held balances never expire.

Sent to channel

Paid automatically to the channel’s donate button.

Claimed

Paid to the wallet the verified owner chose, with its transaction reference.

Limits

New payout destinations wait through a cooldown, and large or rapid payouts are held for review.

08

Wallet and transaction safety

YouPaid should never need a seed phrase or private key. Wallet connections only expose the public account selected by the user, and every launch or claim must be approved in the wallet.

  • Confirm the network before signing: Solana for Pump, Robinhood Chain for pons.
  • Check the token name, ticker, image, source URL, and fee recipient in the final preview.
  • Never approve an unexpected transfer, unlimited allowance, or network switch.
  • Token creation and fee-recipient changes may be irreversible.
09

Risk disclosures

Creator coins are experimental and can be volatile, illiquid, impersonated, or lose all value. A YouTube reference, verified recipient, or creator claim does not mean the creator launched, endorsed, or recommends a token.

No endorsement

A coin named after a creator doesn’t mean the creator is involved. Only a verified channel has claimed its balance.

No price promise

Fees, verification, or graduation do not guarantee demand, liquidity, or returns.

Check the address

Names and images can be copied. The token address is the durable on-chain identifier.

10

Creator opt out

A creator can request that their profile be hidden from discovery while preserving required accounting records. Opting out does not erase on-chain tokens created by third parties, but it can stop new YouPaid attribution and remove promotional display surfaces.

Open creator claims
11

Privacy

Public channel data, public token data, and public wallet transactions are used to display attribution and claim status. Private keys and seed phrases are never collected. Verification codes expire after 30 minutes and are deleted once used. The full Privacy Policy covers what is collected and for how long.