>> (p.1)
    Author Topic: Deterministic wallet compatibility matrix  (Read 13941 times)
    btchris (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 672
    Merit: 509

    a.k.a. gurnec on GitHub


    View Profile WWW
    March 23, 2015, 05:25:02 PM
     #1

    This is a first attempt at creating a compatibility matrix for deterministic wallets. In other words, it tries to answer the questions:

    When using two different wallet apps from different devs, will I have the same list of addresses and the same balance if I:
    • use the same mnemonic sentence (seed) in both?
    • export a master private key from one into the other?
    • export a master public key from one into the other (creating a watch-only wallet)?

    For now, it's an Excel file available for viewing or downloading here: https://onedrive.live.com/redir?resid=584F122BA17116EE%21313.

    It has four tabs. The first, "Details", lists out (hopefully) all relevant details of various wallets that might make them compatible or not with one another.

    The next three are calculated from the first; they try to answer the three corresponding questions above. (Sorry, but Excel Online doesn't render vertical text correctly, so they look a bit ugly online. Either download a local file, or hover over the wallet names in the first row to read them; they're in the same order as the wallet names in the first column.)

    I'm definitely interested if anyone has any input; in particular I'm not at all confident that the Details tab has everything correct, and it's probably missing some deterministic wallets that I'm unaware of. If there are any wallet devs who could take a quick look at their wallet on the first tab to see if I got anything wrong, that'd be great!

    I'm also not sure that the list of requirements (spelled out on the three right-most tabs) is sufficient to guarantee compatibility.

    (Also: don't rely on this without doing your own testing first!)

    I'm not sure where, if anywhere, this is headed, but it'd be nice to turn this into a set of web-based tables on GitHub, perhaps something jekyll-based like this. Again, input is most welcome.
Page 1
Viewing Page: 1