From: Peter Vessenes <peter@coinlab•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [ANNOUNCE] picocoin and libccoin -- C-based bitcoin library and client
Date: Wed, 28 Nov 2012 09:29:04 -0800 [thread overview]
Message-ID: <CAMGNxUsbCJT=wCsw4pyZeHwm5v7yLs=5k8NFb5amC2aoe3ubSg@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2X5zt3qbiqq6AyxM67Rn8woji9j1gEAaatMm0EotKstw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Jeff,
This rocks. Thank you!
Peter
On Wed, Nov 28, 2012 at 3:26 AM, Mike Hearn <mike@plan99•net> wrote:
> Cool, will check it out soon.
>
> > libccoin should work on Windows. picocoin will work on Windows,
> > but be a bit less secure than other platforms due to lack of fork.
>
> FYI, Windows has quite good sandboxing support. You could implement
> the same thing later with Win32 if you want.
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
------------------------------
[image: CoinLab Logo]PETER VESSENES
CEO
*peter@coinlab•com * / 206.486.6856 / SKYPE: vessenes
811 FIRST AVENUE / SUITE 480 / SEATTLE, WA 98104
[-- Attachment #2: Type: text/html, Size: 2709 bytes --]
prev parent reply other threads:[~2012-11-28 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 20:34 Jeff Garzik
2012-11-28 11:26 ` Mike Hearn
2012-11-28 17:29 ` Peter Vessenes [this message]
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='CAMGNxUsbCJT=wCsw4pyZeHwm5v7yLs=5k8NFb5amC2aoe3ubSg@mail.gmail.com' \
--to=peter@coinlab$(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