CTO Takeover

Execute Community Takeover (CTO) operations on existing tokens. Bundle buy into existing projects with coordinated multi-wallet entry.

Overview

Feature	Capability
Purpose	Take over existing tokens
Wallets	Up to 20 per bundle
Execution	Atomic Jito bundles
Platforms	Pump.fun, Raydium

 Location: Sidebar → Tools → CTO Takeover

---

What is CTO?

Community Takeover (CTO) is when a group buys into an existing token:

• Original dev abandoned the project

• Token has potential but no leadership

• Community wants to revive it

• Coordinated entry for better positioning

CTO vs New Launch

Aspect	New Launch	CTO
Token	Create new	Existing token
Control	You're dev	Community-driven
Risk	Technical	Execution timing
Entry	Block 0	Current price

---

How to Execute CTO

Step 1: Find a Token

Look for CTO candidates:

• Dev wallet sold/abandoned

• Active community interest

• Decent liquidity

• Not a honeypot

 Location: CTO Takeover → Enter Token CA

Step 2: Analyze Token

The interface shows:

 CTO ANALYSIS 

 Token: REVIVAL (RVL) 
 CA: 7GCi...W2hr 
 
 Current MCAP: $15,420 
 Liquidity: $8,200 
 Holders: 142 
 Dev Wallet: SOLD 
 
 Top Holders: 
 1. 5dr7...8Hnk - 4.2% 
 2. 9xYz...3Abc - 3.8% 
 3. 2aMn...7Def - 2.1% 
 
 [ Safe for CTO] 

Step 3: Select Wallets

1. Check wallets to use for CTO

2. Maximum 20 wallets per bundle

3. Ensure all have SOL balance

Step 4: Configure Buy Amounts

Method	Description
Equal	Same amount per wallet
Random	Random range (min-max)
Custom	Set each wallet manually

Step 5: Execute Bundle Buy

1. Review total SOL commitment

2. Set Jito tip (0.005-0.01 SOL)

3. Click "Execute CTO"

4. All buys execute in same block

---

Bundle Execution

How It Works

CTO Bundle Execution:

Wallet 1 (0.15 SOL) 
Wallet 2 (0.12 SOL) 
Wallet 3 (0.18 SOL) → JITO BUNDLE → Same Block
Wallet 4 (0.10 SOL) 
Wallet 5 (0.14 SOL) 

Result: All 5 wallets buy in exact same block
 No front-running possible
 Coordinated entry

Benefits of Bundle CTO

Benefit	Description
Atomic	All-or-nothing execution
No front-run	Can't be sniped
Coordinated	Same entry price
Stealth	Appears as organic buys

---

CTO Settings

Jito Tip

Level	Amount	When to Use
Low	0.003 SOL	Low competition
Medium	0.005 SOL	Normal
High	0.01 SOL	High demand

Slippage

For CTO on volatile tokens:

• Minimum: 15%

• Recommended: 20-25%

• High volatility: 30%+

---

Post-CTO Actions

After successful CTO:

1. Monitor Position

• Track MCAP and price

• Watch holder changes

• Set Auto TP targets

2. Community Building

• Share in Telegram groups

• Create social presence

• Engage with holders

3. Exit Strategy

• Set Smart Sell rules

• Configure MCAP targets

• Plan gradual exit

---

Best Practices

Before CTO

• Verify dev wallet sold

• Check contract is safe (no honeypot)

• Ensure sufficient liquidity

• Prepare all wallets with SOL

• Use Stealth Disperse before CTO

During CTO

• Use bundle mode (not individual buys)

• Set appropriate slippage

• Include Jito tip

• Double-check amounts

After CTO

• Verify all buys executed

• Set up Auto TP targets

• Configure Smart Sell

• Monitor for unusual activity

---

Risks & Warnings

::: danger Do Your Research CTO tokens can be risky:

• Original dev might return

• Contract might have hidden functions

• Liquidity can be pulled

• Always DYOR! :::

::: warning Start Small For your first CTO:

• Use small amounts (0.1 SOL per wallet)

• Test with 5 wallets, not 20

• Learn the process first :::

---

Related Guides

• Token Launch - Launch your own token

• Trading - Manual trading

• Smart Sell - Auto-sell configuration

• SOL Distribution - Fund wallets before CTO