Changes to “Transactions”
#90 (zoobc.how, 2026-10-26 20:39 UTC) → #861 (zoobc.how, 2026-10-26 22:31 UTC): Seed article updated
…
2. It submits the signed bytes with `POST /api/v1/transactions`. HTTP 202 means the node accepted the transaction into its pool, not that it is in a block. Resending the same bytes is safe: the copy is marked as a duplicate.
3. Nodes pass the transaction on, and a block producer includes it. A block holds at most 2,000 transactions and 524,288 bytes of payload, and at most one transaction from each account (see [[one-per-block-and-batches]]).
+ 4. `GET /api/v1/transactions/<hash>/status` reports its progress: staging, mempool (with its position), confirmed (with the block height), rejected (with the reason) or not_found.
− 4. `GET /api/v1/transactions/<id>/status` reports its progress: staging, mempool (with its position), confirmed (with the block height), rejected (with the reason) or not_found.
A transaction that no block includes within its window expires (see [[expiry-and-timestamps]]).
…