From: Natanael <natanael.l@gmail•com>
To: Justus Ranvier <justusranvier@riseup•net>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] alternate proposal opt-in miner takes double-spend (Re: replace-by-fee v0.10.0rc4)
Date: Sun, 22 Feb 2015 17:36:39 +0100 [thread overview]
Message-ID: <CAAt2M1-DbpqsYZcng+SJyHMxyt-_POSo5DEsUXz_LzmJud5WaA@mail.gmail.com> (raw)
In-Reply-To: <54EA02E7.8060708@localhost.local>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
- Sent from my tablet
Den 22 feb 2015 17:25 skrev "Justus Ranvier" <justusranvier@riseup•net>:
>
> You just disproved your own argument.
>
> It is possible to predict risk, and therefore to price the risk.
Your fault is that you assume the predictions can be reliable and
trustable.
They can not be.
The data you have available has none of the indicators you actually NEED to
make predictions. You're making extrapolations from the past, not
calculations based on recent trends and behavior globally.
> You also noted that for some Bitcoin users, the price of that risk is
> too high for the types of transactions in which wish to engage.
>
> In what way does that translated into a universal requirement for
> everybody to use multisignature notaries?
It isn't universal. It is just the most practical solution if you need
instant confirmation for high value transactions with customers you don't
yet trust.
> Surely the users who can afford the risk can use zero conf if they
> like, and those who can't can use multisig notaries?
Use whatever you want. I don't care. I will warn you about the risks and
make suggestions, but I won't force you to do anything differently.
[-- Attachment #2: Type: text/html, Size: 1496 bytes --]
next prev parent reply other threads:[~2015-02-22 16:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 8:02 Adam Back
2015-02-22 12:34 ` Peter Todd
2015-02-22 13:29 ` Natanael
2015-02-22 13:50 ` Matt Whitlock
2015-02-22 14:07 ` Peter Todd
2015-02-22 16:00 ` Justus Ranvier
2015-02-22 16:17 ` Natanael
2015-02-22 16:25 ` Justus Ranvier
2015-02-22 16:36 ` Natanael [this message]
2015-02-23 11:03 ` Mike Hearn
2015-02-22 14:44 ` Natanael
2015-02-22 14:11 ` Adam Back
2015-02-22 14:25 ` Bryan Bishop
2015-02-22 14:33 ` Peter Todd
2015-02-22 15:18 ` joliver
2015-02-22 15:41 ` Peter Todd
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=CAAt2M1-DbpqsYZcng+SJyHMxyt-_POSo5DEsUXz_LzmJud5WaA@mail.gmail.com \
--to=natanael.l@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=justusranvier@riseup$(echo .)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