Closed EthanYuan closed 1 week ago
CKB requires to propose the transaction short id before committing it into the chain, and there is a window of blocks that the transaction can be committed. Only in this window, the transaction status will be shown as proposed
, otherwise, it will be shown as pending
. The window of mainnet is 2 ~ 10, so it's an expected behavior that the transaction status is pending
for +1 block after proposing it, and it will be shown as pending
again after +10 blocks.
CKB requires to propose the transaction short id before committing it into the chain, and there is a window of blocks that the transaction can be committed. Only in this window, the transaction status will be shown as
proposed
, otherwise, it will be shown aspending
. The window of mainnet is 2 ~ 10, so it's an expected behavior that the transaction status ispending
for +1 block after proposing it, and it will be shown aspending
again after +10 blocks.
Thx. Understood.
Bug Report
dev chain with
IntegrationTest
moduleCurrent Behavior
submit tx with cli
generate block with
generate_block
rpccall
get_block
->"proposals":["0x842973098828ced54bc8"]
get_transaction
->pending
call
generate_block
again can getproposed
Expected Behavior
Expected Behavior: after tx
proposed
block was generated,get_transaction
status isproposed
.get_transaction
->proposed
Environment
Additional context/Screenshots