You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Congrats for the work you guys have done on the transmuter!
I created many different mutations on devnet, but no matter which option I configure to escrow action ("do nothing", "change owner", even with reversible mutations) the NFT keep locked in the escrow account. To describe a little more, these is what I get when I tried some basic mutations where the user puts in 1 NFT in return of N tokens:
lock forever works fine, user give NFT and get the tokens;
do nothing user receive the tokens but don't get the NFT back from escrow account;
change owner user receive the tokens but the the maker don't get the NFT from escrow account;
reversible user receive the tokens, then reverse, give the tokens back but don't get NFT back from escrow account;
Another thing, if one of the transactions fails for some reason, the user get an error and aren't able to use the transmuter anymore with this same wallet. Checking the console Allocate: account Address { address: SOmEaAccountAdresSSSxXHVXHVHVHXVX, base: None } already in use, which seems like the account created in the first tx to start a mutation.
That's it, thank for your time and for make this repo public!
The text was updated successfully, but these errors were encountered:
gm
Also trying the transmuter on devnet. Got the same error message after a transaction failed: Allocate: account Address { address: DZvUtq1KdsnR6LUVcv3Sk7uNuUsipniZXW9Q5AUG3qQw, base: None } already in use Program 11111111111111111111111111111111 failed: custom program error: 0x0
Have you find a way around this? Is it only on devnet?
Congrats for the work you guys have done on the transmuter!
I created many different mutations on devnet, but no matter which option I configure to escrow action ("do nothing", "change owner", even with reversible mutations) the NFT keep locked in the escrow account. To describe a little more, these is what I get when I tried some basic mutations where the user puts in 1 NFT in return of N tokens:
lock forever
works fine, user give NFT and get the tokens;do nothing
user receive the tokens but don't get the NFT back from escrow account;change owner
user receive the tokens but the the maker don't get the NFT from escrow account;reversible
user receive the tokens, then reverse, give the tokens back but don't get NFT back from escrow account;Another thing, if one of the transactions fails for some reason, the user get an error and aren't able to use the transmuter anymore with this same wallet. Checking the console
Allocate: account Address { address: SOmEaAccountAdresSSSxXHVXHVHVHXVX, base: None } already in use
, which seems like the account created in the first tx to start a mutation.That's it, thank for your time and for make this repo public!
The text was updated successfully, but these errors were encountered: