Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Stuck pending transaction - logs indicate cancellation, but it seems successful

Open
#5,123 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 2 days

@acha-bill is already working on this.

Since Jul 1, 2025.

  • #5138 by @acha-bill — closed without merging

Assessment

This issue has not been assessed yet.

Description

seen
Context

Version: 2.6.0-rc7-027599b3a
Full node, mainnet

Summary

The http://localhost:1633/transactions endpoint lists one pending transaction:

{
"transactionHash": "0xb1cf93a719435aa6118e783441a61d4d08282ac7c7b7e46d4f962d86496f8abf",
"to": "0xdbf3ea6f5bee45c02255b2c26a16f300502f68da",
"nonce": 22,
"gasPrice": "1500001548",
"gasLimit": 77728,
"gasTipBoost": 25,
"gasTipCap": "1500000000",
"gasFeeCap": "1500001548",
"data": "0x095ea7b300000000000000000000000045a1502382541cd610cc9068e88727426b6962930000000000000000000000000000000000000000000000000000452432000000",
"created": "2025-06-24T00:03:36+02:00",
"description": "Approve tokens for postage operations",
"value": "0"
}

The Bee logs indicate that this transaction is cancelled:

"time"="2025-06-24 00:04:44.811867" "level"="warning" "logger"="node/transaction" "msg"="pending transaction cancelled" "sender_address"="0x7a093dE3383d22D9CB2AA1e26328478E81a37072" "tx"="0xb1cf93a719435aa6118e783441a61d4d08282ac7c7b7e46d4f962d86496f8abf"

However, on Gnosisscan, the transaction is successful:

https://gnosisscan.io/tx/0xb1cf93a719435aa6118e783441a61d4d08282ac7c7b7e46d4f962d86496f8abf

After restarting the Bee node, the pending transaction is cleared.

Expected behavior
  1. If cancelled, clear transaction
  2. But since this seems to be successful, why the cancellation in logs?
Actual behavior

Please see description.

Steps to reproduce

The tx was possibly created by an attempt to create a postage batch.

Possible solution

N/A

Dominant language
Go
Stars
1.5k
Forks
390
Avg merge
2d 11h
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ethersphere/bee

All issues in ethersphere/bee

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.