From: Adam Back <adam@cypherspace•org>
To: Thomas Zander <thomas@thomaszander•se>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] trust
Date: Sat, 8 Aug 2015 09:39:52 +0100 [thread overview]
Message-ID: <CALqxMTHpXymxg6ATcMM3gm73gww5tznzNsY5quNbRpzsnxS53g@mail.gmail.com> (raw)
In-Reply-To: <8185694.hShCHQnpze@coldstorage>
If you are saying that some people are happy trusting other people,
and so would be perfectly fine with off-chain use of Bitcoin, then we
agree and I already said that off-chain use case would be a
constructive thing for someone to improve scale and interoperability
of in the post you are replying to. However that use case is not a
strong argument for weakening Bitcoin's security to get to more scale
for that use case.
In a world where we could have scale and decentralisation, then of
course it would be nice to provide people with that outlook more
security than they seem to want. And sometimes people dont understand
why security is useful until it goes wrong, so it would be a useful
thing to do. (Like insurance, your money being seized by paypal out
of the blue etc). And indeed providing security at scale maybe
possible with lightning like protocols that people are working on.
Adam
next prev parent reply other threads:[~2015-08-08 8:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 6:10 Thomas Zander
2015-08-08 8:39 ` Adam Back [this message]
2015-08-08 8:54 ` Thomas Zander
2015-08-08 9:24 ` Benjamin
2015-08-08 11:08 ` s7r
2015-08-08 12:01 ` Benjamin
2015-08-11 4:17 ` Joseph Poon
2015-08-08 11:59 ` Milly Bitcoin
2015-08-08 11:54 ` Adam Back
2015-08-08 12:37 ` Thomas Zander
2015-08-10 20:17 ` Jorge Timón
2015-08-10 20:43 ` Milly Bitcoin
2015-08-10 21:43 ` Thomas Zander
2015-08-08 9:05 ` Venzen Khaosan
2015-08-10 21:45 ` Gregory Maxwell
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=CALqxMTHpXymxg6ATcMM3gm73gww5tznzNsY5quNbRpzsnxS53g@mail.gmail.com \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=thomas@thomaszander$(echo .)se \
/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