Skip to content
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

Open
Rigorously opened this issue Oct 28, 2024 · 5 comments
Open

Unable to unshield with 0.44.0 and 0.44.1 #3955

Rigorously opened this issue Oct 28, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@Rigorously
Copy link

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)

441c shielded-sync $NODE
==== Shielded sync started using ledger client ====

fetched : 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 138/138 [00:02<00:00, 66.16it/s]scanned : 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 2/2 [00:02<00:00, 0.95it/s]applied : 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 2/2 [00:02<00:00, 0.95it/s]
Syncing finished

441c shielded-sync --with-indexer https://masp.knowable.run/api/v1
==== Shielded sync started using indexer client ====

fetched : 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 73/73 [00:01<00:00, 68.76it/s]scanned : 0it [00:00, ?it/s]                                                                                                                                                                                 
applied : 0it [00:00, ?it/s]                                                                                                                                                                                 

Syncing finished

With implicit account as gas payer

441c unshield --source sk44 --target hf2 --token nam --amount 1 --gas-payer hf44 $NODE 
Enter your decryption password for sk44: 
converting current asset type to latest asset type...
Enter your decryption password for hf44: 
Transaction added to mempool.
Transaction hash: 045C65DE46EB04C4EF3D9B18A1BBFC21805004A140377E4EF2B2A1F0B32888B8
Transaction B01A60142DC1E5D28CD6B920524CA54183B6DF08AE27CF95B77B04A2CEA953D4 was rejected by VPs: [
  "tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah"
]
Errors: [
  [
    "tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah",
    "Native VP error: Spend description refers to an invalid anchor"
  ]
]
Changed keys: [
  "#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/commitment_tree",
  "#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/nullifiers/19E8E162C79525A60F7304D8D1412D904015A7690682516D4DEAA67E924B2899",
  "#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qy440ynh9fwrx8aewjvvmu38zxqgukgc259fzp6h/balance/#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah",
  "#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qy440ynh9fwrx8aewjvvmu38zxqgukgc259fzp6h/balance/#tnam1qrdl25wkn567q52pzk2accw69f780e95ms0wthz3"
]

With disposable gas payer

441c unshield --source sk44 --target hf2 --token nam --amount 1 --gas-spending-key sk44 --disposable-gas-payer $NODE 
Enter your decryption password for sk44: 
Created disposable keypair with alias disposable-key-48D49D7CE36D6D0F01B00E4F13F2D1DFD391BB69-created-at-1730130452
converting current asset type to latest asset type...
Error: 
   0: Encountered error while broadcasting transaction: StringTracer: server error: {"codespace":"","code":9,"data":"","log":"Mempool validation failed: Error trying to apply a transaction: Error while processing transaction's fees: Failed masp fee payment","hash":"22096F60FCB3622C71B7DA026BFEA216EAEFA9002809A4B2B27C102B9767DB0B"}
@Rigorously Rigorously added the bug Something isn't working label Oct 28, 2024
@Rigorously
Copy link
Author

Rigorously commented Oct 29, 2024

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.

@sug0
Copy link
Contributor

sug0 commented Oct 29, 2024

how did you build namadac? did you use make build?

@Rigorously
Copy link
Author

Rigorously commented Oct 29, 2024

how did you build namadac? did you use make build?

I used this Docker cluster and set NAMADA_TAG:-tiago/backport-murisi-masp-fixes in docker-compose.yml.
https://github.com/EmberStake/namada-selfhost

In the Dockerfile:

ARG NAMADA_TAG=main
RUN git clone https://github.com/anoma/namada.git
WORKDIR /__w/namada/namada
RUN git checkout ${NAMADA_TAG}

RUN make build-release
RUN make build-wasm-scripts

@Rigorously
Copy link
Author

Rigorously commented Oct 30, 2024

For each time I shield to a spending key, I can unshield an equal number of times without syncing. Is that intended behavior?

@grarco
Copy link
Contributor

grarco commented Oct 31, 2024

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants