Update Knots to v29.3.knots20260210 and BIP 110 to v29.3.knots20260210-bip110-v0.3

[Retropex]

Relevant commits:

• Retropex/docker-bitcoind-prebuilt@72691fb
• Retropex/umbrel-bitcoin@01f9444

Relevant commits for BIP 110:

• Retropex/docker-bitcoind-prebuilt@a27dcd9
• Retropex/umbrel-bitcoin@aec1ebb

[Retropex]

Hey @al-lac, would it be possible to merge this soon?
There are important fixes inside.
Thanks!

[al-lac]

Hey @Retropex, I wanted @nmfretz to have a look first to be sure.

Do you also now want to align the version with the UI version instead of the bitcoin version?

[Retropex]

Yes I should have done that from the start.
It even make more sense today with BIP110 being included.

[dathonohm]

This should be updated to v0.3 before merging, if possible: https://github.com/dathonohm/bitcoin/releases/tag/v29.3.knots20260210%2Bbip110-v0.3

[Retropex]

Updated to v0.3

[Retropex]

@al-lac @nmfretz any news? This really needs to be merged.

[nmfretz]

Sorry @Retropex 🙏. Will get on this today!

[nmfretz]

Looks good and working well @Retropex. Before we go live, do you think it's worth mentioning in the release notes that users who currently have selected BIP110 in Settings don't need to do anything after updating the app, since they'll be automatically upgraded to v29.3.knots20260210-bip110-v0.3?

I'm thinking it could be good for two reasons:

1. Users who are currently on BIP110 might be confused on whether or not they need to do something since all 110 users needed to manually select BIP110 in Settings at some point.

2. The way the version feature says it works in the UI is that if a user selects a specific version in Settings then they ... stay on a specific version until you change it manually.. So it might be good to explicitly mention it in the release notes. It totally makes sense to do in this case, I just want to make sure you don't get attacked here 😅

   

[nmfretz]

Ah, taking a look at the Datum PR now as well @Retropex since you could slip in your change before we merge

Edit: responded here

[github-actions]

🎉   Linting finished with no errors or warnings   🎉

Thank you for your submission! This is an automated linter that checks for common issues in pull requests to the Umbrel App Store.

Please review the linting results below and make any necessary changes to your submission.

Linting Results

Severity	File	Description
ℹ️	bitcoin-knots/docker-compose.yml	Mounted file/directory "/bitcoin-knots/torrc" doesn't exist: The volume "${APP_DATA_DIR}/torrc:/etc/tor/torrc:ro" tries to mount the file/directory "/bitcoin-knots/torrc", but it is not present. This can lead to permission errors!
ℹ️	bitcoin-knots/docker-compose.yml	External port mapping "${APP_BITCOIN_KNOTS_P2P_PORT}:${APP_BITCOIN_KNOTS_P2P_PORT}": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	bitcoin-knots/docker-compose.yml	External port mapping "${APP_BITCOIN_KNOTS_RPC_PORT}:${APP_BITCOIN_KNOTS_RPC_PORT}": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	bitcoin-knots/docker-compose.yml	Using unsafe user "root" in service "i2pd_daemon": The user "root" can lead to security vulnerabilities. If possible please use a non-root user instead.

Legend

Symbol	Description
❌	Error: This must be resolved before this PR can be merged.
⚠️	Warning: This is highly encouraged to be resolved, but is not strictly mandatory.
ℹ️	Info: This is just for your information.

[Retropex]

That make sense, I have added it to the release note.

[Retropex]

@nmfretz the datum discutions is resolved, we can merge this PR.

[nmfretz]

Awesome, thanks for your patience @Retropex! Going live.