public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@hozed•org>
To: Evan Duffield <eduffield82@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Looking for GREAT C++ developer for exciting opportunity in bitcoin space
Date: Thu, 2 Jan 2014 23:11:28 -0600	[thread overview]
Message-ID: <20140103051128.GJ3180@nl.grid.coop> (raw)
In-Reply-To: <CAMkFLsSwKEiEtV1OaAsGPiU8iAWbb77fDNJDmRwbgKnZ_kjG6Q@mail.gmail.com>

On Sun, Dec 29, 2013 at 11:53:19AM -0700, Evan Duffield wrote:
> Hello,
> 
> We’re a startup looking for 1 or 2 really good C++ programmer that is
> familiar with the bitcoin internals to help with a for-profit startup.
> 
> We will be able to provide more information about the project after signing
> a non-compete/non-disclosure agreement. Our coin will be one of the truly
> unique coins that are not just a clone of the original Bitcoin code. In
> short the project will be a merge-mined altcoin that will provide a very
> useful service to the whole crypto-coin ecosystem.
> 
> If you have added any features to Bitcoin or related technologies this is a
> definite bonus. Please include information about the work you’re done in
> the space.
> 
> We have detailed plans on how to implement it and the roles we are looking
> to fill. If interested please email eduffield82@gmail•com with a
> description of your work experience and we’ll vett the applications and
> share our plans to see if you’re interested.
> 
> Thanks,
> 
> Evan & Kyle
> Hawk Financial Group, LLC

Evan & Kyle,

I have a very unique and one-of-a kind offer for you. I will buy your company
from the revenue generated from my AGPLv3 copyright licensed Minco.me(c) 
cryptographic currency, which will revolutionize work by ensuring that anyone
with a Mincome(C) address doesn't need to work.

Ask yourself.. why would someone who can write a cryptocurrency want to *work*
for you, to get paid with... money.. that they can just ...
  ** write code that makes them money **

Please be aware that any concept(s) that I have publicly discussed, or that 
we may or may not have talked about if I would have signed a non-enforceable
non-compete agreement are COPYRIGHT 2013,2014 Troy Benjegerdes, and that I
would advise you seek competent legal council to ensure that this email, or
any other contact we may or may not have had does not contaminate your 
business model with a viral copyright license.


To everyone else on this list, I'm sorry, I just could not resist feeding 
the VC/marketing trolls.


-- Troy, 'da hozer'



  parent reply	other threads:[~2014-01-03  5:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29 18:53 Evan Duffield
2013-12-29 19:27 ` Matt Corallo
2013-12-30 23:22 ` Peter Todd
2013-12-31  1:14   ` Luke-Jr
2013-12-31  7:28     ` [Bitcoin-development] Merge mining Jeremy Spilman
2013-12-31  7:38       ` rob.golding
2014-01-04  8:49         ` David Vorick
2014-01-04 10:05           ` Jorge Timón
2014-01-04 10:08             ` David Vorick
2014-01-04 10:34               ` Jorge Timón
2014-01-01  4:53     ` [Bitcoin-development] The insecurity of merge-mining Peter Todd
2014-01-01  5:09       ` Luke-Jr
2014-01-01  5:25         ` Peter Todd
2014-01-03 19:14       ` Jorge Timón
2014-01-03 21:01         ` Peter Todd
2014-01-04  0:27           ` Jorge Timón
2014-01-06 15:44             ` Peter Todd
2014-01-09 17:19               ` Jorge Timón
2014-01-10 11:11                 ` Peter Todd
2014-01-10 11:25                   ` Peter Todd
2014-01-10 12:37                     ` Jorge Timón
2014-01-10 12:29                   ` Jorge Timón
2014-01-10 17:22                     ` Peter Todd
2014-01-10 18:50                       ` Jorge Timón
2014-01-03  5:11 ` Troy Benjegerdes [this message]
2013-12-29 19:10 [Bitcoin-development] Looking for GREAT C++ developer for exciting opportunity in bitcoin space Jérémie Dubois-Lacoste

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=20140103051128.GJ3180@nl.grid.coop \
    --to=hozer@hozed$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=eduffield82@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