From: Bdimych Bdimych <bdimych@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Block size possible solution - to set minimum size
Date: Sat, 22 Aug 2015 18:30:32 -0500 [thread overview]
Message-ID: <CALNn0ZZ5gY6R7gzpLpbNnFecAz35ZqaLx_RNPxx=SoJTAdHDXg@mail.gmail.com> (raw)
Hi,
As I understand the main problem of the fork Core<->XT is possibility
of double spending:
-I run XT and spend my coins
-it is written in 8mb block
-Core does not accept this block
-I run Core and spend my coins again
-it is written in 1mb block
-but XT accepts this block too
so
-in the XT blockchain both blocks [8] and [1] contain my coins
I thought that possible solution can be to set minimum block size
i.e.
2016: 1mb <= blockSize < 2mb
2017: 2mb <= blockSize < 3mb
2018: 3mb <= blockSize < 4mb
etc
Free space could be filled with zeroes and compressed.
That's all, just an idea.
With Best Regards
Dmitry Bolshakov
bdimych@gmail.com
next reply other threads:[~2015-08-22 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 23:30 Bdimych Bdimych [this message]
2015-08-23 6:40 ` [bitcoin-dev] Block size possible solution - to set minimum size Jorge Timón
2015-08-23 14:04 ` Bdimych Bdimych
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='CALNn0ZZ5gY6R7gzpLpbNnFecAz35ZqaLx_RNPxx=SoJTAdHDXg@mail.gmail.com' \
--to=bdimych@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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