From: Gavin Andresen <gavinandresen@gmail.com>
To: Neil Fincham <neil@asdf.co.nz>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] smart contracts -- possible use case? yes or no?
Date: Sun, 29 Sep 2013 18:32:10 +1000 [thread overview]
Message-ID: <CABsx9T29T+thSeF-xVk+prfeO7ZJQbX=n=tAURqEKQsVtcBpQg@mail.gmail.com> (raw)
In-Reply-To: <CAH+ZByHs00+Cpx5bwybgV3G9=CBfHaHKg7AV9ytywKNAjFVM6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
On Sun, Sep 29, 2013 at 12:28 PM, Neil Fincham <neil@asdf.co.nz> wrote:
> I subscribe to this list so I can keep up-to date with bitcoin
> development, can we keep philosophy and tax evasion out of it?
>
Yes, that's off-topic for this mailing list. Lets stick to technical issues
that we can solve by writing code.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 696 bytes --]
next prev parent reply other threads:[~2013-09-29 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 23:41 [Bitcoin-development] smart contracts -- possible use case? yes or no? Melvin Carvalho
2013-09-28 20:15 ` rob.golding
2013-09-29 2:28 ` Neil Fincham
2013-09-29 8:32 ` Gavin Andresen [this message]
2013-09-29 9:37 ` Adam Back
2013-09-29 17:49 ` Mark Friedenbach
2013-10-01 14:26 ` [Bitcoin-development] homomorphic coin value (validatable but encrypted) (Re: smart contracts -- possible use case? yes or no?) Adam Back
2013-10-01 19:11 ` Adam Back
2013-10-07 19:01 ` Adam Back
2013-09-29 9:44 ` [Bitcoin-development] smart contracts -- possible use case? yes or no? Melvin Carvalho
2013-09-29 9:46 ` Melvin Carvalho
2013-09-29 11:33 ` Mike Hearn
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='CABsx9T29T+thSeF-xVk+prfeO7ZJQbX=n=tAURqEKQsVtcBpQg@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=neil@asdf.co.nz \
/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