-
Notifications
You must be signed in to change notification settings - Fork 960
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
Unable to unshield with 0.44.0 and 0.44.1 #3955
Comments
Also happens with Namada v0.44.1-5-g7054446 tiago/backport-murisi-masp-fixes on housefire-cotton.d3c912fee7462. Also happens with Namada v0.44.1 in a local cluster. Trying to reproduce with tiago/backport-murisi-masp-fixes in a local cluster - Yes, it happens in that case too. Not sure what triggered it. It seems intermittent. Sometimes it works, sometimes it fails. |
how did you build |
I used this Docker cluster and set NAMADA_TAG:-tiago/backport-murisi-masp-fixes in docker-compose.yml. In the Dockerfile: ARG NAMADA_TAG=main RUN make build-release |
For each time I shield to a spending key, I can unshield an equal number of times without syncing. Is that intended behavior? |
Yes it's the current behavior, I've left an explanation for this at point 2 of this comment #3961 (comment) (didn't see your message here) |
Tested with Namada 0.44.0 and 0.44.1 on housefire-cotton.d3c912fee7462.
441c is a symlink to namadac.
$NODE is
--node https://rpc.knowable.run/
Accounts
implicit account
441c balance --owner hf44 --token nam $NODE
nam: 1794.5
another implicit account
441c balance --owner hf2 --token nam $NODE
nam: 99.75
spending key (birthday = 124570)
441c balance --owner sk44 --token nam $NODE
Last committed masp epoch: 1329
converting current asset type to latest asset type...
nam: 50
Shielded sync
(scanned multiple times after adjusting birthday a few blocks before the actual account creation time, so number of blocks may look inconsistent)
With implicit account as gas payer
With disposable gas payer
The text was updated successfully, but these errors were encountered: