Bitcoin Knots 29.3.knots20260210 released! 🎉
Be sure to verify your download(s)!
bitcoinknots.org?29.3.2026021...
11.02.2026 02:54
👍 1
🔁 0
💬 0
📌 0
Bitcoin Knots 29.3.knots20260210 released! 🎉
Be sure to verify your download(s)!
bitcoinknots.org?29.3.2026021...
Every industry has pioneers and on this day 15 years ago @lukedashjr.bsky.social, one of Bitcoin's earliest developers and mining pioneers, learned about Bitcoin.
May your 2026 be full of wonderful discoveries!
Happy New Year 🎉
If you’re at the Seoul Bitcoin Miniconference, don’t miss @lukedashjr.bsky.social’s DATUM workshop with Promenade
Leaders Hall
Today • Nov. 30 • 16:00
Come learn and say hello! 👋
OCEAN Earns SOC 2 Type 1 Attestation, Validating Commitment to Enterprise-Grade Security and Reliability.
This achievement validates OCEAN's robust internal controls and provides institutional miners and hosting partners with trusted, third-party verification of the pool's operational integrity.
Bitcoin Knots 29.2.knots20251110 released! 🎉
Be sure to verify your download(s)!
bitcoinknots.org?29.2.2025111...
Bitcoin Knots 29.2.knots20251010 released! 🎉
Be sure to verify your download(s)!
bitcoinknots.org?29.2?bluesky
Bitcoin Knots 29.1.knots20250903 released! 🎉
Be sure to verify your download(s)!
bitcoinknots.org?29.1?bluesky
Ask them for BOLT12 support
OCEAN already supports bolt 12
Join the bitcoin++ workshop Livestream at 3pm Central US time (in 2hrs) for my workshop on making a new node policy
www.youtube.com/live/J9bRVIX...
We're proud to announce Tonal Bitcoin (TBC) support for the OCEAN Dashboard, now the default unit. Experience the future of Bitcoin mining today!
Not ready for Tonal yet? Use the unit selector to switch back to BTC or sats.
ocean.xyz/dashboard/tb...
#Bitcoin Knots 28.1.knots20250305 released! 🎉
Be sure to _verify_ your download(s)!
bitcoinknots.org?28.1?bluesky
Here's a real block to celebrate:
Brent & Allie (whoever they are) solo mined block 876020 with a mere 10 Ph/s, using DATUM to share rewards w/ other miners using @bitcoinocean.bsky.social
Unlike fake "solo pools", B&A made this block themselves, w/ their own full node
mempool.space/block/876020
Bitcoin Knots 27.1.knots20240801 released! 🎉
Be sure to _verify_ your download(s)!
bitcoinknots.org/?27.1.knots20240801?bluesky
#Bitcoin
#Bitcoin Knots 27.1.knots20240621 released! 🎉
Be sure to _verify_ your download(s)!
bitcoinknots.org?27.1?bluesky
#Bitcoin Knots 26.1.knots20240513 released! 🎉
Be sure to _verify_ your download(s)!
bitcoinknots.org?26.1.knots20...
#Bitcoin Knots 26.1.knots20240325 released! 🎉
Be sure to _verify_ your download(s)!
bitcoinknots.org?26.1?bluesky
Glory to God in the highest; and on Earth, peace to men of good will.
Merry Christmas✝️
OCEAN is on a path to decentralization & very soon we are going to be in a position where hashers will be able to fully perform the intelligent parts of mining such as deciding which version of node software to run and what filters or other policies to apply to block template construction.
They are free to (and should) run their own nodes - it is good for Bitcoin to have more people running nodes, including miners, and there should be a natural diversity in node policies.
Bitcoin does and always has allowed nodes to set filters based on multiple sets of criteria and Knots v25’s defaults are IMO what is best for Bitcoin at this time. Others may disagree and that is ok.
I have some ideas on how to alleviate the recent issue where some coinjoin transactions were flagged as spam from Knots v25, and I am willing, with the full resources of my team, to work collaboratively on a solution in good faith.
These present an innovative tool for increasing Bitcoin’s privacy and, when constructed properly, coinjoins can easily stay within the OP_RETURN limit (indeed, there is no reason for them to have *any* OP_RETURN data at all).
There are also other good technical reasons which I have chosen to retain the lower default in Bitcoin Knots, and no justification for increasing it.
It is not my intention, nor that of my team at @bitcoinocean.bsky.social, to filter coinjoins.
Core subsequently increasing the default to 80 bytes was an entirely voluntary decision and in no way contradicts the design objective that OP_RETURN creates a provably-prunable output to minimise damage caused by data storage schemes, which have always been discouraged as abusive.
At that time, 40 bytes was the default max datacarriersize limit across all node implementations; this was and still is sufficiently large for tying data to a transaction (32 bytes for a hash and 8 bytes for a unique identifier).
The OP_RETURN discussion is not new and dates back to 2014 when Bitcoin Core 0.9.0 was released with the OP_RETURN policy included which was intended to discourage more egregious forms of spam.
This bug was recently fixed in Bitcoin Knots v25.1. It took longer than usual due to my workflow being severely disrupted at the end of last year (v24 was skipped entirely).
Bitcoin Core is still vulnerable in the upcoming v26 release. I can only hope it will finally get fixed before v27 next year.
PSA: “Inscriptions” are exploiting a vulnerability in #Bitcoin Core to spam the blockchain. Core has, since 2013, allowed users to set a limit on the size of extra data in transactions they relay or mine (datacarriersize). By obfuscating their data as program code, Inscriptions bypass this limit.
