Right now, we loose a lot of people between each step of the IDO.
To solve this issue, we want to add an auto-burn mechanism which users can choose to use or not.
As a user, when I check the auto-burn option I want my lottery tickets to be burned automatically when the allocation round begins.
Be careful there are 2 burn functions depending on the number of quests a user has completed as you can see here
You can see here how burn is triggered from the frontend.
Acceptance Criteria
When developing this system, one should keep performance in mind. In fact, there might be around ~50-100k lottery tickets minted for each fundraise.
The whole process shouldn't take more than a few hours to run.
One should use account abstraction multicall to execute as many calls as possible at once.
Description
Right now, we loose a lot of people between each step of the IDO. To solve this issue, we want to add an auto-burn mechanism which users can choose to use or not.
As a user, when I check the auto-burn option I want my lottery tickets to be burned automatically when the
allocation
round begins.Be careful there are 2
burn
functions depending on the number of quests a user has completed as you can see hereYou can see here how
burn
is triggered from the frontend.Acceptance Criteria
When developing this system, one should keep performance in mind. In fact, there might be around ~50-100k lottery tickets minted for each fundraise. The whole process shouldn't take more than a few hours to run. One should use account abstraction multicall to execute as many calls as possible at once.