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

tx signer #922

Open
cxyzhang0 opened this issue Jan 20, 2025 · 2 comments
Open

tx signer #922

cxyzhang0 opened this issue Jan 20, 2025 · 2 comments

Comments

@cxyzhang0
Copy link

Hi,
In example config, there is an optional section for tx_signer. Also, in the tmkms framework, secp256k1 account keys are supported in addition to ed25519 consensus keys. Since CombetFBT only uses ed25519 keys for validators, I assume the secp256k1 keys in tmkms are intended for tx signing only.
I'd like to use the tmkms tx_signer function to have tmkms manage my hsm-backed validator k256 account keys to sign such transactions as slashing, etc. How can that be done?

@tony-iqlusion tony-iqlusion transferred this issue from iqlusioninc/abscissa Jan 20, 2025
@tony-iqlusion
Copy link
Member

TMKMS had legacy support for transaction signing using Amino, but it's long-since removed (see #764).

The current secp256k1 support is for consensus keys (see #644). Notably the Band Protocol uses secp256k1 consensus keys.

@cxyzhang0
Copy link
Author

@tony-iqlusion thank you for the info. I guess I will look for a wallet solution for the validator tx signing key.
Also it is good to know k256 is being used for validator block siging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants