Skip to main content
13 votes

Our parachain doesn't produce blocks [checklist]

The following checklist should help avoiding the most common reasons why a parachain won't produce blocks. The most common reasons on top, the more advanced trouble further down Is your parachain ...
brenzi's user avatar
  • 563
8 votes

Substrate nodes stop producing blocks

The node has 0 peers and as such it refrains from authoring to avoid creating unnecessary forks. You can force a node to author while still having no peers with --force-authoring. Obviously you should ...
André's user avatar
  • 2,465
7 votes
Accepted

Recovering from stalled finality (babe/grandpa)

The issue lacks details to know exactly what went wrong in the first place (why did finality stop?). That said here are the steps you should have taken in order to debug the problem. Use the ...
André's user avatar
  • 2,465
7 votes
Accepted

Is it possible to resurrect babe chains?

We do have the data of the current chain state but we are still bound by the rules that are set in the runtime, one of the current rules is that the BABE pallet assumes that there will be at least one ...
André's user avatar
  • 2,465
7 votes
Accepted

How to use noteStalled to recover from a finality lagging chain?

You should pass #57281 as the second parameter to the noteStalled call since that is the last block that was finalized, this means that when the GRANDPA validator set is forcibly changed it will ...
André's user avatar
  • 2,465
5 votes
Accepted

how can I purge all pending extrinsics in the transaction pool

author_removeExtrinsic support remove extrinsic by value You can also either write a script to calculate the hash, or just read it from polkadot apps under Network -> Node info page
Bryan Chen's user avatar
4 votes

Substrate nodes stop producing blocks

If the two nodes are not on the same local network I suggest you to restart the first node and grab its p2p PeerId. It should print it during startup phase: 2022-04-06 14:47:07 🏷 Local node identity ...
Davide Galassi's user avatar
3 votes

Equivocation crash (network with ~100 Aura Validators)

There are multiple public identities reported in the log message that you provided. The node identity Local node identity is: 12D3KooWQbTk1xVSvp8YM3p8uoJrjSa3LKL2UBt11Excd1i11spW that is shown in your ...
Luke Schoen's user avatar
  • 2,346
3 votes
Accepted

How to set secondary slots for Babe?

The secondary slot authors are the same as the primary slot authors, there's no distinct validator set to configure. The reason your chain has stalled with "Unexpected epoch change" is ...
André's user avatar
  • 2,465
2 votes

What does "there are no validators assigned to core" mean?

If you get an error like "there are no validators assigned to core core=CoreIndex(2)", then it could well be that you're running more parachains then there are relay validators available to ...
Squirrel's user avatar
  • 3,899
1 vote

Specific extrinsic stalls the parachain even though the collation is successfully produced

It turns out that an update to polkadot-v0.9.42 of the runtime did solve the issue. It is not clear yet why this resolved the issue. However, this included the change to XCM v3.
clangenb's user avatar
  • 141

Only top scored, non community-wiki answers of a minimum length are eligible