#Unshielding / Shielded transfer broken ?
1 messages · Page 1 of 1 (latest)
Reported here : https://github.com/anoma/namada/issues/2967
thanks! will alert devs
grarco already responded on the issue, I think they're investigating already. Some people seem to be able @candid cliff mentionned he managed to do a transfer. Maybe @topaz sequoia too ?
I'll try to test it out while on the move via phone.
It does seem that for some reason my shielded-sync resetted completely, so have to do this again. I think it happened either by:
- Running two shielded-sync's accidentally at once
, or Cause of trying to shielded-sync a new VK (after I was already synced) by implicitly calling the command with the--viewing-keysflag.
This will make it slower for me to get up to speed again and test it out.
Feel free to share your commands for what works and what does not work
Okay hmm, I tried. You're right, VP rejects the following:
- Shielded => Transparent (Unshielding)
- Shielded => Shielded
Transparent => Shielded did work.
Log for Unshielding (armor is my shielded addr, zen is my transparent address):
namada client transfer --source armor --target zen --token naan --memo $MEMO --amount 5 --gas-payer zen
Transaction added to mempool.
Wrapper transaction hash: 085CD2806C23A4861EEC052E2A8AF7CE66A5DEFBC6E10EFFD39E2C40A8BA0F0D
Inner transaction hash: 96CFCF65A5F72B9A59619BD12820AE2CAFBD6F77FBDC9185F8A1964ADAB85261
Wrapper transaction accepted at height 245244. Used 70 gas.
Waiting for inner transaction result...
Transaction was rejected by VPs: [
"tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah"
].
Changed keys: [
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/commitment_tree",
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/nullifiers/B338AE0D8C50E1FDC434DDEB52B56065FBC7F46E033DB4AA355761EC068C22E2",
"#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qxvg64psvhwumv3mwrrjfcz0h3t3274hwggyzcee/balance/#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah",
"#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qxvg64psvhwumv3mwrrjfcz0h3t3274hwggyzcee/balance/#tnam1qq22qmw72m3e6c8lajx8jmzzh2h4t3dp7cfs4dxf"
]
Last committed epoch: 62
Transaction added to mempool.
Wrapper transaction hash: 943EDB45B0897B4153987337870D65E4F076908A85F232D7E0A8D54D2AF5873D
Inner transaction hash: 58F1D628C9666F534079A0C2F262760FD1507844FDDD65F34BD76ADD21691AD6
Wrapper transaction accepted at height 245246. Used 70 gas.
Waiting for inner transaction result...
Transaction was rejected by VPs: [
"tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah"
].
Changed keys: [
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/commitment_tree",
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/nullifiers/7D5FAF80F162374C7D25B36EAB31191C9CCD8E910A2F9EF4D88FFB529F4BC68C",
"#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qxvg64psvhwumv3mwrrjfcz0h3t3274hwggyzcee/balance/#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah",
"#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qxvg64psvhwumv3mwrrjfcz0h3t3274hwggyzcee/balance/#tnam1qq22qmw72m3e6c8lajx8jmzzh2h4t3dp7cfs4dxf"
]
Last committed epoch: 62
Log for Shielded => Shielded (the payment address is of a different shielded address):
namada client transfer --source armor --target znam1qqtnyzu97zknt3sff74aj8fnxxx6lr5gke2vqp8w8pmxz7dp25rt7jsmq46dn2g2t0al2ps2paryv --token naan --memo $MEMO --amount 5 --gas-payer zen
Transaction added to mempool.
Wrapper transaction hash: EC358F8D0DDC8322FB8ACF2DC537856E1871800B91CCF9FF24E16326BDC2374A
Inner transaction hash: 15985D85D3C6D241C16D667136A13993C7B3D81E0B4396282C713760F73AB181
Wrapper transaction accepted at height 245255. Used 67 gas.
Waiting for inner transaction result...
Transaction was rejected by VPs: [
"tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah"
].
Changed keys: [
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/commitment_tree",
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/nullifiers/B338AE0D8C50E1FDC434DDEB52B56065FBC7F46E033DB4AA355761EC068C22E2"
]
Last committed epoch: 62
Transaction added to mempool.
Wrapper transaction hash: 0A6FC7A5D643EC07AE93708633D1F693470E093CE31B2F817243A53D0589F2D3
Inner transaction hash: 0DA5D0085B1FB496FDB92E195C346E7692BEC21635571E96E1368B639513F5D7
Wrapper transaction accepted at height 245257. Used 67 gas.
Waiting for inner transaction result...
Transaction was rejected by VPs: [
"tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah"
].
Changed keys: [
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/commitment_tree",
"#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/nullifiers/7D5FAF80F162374C7D25B36EAB31191C9CCD8E910A2F9EF4D88FFB529F4BC68C"
]
Last committed epoch: 62
yep, correct. Ok so the bug seems to be everyone accross the board. Just waiting for hkey who said yesterday he had fixed his shielding issue
A bit out of context, but there has to be a mechanism to prevent shielded-syncing in parallel.
This can be done e.g by creating a .lock file and preventing the command to be run if this .lock file is around. And deleting it at the end of the shielded-sync.
that's a very good point !
That would prevent someone from messing the shielded.dat file
Yeah! Like I probably did 10 minutes ago lol
Yess it was quite fast
Reason: Posted a link
oh shoot
🤣 you've been MEE sixt !
@cedar garden you can report here once you've tested on youru side !
😆
h ttps://github.com/anoma/namada/issues/2967#issuecomment-2025309864 team responded
Complicated issue idk anything about it haha
I love it when they respond with cryptic technical terms and Im here scratching my head "ok, what did he actually say 🤔 ?" ... "oh yeah, we are looking for solutions"
😆 haha make sense
we're discussing this now with devs
@candid cliff were you able to do something? that would make sense to me if it's purely a client issue
A lot of player will get approve point in task Bug =]]
Shielding transfer works.
Shielded transfers are being rejected by the MASP VP.
Unshielding transfers are being rejected by the MASP VP.
for me too
Hi,
I did shielded transfers, and all works fine:
Transparent => Shielded
B20712E49658369824D8F5D61AD67F00E0E3FD9CA907DD915853E30E2DE6CDDD
Shielded => Shielded
A587B609C86BFD6DA5199CF7E3D9BD57F96B1837CB7D2472F17794CA54650BDE
Shielded => Transparent
E429E3E557335906A0D8304A2E935F966A9E9D960C20989C2D4A3E4419E1414F
Did you run shielded-sync only once before trying those?
It is running every minute in a background process.
After HF that process failed, so i restarted it with --from-height 237907
Now it is working without parameters
Like from latest block height - 1 or smth similar?
It's not an expected behaviour anyway, let's see what team has to say after investigating
Sure
yeah, that's what I did too
@reef hatch Did you run exactly namadac shielded-sync --from-height 237907 every minute?
It always starts fetching from block 237907, I think it takes a lot of time after a while? Isn't it
@here has anyone else tested this?
Apologies not sure,
From transparent to shielded working correctly
yeah, unshieldeding and shielded > shielded not working
Yep that's the first thing I tested yesterday when I had the issue. Not working
I don't have any problems either, everything seems to be working fine.
Only first time, after that without height option.
how to solve this?
Sadly I don't think we can atm :(...
not working for me as well
are shielded transactions fixed? have anybody tried it recently?
not fixed yet
@here devs say it will take some days to have a work-around (not solution), probably next week we will have something. no hard fork, it will likely just be a client change
i see the same error with vp reject for shielding ibc-transfer, anybody did shielding ibc transfer correctly?