📅 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>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:31:28
in reply to nevent1q…juyh
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:31:28Event JSON
{
"id": "36830f58a50ba5ded02321ec0fde7f9911c7853a624aaa9dd3caa8903d251c67",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686151888,
"kind": 1,
"tags": [
[
"e",
"bf192ab1459041905386f8a0c7782f07de04af2932326a4e49fe0d6ce14ed93c",
"",
"root"
],
[
"e",
"7e14771d271b7645daf5ebe367216c7e319857e13264d0e6e568a5333d3fb3c2",
"",
"reply"
],
[
"p",
"3a24ce2145c5488aebfb0fc113e7d44234e9d3733afa45e2d880eb259c3eade3"
]
],
"content": "📅 Original date posted:2015-03-11\n📝 Original message:Users will want to have wallets shared between devices, it's as simple as\nthat, especially for mobile/desktop wallets. Trying to stop them from doing\nthat by making things gratuitously incompatible isn't the right approach:\n they'll just find workarounds or wallet apps will learn how to import\nseeds from other apps. Better to just explain the risks and help people\nmitigate them.\n\nOn Wed, Mar 11, 2015 at 3:57 PM, Aaron Voisine \u003cvoisine at gmail.com\u003e wrote:\n\n\u003e I'm not convinced that wallet seed interoperability is such a great thing.\n\u003e There is a wide variability in the quality and security level of wallet\n\u003e implementations and platforms. Each new device and wallet software a user\n\u003e types their seed into increases their attack surface and exposure to flaws.\n\u003e Their security level is reduced to the lowest common denominator. I see the\n\u003e need for a \"fire exit\", certainly, but we must also remember that fire\n\u003e exits are potential entrances for intruders.\n\u003e\n\u003e Aaron Voisine\n\u003e co-founder and CEO\n\u003e breadwallet.com\n\u003e\n\u003e On Wed, Mar 11, 2015 at 12:46 PM, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e\n\u003e wrote:\n\u003e\n\u003e\u003e On Wed, Mar 11, 2015 at 7:24 PM, Ricardo Filipe\n\u003e\u003e \u003cricardojdfilipe at gmail.com\u003e wrote:\n\u003e\u003e \u003e i guess you look at the glass half full :)\n\u003e\u003e \u003e even though what you say is true, we should aim for wallets not to\n\u003e\u003e \u003e require those instructions, by standardizing these things in BIPs.\n\u003e\u003e \u003e let's hope bitcoin doesn't fail in standards as our industries have in\n\u003e\u003e \u003e the past...\n\u003e\u003e\n\u003e\u003e There are genuine principled disagreements on how some things should\n\u003e\u003e be done. There are genuine differences in functionality.\n\u003e\u003e\n\u003e\u003e We cannot expect and should not expect complete compatibility. If you\n\u003e\u003e must have complete compatibility: use the same software (or maybe not\n\u003e\u003e even then, considering how poor the forward compatibility of some\n\u003e\u003e things has been..).\n\u003e\u003e\n\u003e\u003e What we can hope to do, and I think the best we can hope to do, is to\n\u003e\u003e minimize the amount of gratuitous incompatibility and reduce the\n\u003e\u003e amount of outright flawed constructions (so if there are choices which\n\u003e\u003e must be made, they're at least choices among relatively good options).\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e Dive into the World of Parallel Programming The Go Parallel Website,\n\u003e\u003e sponsored\n\u003e\u003e by Intel and developed in partnership with Slashdot Media, is your hub\n\u003e\u003e for all\n\u003e\u003e things parallel software development, from weekly thought leadership\n\u003e\u003e blogs to\n\u003e\u003e news, videos, case studies, tutorials and more. Take a look and join the\n\u003e\u003e conversation now. http://goparallel.sourceforge.net/\n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Dive into the World of Parallel Programming The Go Parallel Website,\n\u003e sponsored\n\u003e by Intel and developed in partnership with Slashdot Media, is your hub for\n\u003e all\n\u003e things parallel software development, from weekly thought leadership blogs\n\u003e to\n\u003e news, videos, case studies, tutorials and more. Take a look and join the\n\u003e conversation now. http://goparallel.sourceforge.net/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150311/2a1f4679/attachment.html\u003e",
"sig": "7986a652bdef2414008ad5febbc7f3649f7c29bc358dfeeaf07ba3799387ae52749c1d1e9ddd08bf9c85492a4ebbb2c0fad7e188c2399415d694d80978d56834"
}