Problem
from @harry-evans
When I am doing vesting transfers for a vesting period, there are always two locks associated with the vesting. However, sometimes the same lock date is used in two vesting dates. If the two usages of the lock get evaluated by the tool to be SAME block, they will have the exact same call data, based on the way the tool makes transactions, and so the second will fail, because the chain will think it is referencing the transaction that already exists vs trying to be a new one.
If the user has already claimed the tokens for the previous lock (not the case in the instance I was dealing with) or the block number gets evaluated to even one block difference (which was surprisingly not happening today), then everything works fine. This was sort of unicorn issue, but if it happens, I can decrement vesting block by 1, and it works without issue.
Solution
A simple solution would be to bump the block by one every time a transaction is submitted and the date isn't changed. Might be a better one
Problem
from @harry-evans
Solution
A simple solution would be to bump the block by one every time a transaction is submitted and the date isn't changed. Might be a better one