-
Notifications
You must be signed in to change notification settings - Fork 118
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
Question: Why SpongyCastle (instead of Bouncy)? #4
Comments
Hi, some time ago when we started work on the cryptography side of the SDK, we looked at many libraries and were a also conscious to ensure that keys generated from the Android+iOS wallets were fully compatible with those generated by the SDK and vice-versa. The Android wallet uses SpongyCastle so to avoid any inconsistencies it felt right to use the same in the Java SDK. Having tried other libraries such as LibSodium, compatibility wasn't consistent. Hope this clarifies. |
Resolve "All QueryBuilders must validate the node pre check on a response from Hedera" Closes #4 See merge request hedera/hedera-sdk-java!86
Hi, in case you need a more recent version of BouncyCastle in the SpongyCastle style, I made a tool called |
I saw (in ECKeypair.java for example) that SpongyCastle is used instead of BouncyCastle
I found this Github issue by the author about Spongy being obsolete or not but most people voted for SC being wanted.
So I just thought it would be interesting to know which advantages of SpongyCastle was attractive to prefer chose it over BouncyCastle 😄
The text was updated successfully, but these errors were encountered: