From: Martijn Meijering <martijn.meijering@mevs•nl>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Reasons to add sync flags to Bitcoin
Date: Tue, 26 Jul 2016 22:58:00 +0200 [thread overview]
Message-ID: <CAODYVYfciFGoVMKtOWs9PNkEJEt768KFZNO6s-qFhzQFchUTXw@mail.gmail.com> (raw)
- Flags will be mined selfishly, and not published until the advantage
gained from withholding is less than the mining reward. This effect may
kill the decentralization features, since big miners will be the only ones
that can selfish-mine flags. Indeed, collusion would be encouraged... just
ship the flag to the miners you do business with, and no one else. At the
expense of loss of flag revenue, your in-group would gain a massive
advantage in main-chain mining.
---
Is there a reason miners would be more likely to engage in selfish
mining of sync flags than they are now with ordinary blocks?
next reply other threads:[~2016-07-26 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 20:58 Martijn Meijering [this message]
2016-07-26 21:45 ` Tier Nolan
-- strict thread matches above, loose matches on Subject: below --
2016-07-26 12:47 Moral Agent
2016-07-26 13:51 ` Tom
2016-07-26 17:27 ` Erik Aronesty
2016-07-26 22:03 ` Nick ODell
2016-07-27 14:42 ` Moral Agent
2016-07-28 16:41 ` Moral Agent
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=CAODYVYfciFGoVMKtOWs9PNkEJEt768KFZNO6s-qFhzQFchUTXw@mail.gmail.com \
--to=martijn.meijering@mevs$(echo .)nl \
--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