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

Jump to bottom

Why is the allocations mapping defined in the TeamAllocation contract? #5

Open
predicador37 opened this issue Aug 12, 2017 · 0 comments
Open

Why is the allocations mapping defined in the TeamAllocation contract? #5

predicador37 opened this issue Aug 12, 2017 · 0 comments

Comments

@predicador37
Copy link

I see this assignment in the constructor:

allocations[teamStorageVault] = lockedTeamAllocationTokens;

But then it's never used again. Unlocking function gets the number of tokens from here:

plr.transfer(teamStorageVault, tokensCreated);

Shouldn't be team allocated tokens transferred to a vault contract which would release them at unlocking time to the team address?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@predicador37