public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] trust
Date: Sat, 8 Aug 2015 07:59:40 -0400	[thread overview]
Message-ID: <55C5EF2C.6090408@bitcoins.info> (raw)
In-Reply-To: <CAOoPuRYk_R+kyfyrROcL8y9Bdfq7ufsyXSH_Uva2GPGcK_jwkA@mail.gmail.com>

> Trust takes many different forms and is not a binary function.

Many Bitcoiners have a rather unusual notion of trust.  While many state 
the established financial systems cannot be trusted they imply that many 
within the Bitcoin world need to be trusted.   There are some very 
irresponsible and unusual people who have authority to do things in the 
Bitcoin world such as manage the Wiki, the Github repository, and are 
given an emergency alert key.  Some of these people are only known by 
some sort of screen name.  If anyone questions any of these processes 
they are chastised and labeled a "troll".  For instance, anyone who 
questioned Mt. Gox back in 2013 was labeled a "buttcoiner" or something 
similar.  So I would say many people, including many on this list, don't 
fully understand the claims they are making about the "truslessness" of 
Bitcoin.

 >Lightning doesn't require explicit trust,

There seems to be semantic issues with describing trust and the 
lightning network.  You need to trust the other party during the 
transactions in the channel for it to work.  Yes there is way to cash 
out if the other party does not cooperate but that is not the same thing 
as saying it is trustless.  Many people are confused about this part of 
decentralization where the network has to take time to reach consensus. 
  Some people think that you can use some kind of technological trick to 
avoid this lag time and still have a completely trustless system.  It is 
a tradeoff.

Russ




  parent reply	other threads:[~2015-08-08 11:59 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
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 [this message]
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=55C5EF2C.6090408@bitcoins.info \
    --to=milly@bitcoins$(echo .)info \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /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