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

allow to update ceremony registration #249

Closed
brenzi opened this issue Jul 28, 2022 · 2 comments · Fixed by #254
Closed

allow to update ceremony registration #249

brenzi opened this issue Jul 28, 2022 · 2 comments · Fixed by #254
Assignees
Labels
enhancement New feature or request

Comments

@brenzi
Copy link
Member

brenzi commented Jul 28, 2022

because of encointer/encointer-wallet-flutter#645
It could be beneficial if a user can provide a proofOfAttendance after registering as a newbie and get upgraded to reputable
(very similar to endorsement after registration)

It could also make sense to support de-registering in the same go.

@brenzi brenzi added the enhancement New feature or request label Aug 1, 2022
@pifragile
Copy link
Contributor

For the unregistering i see the following issue.
The reputation that is used to register is not recorded anywhere, just set to VerifiedLinked.
When we do an unregistering, we do not know which reputation to reset to VerifiedUnlinked. The straight forward solution would be that the participant provides this reputation in the unregister xt.
But then we get an attack vector:
Someone can register with an unliked reputation that is about to expire and then unregister providing a newer reputation that was already linked before, thus tricking reputation lifetime. Another possibility for an attacker would be to transfer unliked reputations through different communities.

I would argue that this threat is not severe and we can just accept it. But I would like to hear your opinions @brenzi and @clangenb before I implement it. What do you think?

@brenzi
Copy link
Member Author

brenzi commented Aug 8, 2022

a reputation refresh is not an attack vector. it's just fixing that one may have previously subscribed (and attended) as newbie without using their reputation. So we don't need to prevent a "refresh"

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

Successfully merging a pull request may close this issue.

2 participants