From: Matthew Beton <matthew.beton@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Solving the Scalability Problem on Bitcoin
Date: Sun, 27 Aug 2017 13:19:25 +0000 [thread overview]
Message-ID: <CALKSEdpcov1ptBMvDEjh=L-XgpZA-Va4fen9c1yKh_EAxiX5Cw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
I think a slight problem with this is that wallets (often ones made by
third party wallet software) do not fully empty. I don't know how often
this happens, but some wallets, even if you tell them to send all funds,
leave a small fraction of bitcoin remaining. If this is the case, it could
be detrimental to the 'pruning idea', as wallets with any coins left cannot
be pruned. For example:
A has 1 BTC
A -> B -> C
If these wallets are not removing all the BTC, and a fraction is left over,
B will not be able to be pruned out of the chain. On the other hand, of the
wallets are completely emptied, the new 'pruned block' will be able to show
A sending 1btc to C.
This could be a problem, and so we need a way to persuade people to get
their wallets to send everything instead of leaving a small fraction left
over. I don't know how problematic this could be, or how frequently this
happens, but I'm just putting it out there.
[-- Attachment #2: Type: text/html, Size: 1089 bytes --]
next reply other threads:[~2017-08-27 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 13:19 Matthew Beton [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-26 19:21 Adam Tamir Shem-Tov
2017-08-26 21:31 ` Thomas Guyot-Sionnest
2017-08-26 22:32 ` Adam Tamir Shem-Tov
2017-08-27 5:18 ` Thomas Guyot-Sionnest
[not found] ` <CAN6UTayLR6rqSuHrsyF+7fFM4Fht7vbgXYRWzBRYXw8i43WzBw@mail.gmail.com>
2017-08-27 12:10 ` Leandro Coutinho
2017-08-27 3:52 ` Btc Ideas
2017-08-27 0:27 ` Weiwu
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='CALKSEdpcov1ptBMvDEjh=L-XgpZA-Va4fen9c1yKh_EAxiX5Cw@mail.gmail.com' \
--to=matthew.beton@gmail$(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