Bitjoe uses Bitkeeper to save business transactions.

1. Bitcoin blockchain is a precious resources and we can only put a hash of the transaction in it.
2. The body of the transaction bitjoe sends to bitkeeper for keeping.

In this incarnation bitkeeper uses Kademlia DHT (distributed hash table) implementation by http://tomp2p.net/ Kademlia is a state of the art DHT used by practically all mainstream p2p programs, like bittorrent.

Bitkeeper provides RESTful service with 2 parameters: key and val if both are specified, value is saved for a key provided, e.g. http://127.0.0.1:8080?key=k1&val=v1

If only the key is specified, then the value is returned to the output stream: e.g. http://127.0.0.1:8080?key=k1

If you want to play with the source code:

1. Clone this repo using: git clone https://github.com/urbien/bitkeeper
2. Copy the conf directory into the build directory
3. Run "java -jar bitkeeper.jar path-to-config.json" from the build directory

If you don't want to play with the source code:

1. Run install.sh
2. Run "java -jar bitkeeper.jar path-to-config.json" from the bitkeeper directory

Then run a second bitkeeper with reverse DHT ports and a different http port, e.g. with this config.json:

    {
      "address" : {
        "host": "127.0.0.1",
        "httpPort": 8009,
        "dhtPort":  7001
      },
      "storageDir": "fileStorage",
      "dhtPeerAddresses" : [
        {
          "dhtHost": "127.0.0.1",
          "dhtPort": 7000
        }
      ]
    }

Now you can send save value on one bitkeeper server and pick it up on another bitkeeper server, e.g.: http://127.0.0.1:8008?key=k1&val=v1

http://127.0.0.1:8009?key=k1

Learn about Bitkeeper architecture in Tradle wiki