Skip to content

Instantly share code, notes, and snippets.

@studioTeaTwo
Last active May 11, 2025 07:30
Show Gist options
  • Save studioTeaTwo/b51f693774134a59d1a5caa0848796b3 to your computer and use it in GitHub Desktop.
Save studioTeaTwo/b51f693774134a59d1a5caa0848796b3 to your computer and use it in GitHub Desktop.

About Bitcoin menu unlocking

About Breez SDK WASM

Demo scenario

Summary

Flow

  1. Launching the self-sovereign browser
  2. Generating at least one key in "Nostr" menu at about:selfsovereignindividual
  3. Accessing and generating mnemonic on the demo app
1. window.ssi.bitcoin.generate
2. window.ssi.bitcoin.shareWith
3. window.ssi.nostr.getPublicKey
And decryption by nostr-tools
  1. Confirming the result on setting page in the browser
    • Access to about:selfsovereignindividual
    • check list
[] Same mnemonic in the app and on the settings page?
[] When/where is the mnemonic generated?
[] How is the shared history confirmed?

NOTE

  • It's not solved yet. Because it's:
    • needed holding/payloading their nostr's secret key somehow inside the SDK
    • able to be got the decrypted secret on memory by a intermediate web app on the same domain
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment