Approval for changing user metadata #5
Labels
No Label
Backlog
Blocked
Doing
Done
Good first issue
Pending
Ready for review
Research
To Do
analytics
api
auth
bootstrap
bug
cache
chain-queue
chain-sync
cic-network
cleanup
cli
core
devops
devtools
documentation
enhancement
evm
flaky-test
hardening
help-wanted
high-priority
kyc
local
metadata
notifications
offline
optimization
portability
prototyping
security
sempo
simulation
spec
test-coverage
trust
usability
ussd
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: grassrootseconomics/cic-staff-client#5
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
this translates to approval for changing user pin, not metadata. closing.
assigned to @spencerofwiti