TikPaySandbox · not live yet
TikPay signal

Integration status

What is real, what is simulated, and what each remaining seam needs.

Sandbox mode. Demo environment. TikTok verification, Pump.fun launches, creator-fee events and treasury actions are simulated sandbox records. Wallet connection and signature checks are real and verify actual keys.

Integration seams

Derived from live server configuration

Wallet connection & signatures

Live

Injected Phantom, Solflare or Backpack wallets. Signatures are verified against the wallet's ed25519 public key on the server.

Needs: Nothing. Working now with Phantom, Solflare or Backpack.

Live market & mint data

Live

Price, volume, liquidity and market cap from DexScreener; mint existence and decimals from a Solana JSON-RPC node. No key, no funds.

Needs: Nothing. Public DexScreener and Solana RPC reads, no key required.

TikTok identity verification

Configured, unverified

TikTok Login Kit is wired through a sandbox app. Sign-in, the server-side code exchange and the basic profile read are real, but only accounts added as sandbox target users can authorise, and verifications are recorded as sandbox.

Needs: An approved TikTok developer app: registered entity, published privacy policy, then app review (several days to two weeks).

Token launches

Sandbox

Deterministic sandbox records with simulated mints and signatures. Nothing is broadcast and no SOL is spent.

Needs: A decision to go live, a treasury wallet, and a spend cap. Launches are permanent and spend real SOL.

Creator-fee index

Simulated

Fee events are generated by the sandbox provider and stored idempotently. A production build reads Pump.fun creator-fee data, which stays the source of truth.

Needs: A real Pump.fun fee reader. Pump.fun stays the source of truth for creator fees.

Treasury buy-and-burn

Simulated

The official TikPay token has not launched, so buy-and-burn batches are simulated with placeholder transaction signatures.

Needs: The official TikPay token to launch, then a live swap-and-burn route.

Pump.fun creator fee sharing

Validated against the official Pump.fun docs and SDK

Create a coin with a named creator

Supported on-chain

A launcher can create a coin and name a different creator address. TikPay does not do this on mainnet yet: this build has no live adapter and broadcasts nothing.

Mechanism: Pump program `create` / `create_v2` (creator pubkey is an argument), plus metadata upload

Signer: Launcher wallet (payer). The named creator does not sign.

Split creator fees 85 / 15 on-chain

Supported, blocked for TikPay

Mechanically possible and expressible exactly as 8500 / 1500 bps. Blocked for TikPay at launch: the creator payout wallet does not exist until the referenced TikTok account owner verifies and signs, and `update_fee_shares_v2` can be written only once before the split locks forever.

Mechanism: Pump Fees program `create_fee_sharing_config` then `update_fee_shares_v2` (shares in bps, total 10,000)

Signer: The coin's current creator (or the Pump admin authority) for the config; `sharing_config.admin` for the one-time share write.

Read accrued creator fees

Supported on-chain

Readable from any Solana RPC node once a real mint exists. TikPay currently reads market data live but generates fee events from the sandbox adapter.

Mechanism: `creator-vault` PDA lamport balance (seeds `creator-vault` + creator, or + sharing_config once migrated)

Signer: None — read-only RPC.

Claim / distribute creator fees

Supported on-chain

This is what keeps TikPay non-custodial: the sweep can be triggered by anyone, yet only the creator or configured shareholders can receive.

Mechanism: `collect_creator_fee_v2` and `collect_coin_creator_fee` for a single creator; `distribute_creator_fees_v2` once a sharing config exists

Signer: Permissionless — any fee payer can send it, and funds always move to the creator or the configured shareholders, never to the caller.

Read the fee-share configuration

Supported on-chain

The on-chain config is the source of truth for who receives what. TikPay's database must mirror it, never define it.

Mechanism: `sharing-config` PDA (seeds `sharing-config` + mint); official SDK exposes an editability check

Signer: None — read-only RPC.

Pump.fun cannot lock TikPay's 85/15 split at launch time.

  • — Fee sharing is a post-creation opt-in (`create_fee_sharing_config`), not an argument to `create`.
  • — The share write (`update_fee_shares_v2`) is one-time and then permanently locked, so a placeholder now cannot be corrected later.
  • — The creator's payout wallet is unknown at launch — it only exists after the referenced TikTok account owner verifies and signs with their own wallet.
  • — Only the coin's creator (or the Pump admin authority) can create the sharing config, so someone holding that authority must sign at the moment the creator appears.

TikPay's database must mirror confirmed on-chain state. Until a real fee-share config exists on-chain, the 85/15 figures in this app are allocation intent, not an enforced on-chain split.

Chosen architecture: TikPay routing authority

Design only — not enabled on mainnet

A routing authority is a TikPay-controlled Solana address that temporarily holds a coin's Pump.fun creator role so the 85/15 creator-fee split can be written on-chain once the referenced creator verifies their account. It is not custody. TikPay never requests or stores a creator's private key or seed phrase, never moves creator funds, and withholds fee distribution until the creator's own wallet is a locked on-chain shareholder.

  • ConfirmedA launcher can name a different `creator` pubkey than the signer at creation.pump-public-docs — create / create_v2
  • ConfirmedThe coin's current creator can call `create_fee_sharing_config`, and becomes `sharing_config.admin`.pump-public-docs — CREATOR_FEE_SHARING.md
  • ConfirmedThat admin authority is retained until the share write, then permanently revoked.IDL error `SharingConfigAdminRevoked`; @pump-fun/pump-sdk notes
  • Confirmed`update_fee_shares_v2` runs once: max 10 shareholders, each > 0 bps, no duplicates, total exactly 10,000.@pump-fun/pump-sdk JSDoc; IDL errors TooManyShareholders / InvalidShareTotal
  • ConfirmedDistribution is permissionless and can only pay the configured shareholders.pump-public-docs — distribute_creator_fees_v2
  • Not confirmedTikPay could transfer the creator role to the creator's wallet instead of settling shares.`set_creator` is gated to Pump's global `set_creator_authority` — not available to TikPay
  • Not confirmedShares can be corrected after the one-time write.No public reset instruction documented; only a `ResetFeeSharingConfigEvent` type exists
  • Not confirmedA shareholder address may be a PDA rather than a system account.Not stated in the docs, IDL or SDK types
  • Not confirmedThe official SDK runs in a Cloudflare Workers/edge runtime.No official compatibility statement; must be proven by bundling it

The 85/15 shareholder write happens once and then locks forever. TikPay writes no placeholder wallet, so a creator who never verifies is never replaced by a stand-in address. TikPay's ledger mirrors confirmed on-chain state. Until a real sharing config exists on-chain, the 85/15 figures are allocation intent, not an enforced split. Referencing a public TikTok handle, verifying that account, or receiving creator fees is not endorsement, sponsorship, affiliation, support, promotion or participation by the referenced account or its owner.

A "Live" seam is exercised by real requests right now. "Configured, unverified" means the credentials exist but the path has not been run against an approved third-party app. "Sandbox" and "Simulated" mean records are stored honestly labelled as not real — no fake blockchain and no fake claimable balance. The 85/15 allocation shown across TikPay is allocation intent recorded in the ledger, not an enforced on-chain Pump.fun fee split.