How realize works

01Overview

Most builders on Pump.fun do not lack ideas. They lack the capital for a first push, and the launches that do get one are too often bundles built to extract and leave. realize exists for the other kind of builder: teams with real tech and a long-term plan who want their community to see, from day one, that the launch was done seriously.

For selected launches realize buys tokens inside the launch transaction with its own SOL, locks the larger part as a Builder Allocation, and keeps a small Recovery Tranche. Creator fees and Recovery Tranche sales bring realize's capital plus a fixed Success Share back. From that point the builder receives 95% of creator fees and the Builder Allocation streams to the builder to grow the project.

No SOL is ever sent to the builder and nothing is ever owed by the builder. realize is not a pump-and-dump product, a price-support promise, an investment product or a guaranteed-return mechanism.

1. 1Anyone can create a launchPay the 0.30 SOL Creation Fee, accept the terms, receive a branded CA.
2. 2Selected launches receive Launch Supportrealize buys with its own SOL inside the launch transaction. Nothing goes to the builder's wallet.
3. 3Creator fees reach the threshold first100% of creator fees go to the Launch Reserve until the Fee-Share Threshold is reached.
4. 4Then the builder is paid95% of every claim to the Builder Fee Wallet, 5% to realize. The Builder Allocation streams to the builder.
5. 5Everything is publicWallets, locks, fee share, positions and the Day-31 policy are verifiable on-chain.

02Core principles

• realize uses Pump.fun as the underlying token-launch infrastructure.
• Anyone can create a launch; only selected builders receive Launch Support.
• Launch Support is realize's own capital. realize never pools or manages anyone else's money.
• The builder never receives SOL from realize and never owes anything to realize.
• Tokens bought with Launch Support are realize property until the Fee-Share Threshold is reached. The Builder Allocation is locked and never sold by realize.
• Founder allocation is subject to public, mandatory vesting.
• Creator fees go 100% to the Launch Reserve until the threshold, then 95% to the builder and 5% to realize.
• Every realize Verified Launch uses a branded contract address ending in pster.

03Launch types

Before a Verified Builder Launch, the builder accepts realize's ownership of its position until the threshold, the fee share, the Day-31 policy, the founder vesting requirements, founder wallet disclosure and the branded contract-address requirement.

04Creation Fee

realize Creation Fee: 0.30 SOL
0.30 SOL → Revenue Router (30% Launch Reserve · 70% Protocol Treasury)

The fee is paid inside the launch flow, before branded CA generation starts, and is non-refundable once generation begins. It is separate from Launch Support, the Builder Allocation, Founder Allocation, Founder Purchase and the fee share. Paying it does not guarantee selection for Launch Support. The fee transaction is shown on the public token page.

It funds product development, frontend, backend, API and database infrastructure, vanity-mint generation, transaction preparation and automation, security monitoring, token pages, dashboards, on-chain analytics and builder-review operations. Through the Revenue Router, 30% of every fee returns to the Launch Reserve to back the next builders.

05Launch Support

realize backs a selected launch with a Support Amount in SOL from its own Launch Reserve. The buy is executed inside the launch transaction itself, so realize is the first buyer on the bonding curve. The purchase is one third larger than the Support Amount and is split into two public positions:

Before launch the token page shows the Support Amount, the Success Share, the Fee-Share Threshold and the maximum position as a percentage of supply. After launch it shows the SOL actually deployed, the exact tokens acquired, both positions, the lock and every Recovery Tranche sale.

06Fee share and threshold

Fee-Share Threshold = Support Amount × (1 + Success Share)

Support Amount: 5 SOL
Success Share: 15%
Fee-Share Threshold: 5.75 SOL

From launch, 100% of creator fees are routed to the Launch Reserve. Recovery Tranche sales count toward the same threshold. There is no deadline: the threshold is reached when it is reached, and if it is never reached nothing is owed by the builder.

Until the Fee-Share Threshold is reached:
    100% of creator fees → Launch Reserve
    Recovery Tranche sales → Launch Reserve

Once reached:
    95% of creator fees → Builder Fee Wallet
    5% of creator fees → realize (Revenue Router)
    Builder Allocation → streams to the builder

The 5% share funds operations, security, the Launch Reserve and builder programs through the Revenue Router. It is never communicated as a return to token holders.

07Recovery engine

realize only wants its capital and the Success Share back. It does not trade the builder's token for profit. The Recovery engine sells the Recovery Tranche gradually, respecting the chart, and records every sale on the token page.

• Maximum price impact per trade: 1% on the bonding curve, 1.5% after migration.
• Maximum per rolling 24 hours: 20% of the Recovery Tranche, or 5% of 24-hour volume after migration, whichever is lower.
• Sales only into strength, at published milestones (3×, 6× and 10× the entry price by default). No selling into a falling market.
• Migration to the AMM is a mandatory milestone: whatever is still missing to reach the threshold is completed in the first hours after migration, in capped chunks.
• One protective exception: if the price falls to where the remaining tranche can only just cover the missing amount, the remainder is sold immediately.
• Once the threshold is reached, sales stop. Remaining Recovery Tranche tokens join the Builder Allocation stream to the builder.

08Founder vesting

Example: a 30% founder allocation needs at least 20 monthly unlock periods after the cliff. All founder-controlled wallets are declared before launch and cannot be changed or supplemented secretly. Mint and other authorities are disclosed and, where required, revoked. Hidden minting, honeypots, mutable hidden taxes, abusive transfer controls and hidden blacklists are prohibited. Vesting cancellation exists only for pre-disclosed fraud or material-breach cases.

09Founder Purchase

After the launch buy, the builder may optionally buy a limited position directly from realize: up to 2.00% of initial supply across all Founder Purchase transactions combined. Inventory sits in a separate Founder Purchase Reserve, never mixed with the Builder Allocation or the Recovery Tranche.

Founder Purchase Price = Allocated realize Cost Basis + 10% Founder Purchase Fee + Direct Execution Costs
Minimum Transfer Price  = Allocated Cost Basis × 1.10 + Direct Execution Costs

Reserved amount: 1.00% of supply
Allocated cost basis: 2.00 SOL   Fee 10%: 0.20 SOL   Execution: 0.01 SOL
Total founder payment: 2.21 SOL

An unpaid or partially paid optional reservation would give the builder a free option while realize bears the downside, so it is not offered.

10Day-31 policy

For the first 31 days the Builder Allocation is locked and realize does not sell it. Recovery Tranche sales follow the Recovery engine only. The single exception is a Security Exit caused by fraud, a rug attempt, an exploit or material security incident, undisclosed supply or minting, a hidden founder-controlled wallet, a vesting bypass attempt or a material breach of launch terms.

From Day 31, if a token is a zombie, realize may sell its position. A token is a zombie when it fails the published Day-31 criteria with no meaningful progress: no builder updates, no meaningful trading volume or creator-fee activity, and no evidence of active building. On the bonding curve the position is sold back to the curve in capped chunks. Sales are recorded publicly. Founder-locked tokens are never sold. Every builder accepts this policy explicitly before launch.

Example Builder Launch criteria (published before launch)
Threshold progress: at least 12.5% of the Fee-Share Threshold
Builder updates: at least 2 during the first 31 days
7-day volume: above the tier minimum
Security compliance: mandatory

11Branded contract address

Every realize Verified Launch uses a token mint address ending exactly in pster. It tells a community at a glance that the launch went through realize's disclosure, vesting and support standard. Tokens without the suffix cannot be displayed as Verified Launches or receive Launch Support, except under a disclosed exceptional policy.

8xK...mYpster
3Fn...Qrpster
A7v...4Lpster

58^5 = 656,356,768 average candidate keypairs

1. 1GenerateA dedicated, ideally GPU-accelerated worker generates candidate keypairs until the public key ends in pster.
2. 2ValidateThe suffix is verified before the launch transaction is prepared. A Verified Launch never proceeds without it.
3. 3Sign onceThe keypair signs the creation transaction through a Pump.fun flow that accepts a custom mint signer.
4. 4DestroyTemporary private-key material lives only in protected volatile memory and is destroyed when no longer required. It never touches frontend code, repositories, logs, analytics, databases or error tracking.
5. 5ConstrainMint and other authorities are revoked or constrained after creation under the realize safety policy.

12Wallet architecture

realize multisig
│
├── Launch Reserve          own capital, revolving
├── Protocol Treasury       operations and growth
├── Revenue Router          splits every revenue 30% Reserve · 70% Treasury
│
└── Per supported token
    ├── Fee Router            on-chain creator-fee split
    ├── Builder Allocation    locked 31 days, streams to the builder
    ├── Recovery Wallet       Recovery Tranche only
    ├── Founder Vesting       builder's own allocation
    └── Founder Purchase Reserve

• Reserve and Treasury controls use a multisig, never a hot wallet.
• Builder assets (creator fees, founder allocation, Builder Allocation after the threshold) are routed and locked on-chain, never held by realize keys.
• Public wallet addresses and explorer links appear on every token page.
• Sensitive treasury movements use approval rules and timelocks where feasible.

13Public token page

Route: /launchpad/[token-address]. Each page shows the token hero with branded CA and market data, the status badge, the Creation Fee card, the Launch Support card with both positions, the Fee Share card with threshold progress, the Creator Fees card, Founder Vesting, Founder Purchase, the Vanity CA card, Security & Disclosure, Builder Activity and the Day-31 Policy card with the Recovery sale log. Browse launches.

14User flows

15Glossary

This documentation describes a product specification. It is not legal, tax, investment or regulatory advice. Before public deployment the final structure must be reviewed by qualified legal and security specialists.