public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: rob.golding@astutium.com
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] smart contracts -- possible use case? yes or no?
Date: Sat, 28 Sep 2013 21:15:34 +0100	[thread overview]
Message-ID: <2c70dbfc173749cf4198c591f19a7d33@astutium.com> (raw)
In-Reply-To: <CAKaEYhLvqT6nkbupEEgR1d9dMP4-pA7xQbBqPDbREiDDV7c0rQ@mail.gmail.com>

> But the regulatory environment in many geographical regions in
> uncertain.   Do we need to pay capital gains?   Do we need to pay a
> sales taxs etc. etc.

In most regions it's not only 'simple' but trivial - BTC is just 
'another currency' and accounted for exactly the same way - it doens't 
matter if you sell your hose for GBP, USD, EUR, BTC or sacks of Pig 
Dung, you still have a GBP tax issue ...

> So my idea is to voluntarily pre empt legislation by giving donations
> to govt (aka taxation) for bitcoin service providers. 

You want to volunteer to pay tax ? I'd suggest stronger medication ...

> However, there is something of a problem with voluntary donations. 
> Most people are not satisfied with the way they are spent.

80% of 'donations' end up spent on 'adminsitration' and not what they 
were donated for, this is a 'greed' issue not a 'currency' issue.

> In the UK
> a recent survey said that only 18% of people thought that tax money
> was wisely spent.

Tax isn't voluntary or a donation. The 18% who think UK tax is well 
spent are the 18% of the population who get the tax money, not the 82% 
that pay it ;)

> Can we fix it?

First we kill all the politicians ...

> So let's say I run a business and I make 1 million euros.  I wish to
> donate 10% of my profits to society.  But let's say I dont want that
> money to go to wars of aggression, but rather, to the fire
> de[department. 

So give it to the FD - what you do with your post-tax profits are up to 
you ;)

> At this point everyone wins.  The business person is happy to make a
> contribution.  The govt. is happy that it gets more revenue.  The
> fire dept. is happy that it has revenue to do its work.  And
> everything has gone to the right place in a kind of democratic way.

Where does gov't come into this ? I think you're confusing 'tax' which 
you have zero control over and 'donations' which you already have 100% 
control over.

Rob



  reply	other threads:[~2013-09-28 20:15 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 [this message]
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
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=2c70dbfc173749cf4198c591f19a7d33@astutium.com \
    --to=rob.golding@astutium.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