There is no obvious reason to pre-calculate the Drip List ID based on the account's total minted count (to validate this before making any changes).
Also, after discussions, we came to the conclusion that this is hard to calculate correctly, if at all. Current logic has some buggy, (very)edge, cases that could result in a "token already minted" error.
The idea now is to generate a random ID and validate it on-chain by calling the NFTDriver.isSaltUsed before using it.
There is no obvious reason to pre-calculate the Drip List ID based on the account's total minted count (to validate this before making any changes).
Also, after discussions, we came to the conclusion that this is hard to calculate correctly, if at all. Current logic has some buggy, (very)edge, cases that could result in a "token already minted" error.
The idea now is to generate a random ID and validate it on-chain by calling the
NFTDriver.isSaltUsed
before using it.Relevant file:
DripsListService.ts