From: "Jorge Timón" <jtimon@jtimon•cc>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
Sergio Demian Lerner <sergio.d.lerner@gmail•com>
Subject: Re: [bitcoin-dev] The use OP_COUNT_ACKS for paying for a common good for miners
Date: Mon, 3 Oct 2016 08:17:25 +0200 [thread overview]
Message-ID: <CABm2gDpA=uOw7g-ARn3QoDPj1jRSyjsADsZmTvV2cfx97Q5RWw@mail.gmail.com> (raw)
In-Reply-To: <CAKzdR-r1mFZidZXDSmwVtHZ-KKPwsjZOHZycqR+H+KUBGBFydQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
When would miners vote no to receive more funds?
Also, why would they spend the funds buying X once they get them?
On Oct 3, 2016 00:58, "Sergio Demian Lerner via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> One side benefit of OP_COUNT_ACKS is that it enables a completely
> different use case:
>
> It allow users to pay for any service miners can provide as group for the
> common good (e.g. fee payment smoothing over many blocks). For instance,
> users could pay miners to jointly buy better Internet service to improve
> bandwidth or reduce latency between them.
>
> By sending bitcoins to a script containing OP_COUNT_ACKS requiring 51% of
> miners approval and adding a special text tag to such outputs such as
> "FOR-MINERS-TO-BUY-X", users can send bitcoins to miners and ask the
> majority of them to vote on the proposal, if accepted create a transaction
> to redeem those funds. This could help to address the so-called tragedy of
> the commons problem that Bitcoin may face in in long-term, by users
> crowdfunding mining of the following n blocks.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 1801 bytes --]
prev parent reply other threads:[~2016-10-03 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 22:57 Sergio Demian Lerner
2016-10-03 6:17 ` Jorge Timón [this message]
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='CABm2gDpA=uOw7g-ARn3QoDPj1jRSyjsADsZmTvV2cfx97Q5RWw@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=sergio.d.lerner@gmail$(echo .)com \
/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