Skip to content

Conversation

@fjl
Copy link
Contributor

@fjl fjl commented Nov 28, 2025

The upstream libray has removed the assembly-based implementation of keccak. We need to maintain our own library to avoid a peformance regression.

The upstream libray has removed the assembly-based implementation of keccak.
We need to maintain our own library to avoid a peformance regression.
@fjl fjl force-pushed the crypto-keccak-vendoring branch from 2d97756 to 43863ae Compare November 28, 2025 14:07
Copy link
Member

@gballet gballet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should both go.mod not be updated in order to remove the reference to the other package?

@fjl
Copy link
Contributor Author

fjl commented Nov 30, 2025

We use some other packages from golang.org/x/crypto still

@rvagg
Copy link

rvagg commented Dec 2, 2025

Since go-ethereum isn't the only project impacted by this (Filecoin is too, there's likely many more), perhaps a separate repo to maintain the extracted package would be good? It could even be a shared concern among those of us that depend on it so we can collectively maintain it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants