Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Concept] SHA256 implementation proposal #882

kilrau opened this Issue Apr 11, 2019 · 0 comments


None yet
2 participants
Copy link

commented Apr 11, 2019

If received payment hash can't be resolved with current hash function:

  • loop through other available hash functions
  • if it can be resolved with another hash function - use this one - and mark sender with this new hash function as default
  • opens raiden generically to support many more hash functions
  • avoids p2p message overhead
  • doesn't require any changes on API (e.g. hash function field in payment)

Anything I missed? @offerm

@kilrau kilrau added this to the 1.0.0-sprint.14 milestone Apr 11, 2019

@kilrau kilrau added the raiden label Apr 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.