Technology
TrustDAG combines Blake3+ proof-of-work block creation, Shoal++ BFT consensus and finality, a Fractal-DAG physical network model, native EVM compatibility, Rust-focused WASM compatibility, and post-quantum security design.
Blake3+ proof-of-work manages block creation through compatible ASIC mining hardware. Miners create and present candidate blocks.
Shoal++ BFT is the consensus and finality layer. It handles voting, quorum agreement, and finality.
The proof-of-work layer and the BFT layer work together, but Shoal++ is the consensus component.
TrustDAG applies the DAG vision beyond code-level data structure. The network is designed as a Fractal-DAG of coordinated clusters.
Each cluster follows the same hybrid rules and runs at the same operational rhythm. Cluster synchronization is called the TrustDAG heartbeat.
The heartbeat is the coordination pulse that keeps the physical network aligned across clusters while preserving the same protocol behavior.
TrustDAG is designed to align critical security paths with NIST-standardized post-quantum cryptography where those controls are implemented.
ML-KEM-1024 protects communication paths that require post-quantum key establishment, including protected website-to-blockchain communication and protected system communication.
ML-DSA-87 protects high-value signing workflows, including DAO voting and Treasury multisig voting where post-quantum digital signatures are required.
SLH-DSA acts as a fallback signing family. Its stateless hash-based design gives TrustDAG a conservative backup path if lattice-based signature assumptions are weakened in the future.
This architecture is a security design commitment, not a claim of absolute immunity, formal certification, or completed third-party audit.
TrustDAG is designed for native EVM compatibility so familiar smart-contract tooling can connect to the ecosystem.
WASM compatibility is focused on Rust-based development paths.
EVM compatibility and EVM equivalence describe how closely a blockchain follows Ethereum execution behavior.
EVM compatibility means a network can run Solidity and Ethereum-style smart contracts, but it can require minor script changes, custom compilers, different gas mechanics, or network-specific adjustments. Examples include zkSync with its custom zkSolc compiler and older sidechain designs.
EVM equivalence, also called EVM-identical execution, replicates Ethereum execution logic and opcodes closely enough for standard Ethereum tooling to work unmodified. Examples include Optimism, Arbitrum, and parallelized EVM designs such as Monad.
Non-EVM chains use different runtimes and do not directly mimic Ethereum's execution model.
TrustDAG chooses EVM compatibility because it gives developers access to familiar Solidity and Ethereum-style workflows while preserving room for TrustDAG's custom Layer 1 design, Blake3+ block creation, Shoal++ BFT finality, Fractal-DAG physical network structure, Rust-focused WASM paths, and protocol-level security rules.
