BIP 110 Bitcoin Knots - #4237
Conversation
|
Yes! I want to utilize the BIP110 and whatever else that will keep Bitcoin about money and only money. Satoshi's "'Bitcoin Constitution'" should remain as is and not be infiltrated by BS. I likened this scenario to what's happening in my Country (USA). We've been infiltrated, robbed, killed and seemingly indoctrinated to other things other than what the Original 'Constitution of the United States of America' means. This Bitcoin scene (Core v Knots) for me, runs deep within me. It's a matter of morality and Just. Keep what's right and clean nor wrong and dirty. That's all I gawt to say 'bout thaaawt. |
|
This PR is voluntary suspended because too many people are rushing to run the code while it's still a release candidate and some bugs are still there. |
|
My Umbrel node and every app within is tied to port 9332. What is the
correct port for Bitcoin/ bitcoind?
…On Sat, Jan 3, 2026 at 11:15 AM github-actions[bot] < ***@***.***> wrote:
*github-actions[bot]* left a comment (getumbrel/umbrel-apps#4237)
<#4237 (comment)>
🎉 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.
|
|
The most common port is 8332 on other platforms, but on Umbrel it’s indeed 9332. |
|
Okay, thanks for the reply. I thought for awhile there I was mining for
LiteCoin. Alrighty kewl! I’m goot then. Thanks again 👍
…On Sat, Jan 3, 2026 at 5:36 PM Léo Haf ***@***.***> wrote:
*Retropex* left a comment (getumbrel/umbrel-apps#4237)
<#4237 (comment)>
The most common port is 8332 on other platforms, but on Umbrel it’s indeed
9332.
—
Reply to this email directly, view it on GitHub
<#4237 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZZQYDKUKY4FUK57T5KSDRT4FBOCTAVCNFSM6AAAAACOYRIRXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBXGQ4DIMBYHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@nmfretz @al-lac This is ready to go! Relevent commits: Retropex/docker-bitcoind-prebuilt@798f808 |
|
Just pushed a quick regex update: |
|
Looking forward to giving it a go |
|
Time to merge this please. Bitcoin is money. |
|
Also waiting for this. Time to tell spammers they can go play on Ethereum. |
|
Go 110, go! |
|
Really sorry for the delay @Retropex! I've been completely distracted by other work. Testing now 🫡 |
|
@Retropex can you pls check that you're able to peer okay with the BIP 110 bitcoind? I'm having issues at the moment and wondering if it's just me. |
|
the switching implementation and curl for DATUM etc is all perfect 👌 |
|
The current behavior is that BIP110 only outbound peer with other BIP110 nodes (it will be changed in RC3 to allow up to two non BIP110 outbound peer) Have you You can test that your resolver can correctly fetch my seed with: |
|
Got tired of waiting on official store to merge, just replaced the docker-compose.yml and umbrel-app.yml from PR source and we're up and running fine with no issues, peering just fine with other bip110 nodes and my other nodes. Disclaimer: I do not recommend doing this unless you know what you are doing and accept all risks of doing so. 
|
|
RC3 is out. Please merge. I want to signal ASAP 💪🏼 |
|
Drafting again by the time I add RC3 |
🎉 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
Legend
|
|
Pushed RC3. Relevent commits: Retropex/umbrel-bitcoin@709f134 @nmfretz RC3 add non BIP110 peering up to two peers, you should no longer have peering issues if your |
|
Yes. Please. 🔥 |
|
I have tested the Bitcoin Knots app on my Raspberry Pi with BIP 110 selected and it seems to work fine 🚀 |
|
Hey @nmfretz @lukechilds @al-lac, I’m getting a lot of requests for this update, would it be possible to merge soon? |
|
I can’t wait for the change to be available. Go Bitcoin! go @nmfretz @lukechilds @al-lac🚀 |
|
Hey @Retropex, thanks a lot for providing this update and your patience. We wanted to test it properly before providing it to all users. As @sharknoon, @nmfretz and myself have now tested it successfully, we can finally go live! 🎉 |
|
Amazing, thanks! |
|
Signaling NOW! |
|
Me too. I think it would be nice if the update message in the Umbrel App Store would indicate explicitly that simply upgrading in itself won't signal BIP110 and that the user needs to change a setting for it to start doing so. |
I agree. I have the "Always use the latest version" selected, but the BIP110 wasn't selected in spite of being newer. I think the sort isn't working well with this special version. So I had to select it manually. |
That's expected, not all users want BIP110. A softfork should be opt-in and not opt-out. |
You're right. |
I agree, a soft fork should be opt-in. However, since most upgrades automatically activate new functionality, there is now going to be a group of people that won't realize they need to do more than just upgrade. I think there now will be many users that will skim over that simple message and think that by installing this release they have activated BIP110. I know I wasn't sure when I upgraded. Honestly, I believe it would be even better if there was a pop-up question when you open Bitcoin Knots, but I don't see anything negative about explaining it a bit more in the upgrade dialog on the App Store. |
12 participants
No description provided.