Druya ⚡️

Over the last 2 weeks, we've assembled multiple teams from around the world to develop a true parallel blockchain: -Team 1: Stage 1 QF (our public roadmap) -Team 2 & 3: Exploring designs for true parallel -blockchain (Stage 2) -Additional teams being formed This technology is cutting-edge, which is why we're starting with our current roadmap while pushing boundaries behind the scenes. We envision multiple teams working in parallel.on achieving stage 2. Our Goal: Deliver a new paradigm in parallelized blockchain. We're releasing parts of these design discussions as they unfold. Here's Team 2's proposal for Stage 2 of QF - a truly parallelized blockchain: 1/ The QF Team 2 discussed approaches for integrating parallelized computing into blockchain, weighing options between using HVM2 and developing a custom ASM-based solution. 2/ Key points: Proposed architecture differs from initial vision Exploring alternatives to HVM2 for broader compatibility Challenges with 32-bit limitations in current HVM2 version Potential limitations in scalability and adaptability of HVM2 due to hardcoded elements 3/ Team debated merits of starting with HVM2 vs custom solution: HVM2: Faster to market, aligns with investor expectations Custom ASM: More flexible, cross-platform, potentially more innovative 4/ Consensus: Consider hybrid approach Start with HVM2 to meet short-term goals Develop custom solution in parallel for long-term scalability 5/ Key challenges identified: Developer accessibility (ASM complexity) Consensus mechanisms for parallel smart contract execution Collecting & compacting results from parallel computing cores 6/ Next steps: Further research on HVM2 internals Prepare whitepaper for Stage 2 7/ The team remains committed to pushing the boundaries of blockchain technology, aiming to create a highly parallelized, GPU-optimized blockchain that can compete with top existing networks.

Q2 Successfully completed Q2 roadmap culminating in basic relayer integration Offchain-Relayer demonstration: Demoing our node, explorer, and HVM relayer in action. Showcasing seamless integration between components, including HTTP requests from a dummy sequencer to the HVM relayer, and successful extrinsic calls to the off-chain-gate pallet. Q3 Design and setup HVM infrastructure with ZK-based verification

1/ Respect to Victor, the genius behind HVM2. It’s a shame you feel this way. Our mission stated on website is clear: "Promote the advancement of the HVM2 and Bend ecosystems, recognizing the ingenuity of their creators." We’ve always acknowledged your contributions. 2/ While our whitepaper may fall short of your expectations. We are striving to build a parallel computing platform for scientists and innovators, using your groundbreaking work on HVM2 as our foundation. 3/ We chose the name QuantumFusion to symbolize innovation, not to imply the use of quantum computers. We extensively reference your work and clearly state our goal of promoting HVM2 and Bend. 4/ If using open-source tech like Rust to write our program means we’re impersonating its creators, then we need to rethink open source. HVM2 is open source, and we’re using it to build and innovate. Credit where credit is due. 5/ Calling us scammers without basis while we’re on track is disappointing. If you don’t want people using your tech, maybe it shouldn’t be open source. We’re here to build, innovate, and promote HVM2 and Bend. 6/ We offered to support you from day one, which you declined. We hold you in high regard and believe your work is groundbreaking. If there’s an issue with the name QuantumFusion, that’s a matter of opinion. 7/ Instead of fighting, let’s collaborate. Help us organize a hackathon to promote the Bend language and further the HVM2 ecosystem. Together, we can achieve even more and give back to the community.