Missing Burn Form Submission & Leaderboard Beta Rewards Update
If you have experienced a missing burn, please complete a Missing Burn Form for EACH instance. Providing accurate details will help us investigate and resolve the issue efficiently.
Was it a MAID or eMAID burn? Address you burned FROM? Address you expect the burn to arrive AT? Transaction Hash (TX Hash) of the burn? Your Name & Contact Information?
Leaderboard Beta Rewards Update:
We are actively investigating issues related to missing leaderboard beta rewards and will provide an update on next steps once we identify a resolution. No form submission is required for leaderboard rewards—this form is strictly for those who burned MAID or eMAID tokens but have not yet received anything in return.
This goes against the anonymity of the exchange between Maid/Emaid and ANT.
And they also ask for a discord account.
I don’t think this is the best way to fix a problem.
The reason we ask for that is we need to be able to contact you to fix the problem and inform you what needs to happen. How else would we know who to direct our response to? We are not keeping the information or storing it once we finish resolving any burn issues.
I have a copy of the data sent and everything, including the signature which I have verified many times, is correct.
The only possibility I can think of is that my browser and Typeform are not working well together and some characters in the signature is changed when I sent it.
Has Rusty said anything about what we have to do now?
Resubmit the form?
I talked to him and we couldn’t figure out why the signatures were failing when they checked them while they were correct on my side.
He did ask me to generate a new signature and fill out the form again. According to what he told me, the Devs had communicated that this time the signature verify well and next Friday I will receive the ANTs. I hope this is the case.
It is true that this last time I changed browser and with Typeform I used Brave instead of Firefox as usual. I don’t know if this may have something to do with the failures.
I know it should work. But the truth is that, in some cases, there is something wrong between the generation and transmission of the signature on one side and the reception and verification on the other.
I still think that Typeform is the main suspect but why and in which specific cases the error may occur is what we have not been able to find out.
Would be good if typeform gave a “receipt” of what it is sending to the team.
That way we can see if anything changed. Maybe some weird spell correction is happening. Or a browser extension is changing something. Like detection of credit card number and blocking sending that to typeform
@rusty.spork Can that be added to typeform that it prints to the browser the data that was collected and has been sent to the team, or maybe even the user can click “OK yes send that” and it gets sent
I had already thought about it but it’s just to try to find an explanation. This kind of errors drive me crazy.
In my case (macOS) and according to Grok there are some complaints:
Some macOS users have reported on Mozilla forums (such as support.mozilla.org) that copy/paste fails intermittently between native applications and Firefox, especially when switching between plain text and formatted text. This may be due to how Firefox handles macOS’s universal clipboard.