Creator Pump Deploy

Inspiration

We wanted to make token launches easier for creators and enable direct fee sharing with influencers and collaborators. PumpFun is popular, but there was no simple way to designate fee recipients by Twitter handle instead of wallet addresses, automatically create wallets for non-crypto users, or let creators claim fees without technical setup. We built Creator Pump Deploy to bridge Web2 (Twitter) and Web3 (Solana), making token launches accessible to creators and their communities.

What it does

Creator Pump Deploy is a platform for launching PumpFun tokens with creator-friendly features. Users can create tokens with custom metadata, images, and social links through a simple UI. The platform enables Twitter-based fee sharing—users can designate fee recipients by Twitter handle (e.g., @username) instead of wallet addresses. When a Twitter user is set as a fee recipient, the system automatically creates a Solana wallet for them via Privy. Fee recipients can sign in with Twitter, view their accumulated fees, and claim them to their connected Solana wallet. The platform automatically uploads token images and metadata to IPFS via Pinata and tracks all token launches. Built using Cross-Program Invocation (CPI), tokens are created directly on PumpFun while adding these enhanced features.

How we built it

Smart Contract Layer: Built an Anchor program in Rust that uses CPI to call PumpFun's create instruction, handling account derivation and instruction data serialization, deployed on Solana devnet/localnet.

Frontend: Next.js 15 with TypeScript and Tailwind CSS, integrated Solana Wallet Adapter for wallet connections and Privy for Twitter authentication and wallet creation, with a real-time UI featuring form validation and preview.

Backend Services: Next.js API routes handle wallet creation via Privy API, Twitter user lookup via Twitter API, IPFS metadata upload via Pinata, fee claiming transactions, and launch data storage. Redis is used for caching wallet mappings and launch data.

Key Integrations: Privy for wallet creation and Twitter OAuth, Pinata for IPFS storage, Twitter API for user verification, and Solana Web3.js for blockchain interactions.

Challenges we ran into

The biggest challenge was implementing CPI to PumpFun, which required reverse-engineering the instruction format, discriminator, and account ordering. We tested multiple account configurations to match PumpFun's expectations. Twitter API integration presented issues with rate limits and error handling, which we solved by adding caching. Coordinating wallet creation with token creation when a Twitter handle is provided required careful async flow management. Building a secure fee claiming flow that coordinates Privy authentication with Solana wallet connections was complex. Ensuring IPFS metadata matches PumpFun's expected format while supporting custom fields required extensive testing. Correctly deriving all PDAs for PumpFun's bonding curve, metadata, and global accounts was also challenging.

Accomplishments that we're proud of

We successfully created a seamless bridge between Web2 and Web3, allowing users to designate fee recipients by Twitter handle without needing wallet addresses. The zero-friction wallet creation system automatically generates wallets for non-crypto users when they're set as fee recipients. We implemented a complete CPI solution to PumpFun, enabling token creation through our program. The user experience is intuitive with a simple UI for token creation featuring real-time validation and preview. We built a secure fee claiming system for Twitter-authenticated users. Most importantly, we successfully integrated smart contracts, frontend, and multiple third-party APIs into a cohesive, working system.

What we learned

We gained deep understanding of Solana CPI, including cross-program invocations, account derivation, and instruction serialization. We mastered advanced Anchor framework patterns for account validation and instruction building. We learned how to effectively combine traditional authentication (Twitter) with blockchain operations. We discovered best practices for storing and retrieving decentralized metadata via IPFS. We developed robust error handling strategies across multiple services (Twitter API, Privy, Pinata, Solana). Most importantly, we learned how to balance simplicity with functionality, especially for non-crypto-native users.

What's next for Creator Pump Deploy

Immediate: Deploy to Solana mainnet and add enhanced analytics dashboard showing token performance, fee accumulation, and creator statistics.

Short-term: Add creator profiles for showcasing launches and earnings, implement social features like share-to-Twitter, leaderboards, and creator discovery, and support advanced fee splitting with multiple recipients and percentage-based splits.

Long-term: Build token management tools for creators to manage multiple tokens and view analytics, optimize mobile experience, implement notification system for fee alerts and token milestones, and create a public API for developers to integrate Creator Pump Deploy functionality. We're also exploring multi-chain support to extend to other chains with similar token launch platforms.

Built With

• anchor
• next.js
• react
• solana
• web3.js