-
Notifications
You must be signed in to change notification settings - Fork 22
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
feat(gno/dao): GovDAO - add T3 members invitations module #1502
Conversation
✅ Deploy Preview for gno-dapp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for teritori-dapp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
gno/r/govdao/messages.gno
Outdated
type AddT2MemberMessage struct { | ||
Address string | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be removed, the correct type is defined above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gno/r/govdao/invitations_test.gno
Outdated
SetProfileString: profile.SetStringField, | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SetProfileString: profile.SetStringField, | |
}) | |
SetProfileString: profile.SetStringField, | |
NoDefaultHandlers: true, | |
}) |
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on this PR: #1501
Add Delegate & Withdrawal method usable from T1, T2 & T3 members
T1 -> 3 delegation point
T2 -> 2 delegation point
T1 -> 1 delegation point
A member can only delegate one point per people
A user need 2 delegation point received to become member T3
A member already tiered T1, T2 cannot become T3 member but can still receive invitation point.
When a withdrawal removed a T3 member, all his invitations are removed meaning it can create a chain recursive effect.
Alice -> dave
Bob -> dave
Carol -> eve
Dave -> eve
if alice remove dave, he will not be a member anymore, so his invitation to eve will be removed too and eve will not be a member anymore too.
I also add limit size of 2 times T1 for T2 membership