-
Notifications
You must be signed in to change notification settings - Fork 284
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
WIP feat(core-crypto): Rework crypto package to be instance-based #3742
Conversation
…lity to instantiate from config or preset
…used with custom blocks
… different package
…erialisation step
This pull request introduces 1 alert when merging 5884991 into 8a2033a - view on LGTM.com new alerts:
|
…nd get static fee correctly
…lances on cryptoManager
This pull request introduces 1 alert when merging 242037e into 8a2033a - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 5fdc249 into 8a2033a - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 6450264 into 8a2033a - view on LGTM.com new alerts:
|
…ld be called with cryptoManager
This pull request introduces 1 alert when merging 5149778 into 8a2033a - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 81a3557 into 4b68d5f - view on LGTM.com new alerts:
|
Closing due to feedback that was given internally. |
Summary
WIP Implementation of #3628
Refactors the
Crypto
package to be instance based - this is now split into two packages:Crypto
which contains default cryptography methods and managers, identities, transactions (and their de/serialisation methods) and libraries.Core-Crypto
which wraps the otherCrypto
package, and which provides a more completeCryptoSuite
, which also includes schema validation and blocks (including factory methods/managers, and de/serialisation methods).This allows more than one configuration to be loaded at run-time, avoids relying on global variables or the node module cache. This in turn reduces bugs caused by subtly shared state.
Checklist