You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the feasibility of making the SHA1 algorithm swappable so that users can implement, for example, BLAKE2?
I know that SHA1 is in the "basic kademlia" spec, but it doesn't look to me like using BLAKE2 will break anything, and for our purposes, we'd like to make it more difficult to create collisions.
The text was updated successfully, but these errors were encountered:
Hey @jMyles - my thoughts here are pretty much the same as for all extensibility requests. I'd like the lib to provide an implementation of the kademlia spec by default, but be highly extensible so that it can be used as a base for all kinds of different applications. Some thoughts around how the current code could be modified to specifically support a different hash function -
I think this could be done by adding a class method to Node for digesting
You could have a NodeFactory class that makes Nodes that is set in Server
Might take some refactoring, but I'm happy to look at any PRs or talk though implementation options before any work starts
What's the feasibility of making the SHA1 algorithm swappable so that users can implement, for example, BLAKE2?
I know that SHA1 is in the "basic kademlia" spec, but it doesn't look to me like using BLAKE2 will break anything, and for our purposes, we'd like to make it more difficult to create collisions.
The text was updated successfully, but these errors were encountered: