public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Neil Haran <nharan81@gmail•com>
To: Lauri Love <lauri.love@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin mining idea
Date: Mon, 28 Sep 2015 22:47:04 -0700	[thread overview]
Message-ID: <CA+9tygLp+-Yc35hZw_NfV7Xkjgo7Xs6TH8WRJMar1o8=FiieyA@mail.gmail.com> (raw)
In-Reply-To: <CA+et0t4VmHWJZmast+VbmYsZGihX2qcvagOR+aqx7R+DGOfTrA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]

My apologies Lauri!

Here is the idea:

I want to build a massive rock paper scissors tournament, the largest the
world has ever seen and one that no one can stop. I imagine re-purposing
bitcoin-qt to do this.

Imagine a tournament like the World Series of Poker, but for RPS.

Each person plays a best of 5 tournament each round. The players are
randomly matched against each other. The number of rounds would effectively
be the depth of a binary tree...

So if a million people play in this tournament, you would need to win 20
rounds to win the tournament and the cash prize.

Now, I will supply this cash prize and I have media connections to get
coverage for this. I fully believe I could get millions playing in this.

Thanks,
Neil


On Mon, Sep 28, 2015 at 6:33 AM, Lauri Love <lauri.love@gmail•com> wrote:

> Don't solicit interest in advance of content, please. Share your idea
> first and if people find it cogent and interesting they will volunteer
> interest/assistance.
>
> On 27 September 2015 at 18:53, Neil Haran via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> > Hi,
> >
> > I have an idea for a gamified bitcoin mining app that I'd like to partner
> > with someone on that is very good with cryptography and knows the bitcoin
> > code base well. I have received interest in this from some, but I'm
> looking
> > for the ideal candidate to work with. If this is of interest, please
> email
> > me at nharan81@gmail•com.
> >
> > Thanks,
> > Neil
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists•linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
>
>
>
> --
> [Any text in this message is copyrighted to the full extent of the law
> in all jurisdictions with the following license: it may be read and
> stored or used to create derivative works by any person or
> organization with the following exceptions: all law-enforcement
> organizations, all national intelligence services, all corporate
> entities that monitize personal information. Any violations of this
> license with be prosecuted relentlessly and the highest possible
> damages sought.]
>

[-- Attachment #2: Type: text/html, Size: 3198 bytes --]

  reply	other threads:[~2015-09-29  5:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-27 17:53 Neil Haran
2015-09-28 13:33 ` Lauri Love
2015-09-29  5:47   ` Neil Haran [this message]
2015-09-29  5:56     ` Trevin Hofmann
2015-09-29  6:13       ` Milly Bitcoin
2015-09-29 21:07 ` Jeff Garzik
2015-09-29 22:58   ` Milly Bitcoin
2015-09-29 23:02     ` Jonathan Toomim (Toomim Bros)
2015-09-29 23:16       ` Milly Bitcoin
2015-09-29 23:54         ` Jeff Garzik
2015-09-30  0:07           ` Milly Bitcoin
2015-09-30  0:10             ` Jeff Garzik

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='CA+9tygLp+-Yc35hZw_NfV7Xkjgo7Xs6TH8WRJMar1o8=FiieyA@mail.gmail.com' \
    --to=nharan81@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=lauri.love@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