From: Tamas Blummer <tamas@bitsofproof•com>
To: Matt Whitlock <bip@mattwhitlock•name>
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 18:44:31 +0100 [thread overview]
Message-ID: <656E7756-5F0B-4594-B9F1-8CC68C7A5EE5@bitsofproof.com> (raw)
In-Reply-To: <2236907.ZtrNgikFVR@crushinator>
[-- Attachment #1.1: Type: text/plain, Size: 735 bytes --]
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.
Tamas Blummer
On Jan 20, 2015, at 6:23 PM, Matt Whitlock <bip@mattwhitlock•name> wrote:
>
> If you have the private keys for your users' bitcoins, then you are every bit as much the owner of those bitcoins as your users are. There is no custodial relationship, as you have both the ability and the right to spend those bitcoins. Possession of a private key is equivalent to ownership of the bitcoins controlled by that private key.
[-- Attachment #1.2: Type: text/html, Size: 1843 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2015-01-20 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 15:46 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 [this message]
2015-01-20 17:47 ` Matt Whitlock
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=656E7756-5F0B-4594-B9F1-8CC68C7A5EE5@bitsofproof.com \
--to=tamas@bitsofproof$(echo .)com \
--cc=bip@mattwhitlock$(echo .)name \
--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