I set up these 4 burn pages. after choosing 10 NFTs to burn (on 10 different steps)
this message pops up and the collectors can’t continue:
example of 2 of the pages:
dev do something 
So it’s a 10 step burn, burn 1x of one of your rodeo posts on each step?
Hm. Maybe the transaction is too large for one block. Will look into this but it may take a day or so to get back to you with a fix/answer!
1 Like
That’s right. thanks for the quick answer Johnny
I couldn’t find a way how you can burn 10 different pieces of the same contract without going the 10 burn steps route.
I believe you did this right! This is on us. Figuring out the issue. Just need to recreate the issue in a testnet scenario so I can simulate the revert tx they’re seeing and go from there!
1 Like
Hm apologies for the delay. I made a 10 step burn using 1155 tokens on testnet and can’t get the same behavior. My thinking right now is maybe this has something to do with the tokens themselves on Base.
Do you have the wallet of the collector perchance?
Also if any of your collectors know how to send screenshots of the Console in google chrome or are able to send the tx data that it would have sent that would have failed that would help.
In the meantime… going to try doing this on base specifically and see if it’s network specific.
Which wallet address was this done from?
Looks like you were able to approve the tokens but then cannot burn them (Just confirming what I see!)
from my wallet
0x05b019870b42788f2F7746Dd1Ddf811f5c9F3290
it jumps to the next step yes, but no transaction was triggered or signed at all throughout the process
Thank you super helpful. It seems like about 16 hours ago you approved all the tokens on the contract for burn by our extension which is correct. Helps but doesn’t give me any answers yet.
Can you send me another screenshot but this time can you expose the “Console” tab in the weird developer tools panel that opens up? There should be a big red line somewhere that you can expand and shows the tx data that was going to get sent to the chain but failed gas estimation.
Finally got some recreation happening it seems! Hopefully have some good news in the next hour or two <3
1 Like
Yahoo found the issue and patched it. All you should have to do is republish your claim (maybe clear you cache for paranoia’s sake before you do that).
All should be well afterward. Thank you so much for the patience!
For archival sake: We were applying the wrong “BurnSpec” and incorrectly identifying OpenZeppelin spec as “invalid” instead of “OpenZeppelin”. Rodeo uses the OpenZeppelin spec so their tokens were being marked incorrectly as invalid. All our cross chain burn redeem users on Rodeo will surely thank you for reporting this issue!
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.