43. Secure Coding Requirements

To ensure the C++ node daemon remains uncompromised, the engineering team adheres to non-negotiable coding standards:

1. Multi-Party Review: All consensus, execution, storage, and cryptographic code is reviewed by at least two engineers, including one designated security reviewer.
2. Strict Bounds Checking: All external inputs (RPC JSON payloads, P2P network frames, EVM bytecode) are fully validated and size-bounded before parsing.
3. Memory Safety: Raw pointer arithmetic is strictly forbidden in consensus and execution paths.
4. Supply Chain Defense: External dependencies are strictly vendored to prevent upstream supply-chain injection attacks.
5. Error Handling: All errors are wrapped in std::expected and enforced via [[nodiscard]]. Silently dropping errors causes immediate compilation failure.