You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugSomething isn't workingbyronRequired for a Byron mainnet: replace the old core nodes with cardano-nodeconsensusissues related to ouroboros-consensus
The problem is that the chain DB pretends that there is a block number when the chain is at genesis, but there isn't. It picks genesisBlockNo, which is wrong, because that is the block number of the first block on the chain; in mkCurrentBlockContext we then take the successor of this block number, and so we end up skipping one.
Fixing this is part of #1571 , and I'm therefore marking it as high priority. The fix will be part of the work on #1578 .
The text was updated successfully, but these errors were encountered:
bugSomething isn't workingbyronRequired for a Byron mainnet: replace the old core nodes with cardano-nodeconsensusissues related to ouroboros-consensus
The problem is that the chain DB pretends that there is a block number when the chain is at genesis, but there isn't. It picks
genesisBlockNo
, which is wrong, because that is the block number of the first block on the chain; inmkCurrentBlockContext
we then take the successor of this block number, and so we end up skipping one.Fixing this is part of #1571 , and I'm therefore marking it as high priority. The fix will be part of the work on #1578 .
The text was updated successfully, but these errors were encountered: