-
Notifications
You must be signed in to change notification settings - Fork 947
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
Offline signing command requesting local node #3201
Comments
Hi @dan-u410 . Thank you for brining these issues up! Over the next few days I'll try to reproduce them and reduce the need for a local node in some of the |
Hi @murisi any update on this? It looks like broadcast is also not able to function without some account's private-keys loaded on a hot machine to act as the gas-payer. imo this is problematic |
it looks like there is a bug in as I currently understand this; generation/signing/broadcast are all broken in some form |
we are currently working on this (pr #3648) |
Hi @Fraccaman any updates here on offline signing? it looks like the PR has been closed. |
Some steps in the offline flow don't match the workflow I'm seeking:
Generation:
Signing:
I've configured my offline wallet with the secret keys necessary for signing, however it seems the node needs to be started locally to sign offline?
sign-tx
command immediately checks for a node connection here but it looks like this is only used to look up the wallet contextBroadcast:
reveal_pk
tx. However, this is not possible when the owner's private keys are not loaded onto the node. I am forking the SDK and removing this line from this command since I will issue thereveal_pk
command indepdentelygas_payer
to be valid. This should be moved to the offlinesign-tx
command so private keys never needed to be loaded to the online machineI am following the offline signing guide in the docs here
Running version:
Namada v0.32.0
on campfire testnetluminara.45fd94fb5c14d0dd304da
The text was updated successfully, but these errors were encountered: