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.

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

[BUG]: Creating teams spam protection requires staked tokens #2154

Closed
gordsport opened this issue Feb 5, 2024 · 0 comments
Closed

[BUG]: Creating teams spam protection requires staked tokens #2154

gordsport opened this issue Feb 5, 2024 · 0 comments
Assignees
Labels

Comments

@gordsport
Copy link
Contributor

Currently the change to fully separate teams and referral sets has not yet been implemented, therefore the spam protection is shared between referrals and teams.

The spec details that a user has to have a certain amount of Vega tokens staked in order to create both a referral set AND a team:

A party staking less than referralProgram.minStakedVegaTokensshould have anyCreateReferralSet transactions **pre-block** rejected

Should this be the case or should this be changed to not have to require staked tokens?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant