- This time BIP-39 has been implemented. It's first time of bitcoin menu in the self-sovereign browser.
- New two APIs,
generation
andshareWith
- generation API
- Generating the mnemonic by BIP-39
- https://api-docs-30b126.gitlab.io/api-references/window.ssi/ssi.bitcoin/generate.html
- shareWith API
- Sharing the bitcoin secrets encrypted by NIP-44 with a counter party
- https://api-docs-30b126.gitlab.io/api-references/window.ssi/ssi.bitcoin/shareWith.html
- generation API
- wasm transplantation and coming to web apps
- Pay attention here
- mnemonic is passing as the plain text
- https://github.com/studioTeaTwo/wasm-example-app/blob/browser-demo/src/services/walletService.ts#L23-L26
- Customising that wasm demo app to use new APIs in the browser
- mnemonic is encrypted and shared using new API (but this demo will decrypt it right away)
- https://github.com/studioTeaTwo/wasm-example-app/commit/5eeff3c70b82e41776327379111ecb2aa77362ee#diff-0555e293f4190323dc482dcd1b9ee4c4f4247c56e9feb929d1eb5baca3117674R39-R49
- Launching the self-sovereign browser
- Generating at least one key in "Nostr" menu at
about:selfsovereignindividual
- Accessing and generating mnemonic on the demo app
- https://wasm-browser-demo.vercel.app/
- List of APIs used - these call the dialog
1. window.ssi.bitcoin.generate
2. window.ssi.bitcoin.shareWith
3. window.ssi.nostr.getPublicKey
And decryption by nostr-tools
- Confirming the result on setting page in the browser
- Access to
about:selfsovereignindividual
- check list
- Access to
[] Same mnemonic in the app and on the settings page?
[] When/where is the mnemonic generated?
[] How is the shared history confirmed?
- 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