Current implementation treats seqno=0 message as a special one and specifies a maximum timeout (effectively, infinite). This might be unsafe and there is no clear reason why this should be done.
I suggest we remove this special case. There is no such treatment in ton-core.
Current implementation treats
seqno=0message as a special one and specifies a maximum timeout (effectively, infinite). This might be unsafe and there is no clear reason why this should be done.I suggest we remove this special case. There is no such treatment in ton-core.