# elizaOS Discord - 2025-04-20

## Overall Discussion Highlights

### Auto.fun Launch and Technical Issues
- **Platform Launch**: Auto.fun, a token launchpad platform developed by Shaw and team, was launched but experienced significant backend issues
- **Technical Challenges**: The site went down multiple times due to high load, with users reporting tokens not showing up, migration delays, and price display problems
- **Continuous Development**: The team has been on a 40+ hour dev call working to fix the issues
- **Maintenance Mode**: The site was temporarily put into maintenance mode for updates
- **First Successful Migration**: KRSK was identified as the first token that successfully migrated with 79 SOL added to LP
- **Security Incident**: Shaw's Twitter account was compromised and used to promote a suspicious token called "COO"

### Auto.fun Technical Details
- **Bonding Curve Mechanism**: Uses 28 SOL initial virtual reserves; tokens graduate to Raydium at 113 SOL (85 SOL + 28 SOL virtual)
- **LP Token Distribution**: 90/10 split between creators and Auto.fun
- **Fee Structure**: 10% of bonded LP fees collected by the platform will be used to buyback $ai16z from the open market
- **Token Verification**: Currently reserved for vetted companies with prior relationships; formal process coming when platform is more stable

### ElizaOS Plugin Development
- **Plugin Issues**: Users encountered problems with Discord and Telegram plugins, particularly around event handling and callbacks
- **Database Errors**: Several users faced PostgreSQL relation errors when starting ElizaOS projects
- **Custom LLM Integration**: Discussions about using custom LLM providers like Deepseek with ElizaOS
- **CSP Issues**: Content Security Policy problems reported on Windows machines
- **MIDI Plugin**: A user mentioned developing a MIDI plugin for agent communication

### Future Developments
- **V2 Launch**: Discussions about a potential V2 launch in the coming week
- **Agentic Features**: Current Auto.fun release focuses on token and content creation, with agent features planned for V2
- **Launch Partners**: Team mentioned they would be sharing information about launch partners in the coming days/weeks
- **Marketing Push**: Planned to start after platform upgrades are completed

## Key Questions & Answers

**Q: How does the bonding curve work?**  
A: Auto.fun uses a bonding curve with 28 SOL initial virtual reserves. When a coin reaches 113 SOL in reserves (85 SOL + 28 SOL virtual), it automatically graduates to Raydium with a 6 SOL flat fee.

**Q: What is the fee structure for Auto.fun?**  
A: The platform collects 10% of the bonded LPs fees, then will buyback $ai16z from the open market, to finally reinvest in ai16z LP to create deeper ecosystem liquidity.

**Q: What happens to tokens created before the official launch?**  
A: Tokens created using the leaked developer link (autoUm program) cannot be supported, while tokens created on the official platform with indexing issues will be fixed.

**Q: What does "locked" status mean for tokens?**  
A: The "locked" status indicates that the token's liquidity pool tokens have been successfully locked as part of a migration process.

**Q: How do you get a verified tick on Auto.fun?**  
A: Currently reserved for companies with prior relationships that have been vetted. A formal process will be released when the platform is more stable.

**Q: What was causing the Jupiter integration errors?**  
A: Too many decimals in calculations, which the team is working to fix.

**Q: Why isn't Degenai included in the buyback mechanism?**  
A: 1) Spartan already gets carry, 2) technical complexity of splitting fees across numerous buyback mechanisms, 3) it would confuse the ecosystem vs agent narrative.

**Q: Is AI16z the native token for auto.fun?**  
A: Some users speculated it might be, though others disagreed since anyone can access auto.fun without having AI16z token.

**Q: Does eliza-v2 work with deepseek?**  
A: You may need to create your own plugin.

**Q: How do I fix the "relation 'logs' does not exist" error when starting the project?**  
A: Drop pg instance -> drop volume.

## Community Help & Collaboration

1. **Token Migration Assistance**:
   - Helper: accelxr | Helpee: joeyseoul | Context: Token stuck in migration for over 16 hours | Resolution: Manually migrated the token
   - Helper: accelxr | Helpee: FatalPie | Context: Token "Eddy" stuck in migration for over 20 hours | Resolution: Successfully migrated the token

