##Introduction
The btcd-cli4j library is a simple Java wrapper around Bitcoin Core's JSON-RPC (via HTTP) interface.
- Latest release: 0.5.1 (.zip; .tar.gz)
- Compatibility: Bitcoin Core v0.10.0/0.10.1/0.10.2/0.10.3 (see here for older versions)
- API coverage: 78 of 80 commands (fully) implemented
- License: Apache License 2.0 (see LICENSE.md)
- Readme updated: 2016-02-17 10:16:43 (UTC)
A list of all bitcoind JSON-RPC API commands currently supported by btcd-cli4j can be found in the Commands enum (see here for more details).
btcd-cli4j follows a layered architecture in that the actions needed to communicate with the Bitcoin network have been separated into multiple levels of abstraction. The central interface used to invoke bitcoind API commands (BtcdClient) is solely concerned with Bitcoin-specific entity mapping & business logic and does not know anything about JSON-RPC or HTTP. Internally, BtcdClientImpl relies on JsonRpcClient for managing cross-application communication and adherence to the JSON-RPC standard. JsonRpcClientImpl, in turn, utilizes the interface provided by SimpleHttpClient to tunnel all JSON-RPC traffic over HTTP. Both the JsonRpcClientImpl and SimpleHttpClientImpl classes rely on external service providers internally (Jackson JSON Processor and Apache HttpComponents Client for the time being) which should be relatively easy to replace, were the need to arise.
By default, all incoming & outgoing decimal values (i.e. amounts, balances, ping times etc) are transformed into BigDecimals with a scale of 8 and rounding mode of RoundingMode.HALF_UP by btcd-cli4j.
##Technologies & dependencies
The btcd-cli4j library has been designed for use with Java 7+, however it should also work fine with slightly older versions of the Java runtime (i.e. Java 6).
Core dependencies:
Other dependencies:
Since the project is currently not hosted on the Maven Central Repository, you should begin by specifying the following custom repository in your pom.xml file:
<repositories>
<repository>
<id>mvn-nemp-ftp</id>
<name>Nemp's Maven Repository</name>
<url>http://mvn.neemre.com/</url>
</repository>
</repositories>
Next, modify your pom.xml to include btcd-cli4j-core as a dependency:
<dependency>
<groupId>com.neemre.btcd-cli4j</groupId>
<artifactId>btcd-cli4j-core</artifactId>
<version>0.5.1</version>
</dependency>
In order to communicate with bitcoind, btcd-cli4j needs to be aware of your node's exact configuration. The easiest way of providing this information is via a node_config.properties file, for example:
node.bitcoind.rpc.protocol = http
node.bitcoind.rpc.host = 127.0.0.1
node.bitcoind.rpc.port = 8332
node.bitcoind.rpc.user = falcon-pc
node.bitcoind.rpc.password = 3F4DN9QGqWrB4DCdfYMXp8xdDYL4HDFzpaS9r76DbNhw
node.bitcoind.http.auth_scheme = Basic
Finally, to begin using the wrapper, create an instance of CloseableHttpClient (the default HTTP provider), load up the properties file created in the previous step and pass the two into a new BtcdClientImpl instance:
PoolingHttpClientConnectionManager cm = new PoolingHttpClientConnectionManager();
CloseableHttpClient httpProvider = HttpClients.custom().setConnectionManager(cm)
.build();
Properties nodeConfig = new Properties();
InputStream is = new BufferedInputStream(new FileInputStream("node_config.properties"));
nodeConfig.load(is);
is.close();
BtcdClient client = new BtcdClientImpl(httpProvider, nodeConfig);
That's it!
MiningInfo miningInfo = client.getMiningInfo();
P.S. To learn more about the default HTTP provider (e.g. performance tuning of CloseableHttpClient instances and/or use of SSL/TLS layering (i.e. HTTPS) (untested!)), see the official HttpComponents Client documentation here and here. Additionally, check out the related code samples: 1 and 2.
##Handling asynchronous events
Bitcoin Core also provides an asynchronous notification API by relying on a set of user-defined shell scripts specified in the bitcoin.conf configuration file (see here for more details). Whenever a particular event is detected on the network, the appropriate shell script gets loaded with data & executed by bitcoind. To take advantage of this feature, add the following lines to your bitcoin.conf file (use any flavor of netcat you're comfortable with, such as ncat or socat):
alertnotify="echo %s | ncat 127.0.0.1 5158"
blocknotify="echo %s | ncat 127.0.0.1 5159"
walletnotify="echo %s | ncat 127.0.0.1 5160"
Next, modify your pom.xml to include btcd-cli4j-daemon as a dependency:
<dependency>
<groupId>com.neemre.btcd-cli4j</groupId>
<artifactId>btcd-cli4j-daemon</artifactId>
<version>0.5.1</version>
</dependency>
To let the daemon know where to listen for notifications, open up your node_config.properties file and specify the ports listed in the shell scripts above, for example:
node.bitcoind.notification.alert.port = 5158
node.bitcoind.notification.block.port = 5159
node.bitcoind.notification.wallet.port = 5160
Finally, instantiate the daemon with a preconfigured BtcdClient instance (see Getting started) like so:
BtcdDaemon daemon = new BtcdDaemonImpl(client);
Alternatively, create a self-contained version of the daemon (i.e. by specifying the affected ports only):
BtcdDaemon daemon = new BtcdDaemonImpl(5158, 5159, 5160);
Great! Now you're ready to add some event listeners:
daemon.addBlockListener(new BlockListener() {
@Override
public void blockDetected(Block block) {
System.out.printf("New block detected! (Event details: '%s')\n", block);
}
});
##Examples
For a short list of usage examples (mostly just sample API calls), see the examples module.
Please note that some of the examples above will only work on the Bitcoin TESTNET3 chain (for obvious reasons).
##Supporting the project
If btcd-cli4j has been useful to you and you feel like contributing, consider posting a bug report or a pull request. Alternatively, a spare beer or pizza would also be much appreciated:
- Bitcoin:
12CfEQ7RAEwpS82jFZg1HgjeH8obbpMeL5 - Litecoin:
LMwTYNgj7Hkugd1x8rjNXBYdYKgNvACjRF - Dogecoin:
D6DUTo8MTxredfHbbQsb7MLqu7zkuFSMnt
If you have any further questions, feel free to visit us at the #bitcoin IRC channel on freenode.