Current both spotTrade and some other Tx like deposit / transfer all have used the AMOUNT signal:
In deposit / transfer this signal is used to express the amount of depositing / transferred;
In spotTrade this signal is used to express the amount of transferring from order 1 to order2;
This sharing of signal would cause issues when we have induced data availability because we need to send an number which has been encoded into 40bit to AMOUNT signal so it can be encoded into part of on-chain data.
However, the amount that order1 sending to order2 inside spotTrade tx may not always be able to being expressed with a 40bit encoded number. consider following case (suppose the prec. of token is 6):
An order has put to sell with 40000.000000
It has be spotted with an order which buy 99.999999, now the unfilled amount become 39900.000001
It has be filled with another order, so in this spotTrade Tx, the amount would be 39900.000001, which has be exceed the 35bit significand
To resolve such issue we should include another signal (maybe just name it 'AMOUNT1') for recording the transfer amounts in a spotTrade Tx. The number inside this signal should NOT be encoded into 40bit float number.
Current both spotTrade and some other Tx like deposit / transfer all have used the AMOUNT signal:
This sharing of signal would cause issues when we have induced data availability because we need to send an number which has been encoded into 40bit to AMOUNT signal so it can be encoded into part of on-chain data.
However, the amount that order1 sending to order2 inside spotTrade tx may not always be able to being expressed with a 40bit encoded number. consider following case (suppose the prec. of token is 6):
To resolve such issue we should include another signal (maybe just name it 'AMOUNT1') for recording the transfer amounts in a spotTrade Tx. The number inside this signal should NOT be encoded into 40bit float number.