From: Adam Back <adam@cypherspace•org>
To: Gavin Andresen <gavinandresen@gmail•com>
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 11:37:08 +0200 [thread overview]
Message-ID: <20130929093708.GA16561@netbook.cypherspace.org> (raw)
In-Reply-To: <CABsx9T29T+thSeF-xVk+prfeO7ZJQbX=n=tAURqEKQsVtcBpQg@mail.gmail.com>
There are some policy decision points in the protocol (and code) that may
become centralized risks or choke points that undermine the p2p nature. So
the extent that those can be argued to have in principle have a technical
fix, it could be quite interesting to research the necessary technology
(advanced crypto, byzantine networking argument etc) that could address
them. eg payee/payer blacklisting by a large group of miners and "committed
transaction" proposal to address it.
However even for that type of thing I think bitcoin-dev would probably
rather focus eg on something that has reached the stage of having a BIP. Eg
it might be better to discuss early stage or speculative ideas on
bitcointalk.org technical thread.
https://bitcointalk.org/index.php?board=6.0
taxation in particular there are examples where even the political sphere
accepts significantly anonymous taxation. eg for europeans with certain
types of investment in a swiss bank, the swiss bank sends however many
million as a single payment across all users per european country to their
passport home country (minus 25% cut for the swiss government). Perhaps
such things could be possible for bitcoin. Again I think bitcoin talk would
be a good place for such a discussion if that was the OP question
indirectly.
Adam
On Sun, Sep 29, 2013 at 06:32:10PM +1000, Gavin Andresen wrote:
> On Sun, Sep 29, 2013 at 12:28 PM, Neil Fincham <[1]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
>
>References
>
> 1. mailto:neil@asdf•co.nz
>------------------------------------------------------------------------------
>October Webinars: Code for Performance
>Free Intel webinars can help you accelerate application performance.
>Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>the latest Intel processors and coprocessors. See abstracts and register >
>http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists•sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2013-09-29 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 23:41 Melvin Carvalho
2013-09-28 20:15 ` rob.golding
2013-09-29 2:28 ` Neil Fincham
2013-09-29 8:32 ` Gavin Andresen
2013-09-29 9:37 ` Adam Back [this message]
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=20130929093708.GA16561@netbook.cypherspace.org \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@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