Skip to content

Conversation

@islathehut
Copy link
Collaborator

No description provided.

@islathehut
Copy link
Collaborator Author


/** Give yourself a role */
public addMemberRoleToSelf = (roleName: string, decryptionKeys: KeysetWithSecrets) => {
assert(this.selfAssignRoles.includes(roleName), `Cannot self-assign role ${roleName}`)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the wrong place to do this. This is essentially trusting people to self moderate. I think the correct place to do this is in membershipResolver:membershipRules so that peers can enforce the rules themselves and throw out invalidated links.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm gonna do it there, too, that piece is just more complicated and this blocks the lockbox creation, too.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to take more time to look at the implications of blocking updates to the chain on these sorts of checks but didn't wanna delay being able to test self-assigns.

@islathehut islathehut changed the title feat(3058): Allow overriding decryption keys on keys* methods and add createLockbox method to team feat(3058): Allow overriding decryption keys on keys* methods, add createLockbox method to team, add self-assign role method Jan 16, 2026
@islathehut islathehut marked this pull request as draft January 19, 2026 14:47
@islathehut islathehut force-pushed the feat/3058-allow-key-override branch from 375c8ec to 9997e86 Compare January 19, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants