Changes to “The node API”

#47 (zoobc.how, 2026-10-26 20:39 UTC) → #847 (zoobc.how, 2026-10-26 22:31 UTC): Seed article updated

…

If a reply is lost, resend the identical signed bytes. The hash is computed from those bytes, so a node that already holds the transaction, even one already included in a block, answers 202 again, marked as a duplicate, and it is executed only once. Signing again with a new timestamp creates a different transaction, which is how double payments happen.

+ ![The status of a posted transaction moves from staging to mempool to confirmed, or to rejected; from version 0.5.8 a confirmed transaction later gets the finalized flag; resending the same bytes gives the same hash and runs once](apps-010.svg)

− ![The status of a posted transaction moves from staging to mempool to confirmed and, from version 0.5.8, finalized, or to rejected; resending the same bytes gives the same hash and runs once](apps-010.svg)

## Signed requests and cancellation

…

History