public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Michael Grønager" <gronager@ceptacle•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Announcement: libcoin
Date: Wed, 1 Feb 2012 15:18:32 +0100	[thread overview]
Message-ID: <D55C3D18-8286-44E9-B877-6FCE7C05E980@ceptacle.com> (raw)

Dear Bitcoiners,

libcoin is now in a state ready for its first release, which I would like to share with you!

=== libcoin is a crypto currency library based on the bitcoin/bitcoin "Satoshi" client. ===

Copenhagen, Denmark - 1st February 2012 Ceptacle announces the release of the first version of the crypto currency library "libcoin" based on the bitcoin/bitcoin "Satoshi" client.

libcoin also maintains a version of bitcoind that is a 100% compatible drop-in replacement of the bitcoin/bitcoind client: You can use it on the same computer on the same files and you can call it with the same scripts. And you can easily extend it without touching the basic bitcoin source files.

The libcoin/bitcoind client downloads the entire block chain 3.5 times faster than the bitcoin/bitcoind client. This is less than 90 minutes on a modern laptop!

In libcoin, the Satoshi client code has been completely refactored, properly encapsulating classes, removing all globals, moving from threads and mutexes to a pure asynchronous approach. Functionalities have been divided into logical units and libraries, minimizing dependencies for e.g. thin clients.

libcoin is chain agnostic, all chain (bitcoin, testnet, namecoin, litecoin, ...) specific settings are maintained from a single class (Chain) and hence experiments with chain settings, mining, security and digital currencies for research and educational purposes are easily accessible. See the ponzicoin example for how you define your own chain.

The build system of libcoin is based on CMake and supports builds of static and dynamic libraries on Linux, Mac OS X, and Windows.

The libcoin license is LGPL v. 3. This mean that you can use it in open source as well as in commercial projects, but improvements should go back into the libcoin library.

======

Read more on libcoin on: http://github.com/ceptacle/libcoin/wiki

Join libcoin on twitter: http://twitter.com/libcoin

Download "libcoin Satoshi release": http://github.com/ceptacle/libcoin/zipball/v0.4.0.1

Best regards,

Michael Gronager, PhD
Director, Ceptacle
Jens Juels Gade 33
2100 Copenhagen E
Mobile: +45 31 45 14 01
E-mail: gronager@ceptacle•com
Web: http://www.ceptacle.com/




             reply	other threads:[~2012-02-01 14:18 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 14:18 Michael Grønager [this message]
2012-02-01 14:59 ` Gregory Maxwell
2012-02-01 15:50   ` Michael Grønager
2012-02-01 16:06     ` Jorge Timón
2012-02-01 15:02 ` Wladimir
2012-02-01 15:52   ` Michael Grønager
2012-02-01 15:09 ` slush
2012-02-01 15:57   ` Michael Grønager
2012-02-01 23:50     ` grarpamp
2012-02-02  8:32       ` Michael Grønager
2012-02-02 11:34         ` Craig B Agricola
2012-02-03  0:19         ` Pieter Wuille
2012-02-03  9:52           ` Michael Grønager
2012-02-01 15:26 ` Luke-Jr
2012-02-01 15:58   ` Michael Grønager
2012-02-01 16:15     ` Luke-Jr
2012-02-01 16:21       ` Michael Grønager
2012-02-01 16:23       ` Aidan Thornton
2012-02-01 16:20   ` Michael Grønager
2012-02-01 16:23     ` Luke-Jr
2012-02-01 17:37     ` Luke-Jr
2012-02-01 17:51       ` Michael Grønager
     [not found] ` <CAAS2fgSQZ1wv=OXnBnGbKnLTZXbn909umpPBaZDF2g6vy8katA@mail.gmail.com>
2012-02-02 17:12   ` Gregory Maxwell
2012-02-02 17:36     ` Gregory Maxwell
2012-02-02 17:46       ` Gregory Maxwell
2012-02-23 17:31 ` Martinx - ジェームズ
2012-02-23 19:48   ` Michael Grønager
2012-02-23 20:01   ` Michael Grønager
2012-02-23 20:35   ` Michael Grønager
2012-02-23 23:29     ` Martinx - ジェームズ
2012-02-24  2:17       ` Martinx - ジェームズ
2012-02-24  7:44         ` Michael Grønager
2012-02-24 16:17         ` Michael Grønager
2012-02-24 18:49           ` Martinx - ジェームズ
2012-02-24 19:40             ` Michael Grønager
2012-02-24 19:57             ` Michael Grønager
2012-02-25  2:11               ` Martinx - ジェームズ
2012-02-26 17:57                 ` Michael Grønager
2012-02-27 19:03                   ` Martinx - ジェームズ
2012-02-27 21:03                     ` Michael Grønager
2012-02-28  9:03                     ` Michael Grønager
     [not found]                       ` <CAJSM8J15LBiT9ojrPDE1-TXqmBLXcVvAmWw0e=5nQfLtMQ42Zg@mail.gmail.com>
     [not found]                         ` <8CEEE576-37DF-4101-9593-73D5FB66D52F@ceptacle.com>
2012-03-22 10:48                           ` Martinx - ジェームズ
2012-03-22 11:34                             ` Michael Grønager
2012-03-28  7:59                               ` Martinx - ジェームズ
2012-03-22 10:50                       ` Martinx - ジェームズ
2012-03-22 11:35                         ` Michael Grønager
2012-03-22 16:34                           ` Peter Vessenes
2012-03-27  9:58                             ` Martinx - ジェームズ
     [not found]                               ` <B4616B21-7C05-4793-8452-376EE4122BEC@ceptacle.com>
2012-04-15  4:32                                 ` Martinx - ジェームズ
2012-07-16 20:14 ` Martinx - ジェームズ
2012-09-12 23:27   ` Martinx - ジェームズ

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=D55C3D18-8286-44E9-B877-6FCE7C05E980@ceptacle.com \
    --to=gronager@ceptacle$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.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