Skip to content
Realtime updates are reconnecting · displayed snapshots may be stale · view service status

Trust & disclosures

Transparency

pumpinhood.fun has one irreversible job: atomically create a fixed-supply token and permanently lock its liquidity. Everything below is either a contract invariant or an explicit known limitation — nothing here is marketing copy.

Permissionless mainnet: no-go

Release blocked

A working interface and green local checks are not mainnet authorization. Execution remains fail-closed until every external approval, production operation, audit, governance, and canary evidence gate below is satisfied.

Trust promises

  • Fixed supply and zero creator allocation.
  • No token owner, tax, blacklist, confiscation, or upgrade path.
  • Existing LP principal cannot be removed, rescued, redirected, or migrated.
  • Fee recipients and splits for an existing launch cannot change.
  • Administrative pause affects new launches only.
  • The indexer may be unavailable or wrong temporarily, but cannot change token ownership or pool state.

Known limitations

  • A 2% address cap is Sybil-able and must never be marketed as one-person-one-allocation.
  • The sequencer, RPC providers, wallets, bridges, ETH/USD source, Uniswap contracts, and hosted interface are external dependencies.
  • Graduation and King are promotional analytics milestones, not endorsements; King uses a TWAP and liquidity guard while graduation remains based on indexed net flow.
  • Permanent liquidity cannot be repositioned if market conditions or protocol integrations change.

Fees & economics

Creation fee
0.014 ETH current configuration; live factory getter is authoritative
Pool fee tier
1%
Dev fee routing
Immutable wallet selected at launch
Token-side pool fees
Burned when collected
Transfer / token tax
None
Max wallet cap
2%
Cap duration
73 min
Graduation threshold
4.2 WETH
King FDV threshold
$15,000
King min net inflow
0.5 WETH

Contract manifest — Robinhood Chain (4663)

  • Canonical WETH0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73
  • Uniswap v3 factory0x1f7d7550B1b028f7571E69A784071F0205FD2EfA
  • Position manager0x73991a25C818Bf1f1128dEAaB1492D45638DE0D3
  • Swap router0xCaf681a66D020601342297493863E78C959E5cb2
  • Launch factory0x5a9B4cd46D1aa3468CFCab6076D11fA2C0461626

Release gates

  • Owner launch charterNamed release owners, wallet roles, budget, operating perimeter, and two-person approvals are not recorded.blocked
  • Local engineering evidenceAutomated contract, API, indexer, browser, wallet, and deployment checks exist; signed human UAT and the frozen evidence bundle remain pending.in progress
  • Production foundationPrivate RPC, database, cache, storage, scanning, monitoring, status, and runbook endpoints require funded vendor accounts and controlled secrets.blocked
  • Legal, brand & policyFinal name/domain, trademark clearance, counsel approval, creator agreement, privacy/terms, and operating jurisdictions remain unresolved.blocked
  • Staging soak & UATThe protected 500-launch / 100,000-trade run and recorded cross-device wallet acceptance have not been executed.blocked
  • Independent audit & freezeNo independent final audit, remediation confirmation, frozen commit, or matching bytecode report is published.blocked
  • Governance & deploymentSafe signers, treasury, timelock, canary creators, deployer, final four-hex suffix, and deployment ceremony are not approved.blocked
  • Bounded canary observationThe allowlisted canary, no-more-than-ten launches, and continuous 72-hour observation have not occurred.blocked
  • Separate permissionless betaRequires signed canary acceptance and a separately verified permissionless factory; the canary factory is never converted in place.blocked

Deployment does not proceed until the economic report, fork tests, external audit, Safe/timelock ownership, legal review, and mainnet canary gates are satisfied.

Owner actions required

Decision gate
  1. Select and clear the final name, controlled domain/social accounts, and attainable four-hex vanity suffix.
  2. Name the product owner, release manager, security owner, SRE owner, moderation owner, incident commander, and two release approvers.
  3. Approve three independent hardware-backed Safe signers, a 2-of-3 threshold, treasury, short-lived deployer, and canary creator wallets.
  4. Retain specialist counsel and approve operating jurisdictions, sanctions posture, final terms/privacy, creator agreement, and moderation policy.
  5. Fund and provision production infrastructure, independent audit, monitoring, content scanners, bug bounty, and canary ETH budget.
  6. Authorize the protected staging soak, human cross-device wallet UAT, deployment ceremony, and canary observation only after prior gates pass.

Do not publish signer identities, recovery material, private keys, vendor secrets, or unredacted legal advice here. Public release evidence should contain addresses, thresholds, hashes, approvals, and verification results without secret material.

Transparency · pumpinhood.fun