First step for a one-person project, and a second RFC 6962 implementation as a test peer
Hello, I write a language called BuildLang. One of its packages computes RFC 6962 Merkle roots. This week the compiler gained a WebAssembly backend, and under it the package's roots for 1, 2, 3, 7 and 16 leaves equal roots computed with Node's crypto. The 3-leaf root also equals the C backend's output. Only roots are compared under WebAssembly so far. Nothing here is signed or witnessed. I'd like to log release checksums for my own tools, and I have two questions. Is submitting to an existing Sigsum log with your stock tools the right first step for a one-person project? Would an independent tree implementation be any use to you as a test peer? The change and its tests: https://github.com/HarperZ9/buildlang/pull/281 Zain Dana Harper harperz9.github.io
participants (2)
-
Niels Möller -
Zain Harper