Approval for changing user metadata #5

Closed
opened 2020-11-13 15:41:25 +01:00 by nolash · 2 comments
nolash commented 2020-11-13 15:41:25 +01:00 (Migrated from gitlab.com)

Changing a user's metadata, specifically phone number (which gives access to funds), should be subject to approval and/or multisig.

If it is possible to adopt a non-hierarchical scheme, then in a p2p scenario we could consider selecting a random peer for the change from peers currently connected.

Changing a user's metadata, specifically phone number (which gives access to funds), should be subject to approval and/or multisig. If it is possible to adopt a non-hierarchical scheme, then in a p2p scenario we could consider selecting a random peer for the change from peers currently connected.
nolash commented 2021-01-07 00:44:36 +01:00 (Migrated from gitlab.com)

this translates to approval for changing user pin, not metadata. closing.

this translates to approval for changing user pin, not metadata. closing.
spencerofwiti commented 2021-04-07 15:12:43 +02:00 (Migrated from gitlab.com)

assigned to @spencerofwiti

assigned to @spencerofwiti
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: grassrootseconomics/cic-staff-client#5
No description provided.