How It Works

How It Works

1. Configure

Set how your PumpSwap creator fees are allocated:

Channel
What it does

LP Injection

Fees routed into deepening the liquidity pool

Team

Percentage sent to your wallet

Example: 80% LP / 20% Team → for every $100 in fees, $80 compounds into the pool, $20 goes to you.

Fee Schedule (Variable by Timer)

Choose how often Bootstrap claims and compounds fees. Higher frequency means more compounding events at a higher fee rate:

Interval
Fee Rate

Every 30 min

1.00%

Every 2 hr

0.75%

Every 12 hr

0.50%

Daily

0.25%

The tradeoff is deliberate — high-volume tokens benefit from frequent compounding, while lower-volume tokens can minimize fees with a longer interval.


2. Lock

Lock your configuration on-chain before launch. Once locked, settings are immutable — buyers can verify them, and you can't change them.

Lock Type
Description

Time-Locked

Immutable for a set period (30, 60, 90 days)

Permanent

Can never be changed


3. Compound

Bootstrap's automation engine runs 24/7:

LP Injection cycle:

  1. Claim fees from PumpSwap

  2. Split 50/50

  3. Buy the token with one half

  4. Deposit both halves into the liquidity pool

Creators choose their compounding frequency: every 30 minutes (1.00%), 2 hours (0.75%), 12 hours (0.50%), or daily (0.25%). Higher frequency means more compounding events at a higher fee rate — configure based on your token's volume and strategy.


Existing Tokens

Bootstrap works for new launches and existing tokens. CTOs and communities can onboard by transferring fee authority to a Bootstrap-controlled wallet. Same lock guarantees, same verification, same compounding.


Architecture

Six layers:

  1. UI — Creator dashboard, config tools, verification pages

  2. Config & Launch — Fee splits, lock mechanisms, deployment

  3. Blockchain — PumpSwap integration, on-chain execution

  4. Automation — Fee claiming, routing, execution

  5. Action Modules — LP injection, team allocation

  6. Verification — Public proof of config, locks, and execution history

Everything is on-chain. Everything is verifiable.

Last updated