A Milestone & Metrics Driven Migration to Mainnet
We're excited to share our ongoing roadmap for migrating XMTP to v1 of our decentralized network. With millions of users and messages already flowing through the protocol, we're taking a measured, milestone-based approach to ensure a smooth transition that maintains the reliability our community depends on.
Why This Matters
XMTP is moving from our current V3 (centralized network) to a decentralized architecture that puts full control into the hands of node operators and the community. This isn't just a technical upgrade but rather a fundamental shift toward a more resilient, censorship-resistant messaging infrastructure. Our goal is to have 7 independent nodes operating v1 of our decentralized of the decentralized network at mainnet.
As part of this work, we’ve outlined a staged approach below.
Stage 1: Testnet Relaunch (December 2025) ✅ - Complete
We've launched a clean-slate testnet using our latest smart contracts and xmtpd code. This isn't our first testnet, but it represents a fresh start with production-ready technology.
Key accomplishments:
- XMTP mainnet chain launched with all smart contracts deployed
- Three nodes deployed (including one from XMTP Labs)
- Pre-seeding the network with all non-expired messages from XMTP V3 to create a realistic storage footprint
- Testing gateway service deployed
Stage 2: Testnet Validation (February 2026) — In Progress
With a realistic dataset and complete client support, we're now validating that the network can meet the needs of apps currently using XMTP. We're focused on three key metrics: latency, throughput, and reliability.
Latency Targets
We've set specific performance benchmarks for common operations:
| Single Operation Metrics | Target (p95) | XMTP V3 |
|---|---|---|
| Sync a group | <100ms | ~100ms |
| Send message to group - members can see the message (including stream) | <400ms | ~250ms |
| Create a group with 100 members | <2.5s | ~4s |
| Register a single new identity on the network | <1.5s | ~350ms |
| Add a new member to a 10 person group | <1.5s | ~250ms |
| Add a new member to a 250 person group | <1.5s | ~750ms |
| Group rename (10 member group) | <1.5s | ~100ms |
Throughput Requirements
The network needs to handle both current volume and expected growth:
- 1,000 offchain messages per second (burst)
- 50 onchain messages per second (burst)
- 10 million messages daily sustained throughput with 3 nodes
Reliability Standards
- 99.99% node reliability
- 0% fork rate in testing
- 100% integration test pass rate over 5 runs
You can track the progress of these performance benchmarks here:
https://xmtp.to/decentralization-metrics
Beyond the numbers, we're validating real-world experience by working with partners to test how their own applications UX are on the testnet. Metrics are important, but with messaging how it feels to actual users matters even more.
We'd love your feedback on our latency, throughput, and reliability targets. You can join our dev community discussion at:
https://xmtp.to/dev-community
Stage 3: Mainnet Preparation
Once testnet validation is complete, we'll begin a 60-day migration countdown. During this period, all XMTP apps will need to migrate to a mainnet-compatible SDK and connect to a funded gateway.
The mainnet-compatible SDKs will initially continue connecting to V3, ensuring no disruption while everyone prepares for the switch. Behind the scenes, we'll be deploying mainnet nodes and smart contracts while migrating data from V3 to mainnet.
Stage 4: Mainnet Launch
The final migration will be a coordinated cutover. At a predetermined (and highly communicated) time, the V3 network will signal clients to switch to mainnet. All communication will then flow through the decentralized network, with writes going through each application's configured gateway.
Please note: App developers should expect approximately 30 minutes of downtime during this transition.
What This Means for Developers
If you're building on XMTP, here's what you need to know:
- Test early: Connect to our testnet now to help validate your integration.
- Plan your migration: You'll have 60 days once mainnet preparation begins, and all latency, throughput, and reliability targets have been met to upgrade your SDK and set up a gateway.
- Fund your gateway: Applications will need to maintain funded gateways to subsidize messaging fees for users.
- You can read more about how to fund your application here
- Members of the XMTP community are also developing payer gateway services such as GatewayHost.dev
- Monitor our updates: We'll be sharing progress against our validation criteria throughout this process.
Transparent Progress Tracking
We're committed to transparency throughout this migration. You can follow our progress in real-time:
- Testnet funding portal (coming soon)
- Performance metrics from our automated testing suite
- Integration test results across all SDKs
- Community feedback from partner applications
Join Us
Decentralization isn't just about technology but rather about building a messaging infrastructure that no single person, company, or country can shut down or censor. We're taking this journey carefully and deliberately because we believe the future of communication should be open, resilient, and community-owned.
Stay tuned for updates as we hit each milestone. You can track detailed progress on our Improvement Forum and learn more about running a gateway in our documentation.