The alternative is a centralized system
The template has to be at least subtly different for every hash (which a mining chip does billions of every second)
Core+Antispam also shouldn't have the whirlpool issue FWIW
Why?
That's not a possible conclusion, so either you can't or haven't or are simply lying
Learn to read. Or code. Or whatever it is impacting your ability to understand that this IS a vulnerability.
If you can make software do something that the developers didn't intend for it to do, I'd call that exploiting a bug. But why is this classified as a security vulnerability? nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:note1ahdy5z49l6mkm6tu7nca7n2xgkdwrde4fz0vuwzdjxgr5asgghaqklhmmf
It's being actively exploited as a denial of service attack on the Bitcoin blockchain, significantly impacting availability and long-term usability.
The CVE is for the vulnerability enabling Inscriptions to bypass node policy (regardless of what it's set to).
There should be no reason to be angry. It's just the normal procedure for security issues
It only takes one miner to include your transaction
With centralization, you have to convince one of a mere 11 pools
The standard datacarriersize Knots has always used is 42 bytes. They knew that and ignored it. We haven't changed anything in this regard.
Brc20 comes in at 45 bytes, so just increasing it isn't a viable solution. That doesn't mean we're giving up - we do want to mine these - but it's going to take some work if Samourai doesn't fix the issue on their end (ultimately there's no good reason for ANY of this data)
Yes, it can use the same data directory as Core so long as both aren't running at the same time
Per nostr:npub1x458tl7h9xcxa66vr4a8pg0h2qz96pnhwnfpcra0le9090uk5t5qw7armt : Core… has had 80 byte OP_RETURN for nearly a decade now. 85%+ miners have been set to 80 bytes for the same amount of time. Read the commit log. Read the bitcoin-dev mailing list.
That's called centralization, and is exactly what OCEAN exists to combat
More pools isn't enough. Each and every miner needs to be deciding for himself.
Until OCEAN, miners had no choices. Now they have one more. Soon, we'll release the flood gates so they have infinite possibilities
With the bug, whatever you set it to is IGNORED for Inscriptions. So if you set it to 0, it won't do anything. If you set it to 40 or 80, still won't work.
That's my point. It's a bug. Fixing the bug just puts you back in control of your own node
