JungleAlpha.eth

.@cypher_stack completed their audit of carrot_core! github.com/cypherstack/carro… Summary of results • The security properties defined in the specification were found to be present in the implementation. • Both C++ and Rust use Blake2b keyed mode per RFC 7693; the specification notation uses concatenation syntax. Both implementations appear structurally consistent with the specification, though equivalence is not proven here. • The enote scan algorithm tracks the specification closely; one specification step (Step 18) is not included but is mathematically redunant. • Step 18 of the specification is not included in either the C++ or the Rust implementation, but it is mathematically redundant. • All domain separator constants in config.h match the specification byte-for-byte. Conclusion The carrot core library closely tracks the CARROT specification. Key derivations, enote constructions, scan algorithms, and domain separators were checked for consistency with the specification. The only protocol-level deviation identified was the exclusion of Step 18 (redundant by construction). Outside of the scope of carrot core itself, a divergence regarding the domain separator used in the coinbase extension path was also observed between the C++ carrot core and the Rust carrot-rs.

Scaling Blockchain Surveillance - ArticMine @monerotopia 2026 #Monero $XMR