I'm pretty sure that that's a bug in blockscan.com. Amounts of indivisible assets (like TEST) should not be divided by 10^8 for display the way that divisible assets are.

EDIT: mtbitcoin, that 'orders' page looks great (I love the colour-coded 'Remarks' column)!

Currently counterparty-explorer.com only shows the XCP obtained by burning. To check the XCP sent by others (e.g. sent by Maxmint), please use blockscan.com instead.

That's the correct way, and there's definitely a bug in counterpartyd.

EDIT: I fixed the bug and pushed to GitHub.

Any thoughts from developers about this potential issue?

The developers already burned at least 4 BTC, if not much more (20-40 is probably around the right ballpark).

I fixed the problem. It was a rounding error. But yes, please do put up more orders!

We are in a position to be able to support bounties at least during that crucial initial 3-6 month period post-burn. Our goal for bounties is that the amount awarded is enough to motivate people to build things around Counterparty, which themselves will quite often generate revenue (or give them benefit in some other way). Publicity and community awareness will also be a big focus as well (and a way in which non-developers can easily get involved). This all being said, bounties won't be nearly as large as with Mastercoin, for instance -- due to their different offering model. However, we believe that the functionality and opportunity that Counterparty already provides as a base framework creates ample opportunity, and bounties will really help kickstart community and possibly corporate developments around it, as well as getting the word out to people and organizations that would find what we have here to be useful.

With the new version, that has those rounding errors fixed, I do see 10 TEST transacted:

(Obviously that last match is funny. I'll fix it.)

On the old version, it's only 1 TEST.

Sorry about that. The assets (like TEST) should not be divided as they are not denominated in "satoshi's style". I have updated the view->order page on blockscan

How is the expiration value calculated and what is this based on? I assume this is countdown from a specific start time? If yes, is the specific start time based on the block time or some other value?

Cheers