2. **Technical Troubleshooting**:
   - Helper: accelxr | Helpee: yikesawjeez | Context: Sell button not working for $WWF token | Resolution: Team identified the issue was related to decimal handling in Jupiter integration
   - Helper: mortenssen | Helpee: mortenssen | Context: Database relation errors on startup | Resolution: Suggested dropping PostgreSQL instance and volume if running in Docker

3. **Custom Integration Support**:
   - Helper: Kenk | Helpee: BowTiedBlueFin | Context: Needed to use custom OpenAI API compatible base URL | Resolution: Suggested creating a new plugin or adding a new instance provider in env file
   - Helper: Kenk | Helpee: mortenssen | Context: Using Deepseek LLM with ElizaOS | Resolution: Suggested creating a custom plugin and shared relevant documentation links

4. **User Guidance**:
   - Helper: jin | Helpee: Multiple users | Context: Users reporting tokens not showing up after creation | Resolution: Advised users to post in #support-auto-fun channel with details/contract address
   - Helper: Mr G | Helpee: Pyroman | Context: User had questions about token migration and platform functionality | Resolution: Explained differences between importing and migrating tokens and how the platform works

## Action Items

### Technical
- Fix backend issues causing auto.fun to go down under load (Mentioned by: shaw)
- Fix token migration process for early tokens (Mentioned by: Multiple users)
- Fix price display issues for tokens (Mentioned by: abhi_ironman)
- Fix issue with created tokens not showing up (Mentioned by: casper, phetrusrodrigues)
- Fix "locked" status for tokens where users can't sell (Mentioned by: noj)
- Fix claim fees functionality and "failed to claim fees" error (Mentioned by: Xyness)
- Fix Jupiter integration errors with decimal handling (Mentioned by: accelxr)
- Fix how Discord plugin events are being subscribed to (Mentioned by: mortenssen)
- Fix double callback issue in plugin-bootstrap (Mentioned by: mortenssen)
- Fix database relation errors on startup (Mentioned by: mortenssen)
- Fix CSP issues with V2 on Windows machines (Mentioned by: mortenssen)
- Fix bonding filter accuracy (Mentioned by: Pyroman)
- Fix the "Install MyWebsite" text when installing the site on mobile (Mentioned by: Patt)
- Address security issues with team accounts after Shaw's Twitter was compromised (Mentioned by: eskender.eth)

### Features
- Implement bounty rewards for FUN token (Mentioned by: Rick)
- Create a potential "hit coin" to generate interest in auto.fun (Mentioned by: Moliza)
- Add ability to sort tokens by "most filled" to see which are close to bonding (Mentioned by: thatjpeg)
- Create a community memecoin as a mascot for auto.fun (Mentioned by: wire)
- Enable attaching newly generated images/videos directly to token-gated chat (Mentioned by: yardy)
- Add support for posting random images from a folder (Mentioned by: TruffleSoul)
- Add support for custom OpenAI API compatible providers (Mentioned by: BowTiedBlueFin)
- Add Deepseek LLM support (Mentioned by: mortenssen)
- Implement a technofeudalist DAO with token value backed by land (Mentioned by: Mr. Nucleus)
- Add bonding curve percentage to Telegram bot data (Mentioned by: MONO)
- Implement footer accessibility with infinite scroll (Mentioned by: Pyroman)
- Add multiple parameter sorting (Mentioned by: Curtisdonthurtus)
- Add more interactive filters (volume, age, verified, holders, etc.) (Mentioned by: Lucid)
- Add disconnect wallet button (Mentioned by: yikesawjeez)

### Documentation
- Provide information on launch partners (Mentioned by: Kenk)
- Provide status updates on AutoFun's X account (Mentioned by: HoneyBadger)
- Establish customer support via AutoFun's X account (Mentioned by: HoneyBadger)
- Clarify the token migration process and expected timeframes (Mentioned by: Multiple users)
- Update messaging around "locked" status for tokens (Mentioned by: shaw)
- Create clearer UI for fee claiming process (Mentioned by: accelxr)
- Add website link option for token pages (Mentioned by: 🧧ThanosDaSith24🧧)
- Release formal tokenomics article (Mentioned by: accelxr)
- Create success stories of token launches for marketing (Mentioned by: hubert)
- Establish formal verification process for tokens (Mentioned by: eskender.eth)