You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be helpful to add for others following this guide since the error message returned without this is very confusing at first
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?
the sign-tx command immediately checks for a node connection here but it looks like this is only used to look up the wallet context
is there a way to pass in a wallet file or similar as an argument and forego any node requests when offline?
namadac sign-tx --tx-path transfer.tx --owner wallet1
Failed to query node status with error:
0: HTTP error
1: error sending request for url (http://127.0.0.1:26657/): error trying to connect: tcp connect error: Connection refused (os error 61)
....
Broadcast:
I've gotten this working but there are some sharp edges that I wanted to note:
i) this command wants to automatically submit a 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 the reveal_pk command indepdentely
ii) This transaction needs to be signed by the gas_payer to be valid. This should be moved to the offline sign-tx command so private keys never needed to be loaded to the online machine
namada client tx --tx-path tx.tx --signatures sig1.tx --owner view-only-wallet --node https://rpc.luminara.icu --gas-payer view-only-wallet --force
Submitting a tx to reveal the public key for address <address>...
Error:
0: unable to sign transaction with <pubkey>
....
I am following the offline signing guide in the docs here
Running version: Namada v0.32.0 on campfire testnet luminara.45fd94fb5c14d0dd304da
The text was updated successfully, but these errors were encountered:
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: