Understand adoption and existing-record recovery

Creating and managing tokens · Explanation and troubleshooting · New Pump and StonkFun adoption admission is deferred. Existing records remain subject to their own recovery capabilities.

Separate creator identity proof from permanent fee assignment or guarded delegation.

Reviewed: 2026-10-18

Before you start

  • No account is needed to read.
  • Existing-record actions require the original creator proof, owning account and current capability.

Connectivity is not new adoption admission

New Pump and StonkFun adoption are deferred. A source card labeled connected, an identity preview or implemented signing screen is not permission to start a new adoption.

Use this guide to interpret an existing record and its proof/fee boundaries. Do not try to bypass an admission blocker through an old URL, manual packet or another wallet.

Identity proof does not assign fees

A preview can resolve the mint, finalized creation signature, creator and fee wallet. An identity message uses a single-use nonce and matching original creator wallet. Signing that message proves scoped identity; it does not move funds or assign creator fees.

Expired or missing proof must be refreshed through an offered authorized preview, not reused. Check the exact mint and account binding before any existing-record proof action. Never paste a private key where a public signature is requested.

Pump fee assignment is a separate irreversible step

Pump fee-sharing assignment is distinct from identity verification and can be permanent and irreversible. For an eligible existing record, inspect the exact assignment destination, network/rent maximum, policy and acknowledgment before any separately offered transaction.

A prepared packet, submitted signature or identity success is not finalized adopted status. Preserve an uncertain existing assignment and check its status; do not repeat it or imply that new assignment admission is open.

StonkFun delegation has a guarded policy

StonkFun adoption uses a guarded delegated claim-and-forward policy, not the same permanent assignment mechanism as Pump. A policy revision defines permitted operations and limits; an acknowledgment is scoped to that review.

Recorded consent alone is not successful forwarding. Completion requires the relevant first finalized guarded forward. Read its evidence and status separately from creator identity proof, and do not infer live operation from connectivity.

Inspect the saved record without duplicating it

Return to the original account-bound adoption record and use Refresh status or its permitted recovery controls. Distinguish not found, access denied, expired proof and temporary provider failure; none automatically authorizes another assignment.

Retain the non-sensitive record reference, mint and any public signature. Keep full proof messages, credentials and signing material out of public reports. If no permitted next action exists, preserve the record rather than attempting a new adoption.

  1. Verify the original account and exact mint.
  2. Read the current saved status and any proof/delegation/assignment reason.
  3. Refresh that record when reads fail; use only an explicitly permitted existing-record action. If outcome is unknown, do not resubmit.