From: Erik Aronesty <erik@q32•com>
To: Tom <tomz@freedommail•ch>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reasons to add sync flags to Bitcoin
Date: Tue, 26 Jul 2016 13:27:22 -0400 [thread overview]
Message-ID: <CAJowKgLw+0LZJkQ-F2xi_t11dpJoWvTDQnyMjFPB+XfD98RvYw@mail.gmail.com> (raw)
In-Reply-To: <1659997.Te2m0CHHuS@garp>
[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]
- 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.
On Tue, Jul 26, 2016 at 9:51 AM, Tom via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> > #Basic idea:
> >
> > Ideally, all miners would begin hashing the next block at exactly the
> same
> > time. Miners with a head start are more profitable, and the techniques
> that
> > help miners receive and validate blocks quickly create centralization
> > pressure.
> >
> > What if there was something that acted like the starting flag at a race,
> > which could suddenly wave and cause all of the miners to simultaneously
> > begin hashing the next block?
> >
> > #Implementation:
> >
> > Let a sync flag be a message consisting of:
> >
> > 1. Hash of the previous block.
> > 2. Bitcoin address
> > 3. Nonce
> >
> > This tiny message could propagate through the network at maximum speed.
> If
> > miners had to include the hash of this flag in the next block, then all
> > miners wait for this flag, and when it suddenly spread through the
> network,
> > all miners could simultaneously begin hashing the next block.
>
> What you describe in this part of your message can be done with no forks
> whatsoever and I think that this is enough. Don't really see the reason for
> any change in funding.
>
> The idea of sending out a block header is essentially what I called
> "optimistic mining" and has been described in more detail in my blog here;
> http://zander.github.io/posts/Innovation%20-%20OnlineScaling/
>
> The video explains with graphics too...
>
> You may find this interesting :)
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3007 bytes --]
next prev parent reply other threads:[~2016-07-26 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 12:47 Moral Agent
2016-07-26 13:51 ` Tom
2016-07-26 17:27 ` Erik Aronesty [this message]
2016-07-26 22:03 ` Nick ODell
2016-07-27 14:42 ` Moral Agent
2016-07-28 16:41 ` Moral Agent
2016-07-26 20:58 Martijn Meijering
2016-07-26 21:45 ` Tier Nolan
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=CAJowKgLw+0LZJkQ-F2xi_t11dpJoWvTDQnyMjFPB+XfD98RvYw@mail.gmail.com \
--to=erik@q32$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tomz@freedommail$(echo .)ch \
/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