From: Mark Friedenbach <mark@monetize•io>
To: Adam Back <adam@cypherspace•org>,
Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] smart contracts -- possible use case? yes or no?
Date: Sun, 29 Sep 2013 10:49:00 -0700 [thread overview]
Message-ID: <5248680C.60404@monetize.io> (raw)
In-Reply-To: <20130929093708.GA16561@netbook.cypherspace.org>
This kind of thing - providing external audits of customer accounts
without revealing private data - would be generally useful beyond
taxation. If you have any solutions, I'd be interested to hear them
(although bitcoin-dev is probably not the right place yet).
Mark
On 9/29/13 2:37 AM, Adam Back wrote:
> 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.
next prev parent reply other threads:[~2013-09-29 17:54 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
2013-09-29 17:49 ` Mark Friedenbach [this message]
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=5248680C.60404@monetize.io \
--to=mark@monetize$(echo .)io \
--cc=adam@cypherspace$(echo .)org \
--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