You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AdvisorVestingWallet.sol contract has its vesting start time defined as a constant variable (_VESTING_START) with the value of 1_698_768_000 (October 31, 2023 at 12:00pm EST). This value was unchanged when 3 advisor contracts were deployed today for Joey Santoro, Cogsy, and nap. This means that all 3 parties will have a portion of their advisor tokens vested from that time vs. vesting from the deployment time. Given the ongoing support Brrito has received from the 3 individuals, which started well before the vesting date, it is a mistake that I believe to be acceptable.
Going forward, future advisor tokens will start their vesting from the deployment block timestamp, and the contracts will be updated to reflect that rule shortly before the next advisor tokens are allocated.
The text was updated successfully, but these errors were encountered:
The issue was made for the sake of transparency and as a reminder to implement the changes mentioned above should we bring on any other advisors in the future.
The AdvisorVestingWallet.sol contract has its vesting start time defined as a constant variable (
_VESTING_START
) with the value of1_698_768_000
(October 31, 2023 at 12:00pm EST). This value was unchanged when 3 advisor contracts were deployed today for Joey Santoro, Cogsy, and nap. This means that all 3 parties will have a portion of their advisor tokens vested from that time vs. vesting from the deployment time. Given the ongoing support Brrito has received from the 3 individuals, which started well before the vesting date, it is a mistake that I believe to be acceptable.Going forward, future advisor tokens will start their vesting from the deployment block timestamp, and the contracts will be updated to reflect that rule shortly before the next advisor tokens are allocated.
The text was updated successfully, but these errors were encountered: