Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New mined blocks in miner mode are not delivered to the block consumer component. #13862

Open
eastorski opened this issue Feb 18, 2025 · 0 comments
Assignees

Comments

@eastorski
Copy link
Member

We have the main cycle of the block consumer component inside the sync.Run() function, and we expect all new blocks (including blocks produced by the local miner component) to be available through the P2P sentry subscription.

Here is the event where we expect the block to be received:

   case EventTypeNewBlock:
      if err = s.applyNewBlockOnTip(ctx, event.AsNewBlock(), ccBuilder); err != nil {
         return err
      }

However, for some reason, this event never occurs, even when we successfully produce a new block:

INFO[02-18|16:26:22.879] [1/4 MiningCreateBlock] Start mine       block=1 baseFee=937500000 gasLimit=10009764  
INFO[02-18|16:26:22.880] [2/4 MiningBorHeimdall] Processing spans... from=0 to=0  
INFO[02-18|16:26:22.882] [2/4 MiningBorHeimdall] Finished processing progress=1 lastSpanID=0 lastStateSyncEventID=0 stateSyncEventTotalRecords=0 stateSyncEventFetchTime=0s  
INFO[02-18|16:26:22.884] Filtration                               initial=0 no sender=0 no account=0 nonce too low=0 nonceTooHigh=0 sender not EOA=0 fee too low=0 overflow=0 balance too low=0 bad chain id=0 filtered=0  
INFO[02-18|16:26:22.897] [3/4 MiningExecution] Done Commit every block blk=1 blks=2 blk/s=164.9 txs=4 tx/s=329 gas/s=0 buf=104.7KB/512.0MB stepsInDB=0.00 step=0.0 inMem=true alloc=32.5MB sys=86.1MB  
INFO[02-18|16:26:22.897] FinalizeBlockExecution                   block=1 txn=0 gas=0 receipt=0 payload=0  
INFO[02-18|16:26:22.904] [bor] Waiting for slot to sign and propagate number=1 hash=0x10190d2c0 delay=-904.137ms TxCount=0 Signer=0xA563d7B2e11164e1C708bD17bA4D11252503517a  
INFO[02-18|16:26:22.904] [bor] Sealed in-turn   

As a result, the mining process keeps producing the same block repeatedly because it was not added to the state of known blocks.

@eastorski eastorski self-assigned this Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant