1.2.0-BETA

This release moves most counterblock functionality into plug-in modules.

NOTE: THIS RELEASE REQUIRES COUNTERPARTY 9.51.0

For the list of modules, and their purpose, as well as how you can write you own modules, please see this link.

Upgrading from 1.1.0

Assisted / Federated Node

If on a federated node, the easiest thing is to just update to the newest federatednode_build master, and rerun ./run.py, selecting r to rebuild.

Manually

If you'd like to manually make these changes, you'll need to create a few config files in your counterblock config-dir (e.g. ~xcp/.config/counterblock/). The first is a modules.conf (and possibly modules.testnet.conf) file, which on a Counterwallet system (which enables all available plugin-modules) will look like this:

[LoadModule]
lib/modules/assets = True
lib/modules/counterwallet = True
lib/modules/counterwallet_iofeeds = True
lib/modules/dex = True
lib/modules/transaction_stats = True
lib/modules/betting = True

If you don't need all of these modules enabled, you can set any of the above to False.

If you're running a Counterwallet server, you'll also need to create a counterwallet.conf / counterwallet.testnet.conf file in that same directory. That file will contain the following:

[Default]
support-email=<your support email>

Of course, change <your support email> to whatever email address you use.

Upon making these changes, you should then be able to restart counterblock, and it will load the appropriate plugins.

Reparse Recommended

NOTE: We highly recommend doing a manual re-parse the first time launching counterblock 1.2.0. Do this by specifying the --reparse flag, e.g. sudo su -s /bin/bash -c 'PYTHON_EGG_CACHE=/tmp/counterblock.eggs counterblock --reparse' xcpd for mainnet.