Skip to content

kocmo/bitcoin-testnet-box

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

68 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

bitcoin-testnet-box

docker pulls

Create your own private bitcoin testnet

You must have bitcoind and bitcoin-cli installed on your system and in the path unless running this within a Docker container (see below).

Large Git History

If you'd like to clone this git repository locally and disk space or bandwidth usage is of concern, it's suggested to do a shallow clone, excluding some earlier history of the repo, where some testnet data was included.

Regular clone: du -sh . 44M

Shallow clone: du -sh . 168K

Regular Clone

git clone git@github.com:freewil/bitcoin-testnet-box.git

Shallow Clone

git clone --shallow-since 2014-10-18 git@github.com:freewil/bitcoin-testnet-box.git

Starting the testnet-box

This will start up three nodes using their respective datadirs 1, 2, and 3. They will only connect to each other in order to remain an isolated private testnet. Three nodes are provided, as one is used to generate blocks and its balance will be increased as this occurs (imitating a miner). You may want 2nd and 3rd nodes where this behavior is not observed.

Node 1 will listen on port 19000, allowing nodes 2 and 3 to connect to it.

Node 1 will listen on port 19001, node 2 will listen on port 19011, and node 3 will listen on port 19021 for the JSON-RPC server.

$ make start

Check the status of the nodes

$ make getinfo
bitcoin-cli -datadir=1  -getinfo
{
  "version": 160200,
  "protocolversion": 70015,
  "walletversion": 159900,
  "balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 2,
  "proxy": "",
  "difficulty": 4.656542373906925e-10,
  "testnet": false,
  "keypoololdest": 1533354599,
  "keypoolsize": 1000,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "warnings": ""
}
bitcoin-cli -datadir=2  -getinfo
{
  "version": 160200,
  "protocolversion": 70015,
  "walletversion": 159900,
  "balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 4.656542373906925e-10,
  "testnet": false,
  "keypoololdest": 1533354599,
  "keypoolsize": 1000,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "warnings": ""
}
bitcoin-cli -datadir=3  -getinfo
{
  "version": 160200,
  "protocolversion": 70015,
  "walletversion": 159900,
  "balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 4.656542373906925e-10,
  "testnet": false,
  "keypoololdest": 1533354599,
  "keypoolsize": 1000,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "warnings": ""
}

Generating blocks

Normally on the live, real, bitcoin network, blocks are generated, on average, every 10 minutes. Since this testnet-in-box uses Bitcoin Core's (bitcoind) regtest mode, we are able to generate a block on a private network instantly using a simple command.

To generate a block:

$ make generate

To generate more than 1 block:

$ make generate BLOCKS=10

Need to generate at least 100 blocks before there will be a balance in the first wallet

$ make generate BLOCKS=200

Verify that there is a balance on the first wallet

$ make getinfo

Generate a wallet address for the second wallet

$ make address2

Sending bitcoins

To send bitcoins that you've generated to the second wallet: (be sure to change the ADDRESS value below to wallet address generated in the prior command)

$ make sendfrom1 ADDRESS=mxwPtt399zVrR62ebkTWL4zbnV1ASdZBQr AMOUNT=10

Does the balance show up?

Run the getinfo command again. Does the balance show up? Why not?

$ make getinfo

Generate another block

$ make generate

Stopping the testnet-box

$ make stop

To clean up any files created while running the testnet and restore to the original state:

$ make clean

Using with docker

This testnet-box can be used with Docker to run it in an isolated container.

Building docker image

Build it yourself from this directory

  • docker build -t bitcoin-testnet-box .

Running docker container

The docker image will run three bitcoin nodes in the background and is meant to be attached to allow you to type in commands. The image also exposes the three JSON-RPC ports from the nodes if you want to be able to access them from outside the container.

$ docker run -t -i -p 19001:19001 -p 19011:19011 -p 19021:19021 bitcoin-testnet-box

About

Create your own private bitcoin testnet

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Makefile 39.7%
  • Dockerfile 39.6%
  • Shell 20.7%