public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Adam Back <adam@cypherspace.org>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] patents...
Date: Mon, 19 May 2014 16:47:09 +0200	[thread overview]
Message-ID: <20140519144709.GA29574@netbook.cypherspace.org> (raw)
In-Reply-To: <5379FF38.4050909@certimix.com>

someone recently wrote (not pointing fingers, nor demanding a spirited
defense from that person, its a generic comment):
>   PS: the device has patents pending

btw about patents, I wonder if people who feel the need to do that, would
you consider putting those patents into like a linux foundation defensive
pool?

I imagine a number of other bitcoin companies have patented things, but if
you think ahead a little bit, or look at prior ecash history, patents held
by individuals or companies can be outright dangerous.  

We saw this in the past eg the digicash patents after the company went
bankrupt were sold by the investor to some random large company that parked
it in its huge pile of patents, didnt use it, and prevented anyone else from
using it - stalling Chaum dependent payment innovation for perhaps 5 years
until the thing expired, and a Chaum patent expiry party was held.

Just some food for thought.

hmm Yes and this topic now is more than a bit non dev related.  Sorry about
that.  There seems to be no convenient mailing list format for non-dev stuff
or I would Cc and set Reply-To for example?  (Web forums somewhat suck IMO). 

Adam



  parent reply	other threads:[~2014-05-19 14:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17 15:31 [Bitcoin-development] Paper Currency Jerry Felix
2014-05-17 15:45 ` Matt Whitlock
2014-05-17 16:07 ` Chris Pacia
2014-05-17 16:40   ` Gregory Maxwell
2014-05-18 11:47     ` Alex Kotenko
2014-05-18 12:14       ` Andreas Schildbach
2014-05-18 12:51         ` Alex Kotenko
2014-05-19 13:06           ` Brooks Boyd
2014-05-19 13:50             ` Alex Kotenko
2014-05-18 13:50       ` Natanael
2014-05-18 18:47         ` Alex Kotenko
2014-05-18 20:10           ` Natanael
2014-05-19 10:26             ` Alex Kotenko
2014-05-19 12:55       ` Sergio Lerner
2014-05-19 13:34         ` Martin Sip
2014-05-19 13:53         ` Alex Kotenko
2014-05-19 14:47         ` Adam Back [this message]
2014-05-19 15:09           ` [Bitcoin-development] patents Mike Hearn
2014-05-19 18:27             ` Peter Todd
2014-05-19 18:40               ` Mike Hearn
2014-05-19 18:43             ` Gregory Maxwell
2014-05-19 18:46               ` Peter Todd
2014-05-19 18:49               ` Mike Hearn
2014-05-19 22:15             ` Bernd Jendrissek
2014-05-20 10:30           ` Jeff Garzik
2014-05-18 13:50 ` [Bitcoin-development] Paper Currency Andreas Schildbach
2014-05-19 12:21 ` Mike Hearn
2014-05-19 18:20   ` Justus Ranvier
2014-05-19 18:39     ` Peter Todd

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=20140519144709.GA29574@netbook.cypherspace.org \
    --to=adam@cypherspace.org \
    --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