keybase / keybase/keybase-issues

XLM wallet UI - public memo and private note fields are easily muddled

Open
#3,539 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

The UI makes it easy mix the public memo and encrypted note fields. Memo ID's are often required for payments to be authorized or correct online accounts credited. A missing memo can at best require manual intervention to resolve and loss of funds at worst. Alternately notes which where intended to be encrypted in a private keybase wallet could be irreversibly be published to the the global ledger.

I think the private notes should not be added on the same screen as the public memo.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the XLM wallet UI entry point and trace where the public memo and encrypted private note fields are presented. Define the separate-screen behavior and verify that public memos remain available for payment authorization while private notes are not exposed to the global ledger.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.