-
Notifications
You must be signed in to change notification settings - Fork 122
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
Enable support for secp256k1 consensus key #761
Comments
it's merged. Actually it would be nice if we could cut minor release (that would include): we are running a forked version. @activenodes our band runs with the patch for couple of months and no issues so far |
Sorry @mkaczanowski trying to build (from main too) the result is always the 0.12.2 without the support for secp256k1 |
I suppose I can cut a minor release, although it technically breaks some of the contracts we set out for in the README.md, like preserving MSRV |
It would probably make more sense for me finish slogging through some of the other upgrades and cutting a major release instead |
Sorry @mkaczanowski @tony-iqlusion |
@activenodes |
Testing with a VM, same result... mmm...
|
Unfortunately I don't think softsign is currently supported. It would need to be added to tendermint-rs, which currently only supports Ed25519 private keys: https://docs.rs/tendermint/0.33.2/tendermint/private_key/enum.PrivateKey.html |
It's used here in the first example #644 |
I would suggest asking @mkaczanowski as I have no idea how it would be possible to import such a key given the current code |
ah, we haven't used the softsign, but yubihsm. I felt this was too easy PR :). Lemme see what I can work out here |
@activenodes the
you can see it in the original PR: and here you have a configuration snippet that works:
simply don't use the |
To solve this issue properly I would have to at least touch two repos: so that won't be a quick fix. I also wonder if it is even worth doing it that way, band is likely the only network nowadays that uses You can sign with tmkms, as described above. I don't think the I am leaning towards #wontfix |
The tendermint-rs crates are all in a monorepo, so you can change both in a single commit: https://github.com/informalsystems/tendermint-rs They're under the |
okay, lemme see what I can do here then |
I'm doing some tests and if copying |
Working!
Thanks guys 💯 |
I've made the PR in I slightly hacked the current
^^ ignore ed25519 message, it is secp256k1 key. @tony-iqlusion do you have any plans to upgrade the |
Yes, I have a local PR to do it, but it's a mess because I started working on it before merging the secp256k1 consensus PR and a lot has changed upstream in tendermint-rs. I need to finish rebasing it. |
After changed my key with previous key json
|
informalsystems/tendermint-rs#1358 is merged, now I think I'll wait for @tony-iqlusion to push his upstream rebase PR (#761 (comment)) |
This is released as v0.13.0-pre.1 in #779 |
@mkaczanowski want to integrate private key import support now? |
yeah, lemme prepare a PR |
@tony-iqlusion @mkaczanowski is there a way to enable and test this?
#644
One year ago...
The text was updated successfully, but these errors were encountered: