September 19, 2015

It’s time for another community update to bring you up to speed with recent developments in the Counterparty project.

Development Updates

This week we pushed an update to the counterparty-lib develop branch that addresses performance and unresponsiveness issues with the large mempool sizes. Thus far, all queries that involved search_raw_transactions() were causing issues, as they fetched and reparsed the entire mempool every single time (fetching the raw transaction data from bitcoind for all txes in the mempool, as well as all input txes of those mempool txes). With this update, unconfirmed_transactions() pulls from the filtered mempool cache established in blocks.py (i.e. only pulling from actual CP transaction hashes). This seems to remove the bottleneck with the only downside being a slight delay with unconfirmed_transactions() if a new Counterparty tx is broadcast (up to 1 second). Counterparty-server CPU utilization seems to be reduced as well.

If you are having issues with counterparty-server, please give this update a try. However, note ​the update is experimental​, so be careful on anything production-level. Also, note that if you apply this newest update in develop, you should use the develop version of counterparty-cli: https://github.com/CounterpartyXCP/counterparty-cli/tree/develop)

From the Community

Once again, our forums and community channels have been filled with interesting news and discussions. Our picks for this week are:

What’s your favorite Counterparty project? And why?

What happened to betting?

List of all Counterparty Assets

XCP Weekly Update #16 – Joel and Thomas from SWARM

That concludes our update for this week. If you have any questions you can contact us via our gitter, forum or github.

Don’t forget to follow us on social media and subscribe to our newsletter to receive weekly updates via email.