Replies (24)

Default avatar
npub17u5d...t4tp 0 months ago
IIRC there have already been several releases and close to a thousand nodes running Dathan Ohm's code, which likely has this bug.
3 replies ↓
Default avatar
npub17u5d...t4tp 0 months ago
It's gone 3 months without being noticed. Also, Dathan has released his own fork that nearly 1,000 nodes are running. I expect this bug exists in that code.
2 replies ↓
JackTheMimic's avatar
JackTheMimic 0 months ago
And that's how code dev works. You realize you aren't running the release candidate of Bitcoin right?
TheYOLOSpirit's avatar
TheYOLOSpirit yolospirit@nostrplebs.com 0 months ago
It happen all the time in software projects, this doesn't make the project not serious. 3 months is not a lot and if the bug can only happen during the transition window, it's not a problem until it happen?
1 replies ↓
dazzling's avatar
dazzling dazzling@getalby.com 0 months ago
Bugs in code happen. That in itself does not signal a lack of seriousness. But if Knots does not get more developers and a more structured development process then it most certainly signals a lack of seriousness! I should be clear here, I don't follow Knots to any degree at all, so maybe the process and devcount is changing in a good way.
1 replies ↓
Pixel Survivor's avatar
Pixel Survivor 0 months ago
consensus flaws knot funny. serious find, serious implications. curious if this pushes more folks toward simpler core or sparks a broader audit across implementations.
n0>1 signals bip110's avatar
n0>1 signals bip110 3 weeks ago
Youe evil and you know it. What does that feel like? It must suck. I guess there is no turning back now, huh?
↑