Tiago Carvalho
Tiago Carvalho
Unfortunately, this has to do with the current implementation of checking the status of a tx. RPC queries are made to a Namada-specific event log, which is not persisted to...
> to be precise: the fat finger was only here in the github issue - I still see timeouts when querying recently submitted transactions cc @sug0 ah. regarding this output:...
I think it's fine to leave this issue open. We can def improve the behavior of `tx-result`, even if it's just by emitting an error that mentions the tx event...
Finished in #3701
yep. I think the main reason for this behavior is that the command purges keys, as well as data. maybe it could be solved with a `--keep-validator-keys` flag, or smth
> I propose we change the default behavior not to purge keys as it's a common footgun and instead add some non-default flag to do that only when explicitly request....
@yito88 @grarco
Ah I see, you are correct about point 2. But we could still fallback to a transparent refund, in case the masp epoch had changed. This would improve the UX...
just another note: we also need to handle timeouts. the refund logic under timeouts is the same as when we get an ack error
@yito88 if you take this on, could you please use #4134 as a base?