From: odinn <odinn.cyberguerrilla@riseup•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Why Bitcoin is and isn't like the Internet
Date: Wed, 21 Jan 2015 19:44:35 +0000 [thread overview]
Message-ID: <54C001A3.8020301@riseup.net> (raw)
In-Reply-To: <CADCNpyOTMij44XwNwgmdViyaiL2xcyit1xEqV5-UEg_0_EZjQw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
3rd party / web wallets are no longer viable except as means to burn
customers and divulge (or be forced to divulge) their data to
governments and corporations.
Rather than restate what I have already posted on this matter I'll
leave it there. It's time also for those who are managing bitcoin.org
to reconsider what's posted there (the criteria for what's posted there
- at present the "web wallet" section should be excluded, that is to
say, Removed! from bitcoin.org
with the possible exception of CoinKite to remain, which has a
reasonable argument for having made such privacy advances as to merit
usage by people (and to remain at bitcoin.org)
Additionally, I see no point in recommending any of the other wallets
except Electrum, Mycelium, Core, and in the hardware side, the ones
that appear (Trezor and HW1).
Furthermore, I believe those of you who are working for Coinbase
customer operations or Bitpay (I will not name names, you know who you
are) should resign from your employment. I will bring this point up
regularly. You can easily find employment elsewhere, your skills are
in high demand.
- -O
Alon Muroch:
> 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
>
>>
>>
>
>
>
> ------------------------------------------------------------------------------
>
>
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in
> Ashburn. Choose from 2 high performing configs, both with 100TB of
> bandwidth. Higher redundancy.Lower latency.Increased
> capacity.Completely compliant. http://p.sf.net/sfu/gigenet
>
>
>
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJUwAGjAAoJEGxwq/inSG8CJoAIAMDR0h40IhFQNa8BW4AFeKUR
7tg84e752c7wY153GY/P7MOFL6w3E9h4tXzxdohTMMfF5Q6Ip6HaaifYmMpegFSS
WEHK0a3C2F+4sQMmMBtWbfyPsG5sJYtldY5hboSbh/6vXJJLXLSd+Sz3WHYx1Qjs
qn6sw5CA2Q0fborTxcsNZixUXD/OF5tTjDozp+KfnZ0imvBoKfhfJFlaNUXNon7U
zdPfahOrRIM5o70pjo6VwoutKRXr49JIoi47r9Uc3ujckUbLA5CVBApj4FApayb5
sXk8Ks+p6IvBr6Q0ycxXOKmPwbSALC5pLa7Ncb1MFFBGzxKFsMjoRwOLTXHlLUE=
=WgO4
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-01-21 19:44 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
2015-01-21 19:44 ` odinn [this message]
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=54C001A3.8020301@riseup.net \
--to=odinn.cyberguerrilla@riseup$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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