Dear Arweavers, I am happy to share that we have cleared all misunderstandings with @samecwilliams and the core Arweave crew in regards to forking Arweave. I’ve enjoyed working with Sam and the Arweave crew for the past few years, and I’m excited to keep working with them moving forward! I want to use this tweet to explain our position and address the key concerns we have heard from @irys_xyz users over the last couple weeks. Firstly, let’s clarify where matters stand: - Still, there has been no decision to fork Arweave. - Further, there are no changes on our side, technical or otherwise. We have always supported the Arweave Ecosystem and have no intentions of stopping. So, what has changed for our users? - Absolutely nothing. - All gateways will operate as expected. The optimistic cache has neither been revoked nor have we been told that it will be in the future. No changes are required on your end. From day 1, we’ve been focused on optimizing the developer experience (DX) on Arweave, which has always led to us having an interest in the core mechanics of Arweave. We are wondering if we might be able to make contributions to the system that help it grow and become even more resilient over time. So, what might it look like if we decide to fork? We will build exciting new provenance tech for the network while adhering to the framework for evolving Arweave. Moreover, we will continue to support Arweave itself and will never force users to migrate. We will continue to do what we do best: build infrastructure to support the growth of the Arweave ecosystem. We understand that Irys is critical infrastructure for most of our users. We do not take this responsibility lightly. We apologize for any distress this misunderstanding may have caused. If you have any questions or concerns, my DMs are open. Now, let’s get back to building 🫡