If you happen to be running an elementsd node, part of the Liquid network and you don’t subscribe to the mailing lists, you may have missed a breaking change that happened on June 1st. If your elementsd version wasn’t greater than 23.3.1 at the time, your node will be stuck at block 3911103 and won’t get any new blocks, even if you do upgrade the binary and restart it.

$ elementsd --version
Elements Core version v23.3.3
Copyright (C) 2009-2026 The Elements Project developers
Copyright (C) 2009-2026 The Bitcoin Core developers

Please contribute if you find Elements Core useful. Visit
<https://elementsproject.org/> for further information about the software.
The source code is available from
<https://github.com/ElementsProject/elements>.

This is experimental software.
Distributed under the MIT software license, see the accompanying file COPYING
or <https://opensource.org/licenses/MIT>

$ elements-cli getblockcount
3911103

Turns out the block will be marked invalid if you were running an old version (like I was) so the solution is to re-evaluate that previous block.

$ elements-cli reconsiderblock 00b06268d2b1bb517e9d2902f8289bfa6b6fe9198700de7e001ac5bc432b5b58

Once you run that it’ll update the latest tip to 3911104 and after a little bit will find other peers with newer blocks and accept them. That block hash is from block 3911104.

$ elements-cli getblockcount
3916508