public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Whitlock <bip@mattwhitlock.name>
To: Tamas Blummer <tamas@bitsofproof.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] The legal risks of auto-updating wallet software; custodial relationships
Date: Tue, 20 Jan 2015 12:47:04 -0500	[thread overview]
Message-ID: <30930479.sqHpaOe3cY@crushinator> (raw)
In-Reply-To: <656E7756-5F0B-4594-B9F1-8CC68C7A5EE5@bitsofproof.com>

On Tuesday, 20 January 2015, at 6:44 pm, Tamas Blummer wrote:
> Knowing the private key and owning the linked coins is not necessarily the same in front of a court.
> 
> At least in german law there is a difference between ‘Eigentum' means ownership and ‘Besitz’ means ability to deal with it.
> Being able to deal with an asset does not make you the owner.

So what we're telling the newbies in /r/bitcoin is plain wrong. Bitcoins *do* have an owner independent from the parties who have access to the private keys that control their disposition. That's pretty difficult to reconcile from a technological perspective.




  reply	other threads:[~2015-01-20 17:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 15:46 [Bitcoin-development] The legal risks of auto-updating wallet software; custodial relationships Peter Todd
     [not found] ` <CAHpxFbEoDLMGKB7arHbgB+4kx8BwgcX7nBUZz6yP9k4LjZeu1A@mail.gmail.com>
2015-01-20 17:15   ` Peter Todd
2015-01-20 17:23 ` Matt Whitlock
2015-01-20 17:40   ` Peter Todd
2015-01-20 17:44     ` Matt Whitlock
2015-01-20 17:44   ` Tamas Blummer
2015-01-20 17:47     ` Matt Whitlock [this message]
2015-01-20 17:49       ` Peter Todd
2015-01-20 17:56       ` Tamas Blummer
2015-01-20 17:47 ` Justus Ranvier
2015-01-20 18:48   ` Tamas Blummer
2015-01-20 19:31     ` Justus Ranvier
2015-01-20 21:33     ` odinn
2015-01-20 21:49 ` Roy Badami

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=30930479.sqHpaOe3cY@crushinator \
    --to=bip@mattwhitlock.name \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=tamas@bitsofproof.com \
    /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