From: Chris Stewart <chris@suredbits•com>
To: Christian Decker via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin-s v0.3.0 release
Date: Sun, 22 Mar 2020 17:09:00 -0500 [thread overview]
Message-ID: <CAFQwNuxo4h3c7h2ODxomgOFzSyANJ-+Aepi_UyqcQMj7a1tqDw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Hi all
We just released v0.3.0 of bitcoin-s.
Bitcoin-s is a loosely coupled set of cryptocurrency libraries for the JVM.
They work well together, but also can be used independently. This project's
goal is NOT to be a full node implementation, rather a set of scalable
cryptocurrency libraries that use industry standard tools (rather than
esoteric tech often found in cryptocurrency) where possible to make the
lives of professional software engineers, security engineers, devops
engineers and accountants easier. We are rapidly iterating on development
with the goal of getting to a set of stable APIs that only change when the
underlying bitcoin protocol changes.
Here is an interactive code editor that allows you to play around with
basic data structures in bitcoin-s like private keys, psbts, and block
filters:
https://scastie.scala-lang.org/Christewart/IqidPZ3gTbOUbMmAf6F2MA/5
You can find more examples of how our neutrino node, wallet, bitcoind rpc
client and secp256k1jni (bindings for libsecp256k1) work on our website:
https://bitcoin-s.org/docs/next/getting-setup
You can find the release notes for v0.3.0 here:
https://github.com/bitcoin-s/bitcoin-s/releases/tag/v0.3.0
-Chris
[-- Attachment #2: Type: text/html, Size: 2707 bytes --]
reply other threads:[~2020-03-22 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFQwNuxo4h3c7h2ODxomgOFzSyANJ-+Aepi_UyqcQMj7a1tqDw@mail.gmail.com \
--to=chris@suredbits$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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