public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Assurance contracts to fund the network with OP_CHECKLOCKTIMEVERIFY
Date: Fri, 8 May 2015 16:03:28 +0100	[thread overview]
Message-ID: <CAE-z3OVMfxioXUrFVAzcD7kpqsUA9_V=iCx67k+WkbZkFHrVig@mail.gmail.com> (raw)
In-Reply-To: <CAOoPuRZo6M1-XTYk6LebADHwQVwKEOYtaHGvEoRkk5AfevvJYw@mail.gmail.com>

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

Sorry for the spam of the last mail.  I hit send by accident.

Assurance contracts are better than simple donations.

Donating to a project means that you always end up losing the money but the
project might still not get funded.

An assurance contract is like Kickstarter, you only get your CC charged if
the project is fully funded.

There is lower risk, either you get your money back or the project is
funded.  It might still be worth risking it and hoping it gets funded.

Kickstarter does have pledge rewards to reward pledgers.  That helps with
creating the momentum to encourage people to pledge.

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

  parent reply	other threads:[~2015-05-08 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 23:32 [Bitcoin-development] Assurance contracts to fund the network with OP_CHECKLOCKTIMEVERIFY Tier Nolan
2015-05-08  9:49 ` Mike Hearn
2015-05-08 10:01   ` Benjamin
2015-05-08 14:15     ` Tier Nolan
2015-05-08 14:54       ` Benjamin
2015-05-08 14:56         ` Tier Nolan
2015-05-08 15:03         ` Tier Nolan [this message]
2015-05-08 10:00 ` Jeff Garzik
2015-05-08 16:43   ` Peter Todd

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='CAE-z3OVMfxioXUrFVAzcD7kpqsUA9_V=iCx67k+WkbZkFHrVig@mail.gmail.com' \
    --to=tier.nolan@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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