#usdc ibc out
1 messages ยท Page 1 of 1 (latest)
Hey are you using namadillo or cli? Your description is a little confusing to me
can you put up a few screenshots of the error?
Sorry, i use translator, when trying unshield usdc, this error happens regardless of the fee I put
using namadillo
can you share a full screenshot of how it looks before you send the tx? Ie what selections you made etc. you can grey over the private addresses etc
could you try the 5elements interface instead if it's not the one you are using, and see if that works?
i try 3 interfaces, i try 5elements now , it takes a while to synchronize and to write the masp transaction is taking about 2min, I think it is because it has many inputs
if I pass 5nam de fee, this error appears
that's normal
hm ok
will note to devs
as an attempt at a workaround (and if you don't mind it becoming transparent) could you try unshielding it and see if transparent ibc out would work?
which OS and browser are you using?
unshield to transparent not work too, i try send 100usd its works, i will try to withdraw in small pieces, but strange that the total balance does not work, I used windows 11 24h2 with brave Brave 1.80.115
Chromium: 138.0.7204.97
when I try to send all the balance, the raw transaction appears gigantic, I believe that because of the many inputs, when I send a lower value, the raw transaction appears much smaller
the error reappeared , this balance I can not do anything with it, this stuck somehow
is it possible the balance is wrong? are you sure the usdc balance showed is the amount of usdc you actually had in your account (the amount you transfered into the masp)?
usdc ibc out
the total amount I had in the wallet yes before the initial transfers, the remaining balance is not deducting the failed attempts, I don't know if it was supposed to deduct, but I resynced the wallet several times to be sure, and it always shows the same balance, both in usdc and in NAM
From what I understand, it seems that there is a fee limit inside the masp, maybe I am hitting that limit, since I have a lot of inputs
I need to understand precisely here: the amount of usdc showed in the interface before you started withdrawing, 862 usdc, was that the amount you transfered in, or did it suddenly show more usdc than you should have had, that you then tried to withdraw?
Yes, the 862usdc were made in 15 to 18 transfers over 18 days, when trying to transfer all balance I had the error I showed, but when transferring in small pieces, I managed to withdraw 700usd, but the remaining 162, give the error of fee already shown
ok but you are sure you transfered all the 862usdc into the masp, that the balance shown there is correct?
yes, I'm sure the value is correct
i had osmo, neutron, all I managed to withdraw, only this usd value of the error when trying to withdraw or transfer
if you want, I can send you the raw transaction that comes up before I sign it
no it's fine, i've notified dev about this, hoping they will have time to take a look
it's correctly understood that you were also unable to unshield, yes?
yeah, I can't unshield
@barren coral One for you this
@unkempt vigil Can you share tx details from the extension? They are safe to share
ok I think you are hitting the limit which is 100_000
You should still be able to unshield one note at a time though, at least I think so
I will do some more testing
he said he tried with 5M gas btw
it's too much, there is masp fee limit and also gas limit per block
Ok there are two problems I think:
- interface does not display proper error message. It should be something along the lines of "Masp tx fee limit exceeded" or we should just validate it before we submit tx
- the limit is too low - this can be changed via governance only, but there are some downsides of increasing it
We can also add an ability to pay fees with transparent balance, but this can potentially leak privacy unless users create fresh account for each unshielding
what is the masp tx fee limit?
the latter option (paying with transparent balance) seems like a really bad idea to me.. (privacy issues as you mention)
it's a chain parameter that basically says how much gas(maximally) you can unshield to pay fees.
When you unshield in namadillo some part of your shielded balance is used to pay fees, it works by unshielding the required amount to disposable(one time) transparent address and then using this address as a signer and fee payer.
When the required amount is more than 100k the tx will fail
hm ok, that sounds like it should be increased via governance asap?
Asked protocol guys. I ll add new issue on github
thanks appreciate!
@unkempt vigil looks like you may have to wait a bit for it to get fixed for the last bit. hope it's not too much of an inconvenience.
The workaround to get you unlocked is to look at tx details and spend smaller amount of notes, so let's say you want to unshield all of your nam and you see multiple values in maspTxIn
"maspTxIn": [
{
"token": "tnam1q9gr66cvu4hrzm0sd5kmlnjje82gs3xlfg3v6nu7",
"value": "899.9375",
"owner": "zvknam1qwyqy304qqqqpqzwc6u9j2knncvt0dg5j44w4fn5z6qt8mfeyakdgg6hweegr2p56efz088hcna9aglccepsmg79qg3lvc994drt0dcqq85ued5zmnzrvptz7s3jrxrsa7lcd6zg7ccu4zt2u0tzp4z4cmtu6hsu2gt9wczm3ekkr3h0lccuvhgp4ddjxkcdc5p2xh5k9lstz2mnn4a95qkxlh0qfxed4ng20aa74nxrwaef4cs23xhn303s24dtcugl286md56h7zgr7cepg"
},
{
"token": "tnam1q9gr66cvu4hrzm0sd5kmlnjje82gs3xlfg3v6nu7",
"value": "100",
"owner": "zvknam1qwyqy304qqqqpqzwc6u9j2knncvt0dg5j44w4fn5z6qt8mfeyakdgg6hweegr2p56efz088hcna9aglccepsmg79qg3lvc994drt0dcqq85ued5zmnzrvptz7s3jrxrsa7lcd6zg7ccu4zt2u0tzp4z4cmtu6hsu2gt9wczm3ekkr3h0lccuvhgp4ddjxkcdc5p2xh5k9lstz2mnn4a95qkxlh0qfxed4ng20aa74nxrwaef4cs23xhn303s24dtcugl286md56h7zgr7cepg"
},
... more here
you can try spending 900 first so it will only use two notes
this will require less gas
I know this sucks
i already got unshield part of the balance, but it seems that now any value of the error, I have to take exactly the values of each entry?
before I had more maspTxIn, but it seems that by taking a little, gave a reduced
you can try exact values just denominate them to usdc, so basically what you see divided by 1_000_000 I think
@unkempt vigil deleted ur message cuz I forgot it contains viewing key
not a bit of a deal but still ๐
It worked perfectly!!! Thank you very much for the help. @barren coral @chilly fulcrum @long ledge , if you need anything, you can count on me.