Chain extended new tip

Hello all,

I’m looking for some assistance with setting up a stake pool.

I have a setup with 1 BP at my house and 1 Relay node in Azure.

The only things that are logged in the BP and Relay nodes are the ones below.
Logs from BP:

Mar 22 14:29:53 block-producer bash[17361]: [block-pr:cardano.node.BlockFetchDecision:Info:44] [2021-03-22 18:29:53.39 UTC] [TraceLabelPeer (ConnectionId {localAddress =, remoteAddress =}) (Right [At (Block {blockPointSlot = SlotNo 24871502, blockPointHash = 26e75e3daa4281bf5c26b0b82d344e59b9357bf438a5956357caa10ac8d40794})]),TraceLabelPeer (ConnectionId {localAddress =, remoteAddress =}) (Left FetchDeclineInFlightThisPeer),TraceLabelPeer (ConnectionId {localAddress =, remoteAddress =}) (Left FetchDeclineChainNotPlausible)]
        Mar 22 14:29:53 block-producer bash[17361]: [block-pr:cardano.node.ChainDB:Notice:34] [2021-03-22 18:29:53.41 UTC] Chain extended, new tip: 26e75e3daa4281bf5c26b0b82d344e59b9357bf438a5956357caa10ac8d40794 at slot 24871502

Logs from Relay:

Mar 22 16:23:33 VM-RelayNode01 bash[1690]: [VM-Relay:cardano.node.ChainDB:Notice:34] [2021-03-22 16:23:33.50 UTC] Chain extended, new tip: 942237bc70f9aee9d6be4992f6d9649d2436341cd1025c35518694dfac6e8031 at slot 24863922
Mar 22 16:24:29 VM-RelayNode01 bash[1690]: [VM-Relay:cardano.node.BlockFetchDecision:Info:44] [2021-03-22 16:24:29.28 UTC] [TraceLabelPeer (ConnectionId {localAddress =, remoteAddress =}) (Right [At (Block {blockPointSlot = SlotNo 24863977, blockPointHash = c1baf8c41e48840d42230a0ddb0da0f12b1ccb84e21bec834f97297f55f6281b})]),TraceLabelPeer (ConnectionId {localAddress =, remoteAddress =}) (Left FetchDeclineChainNotPlausible),TraceLabelPeer (ConnectionId {localAddress =, remoteAddress = redacted:6001}) (Left FetchDeclineChainNotPlausible)]

Even if I change “TraceBlockFetchDecisions” to false we see this all the time:

Mar 22 14:32:59 cardano-relay bash[19967]: [cardano-:cardano.node.ChainDB:Notice:34] [2021-03-22 18:32:59.25 UTC] Chain extended, new tip: 25ea43523b8bdb23b18d69537a484093cf427e689e9e784c54cb28fcc3eaa4ba at slot 24871688
Mar 22 14:34:09 cardano-relay bash[19967]: [cardano-:cardano.node.ChainDB:Notice:34] [2021-03-22 18:34:09.94 UTC] Chain extended, new tip: c0c1dc35b557ed903147ab914d251d63aa73ce3bd4c629ad2458db3fc2524e02 at slot 24871758
Mar 22 14:34:23 cardano-relay bash[19967]: [cardano-:cardano.node.ChainDB:Notice:34] [2021-03-22 18:34:23.99 UTC] Chain extended, new tip: 82a65cb85e9f89d0778799d08603932cf882dd5eafeb04408b3e376de419d23e at slot 24871772

Is this common behavior? I’d like to have some confirmation. I’m using version 1.26.0 of cardano-node/cli.

Thank you.


Great - your node is syncing - and the log tells what is the current slot height
Once it is reaching the current height - - that means the node is in sync
use cardano-cli query tip --mainnet to check the BlockNo and compare it what you see on the explorer

1 Like