Also, I would like to throw into your requirements bucket, a profitability page.  It should all kinds of metrics on the bottom line, i.e. share burndown charts, fee charts, etc.  This will make getting referrals much easier.

Again, great job devs!!

I can appreciate the mitigation against increasing blockchain exposure to spam attacks, but, really, this is a bad trade-off when you consider unreturned fee on cancellation as friction against liquidity.  I'm now much less interested in quickly responding to market changes since it costs me to simply change/cancel an existing order to respond to changing market conditions.  I think a better mitigation is to return the fee after a short period of time, say a minute or two, enough so that the malicious spam attack would not be noticeable by the market.

Within OpenLedger you can cancel an order that has NOT yet been transacted, but a fee has already occurred.  I assumed that when I cancelled the order from the orderbook, the transaction fee would be returned.  It does not.  I think you agree, that is wrong or is a bug that needs to be fixed. 

Why does OpenLedger not return the transaction fee when the transaction is cancelled.  This is frankly wrong.  I would expect transaction fees to be returned when there has been NO transaction.  This is almost equivalent to theft.

Is everyone OK with this???