From: Alon Muroch <alonmuroch@gmail•com>
To: 21E14 <21xe14@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
joi@media•mit.edu
Subject: Re: [Bitcoin-development] Why Bitcoin is and isn't like the Internet
Date: Wed, 21 Jan 2015 10:20:42 +0200 [thread overview]
Message-ID: <CADCNpyOTMij44XwNwgmdViyaiL2xcyit1xEqV5-UEg_0_EZjQw@mail.gmail.com> (raw)
In-Reply-To: <CAFZQHkFfpTw2rua8D21BEB9S723+VQ+8xt19AjPm0_iQSs5YuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
Bitcoin has a major crossroad ahead regarding a suitable platform for the
average non technical main stream user. Until now the majority of the
available solutions were at two extremes, or DIY your security and privacy
*OR* let a 3rd party service do it for you. The DIY solution is obviously
not scalable, but it seems that 3rd party solutions are not scalable as
well. If we compare for a second a 3rd party services with traditional
banks, it seems banks have two major "advantages" over them. Entry costs
for creating a bank are HUGE so a priori very few people can actually
create such a service, second, their physical and IT security
infrastructure are heavily regulated which insures a minimum of security
level to the end user (and even so money is stolen frequently). Entry costs
and regulation do not exist in the bitcoin space, meaning two programers in
their spare time can create a wallet/ platform and the non technical end
user cannot know if his money is safe, did they hire the right security
expert, did they invest enough in protecting and backing up his keys, etc.
Many services tried to tackle those problems with multisig (2 of 2 and 2 of
3) to create a syntactical 2 factor authentication/ authorisation mechanism
but in reality those solutions didn't really increase security and their
failure point is always a single device. Coupling those said problems with
the fact that bitcoin transactions are irreversible and are a scarce
commodity, trying to insure them the way our money is insured by the
government when we deposit it in the bank becomes a huge problem. Premiums
will be very high and will only grow as the appetite of hackers to steal
coins increase.
I personally believe we have the tools for creating a platform that is both
secure and private but most importantly it does it in a decentralised way.
Creating true 2 (or more) factor authentication/ authorisation schemes can
improve dramatically personal security to a point where 3rd party wallet
services will become a thing of the past. Succeeding in that will mean the
next billion non technical bitcoin users will have a platform to use
securely and a base line for building cool services on top.
Alon Muroch
bitcoinauthenticator.org
>
>
[-- Attachment #2: Type: text/html, Size: 2815 bytes --]
next prev parent reply other threads:[~2015-01-21 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 6:07 21E14
2015-01-21 7:35 ` Aaron Voisine
2015-01-21 8:20 ` Alon Muroch [this message]
2015-01-21 19:44 ` odinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADCNpyOTMij44XwNwgmdViyaiL2xcyit1xEqV5-UEg_0_EZjQw@mail.gmail.com \
--to=alonmuroch@gmail$(echo .)com \
--cc=21xe14@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=joi@media$(echo .)mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox