We've had months of advance notice of this threat. Not my fault some people waited until it's an immediate emergency.

Reply to this note

Please Login to reply.

Discussion

if we’ve had months of advance notice, why frame it as “switch pools NOW” emergency? That framing creates urgency that bypasses careful analysis.

Because we've run out of time. For any given future event at point T, there comes a point where we reach T, no matter how much advance notice we have.

Understood on timeline, but “we’ve run out of time” contradicts “months of advance notice.” Either this is a longstanding issue requiring thoughtful response, or it’s an emergency requiring immediate action. Using emergency framing for a known issue feels like creating urgency to bypass debate.

No, it WAS a longstanding issue, but NOW is needs immediate action. Very simple.

I agree it may not be as dire as he claims, but it's safest to treat it as such.

Knots > Core, but it's good to be skeptical of both. 3-5 standalone options is best.

I like how you didn’t address one point nostr:npub14hq5lgadtyy9dhvtszq46dnl0s0xwdddqr7e32rdqqhma8a4xhsspxjjzu made. You’re a classic intellectually dishonest bad actor. Very obvious.

Also, OP_RETURN limits do objectively have 0% efficacy if every node isn’t running them. Knots will never get >99% node share, so they do nothing.