David Pokora

Sorry, this issue will be addressed in the coming days. Meadow was not maintained for some months, as it was a project we started at Hosho, before we moved on...

More loose thoughts: - We can probably make printf style logging if we wrap colors in an intermediate structure and disable/enable the values depending on context provided (if the logging...

Just for more information, this seems to be a non-issue, and not a problem on our end: - https://github.com/golang/go/issues/61229 - https://github.com/golang/go/issues/61558

Updated the title here and removed CODEOWNERS as a TODO so it doesn't get bundled up as we also had #64.

ABI values are serialized here, I'd check this out: https://github.com/crytic/medusa/blob/e471c52460ae9a37f5e168a96cbb0fbbe4db33a0/fuzzing/valuegeneration/abi_values.go#L534C13-L534C13 Solidity strings are just byte arrays with a given length, so \x00 should be retained, but it's probably lost in...

References for any engineer: https://blog.carlmjohnson.net/post/2023/golang-git-hash-how-to/ (this looks simpler) https://www.forkingbytes.com/blog/dynamic-versioning-your-go-application/ (this looks like it requires you to use special params for `go build`, which isn't ideal, but hopefully it brings you...

Good callout. We've had similar discussions with @Jaime-Iglesias . I'll drop some thoughts here stemming from those discussions. This PR should extend past TestChain and we can provide some nice...

Idea: The fuzzer_metrics.go file is pretty simple/sad. We could revamp it to track this and other statistics there. And leave room for arbitrary statistics users might have in their tests.

We will leave this issue open, but this is not a priority for now. We do differentiate contracts with the same name now, but maybe not everywhere. Removed the "good...

This was necessary when crytic-compile had a fatal bug and we still wanted to work around it, so it should be less relevant now if I remember correctly. I don't...