some tx21 description refinements needed

[marv-engine]

Just capturing that the following changes/clarifications have to be made:

1. liquidity bonus deferred
2. Cancel (Actions=2,3,4) is invalid if no active tx21's affected
   • Also: for tx20, update/cancel are invalid if no active tx20
3. move Action field to immediately after txtype field
   • per Changes to TX21 per issue #270 #276 (comment)
4. for Action=3, the amount fields are not validated
5. for Action=4 (Cancel all), only one field follows - ecosystem
   • no currencies or amounts necessary

Edit: txversion=1 will support this msg layout with the ecosystem field

[marv-engine]

We need to explicitly state when/how a sell order is filled, and no longer a candidate to match a new sell order - e.g. when the full amount for sale has been transferred.

[dexX7]

I think this is a broader issue. Due to the merging I can imagine there is no clear line and unfortunally it looks like as if an order isn't identifiable, because it loses it's id, once merged. At best I can think of a composition or a chain of transactions that points to an order. Because orders can also be partially filled and there might be overlaps, I'm not sure, if this can serve as unique idedntifier.

But if orders were trackable or fully identifiable, it's just a question of keeping track, so to speak, which seems doable.

[marv-engine]

Per @zathras-crypto merging is still open for debate. We need to nail down all the details so coding and testing can be completed.

[dacoinminster]

It would be good to specify that liquidity bonus is not in version 1, but I'm not aware of other open issues which are still being debated at this point.

[marv-engine]

numbers 2, 4, and 5 should be explicitly stated in the spec.

[dexX7]

I agree, noticed this a few minutes ago, too.