Intro and Getting Started
Philosophy
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.
If you are a professional working a cryptocurrency business and have feedback on how to make your lives easier, please reach out on slack, gitter or twitter!
If you want to setup Bitcoin-S locally
Then go to this document.
REPL
You can try out Bitcoin-S in a REPL in a matter of seconds. Run the provided "try bitcoin-s" script, which has no dependencies other than an installed Java 8. The script downloads and installs Coursier and uses it to fetch the Ammonite REPL and the latest version of Bitcoin-S. It then drops you into immediately into a REPL session.
$ curl -s https://raw.githubusercontent.com/bitcoin-s/bitcoin-s/master/try-bitcoin-s.sh | bash
Loading...
Welcome the Bitcoin-S REPL, powered by Ammonite
Check out our documentation and examples at
https://bitcoin-s.org/docs/getting-started
@ val priv = ECPrivateKey()
@ val pub = priv.publicKey
@ val spk = P2WPKHWitnessSPKV0(pub)
@ val address = Bech32Address(spk, MainNet)
@ address.value # Tada! You've just made a Bech32 address
res4: String = "bc1q7ynsz7tamtnvlmts4snrl7e98jc9d8gqwsjsr5"
Getting prebuilt JARs
If you want to add Bitcoin-S to your project, follow the instructions for your build tool
sbt
Add this to your build.sbt:
libraryDependencies +="org.bitcoin-s" % "bitcoin-s-secp256k1jni" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-core" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-chain" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-bitcoind-rpc" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-eclair-rpc" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-key-manager" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-node" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-wallet" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-testkit" % "0.4.0"
libraryDependencies += "org.bitcoin-s" %% "bitcoin-s-zmq" % "0.4.0"
Nightly builds
You can also run on the bleeding edge of Bitcoin-S, by
adding a snapshot build to your build.sbt. The most
recent snapshot published is 0.5.0+10-6d898074-SNAPSHOT.
To fetch snapshots, you will need to add the correct
resolver in your build.sbt:
resolvers += Resolver.sonatypeRepo("snapshots")
The official maven repo for releases is
https://repo1.maven.org/maven2/org/bitcoin-s/
The repo for snapshots, which are published after everytime something is merged to master:
https://oss.sonatype.org/content/repositories/snapshots/org/bitcoin-s/
Mill
TODO
Building JARs yourself
If you want to build Bitcoin-S JARs yourself, you need to use the
sbt build tool. Once you have sbt
installed, run sbt publishLocal. This places the required JAR
files in your .ivy2/local folder. On Linux, this is located at
$HOME/.ivy2/local/ by default.