Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Improving passphrase support

Offen
#231 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@ardier16 arbeitet bereits daran.

Seit 14.8.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

feature request
Description

I'm evaluating a Jade wallet in conjunction with Green and BIP39 passphrases. The UI implementation needs improvement.

Firstly, with logging into a wallet it takes some time to enter the pin and passphrase on the Jade. While the user is doing that, Green starts reporting that the Jade must be reconnected, or that timeouts occurred. Once the user has finished, Green often gets stuck or loops back to requiring a pin code entry again. Reconnecting the Jade doesn't seem to help. All of my testing has been via a USB connection.

Secondly, after the wallet is setup and accessed from Green, the experience of accessing the wallet with a different passphrase is quite problematic. In addition to the connection and timeout errors described above, Green flashes an error so quickly that it's barely readable, which states that the wallet hash has changed. Obviously the wallet hash has changed, that's the whole point of having passphrases. To get a second passphrase working, one has to tell Green to create a new wallet. But then the existence of two hardware wallets is displayed in Green, which defeats the discretion of passphrases, and one has to remember which wallet uses which passphrase.

Please can these passphrase usability issues be worked on?

Additionally, in Green there seems to be no way of displaying the wallet hash. Somewhere it would be good if the wallet hash is displayed. It'd be great if the wallet's derivation path could also be seen somewhere.

Version

4.0.38

Vorherrschende Sprache
Kotlin
Sterne
273
Forks
111
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Blockstream/green_android

Alle Issues in Blockstream/green_android

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.