BitCoin Server Emulator

A basic Sinatra app to emulate the JSON-RPC commands of the open source BitCoin server daemon, for testing purposes. It is in used to speed up tests for BitPiggy.

Why emulate the BitCoin server?

In a word, speed.

BitCoin transactions take on average ~10 minutes to be verified by the BitCoin network, and thats on the live network. On the testnet BitCoin blockchain transactions can take hours to process. Hence trying to run tests on the live or test blockchain could take literally days to get results, not to mention cost money in BitCoin transaction fees.

What if the BitCoin server API changes?

If it does change, we'll have to update this code. Please let me know if this happens!

That said, hopefully change will be slow due to the wide adoptance of the current open source project and hence its current API, with literally millions of dollars on the line.

As said above though, please send me a message (on GitHub) if the interface changes!

Installing and running

Currently this is not a gem, so you'll need to clone this repository to a directory.

git clone git://github.com/matholroyd/bitcoin-server-emulator.git

The app is a Sinatra app, so to run it you will need to install Sinatra:

gem install sinatra

To run, use the following in the directory you cloned this repository to:

ruby -rubygems start.rb (defaults to port 4567)

Or if you prefer to use Shotgun:

gem install shotgun
shotgun start.rb  (defaults to port 9393)

Using

To interact with the running server, you'll need to send POST requests to the bitcoin server emulator's URL. If you run the server via the ruby command, the default URL is http://localhost:4567/[your-app-name], where your-app-name should be the name of your app.

Note for each your-app-name, a separate, persistent database is used. For instance, if you had a rails app called alpaca-socks that uses a bitcoin server to do payments, and you want to check it working in both development and testing, you could use the URLs http://localhost:4567/alpaca-socks-development and http://localhost:4567/alpaca-socks-test. That way, you can play around with your app in development and the state will be remembered, and then if you run tests, your tests will not clobber the development data.

The interface of the emulator is designed to be a direct replica of what the official open source bitcoin server does, hence refer to that to learn what the commands are and what they should be returning.

As a reference, the two pages you are mostly likely interested in are:

• API call list
• [API reference (JSON-RPC)](https://en.bitcoin.it/wiki/API_reference_(JSON-RPC\))

Below is a code snippet from the [API reference page](https://en.bitcoin.it/wiki/API_reference_(JSON-RPC\)) for sending POST requests in Ruby. Note I've changed the ServerProxy.new() example code to reflect the fact you don't need to set a username or password, as well as the default URL you would need to call.

=begin
Make sure to do:
    gem install rest-client

Usage:
    h = ServiceProxy.new('http://localhost:4567/alpaca-socks-development')
    puts h.getbalance.call 'store-balance'
=end
require 'json'
require 'rest_client'

class JSONRPCException < RuntimeError
    def initialize()
        super()
    end
end

class ServiceProxy
    def initialize(service_url, service_name=nil)
        @service_url = service_url
        @service_name = service_name
    end

    def method_missing(name, *args, &block)
        if @service_name != nil
            name = "%s.%s" % [@service_name, name]
        end
        return ServiceProxy.new(@service_url, name)
    end

    def respond_to?(sym)
    end

    def call(*args)
        postdata = {"method" => @service_name, "params" => args, "id" => "jsonrpc"}.to_json
        respdata = RestClient.post @service_url, postdata
        resp = JSON.parse respdata
        if resp["error"] != nil
            raise JSONRPCException.new, resp['error']
        end
        return resp['result']
    end
end

Persistence

If you look inside the wallet.rb file you'll notice a PStore is used. This is used to persist the state of the 'wallet'. Hence if you use this app in development, balance/addresses/etc will be remembered.

Simulate and helper methods

To help with setting up and simulating a running bitcoin server, several methods are provided to:

• simulate certain events, e.g. receiving BitCoins from an outside source
• help setup the server, e.g. account 'savings' has 10 BitCoins.

The methods are:

Simulate methods

simulate_incoming_payment(address, amount)

Helper methods

helper_reset
helper_random_address
helper_random_txid
helper_set_fee(fee)
helper_set_confirmations(confirmations)
helper_set_time(time)
helper_adjust_balance(account_name, amount)

Command reference

Implemented

Note that for the following the [minconf=1] and [comment] options are not implemented.

getaccount <bitcoinaddress>
getbalance [account] [minconf=1]
getaddressesbyaccount <account>
getreceivedbyaccount <account> [minconf=1]
getreceivedbyaddress <bitcoinaddress> [minconf=1]
gettransaction <txid>
listaccounts [minconf=1]

getnewaddress [account]
move <fromaccount> <toaccount> <amount> [minconf=1] [comment]
sendfrom <fromaccount> <tobitcoinaddress> <amount> [minconf=1] [comment] [comment-to]
listtransactions [account] [count=10]

To be implemented

(none for the moment)

Not implemented

backupwallet <destination>

getaccountaddress <account>
getblockcount
getblocknumber
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getwork [data]

help [command]

listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]

sendmany <fromaccount> {address:amount,...} [minconf=1] [comment]
sendtoaddress <bitcoinaddress> <amount> [comment] [comment-to]
setaccount <bitcoinaddress> <account>
setgenerate <generate> [genproclimit]

stop
validateaddress <bitcoinaddress>