Runway was never designed to be a finished destination. It was designed to push the boundaries of what’s possible on Canton. Over the past few weeks, community participation pushed Runway well beyond its original operating assumptions. In doing so, it revealed opportunities to further optimise how the application manages state and memory at scale. Those improvements have already been implemented and are now being rolled out through the ongoing mainnet migration. That is exactly why Runway exists. Real infrastructure isn’t validated in a test environment. It’s validated when real users arrive and begin interacting at scale. Thanks to this community, we’ve been able to identify, improve and strengthen Runway long before opening it to a much wider audience. We know the experience hasn’t always been seamless, and we understand the frustration caused by the issues many of you have encountered over the past few weeks. Every bug report, support ticket and piece of feedback has helped us identify edge cases that simply don’t appear in controlled environments, making the platform stronger with every iteration. Participation has always been at the heart of Runway. Your testing has directly shaped the improvements now being deployed, and rewards have already been distributed to active community members who helped move the platform forward. This migration is more than a collection of bug fixes. It’s the foundation for everything that’s coming next: native EDEL swaps, asset withdrawals, broader access beyond the initial cohort and a platform engineered to support significantly more users. Building new infrastructure means continuously raising the bar, learning from real-world usage and improving with every release. That’s exactly what this community has helped us do. We’re not interested in shipping a platform that only works until adoption arrives. We’re building one that works because adoption arrived first.