hm, it'll be interesting to watch for sure.

It won't be a hard fork, but rather a soft fork (new rules are a subset of old rules) with possible chain split, if majority of miners do not follow BIP110. 110nodes will follow a different chain until reorg because they only accept valid blocks according to BIP110 rules, leading to longer txs confirmation and also possible problems with Lightning as Lightning relies on synchronous blocktime between nodes (e.g. justice-tx, cltv, chan confirmation heights).
tl;dr: no new coins for you

wen Linux and Android?
it's about time, guys.

for rarteds like us
https://www.thewordfinder.com/wordle-solver/

Jolla (Sailfish OS), Volla (Volla OS / Ubuntu Touch), Pixel (GrapheneOS)... a lot to consider.

Not true. Opening and closing addresses are not the same.
Example: https://mempool.space/lightning/channel/987720982097362945

Sure.
So here's my small setup running bitcoind, pool_sv2 and translator_sv2.

Starting up translator_sv2 (both self-compiled and binary from github) with given translator-config.toml, I get errors about missing fields: "supported_extensions" and "required_extension". Even if empty, both need to be present in the toml file, they are commented out. pool-config.toml has it right and loads correct.

$ ./translator/translator_sv2 -c config/translator-config.toml

Translator proxy config error: Bad `config` TOML deserialize: `missing field `supported_extensions``

After uncommenting both options, pool_sv2 and translator_sv2 are starting up just fine. 👍

Pretty awesome! It has been a small riddle to find out how everything connects to each other. This makes it a lot easier.

BFCM25

that was remarkably fast actually

https://minibolt.minibolt.info (x86/AMD64)
https://raspibolt.org (ARM)
https://github.com/alexbosworth/run-lnd (AWS)