From: Mike Hearn <mike@plan99•net>
To: Andy Parkins <andyparkins@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Protocol changes
Date: Fri, 12 Aug 2011 00:02:09 +0200 [thread overview]
Message-ID: <CANEZrP1Dt9pqQ7-kj=DjPDi6zU83JgWqjRQa1t4SZt+CErxm9w@mail.gmail.com> (raw)
In-Reply-To: <201108111824.42807.andyparkins@gmail.com>
> I can't say I see what the point of all that added complexity is, contracts
> are usually more than just financial
The term "contract" is sort of misleading, but there isn't a better
word for it. Satoshi called them contracts so that's what I call them
too.
http://en.bitcoin.it/wiki/Contracts
The point is to allow for lower trust in certain types of
transactions. For instance, consider Kickstarter. They allow people to
club together to fund the creation of new things, typically indie
movies and games. The problem is you need this trusted middleman to
collect peoples pledges and aggregate them. That adds fees, etc. With
contracts it can be done entirely with software, all the artist/game
programmer would need is to run some software on their website.
> What then allows the contract out of the memory pool into a chain? The
> locktime? No, no, forget it... I don't want to open a new can of worms.
;)
Lock time or if every sequence number is UINT_MAX.
prev parent reply other threads:[~2011-08-11 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 16:17 Mike Hearn
2011-08-11 17:24 ` Andy Parkins
2011-08-11 22:02 ` Mike Hearn [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='CANEZrP1Dt9pqQ7-kj=DjPDi6zU83JgWqjRQa1t4SZt+CErxm9w@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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