From: Dave Scotese <dscotese@litmocracy•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 2, Issue 95
Date: Fri, 24 Jul 2015 09:32:34 -0700 [thread overview]
Message-ID: <CAGLBAhe8-u+Tx25Q9nq8DYFvdmDes3GaAuOOQrjdS+Q=1pjwcg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
> Alternatively I think instead of displaying a meaningless number we ought
> to go by a percentage (the double spend improbability) and go by
> 'confidence'.
That is a great idea, and not too hard to implement. A bit of code can
determine over the last N blocks, how many blocks that were at the current
depth of the present transaction were orphaned and divide that by the total
number of blocks solved (orphaned or not) while those N blocks were
solved. That's the historical number (H), and then the "51% attack" number
(A) can make an explicit assumptions like "Assuming a bad actor has 51% of
the hashing power for 24 hours starting right now, the block holding this
transaction has an X% chance of being orphaned." Report "# confirmations"
as "99.44% confidence" using [100% - max(H,A)].
[-- Attachment #2: Type: text/html, Size: 1100 bytes --]
reply other threads:[~2015-07-24 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGLBAhe8-u+Tx25Q9nq8DYFvdmDes3GaAuOOQrjdS+Q=1pjwcg@mail.gmail.com' \
--to=dscotese@litmocracy$(echo .)com \
--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