-
Notifications
You must be signed in to change notification settings - Fork 224
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
Move Secret Connection crate back to KMS #27
Comments
Moving this back would unblock KMS on #11 and allow us to experiment with solving timeouts with various async strategies |
…mint-rs#27) This commit wires up the Secret Connection implementation, whose code is otherwise by definition identical to the `tendermint-rs` v0.10 crate today, as it used to live in this repo and was restored by reverting it in commit 104bb82. Otherwise this is the minimum necessary changes needed to use the in-tree copy as opposed to `tendermint-rs`. It otherwise performs no changes or upgrades other than the ones needed to make the code compile and pass the latest `clippy`.
PR open to move Secret Connection back to the KMS here: After that lands, I'd suggest deleting the copy of Secret Connection in-tree in this repo, as well as removing ring (see #11) and |
Vendor Secret Connection (fixes informalsystems/tendermint-rs#27)
Secret Connection is a bit heavy duty for this library. It's currently needed by the KMS, and will likely see some upgrades in the near term that will need to be closely integrated with the KMS (ie. to support timeouts via async/await - #2). See also the relevant dependency issue #11 and PR #21.
We likely won't won't need Secret Connection here for a while as we're focusing first on the light client and deterministic simulation of reactors, and by the time we look to integrate with peers, with any luck, a libp2p solution will be ready for Tendermint adoption.
The text was updated successfully, but these errors were encountered: