Is your feature request related to a problem? Please describe.
Today we do vesting with a custom contract. Each new vesting schedule needs a new contract to be deployed. This leads to inconsistencies and lots of operational time spent adding new users.
Describe the solution you'd like
Build a vesting contract following the same math then https://github.com/GetAlluo/governance-token/blob/master/contracts/vesting/TeamVestingV2.sol there should however be a function with the following inputs.
addRecipiant(uint clifPeriod, uint vestingWeeks, address recipiantAddress, uint totalAllocation, address tokenAddress)
the function should be able to add to an array the address passed with the following parameters. However, it should be before adding checking if the contract holds enough $ALLUO to fulfil all the vesting schedules that were added.
the function to add a Recipient should not be only callable by the Admin of the contract, but should rather be open.
All other functionalities of the vesting contract previously build should remain the same.
Describe alternatives you've considered
Lots of solutions are available online, but none of them are vastly adopted or used. This therefore does not bring confidence.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Today we do vesting with a custom contract. Each new vesting schedule needs a new contract to be deployed. This leads to inconsistencies and lots of operational time spent adding new users.
Describe the solution you'd like
Build a vesting contract following the same math then https://github.com/GetAlluo/governance-token/blob/master/contracts/vesting/TeamVestingV2.sol there should however be a function with the following inputs.
addRecipiant(uint clifPeriod, uint vestingWeeks, address recipiantAddress, uint totalAllocation, address tokenAddress)
the function should be able to add to an array the address passed with the following parameters. However, it should be before adding checking if the contract holds enough $ALLUO to fulfil all the vesting schedules that were added.
the function to add a Recipient should not be only callable by the Admin of the contract, but should rather be open.
All other functionalities of the vesting contract previously build should remain the same.
Describe alternatives you've considered
Lots of solutions are available online, but none of them are vastly adopted or used. This therefore does not bring confidence.
Additional context
Add any other context or screenshots about the feature request here.