Last week we unveiled a new standard we are working on: ZKThreads 🧑‍🔬 This standard, being developed in collaboration with @cartridge_gg, introduces a novel framework for execution sharding that provides scalability and customizability without fragmentation. It also allows for direct fallback onto the base layer, ensuring continuous operation at every step. In simple terms, ZKThreads will offer developers improved: ✅ Security: Developers can execute directly on Starknet when necessary, ensuring continuous operation at every step and a leaner design for dApps. ✅ Composability: Developers are provided with a standard, composable toolkit to create a wide range of provable applications, including native bridging, common DA layers, and security mechanisms. ✅ Interoperability: All applications using the ZKThread standard will seamlessly interact with each other, reducing fragmentation and opening up numerous new use cases. For users, ZKThreads will bring: ✅ Enhanced UX: Thanks to the interoperability provided by ZKThreads, users can switch between apps built as ZKThreads without changing networks or other infrastructure. ✅ Lower transaction fees: Similar to L3s, ZKThreads allows for further scaling on Starknet by adding an additional layer of proof compression before settlement, resulting in even lower costs than on the public Starknet L2. ✅ No fees on the thread: Apps operating as a ZKThread update the base layer in bulk at regular intervals. This means users won't have to pay fees on their individual transactions within the thread. Fees only apply when settling on the base layer. Yes fam, this is huge! Learn more by reading the following article and stay tuned for even more!