From: Gregory Maxwell <gmaxwell@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] patents...
Date: Mon, 19 May 2014 11:43:15 -0700 [thread overview]
Message-ID: <CAAS2fgRhEJUT4JEXtZSqnNnBV=tLFD4qjLFOQpeA-V2jA_UtHg@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3sDh3Q9T0xFi7maNQR9Z6R7gQ6vT5kjchcMkD0hMHOdw@mail.gmail.com>
On Mon, May 19, 2014 at 8:09 AM, Mike Hearn <mike@plan99•net> wrote:
> The first rule of patents is you do not go looking for patents. US law is
> written in a really stupid way, such that if you knowingly infringe, damages
> triple. Because America uses the patent office as a revenue source,
You have received outdated advice on this point. In Re Seagate
(http://patentlyo.com/patent/2007/08/in-re-seagate-t.html) this
precident was over-turned (and has subsequently been upheld in other
cases). Avoiding willfull infringement no longer requires paying off a
patent attorney to get a freedom to operate review. This isn't to say
that reading patents is always productive now: They're often nearly
inscrutable (especially to people without substantial patent reading
experience), and you may discover potential infringement that creates
more work for you to sort out (especially since people without patent
experience tend to read patents much more broadly than they actually
are).
There are other defensive approaches which are interesting than hoping
to use patents as a counter attack: For one— filing a patent gets the
work entered in the only database that USPTO examiners are
_guaranteed_ to consult when doing a prior art search, so it may have
a fighting chance of precluding someone else patenting the same
material later (they may also search the internet and use other
resources, but they're guaranteed to consult the existing patents and
applications). Patents can also be used defensively as leverage in a
licensing negotiation: Without your own patents you don't get invited
to the negotiating table at all with someone else who may hold patents
in a space that you're working on. These are somewhat thin advantages
so great care is required to make sure that things are setup so that
badness cannot happen later when inevitable changes of ownership
happen.
next prev parent reply other threads:[~2014-05-19 18:43 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 ` [Bitcoin-development] patents Adam Back
2014-05-19 15:09 ` Mike Hearn
2014-05-19 18:27 ` Peter Todd
2014-05-19 18:40 ` Mike Hearn
2014-05-19 18:43 ` Gregory Maxwell [this message]
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='CAAS2fgRhEJUT4JEXtZSqnNnBV=tLFD4qjLFOQpeA-V2jA_UtHg@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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