Someone's lying to you
Core changed theirs to 80, but 40 is what the standard was.
If they don't want to comply, that's fine, but blaming me for their decision not to is dishonest.
It's a bug if they expected it to work under the 40 byte spec.
If they knowingly exceeded it... Then what are they complaining for? That's on them
Nothing was false advertised
No, this is a bug in Samourai's implementation.
Other conjoin implementations work fine afaik.
and it's not one of the notable changes?
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-25.1.md
That's Bitcoin Core. It's only fixed in Knots so far
It's worth noting you still can configure the limit however you want in Knots. This fix just means it will actually honour your choice.
Your node has limited impact by itself, but the more people who fix this, eventually yes
Yes and no
By the byte, yes
But they also enable miners to make the blocks larger (which is a second bad effect)
If you tell your node not to allow extra data beyond 40 bytes, and it then allows 40k, how is that ever not a bug?
Hey nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk this is the first I've heard of it. Thanks for putting this out there.
Is Bitcoin Knots a drop in replacement for core or do I need to build a different config and redownload the chain?
Drop in replacement
PSA: “Inscriptions” are exploiting a vulnerability in #Bitcoin Core to spam the blockchain. Bitcoin 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.
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.
Currently 10 TBC (0.01048576 BTC)
Planning to make it configurable
ocean love ordinals ??
nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk node different with ocean node ?
make me wonder đź‘€
#ocean
Sorry, working on it
8 times the current difficulty, so each share should be on average paid in 8 blocks
TIDES is basically PPLNS as it was originally supposed to be, with a very long N.
PPLNS today has become something very different, so we picked a new name to avoid confusion
nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze
nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk
Maybe a basic AF question but:
If my machines are offline when Ocean finds a block do I get paid for previous shares completed?
As a home heating miner I have quite variable hashrate.
Yes, until there's 8 blocks of work done after it
If you were waiting for me to publish my new "master" OpenPGP key announced at #FutureOfBitcoinMining, it should now be available from keyserver.ubuntu.com along with signatures:
- master key signing codesigning key (used for Knots v25.1)
- master key signing security communication key (for email about security issues)
- codesigning key signing master key
Master key: 93CB4961F69A65082D4410802CBA8253089655C3
Codesigning key: 1A3E761F19D2CC7785C5502EA291A2C45D0C504A
Security comms key: FAC098FE8DF9975F902418813666E2B1782A18E1
There was a minor issue with one of the three main features that we promptly fixed. 🙄
The known-late feature (better spam filtering) was not advertised yet as it wasn't/isn't ready.
