Transaction broadcast succeeded but was not included on-chain
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #6713 by @xxo1shine — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- java
- Domain
- backend, distributed-systems
Research direction
Start by reproducing the private-network setup with one SR node and two Fullnodes while both Fullnodes are catching up, then review the network logs around transaction broadcast and block production. Done means identifying why the successfully broadcast transaction is not selected for a block during synchronization and confirming normal inclusion after the cause is addressed.
Written by the indexing model from the issue text.
Description
Software Versions
OS : Linux
JVM : Oracle Corporation 1.8.0_161 amd64
Version : 4.8.0
Expected behaviour
After a transaction is broadcast successfully, it should be packaged into a block and included on-chain normally.
Actual behaviour
An abnormal behavior was observed in a private network: transactions that were broadcast successfully were not included on-chain.
- The private network consists of 1 SR node and 2 Fullnodes, all connected to each other.
- The two Fullnodes were started at the same time and immediately began synchronizing blocks from the SR (both were in the block-catching-up state).
- During the catch-up process, a transaction was broadcast to one of the Fullnodes:
- The Fullnode returned a transaction broadcast success response.
- However, the transaction never included on-chain, and it did not appear in any subsequent blocks.
- Based on network logs alone, the transaction seemed to be received and propagated by the nodes during the catch-up period, but it was not selected by the SR for block production.
Once block syncing completed, the issue disappeared and the system returned to normal behaviour.
Frequency
This issue had not occurred previously. It was discovered during a recent private network deployment and testing.
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 1.8k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 51
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tronprotocol/java-tron
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
tronprotocol/java-tron#7044 · 4 comments ·
Maintainers usually reply within 1 day
-
[Feature] Remove unused discovery message definitionsPossibly taken A pull request linked to this issue is open or already merged. Opentype:feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tronprotocol/java-tron#7013 · 3 comments ·
Maintainers usually reply within 1 day
-
[Feature] Validate ECKey inputs and improve key handlingPossibly taken A pull request linked to this issue is open or already merged. Opentype:feature
Difficulty 4/5 3-5 days Newbie friendliness 40/100
tronprotocol/java-tron#6994 · 5 comments ·
Maintainers usually reply within 1 day
-
type:feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/java-tron#6989 · 7 comments ·
Maintainers usually reply within 1 day
-
[Feature] decouple json-rpc filter processing from ManagerPossibly taken A pull request linked to this issue is open or already merged. Opentype:feature
Difficulty 5/5 Over a week Newbie friendliness 48/100
tronprotocol/java-tron#6963 · 8 comments ·
Maintainers usually reply within 1 day
All issues in tronprotocol/java-tron
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
citrusframework/citrus#2044 ·
Maintainers usually reply within 1 day
-
[bug]打火石不能被放在厨具架上Open
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
KaleidoscopeMods/KaleidoscopeCookery#237 · 1 comment ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
molgenis/molgenis-emx2#7059 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
quarkiverse/quarkus-flow#1169 ·
Maintainers usually reply within 1 day