Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Transaction broadcast succeeded but was not included on-chain

Aperta
  • Qualcosa non va?
#6,546 12 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

  • #6713 di @xxo1shine — chiusa senza merge

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
java
Ambito
backend, distributed-systems

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

topic:net
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.

Lingua principale
Java
Stelle
4.2k
Fork
1.8k
Merge medio
3g 21h
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tronprotocol/java-tron

Tutte le issue di tronprotocol/java-tron

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.