public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] trust
Date: Mon, 10 Aug 2015 23:43:46 +0200	[thread overview]
Message-ID: <2674312.GqtxTJeqiO@coldstorage> (raw)
In-Reply-To: <CABm2gDrJH8-6VPp1Lk4ueJA2ShOU+evTgK-S1zNjuqN8h8Je+Q@mail.gmail.com>

On Monday 10. August 2015 22.17.52 Jorge Timón wrote:
> But I don't see how that is relevant, allowing trust to be involved in
> different ways is a feature, but it's optional.

Agreed.

> I think the point "you don't need to trust anyone to use Bitcoin" remains.

yes, and thats fine.


The argument that Adam was making was the other extreme; that Bitcoin was 
useless the moment he has to trust any 3rd party.
And that is why I started this thread, because that idea that Bitcoin looses 
its functionality when you deviate from the trust-no-one path, is destructive.


For instance I suggested a week ago that the Chinese firewall (blocksize 
propagation) problem could maybe be solved by having a chinese miner partially 
trust some full nodes on Internet hubs. For instance in Amsterdam, one in 
Stockholm, etc.
And then propagation of a newly mined block would make the miner only sent the 
header to this server where a full x-MB block is then created by some 
specialized software that bases it on the mempool of its bitcoind.

Propagation of a Chinese miner then suddenly doesn't care about blocksize when 
hopping over the chinese firewall. You'd only send a small amount of data, 
likely around 20Kb for even 8Mb blocks.

A critic would argue its a useless strategy because you'd have to trust the 
data center operators.
I'd argue that its a risk, for sure, but one that can be mitigated easily by 
having various datacenters around the world where you'd run your software so 
you'd be able to check the validity of each.

Risks can only be assessed fairly if people are less black/white in their 
thinking.

I love that about Bitcoin, it combines technical specialized thinking with 
Economics and planning. If you don't have both, you probably end up rejecting 
the best ideas.


> Adam, I think he means a multisig escrow transaction where the escrow
> is trusted by both parties, and other examples like that.

Yes, thats one example. Thanks Jorge!

A similar but relevant example would be like the M-Pesa example.
People that have a phone but not a smart phone can choose to have their 
private keys stored at a trusted company in their own country. Some payments 
can be off-chain, but as soon as you deal with people outside of this small 
community they would be on-chain.

When we are talking about remittances, this means one of the two parties does 
not have an account at the trusted party and as such this will be an on-chain 
transaction.
Same for a farmer in Nairobi buying equipment from a company in Cairo, or a 
Internet startup in Kampala/Uganda selling services to users in Europe and 
those users send their payments on-chain.

All of these examples are about the largest group of people in the world; the 
unbanked. Bitcoin could mean a huge change to these people and I care a lot 
about this usecase. We need bigger bocks for these usecases as LN will not do 
anything for them.

-- 
Thomas Zander


  parent reply	other threads:[~2015-08-10 21:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-08  6:10 [bitcoin-dev] trust Thomas Zander
2015-08-08  8:39 ` Adam Back
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 [this message]
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=2674312.GqtxTJeqiO@coldstorage \
    --to=thomas@thomaszander.se \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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