This PR updates the gohashtree library to this fork. We do it because we rely on a branch of gohashtree to perform zero allocation of bytes which is not yet on main branch and I am not sure when it will land. Because of that, fastssz was forced to vendor the dependencies.
By using a fork, we ensure the liveness of that specific feature and we can remove vendors from fastssz.
This PR updates the gohashtree library to this fork. We do it because we rely on a branch of
gohashtreeto perform zero allocation of bytes which is not yet onmainbranch and I am not sure when it will land. Because of that,fastsszwas forced to vendor the dependencies.By using a fork, we ensure the liveness of that specific feature and we can remove vendors from
fastssz.