rich1.0npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydhttps://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydnjumphttps://nostr.ae📅 Original date posted:2015-03-11 📝 Original message:Users will want to have wallets shared between devices, it's as simple as that, especially for mobile/desktop wallets. Trying to stop them from doing that by making things gratuitously incompatible isn't the right approach: they'll just find workarounds or wallet apps will learn how to import seeds from other apps. Better to just explain the risks and help people mitigate them. On Wed, Mar 11, 2015 at 3:57 PM, Aaron Voisine <voisine at gmail.com> wrote: > I'm not convinced that wallet seed interoperability is such a great thing. > There is a wide variability in the quality and security level of wallet > implementations and platforms. Each new device and wallet software a user > types their seed into increases their attack surface and exposure to flaws. > Their security level is reduced to the lowest common denominator. I see the > need for a "fire exit", certainly, but we must also remember that fire > exits are potential entrances for intruders. > > Aaron Voisine > co-founder and CEO > breadwallet.com > > On Wed, Mar 11, 2015 at 12:46 PM, Gregory Maxwell <gmaxwell at gmail.com> > wrote: > >> On Wed, Mar 11, 2015 at 7:24 PM, Ricardo Filipe >> <ricardojdfilipe at gmail.com> wrote: >> > i guess you look at the glass half full :) >> > even though what you say is true, we should aim for wallets not to >> > require those instructions, by standardizing these things in BIPs. >> > let's hope bitcoin doesn't fail in standards as our industries have in >> > the past... >> >> There are genuine principled disagreements on how some things should >> be done. There are genuine differences in functionality. >> >> We cannot expect and should not expect complete compatibility. If you >> must have complete compatibility: use the same software (or maybe not >> even then, considering how poor the forward compatibility of some >> things has been..). >> >> What we can hope to do, and I think the best we can hope to do, is to >> minimize the amount of gratuitous incompatibility and reduce the >> amount of outright flawed constructions (so if there are choices which >> must be made, they're at least choices among relatively good options). >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub >> for all >> things parallel software development, from weekly thought leadership >> blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development at lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150311/2a1f4679/attachment.html>