core goes down
Core: Let's fix mining centralization by making spam easier.
the brain gymnastics you need to come that conclusion.
just run DATUM.
see how clueless core is:
damn core nodes went down
they are seeing 17k now
knots already detects parasite protocols like inscriptions
im gonna be honest core count has been going down hardly.
but also im running a node with knots at the same time.
and my irl friends as well, we all running knots now.
everyone irl i orange pilled before running knots
i was thinking about it.
i wouldn't even accept 1,000 bitcoin to corrupt it's codebase.
i wouldn't even accept 1 trillion usd.
i would say fuck you.
Nothing technical stopped inscriptions pre-Taproot except the script size filter. So blaming Taproot is kind of a misdiagnosis, the policy(filter) change(dropping the limit) is the true enabling factor.
In short:
Taproot didn’t create inscriptions. Lack of a script-size filter did.
Once we decentralize mining, nodes can have a feature to slow down the propagation of the bad blocks on purpose.
It would give nodes more power to decide what goes on to the blockchain by allowing bad blocks to become stale.
And it's not a consensus change that would cause a chain split. It's just you are weighting TXs that doesn't fit into your policy more in terms of bandwidth, so slowing down its propagation. nostr:nevent1qqsrq625dk7lckj7lgjtjkusymu5sa6ntujte040xjkaznj5a47t8nqlqxlw4
To answer my stand on soft/hard forking bitcoin against spam:
The way people store data changes, that's why fighting against blob data spam on the policy(filter) level matters. So you can make changes without breaking consensus and without doing constant soft forks.
Policy is as strong as Consensus if the mining is not centralized.
So another focus is decentralizing mining and DATUM is the thing for it.
People forget Nostr and Blossom exists as hard to censor message relays and blob data storage. Hard to censor technically, Uncensorable practically.
Bitcoin is money, keep it that way, and fight the good fight to keep it that way.
Why knot just limit the Tabscript size like it was with SegWit v0?
Oh wait Luke already opened a PR for it and core rejected it.
There was NOTHING stopping inscriptions from existing pre-Taproot at SegWit v0 except the script size limit policy (filter).
The only reason inscriptions use Tapscript is because there is no size limit filter. nostr:nevent1qqsq4m8es9z2ylyy4et9ys2qysv79zumsjy9maqhcv9wyqvrkjkltsgtsgxcf
btw DATUM Gateway is still at version 0.4.0beta
so i believe they will publish DATUM Prime's code (the pool side), when they are fully finish it.
i think they don't wanna hurt Ocean if there are any exploits in the code.
but again, some documentation on how to communicate with a DATUM Gateway would be cool, so we can implement our own pools easier, even if its beta.
core is the midwit
the whole idea block propagation speed being slow makes mining more centralized makes no sense. its based on the idea that there is already a centralization... so dumb.
just mine with DATUM, solved
decentralization > democracy
democracy is eventually centralized. in a democracy answer is either yes or no. its collective becoming one big entity.
decentralized let's yes and no to live in parallel at the same time. if they disagree they might even split, and one might die while other one is living.
so instead of predicting the future, it lets two futures live together and the bad option dies. infinity better than predicting.
blossom is great for blob data, if you not using it on nostr you should, many clients support it. actually you are probably using it without knowing.
filters them as well.
shows only the ones that are not spam and only consolidations.
the repo:
sleeping now, promise nostr:note1kaa5gmgjda2pwt38cpz22hufxylzuzxjaqyv5qal0j97376yqyushsq49x
i have never think of this before.
so Ocean is more profitable for the miners, both because the way they distribute the rewards, but also because these miners protecting bitcoin from parasites. so on the long run they are basically protecting their and all of humankind's future (aka bitcoin).
so these miners use DATUM which is recommended to be used with Knots.
so as Ocean gets more miners. Knots node count will also go up as well.
nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr When will Ocean open source the DATUM Prime. do we have to reverse engineer it? or there is something like a documentation on how it communicates with the DATUM Gateway? nostr:nevent1qqs9mjqcdsuy9xcul2gtn3dsdtj0p3a8qdz5usn9mz7yvk58mwachecmnvjsk
you dont like bitcoin. you like the thing in your mind that you named "bitcoin".
bitcoin doesnt make it possible, current changes of core does.
i explained things in my long post you probably read and still replied with this. so i dont think you are answering based on anything i said atm. and im not gonna repeat myself.
for other plebs here: nostr:nevent1qqspkljq077pacvj5h2pq9yq8rzq247edcu6ctgfy4urkhjmz8n25rc9lqpru
the wording is hilarious. "censorship" of parasite protocols, abusing the bitcoin monetary network instead of having their own network.
is that your definition of censorship? things weren't even possible if core didn't changed the constant script size policy for the tapscript.
I see way too many people on Nostr that are still confused about the Core vs Knots debate. This is a tl;dr for them. If a longer explanation is needed, they should go over the website below.
tl;dr:
SegWit introduced the witness discount, that ended up making junk data up to 75% cheaper, which opened the door for arbitrary data-carrying transactions to directly compete with monetary transactions for blockspace. In practice, that ended up being an unintended de facto subsidy for spam.
Taproot then provided a way for inscriptions to sidestep the old datacarriersize filter, which is why the UTXO set exploded from around 4 GB in 2023 to nearly 12 GB by 2025, putting real strain on low-end node hardware.
Meanwhile, the Core devs’ reaction has been pathetic — hand-waving it away for two whole years as “free market dynamics” or saying that fixing the exploit is considered “controversial”. At the same time they did a stealth documentation change to pretend the broken filter is “working as intended”. nostr:npub100mahqlhxg50thmt5dyynu40nl25hat9kkkknzk8pqjfkvgq0xsqtdfyy5 caught them red handed, but instead of apologising for hiding it, they claimed that changing the documentation is a valid way for fixing bugs.
Now they’re doubling down their efforts “to fight spam” they willingly allowed by gutting another spam filter (OP_RETURN) that has worked for 11 years, and helped keep 99.9% of all OP_RETURNs at or under 80 bytes. Larger payloads were possible, but never at the absurd size of 100 KB in a single output.
Core v30, due in early October, will raise the default limit to 100 KB (an 1200x increase), which makes it trivial to upload entire malware files or worse straight into the chain. This isn’t hypothetical — when BSV made the same change in 2019, it was immediately hit with child p[]rn.
The legal and practical fallout for Bitcoin node operators, especially those on cloud infrastructure, hasn’t even begun to be fully grasped.
All these absurd and rushed decisions raise the obvious questions: why push this change through despite massive pushback; who stands to profit from it; and why are the real risks of this happening being ignored or swept under the rug?
just to add some details: tapscript size being unlimited caused the inscriptions, which is in the witness data. before taproot, with segwit v0 there was a P2WSH script size limit, which limits the size of witness while spending a P2WSH output.
this whole file is about policy settings, aka filters. these settings are policy so we don't have to fork the chain each time we wanna change these.
if you are asking what does this have to do with P2WSH, witness data is in the input side of the tx. so meaning of witness data is decided by scriptPubKey of the output we are spending.
of course inscriptions were possible before taproot, but only really small images. or you had to split it into multiple inputs. which increases the total size and fee you have to pay.
tapscript(which is basically witness space in taproot) being unlimited made it attractive as blob data storage.
we can limit the tapscript size, or we can detect inscriptions specifically and other similar methods and filter them specifically, because they are using the script space as data storage, which is unintended use. parasite.
knots does similar stuff.
that's the TRUTH
bitcoin is a monetary network.
it can't scale being everything.
and if you scale it, it cant stay decentralized.
bitcoin doesn't run on the sky.
it runs on people's laptops.
you can't make it do everything.
these are parasite protocols trying to use the existing bitcoin network for their garbage.
they do it on purpose, this much cant be just a "bad decision".
its too deliberate step by step for years.
i have few ideas where the root of these ideas are coming from:
- they simply hate bitcoin and wanna destroy it.
- evm is hell of a drug.
- they some how wanna copy evm and allow rollups. which btw is a dumb "scaling" solution which uses another blockchain.
but yeah nobody supporting core cares about bitcoin being a decentralized money. unless they are just sheep.
heck they dont care about its being decentralized. which asks the question what the hell are they doing with bitcoin, just use solana or something. but i think deep down they know that its shit. and they know bitcoin has more rep. and they fail to realize bitcoin has the rep because bitcoin is bitcoin.
but again many of the core devs behind this idea friends with devs of scam bitcoin forks like bsv, bch, etc.
so i dont know what exactly is happening. but its clearly not something good.