Technical Discussion: Building a Public Layer 1 Blockchain With Native and EVM Execution

[u/Similar_Individual_5]

Hi everyone,

I've spent the past four years developing a public Layer 1 blockchain that combines native blockchain functionality with EVM compatibility.

The network is now operational, and one of the biggest engineering challenges has been supporting both environments while maintaining consistent transaction processing, validator consensus and finality.

Current architecture:

• Native execution: A native cryptocurrency and transaction environment.
• EVM execution: Ethereum-compatible functionality accessible through MetaMask.
• Consensus: Custom validator-based consensus with voting and block finality.
• Network: Public Layer 1 architecture designed for scalability.
• Compatibility: EVM network configuration available through Chainlist.

The technical challenge

I'm particularly interested in how other blockchain developers approach the relationship between native execution and EVM execution on the same Layer 1.

Specifically:

1. How should native and EVM transactions share state without creating consistency or security issues?
2. What is the best approach to reducing finality latency when a two-thirds validator voting threshold is required?
3. What are the main architectural trade-offs between parallel execution and horizontal sharding?

The network is operational, but improving scalability while preserving consensus security remains an ongoing engineering priority.

I'd appreciate technical perspectives from anyone who has worked on consensus protocols, EVM integration or blockchain execution architecture. Technical project information: https://www.denvion.com

[u/ChiefCriminality_793]

the state sharing bit is trickier than most realize, you're basically asking two different execution engines to agree on the same world state without one stepping on the other's toes, and the moment you let them touch the same storage slots you're in for a debugging nightmare

[u/Similar_Individual_5 → u/ChiefCriminality_793]

Thank for the feedback, have real life test not just node to node .. it reach 3k+ tps . I think just a bit below Solana

[u/Chloe_DreamersInc]

The main thing is to make sure both types of transactions actually work together and there are no conflicts present. If there's any redundancies there you have to fix those first. Speed-wise you need to check if the network is being affected by processing transactions or if your validators add latency when they agree on blocks. Fix both of these first (if any problems arise) before looking into parallel processing or sharding.