BTNS and Counterparty parsing blocks in lockstep

[jdogresorg]

BTNS is meant to run on top of Counterparty, and by default does not need to be counterparty-aware. However, there is a bunch of fun functionality that can be played with by making BTNS counterparty-aware (perform BTNS actions using CP transactions, balances, holders, etc).

Making BTNS CP-aware is pretty straightforward, but need to be VERY careful that Counterparty and BTNS parse blocks in lockstep (ie. CP parses block X, then BTNS parses block X).

Things could go off the rails pretty quickly if BTNS is trying to get holder/balance data for block X, while CP is on some future block Y... ie, incorrectly paying out a BTNS DIVIDEND to CP ASSET holders, etc.

• counterparty2mysql.php --single --block=X
• indexer.php --single --block=X