We know that avalanche is very useful for 0-conf
But smart contract solution of BCH ( like WHC ,keoken) cant benefit from avalanche, they must require confirmation. I cant explain it clearly with my poor English. But I know many developer know why.
Here is my thought:
Is it possible to timestamp unconfirmed transaction via avalanche ?
The "timestamp" should be temporary, because it will be useless when the transaction is confirmed.
The form of "timestamp" is not Unix timestamp (like 1549965819) , it could like block height. let's call it temporary block.
The temporary block generates per 10 sec (more or less)
here is how temporary block works:
for example: There is totally 100 tokenX in address A
tx1: A move 100 tokenX to B
tx2: A move 100 tokenX to C
if tx1 is in temporary block height 100 , tx2 is in height 101,then we can know tx1 happens before tx2,so tx1 is valid, tx2 is invalid
if tx1 and tx2 are all in temporary block height 100 ,then they are all invalid.
if tx1 is in temporary block height 101 , tx2 is in height 100, then tx1 is invalid, tx2 is valid
See,this is what smart contract need, the transaction sequence is very important,becau the smart contract are all account system (not utxo)
If above thought can be done , the smart contract can work with the temporary block perfectly and will be extremely competitive.