I assume the devs will push a hotfix soon, although it does worry me a little bit that activity on the counterpartyd repo (including the dev branch) seems to have tailed off -- and right when I was starting work on a GUI!. Hope the large influx of capital hasn't diluted their shares to the point where they're losing interest. This is a extremely promising project.
I haven't had good Internet access is all! And if there're are any particular changes to counterpartyd that you'd like to see happen in the near future, let us know.
Excellent, glad you're here.
I really like the zmq API in the dev branch. ZeroMQ is a brilliant piece of engineering that makes true parallelism in Python a snap. Is that going to be integrated into production? If so, I'll use its pubsub for the GUI I'm building to get updates instead of polling the JSON-RPC API.
Also, are you drawing the line at 1 confirmation? i.e, do you not want to show any 0 confirmation transactions? If not, an easy and effective way in Python to signal whenever a new tx hits the network is to use one of the many implementation of ArtForz's old Python half-node, which is effectively a Bitcoin node (as you probably know). In fact, Jeff Garzik has made this into a full Bitcoin node in PyNode.
Anyway, the asyncore imple is probably best for this project since it wouldn't introduce any external dependencies and can be used with any Python3 (asyncio/tulip is very cool but only 3.3+). But this way, you can get notification of new 0 confirmation transactions without polling bitcoind listsinceblock, which is inefficient and cumbersome since you have to keep up with the tx's you've already processed.
This way, there's no 10 minute delay before a new tx shows up (of course, you'd need to indicate it's a 0 confirmation tx). But I can understand if you've decided to only officially display 1 confirmation transactions.
