ledger tx issues

[inland acorn]

did it actually get to you signing the tx with the ledger before you got the error?

[upbeat panther]

yes, it did

namada app on the ledger is v3.0.4

[inland acorn]

could you try adding an explicit --signing-keys parameter?

[upbeat panther]

already tried that

[inland acorn]

which validator tnam are you wanting to claim from?

are you adverse to sharing the source address as well?

[upbeat panther]

can we move this to DM then please?

[inland acorn]

would rather keep it here, but you can send me the addresses via dm yes

going a bit to and from in the chat atm so may have some reply time lag

[upbeat panther]

on https://namada.omniflix.co/, after clicking on Claim, and approving on the ledger, the UI says success, but then all the numbers (available tokens, staked tokens, rewards, etc) went to 0, and the block explorer showed the transaction as failed

[inland acorn]

ok so I checked the info you sent me in dm and there is something funky with your source account - did you create it as an established account or was it derived from the ledger by deriving it via namadaw derive?

I kinda understand why you got the error you did as there is no public key attached to that acct (check namadac query-account). but can't check rn if that's normal for the ledger-derived ones. looks really weird though

not what I asked..

how did the source account you staked from come into being?

i've seen a similar error a while back when I did something really dumb with the cli 😅

particularly did anyone use a --force parameter at any point in creating that account, if you know?

[upbeat panther]

should be namadaw add --alias $ALIAS ..

let us try removing it from wallet.toml and adding it back

[inland acorn]

actually, could try running a reveal-pk tx for that tnam and see what happens?

[inland acorn]

no please keep it for now

[inland acorn]

this won't add it properly afaik. should be namadaw derive I believe?

[upbeat panther]

ah right sorry, it was namadaw derive --alias $ALIAS --use-device --chain-id namada.5f5de2dd1b88cba30586420

[inland acorn]

ok good

[inland acorn]

can you do this?

and lmk if/when it finishes ok?

[upbeat panther]

ok, please hold

so this is an implicit account, and no established account associated with it

$ namadac query-account --owner $ADDR --chain-id namada.5f5de2dd1b88cba30586420 --node $NODE
Address: $ADDR
Threshold: 1
Public keys:

$ namadac reveal-pk --public-key $ADDR --chain-id namada.5f5de2dd1b88cba30586420 --node $NODE
Submitting a tx to reveal the public key for address $ADDR
Error: 
   0: unable to sign transaction with tpknam1...

namadaw derive --alias $ALIAS --use-device --chain-id namada.5f5de2dd1b88cba30586420 was done when the ledger had an older version of the app installed

tried running the command again into an empty wallet.toml with the current v3.0.4 of the app, but the entries generated seem to be the same as before

[inland acorn]

hmm

[upbeat panther]

$ namadac --version
Namada v101.1.1

[inland acorn]

I'm curious if you can do it in namadillo if you connect your ledger to the keychain extension

@upbeat panther

[upbeat panther]

not so familiar with namadillo. is it a webui?

ok, found it, or them rather

[inland acorn]

if you connect your ledger to the keychain extension first, then try doing it in namadillo, want to see if it works there or fails there too

use namadillo.5elementsnodes.com

[upbeat panther]

Some claim rewards transactions were not successful
Successful transactions: 1
Unsuccessful transactions: 0
Inner transaction failed

rewards are not claimed

[inland acorn]

this from namadillo?

could you just double-check in cli that the rewards are still unclaimed?

[upbeat panther]

not sure. it was from a pop-up, so could be the Namada Keychain wallet?

[upbeat panther]

ok, hang on

[upbeat panther]

yes, confirmed rewards unclaimed. balance is the same as before.

[inland acorn]

resolved. claim attempt in namadillo seems to have triggered a successful pk reveal but failed claim. subsequent claim in cli worked. best guess is pk reveal in cli somehow did not work.