When using fetchTransaction to query a transaction sent by ckblightClient, the result will remain in a pending state:
If the transaction is committed on the chain, the status will be changed from pending to commit once the light node synchronizes the transaction.
If the transaction is a rejected transaction, it will remain in pending status.
Scenarios:
when a user replays a transaction on the chain, it will remain in pending status and cannot be changed through fetchTransaction unless the transaction is synchronized again using setScript.
if a user's transaction is rejected by the chain, querying it through a light node will always result in a pending status. The reason for rejection can only be known by querying full ckb, which can lead to users who only use light nodes being unable to determine the reason for a transaction failure.
light client version:CKB Light Client 0.2.1
When using fetchTransaction to query a transaction sent by ckblightClient, the result will remain in a pending state:
pending
tocommit
once the light node synchronizes the transaction.pending
status.Scenarios:
when a user replays a transaction on the chain, it will remain in
pending
status and cannot be changed throughfetchTransaction
unless the transaction is synchronized again usingsetScript
.if a user's transaction is rejected by the chain, querying it through a light node will always result in a
pending
status. The reason for rejection can only be known by queryingfull ckb
, which can lead to users who only use light nodes being unable to determine the reason for a transaction failure.