# elizaOS Discord - 2025-11-25

## Overall Discussion Highlights

### Token Migration Issues
- A snapshot for AI16Z to ELIZAOS token migration was taken on November 11th, establishing a 1:6 migration ratio
- Major controversy emerged regarding Korean exchanges (particularly Bithumb) where users claim the exchange announced full migration support but later backtracked
- Similar migration issues reported with Kraken users
- Team maintains that tokens purchased after the snapshot date won't be migrated
- 90-day migration window is in place, providing time for resolution
- Users who held tokens before the snapshot but on exchanges are advised to keep them there for automatic migration or submit manual migration requests with proof of pre-snapshot ownership

### Project Development
- PR #6166 in the elizaOS/eliza repository was updated and expanded by Odilitime, later approved by Stan
- Babylon project has reached 100k signups, with effective referral mechanisms driving growth
- Ethereum Foundation is supporting AI builders and the development of open standards (8004 and x402) for autonomous agents
- Babylon has been promoted within Ethereum communities and was demonstrated at the Trustless Agents day event

## Key Questions & Answers

**Q: In which communities is Babylon going viral to reach 100k signups?**  
A: It's been pushed within Ethereum communities, demonstrated at Trustless Agents day (organized by dAI teams), and promoted via influencers like Shaw and Marco. The referral mechanism is working effectively. (Kenk)

**Q: Did the team inform Bithumb immediately after taking the snapshot?**  
A: "Of course we did" (jasyn_bjorn)

**Q: How do I solve the issue regarding tokens not eligible for migration after withdrawal from exchange?**  
A: "You have to wait and leave it on the exchange" (Serikiki)

**Q: Do you know when Kraken will migrate from ai16z to elizaos?**  
A: "No one knows if and when Kraken will migrate.. No information" (Serikiki)

## Community Help & Collaboration

1. **Migration Support for Exchange Users**
   - hns71 shared information from Kraken support confirming they're working on the migration issue
   - Serikiki confirmed that providing screenshots of token purchases before Nov 11 to the team is sufficient proof for migration
   - Arceon explained that tokens held before snapshot are eligible for manual migration with proof of ownership

2. **Technical Assistance**
   - jasyn_bjorn manually granted access to the ticket channel for a user experiencing CAPTCHA verification issues
   - The Light directed users with migration issues to the dedicated migration questions channel
   - Stan approved PR #6166 after Odilitime's request, acknowledging he had already reviewed it but forgot to press the approve button

## Action Items

### Technical
- Resolve migration issues for Korean exchanges (Bithumb, Coinone) (mentioned by multiple users)
- Finalize migration process with Kraken (mentioned by jasyn_bjorn)
- Implement manual migration process for users who held tokens before snapshot (mentioned by jasyn_bjorn)
- Review and merge PR #6166 in elizaOS/eliza repository (mentioned by Odilitime)
- Continue development of open standards (8004 + x402) for autonomous agents (mentioned by Kenk)

### Documentation
- Provide clear communication about snapshot rules and migration eligibility (mentioned by degenwtf)
- Create timeline/deadline for exchange migration decisions (mentioned by Will123)
- Share documentation of communications with exchanges regarding migration (mentioned by dracok)

### Feature
- Establish verification system for pre-snapshot token ownership (mentioned by multiple users)
- Distinguish between airdrop farmers and genuine users in Babylon's referral system (mentioned by Kenk)