Attention: v9.24.2 of counterpartyd fixes a bug in the version checking function, so all users are required to upgrade their counterpartyd to the latest version manually, or they run the risk of running an old, incompatible version without being warned about it.
Also, I just pushed v9.25.0 to develop. This update has a lot of goodies packed into it, including the removal of the issuance fee for all issuances after the first, and the inclusion of the ability to change the amount of BTC sent along with any other asset on a per-tx basis (which feature will soon be integrated into Counterwallet). Also, now orders that compose expired order matches will rematch other orders as appropriate. This should improve the liquidity of the BTC distributed exchange measurably. All of these protocol changes go live with block 310000 on mainnet; they are retroactive on testnet (as usual). We’re going to test these improvements out over the next couple of days, and merge the updates into master soon. Please see the CHANGELOG and the commit log for details.
Even bigger, more dramatic changes are on their way soon: totally new, completely revolutionary functionality for Counterparty and Counterwallet that everyone will be able to benefit from and use. Stay tuned! 
[quote author=PhantomPhreak link=topic=394.msg2659#msg2659 date=1402680633]
This update has a lot of goodies packed into it, including the removal of the issuance fee for all issuances after the first, and the inclusion of the ability to change the amount of BTC sent along with any other asset on a per-tx basis (which feature will soon be integrated into Counterwallet).
[/quote]
This is awesome. I was just thinking the other day that the issuance fees could become a problem (i.e, expensive) for assets where new units will be created frequently.
Can you clarify what you mean on changing amount of BTC sent along with asset on per-tx basis?
[quote author=cryptonaut link=topic=394.msg2696#msg2696 date=1402865664]
Can you clarify what you mean on changing amount of BTC sent along with asset on per-tx basis?
[/quote]
For instance, when you send XCP to another address, you also send a small about of BTC to them. By default, this value is 5430 satoshis, and now it can be set with every create_send or do_send API call.
[quote author=PhantomPhreak link=topic=394.msg2704#msg2704 date=1402918366]
[quote author=cryptonaut link=topic=394.msg2696#msg2696 date=1402865664]
Can you clarify what you mean on changing amount of BTC sent along with asset on per-tx basis?
[/quote]
For instance, when you send XCP to another address, you also send a small about of BTC to them. By default, this value is 5430 satoshis, and now it can be set with every create_send or do_send API call.
[/quote]
Cool. So, when I look at a counterparty transaction (like this one: https://blockchain.info/tx/0f17367bfeb7a2627bd19506208155cf5b47be6dd3a568db66bc7a72e8e1e8c4 ) is that 0.0001086 the amount of BTC that the asset is basically riding on top of? And this is now configurable amount?