Erick λ
Erick λ
Good suggestions! Those are definitely worth having.
@NishantBansal2003 Are you planning on working on adding the other modules?
We could consider accepting multiple definitions in the bitcoinfuzz Makefile. However, I'm uncertain about the potential consequences of implementing this approach. ```Makefile ifeq ($(UNAME_S), Darwin) LDFLAGS = -framework CoreFoundation -Wl,-ld_classic...
> Add the base58 utils to "modules/custommutator/" (similarly to how bech32 and sha256 are there)
> Does this mean that the initial `fuzz_data` that the mutator receives is a (valid) key encoded in base58? I thought the mutator receives random bytes and works with them......
Working in this one
Would it be worth reusing secp256k1 inside the Bitcoin folder instead of copying it from there to the custom mutator folder?
> How would you reuse it? If it means to build the Bitcoin Core module, so I prefer to not use it. Also, using secp from Bitcoin module means that...
Actually I will put this in draft for now, because I don't think that we need to create 2 different targets and custom mutator for decoding onions.
> Nice work. Do you have a link to the legacy format to help in reviewing this? Thanks! There is a book mastering lightning network and the old bolt 04...