Adds a new page about application interoperability #108
Conversation
Not 100% sure but think this should be are not is.
|
Great start. Made some minor commits that should have been PR's instead, sorry. Feel free to revert where you want. The QR code image seems like it might have the QR code in the wrong position (outside of the image)? Good next steps could be to have actionable suggestions for each sub section, i.e suggesting a standard format for user data etc. |
|
Looks good, I think a simple one or two-liner on what interoperability is could be nice to add at the start as well. Although the illustration in the banner does a nice job as well. |
| layout = "float-right-desktop" | ||
| %} | ||
|
|
||
| Allow for wallets generated in one application to be easily restored in another application. Over the years, Bitcoin applications have implemented various technical details in different ways, partly because standards take time to evolve. See [Wallets Recovery](https://walletsrecovery.org) as an illustration of the problem. |
There was a problem hiding this comment.
This is extremely important section. Should we maybe expand it a bit and add that following BIP's that are widely adopted helps solve this? I am so glad you included that link to walletsrecovery.org it's a great resource, but we may want to emphasize some of their points in this section?
I mean we provided a problem here but not a concrete solution is what I'm thinking.
There was a problem hiding this comment.
Good point. I added a bit more info, recommending that wallets should put extra effort to empower users with all the info they need to recover wallets in the future. Big topic. Daniel had mentioned he is thinking of creating a dedicated page for wallet recovery, this would be a good spot to link there.
There was a problem hiding this comment.
Excellent idea, I think a dedicated wallet recovery page is needed.
There was a problem hiding this comment.
@danielnordh two votes here for your idea for a page about wallet recovery.
|
|
||
| QR codes (Quick Response codes) are visual representations of data. Since most devices today feature cameras with built-in support for reading QR codes, this technique has become a convenient method to transfer data from one device to another, even if those devices are offline. Common use cases include reading payment invoices (such as the payment links described above), or importing wallet keys from a backup. | ||
|
|
||
| Static QR codes can only contain small amounts of information. Animated QR codes address this problem by splitting up the data over multiple static QR codes. Reading animated QR codes is not a standard feature yet. |
| layout = "float-right-desktop" | ||
| %} | ||
|
|
||
| Transaction data is stored on the Bitcoin block chain and available in any wallet a user has set up. As is, this transaction data does not contain any useful information about the reasons why transactions were made, who owns each address, etc. To better understand and organize their finances, users typically enrich transaction data by assigning contacts, notes, labels, and other useful information. This data should be stored in standardized, open formats and easily synced between applications. This is especially useful for users who rely on multiple devices. |
There was a problem hiding this comment.
Are there any standards for this we can reference to?
There was a problem hiding this comment.
There was a problem hiding this comment.
Thanks for looking into it.. For example, I know that Electrum has labels, but it's unclear to me how they can work and can be exported. One day it'll be essential to have a standard in Bitcoin for this sort of data, as ideally nobody wants to loose precious data when switching wallets.
| layout = "float-right-desktop" | ||
| %} | ||
|
|
||
| While it is extremely convenient when applications provide their own node connections, it is recommended to allow users to have a choice, and potentially even encourage them to set up their own node. This results in better decentralization, and also has privacy and security benefits. |
There was a problem hiding this comment.
Would be a good spot to link to a "Principles" or "Values" section.
Co-authored-by: Conor Okus <[email protected]>
Co-authored-by: Pavlenex <[email protected]>
Co-authored-by: Pavlenex <[email protected]>
|
@johnsBeharry good idea. I just updated this PR with a skeleton for a "Foundations" section that we can use. Good to merge this one? |
Based on issue #30, this page explains some of the ways that users rely on applications playing well with each other.
If you know more use cases, please add comments.
Not sure on the best place for this in the nav structure yet. I put it in "Resources" for now.