Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update PPTimedVesting.md #8

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update PPTimedVesting.md #8

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9087c3e
Update PPTimedVesting.md
polipaul May 27, 2021
dbad333
Update PPTimedVesting.md
polipaul May 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion specifications/PPTimedVesting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The contract contains addresses, which should receive `CVP` tokens with lock and
## Significant changes from `ppVesting.sol`
- Vesting values are calculated using timestamps instead of block numbers (vote caching still uses block numbers);
- Ownable trait was added back;
- Owner can increase `durationT` value any number of times he wants with limit;
- Owner can increase `durationT` value any number of times he wants with a limit of 180 days a time;
- Owner can increase `personalDurationT` for a particular member;
- Owner can disable member anytime;
- A member can renounce his membership anytime;
Expand Down Expand Up @@ -43,6 +43,7 @@ The following params could be changed later by the owner:
- compilation configuration: Solidity version: v0.6.12, optimizer: enabled, runs: 200, EVM: Istanbul (we're flexible on compiler version);
- the contract doesn't use a proxy pattern. There is no way to upgrade it;
- there will be multiple instances of this contract with different initialization parameters;
- the Owner should keep personalDurationT member values greater than durationT
- the contract is compatible with the `CompInterface` and provides cached `getPriorVotes()` information as the `CVP` token does;
- to provide detailed information about the claimed votes at a specific block by a member, each `claimVote()` creates a corresponding vote checkpoint;
- a member has an option to transfer his or her vested tokens and votes to a new address, for example, when a private key is compromised. The new address means that it has never been used as the vesting contract member address before.
Expand Down