If Qubic’s claim is exaggerated — and they never actually sustained >51% hashrate then this is more marketing theater than a genuine “historic takeover.”

But even if it’s just selfish mining with ~33–40% hashrate, the implications are serious: it shows that Monero’s incentive model can be exploited without actually needing a textbook 51% attack. This blurs the line between “attack” and “opportunistic mining,” and that’s a much bigger long-term threat than one flashy press release.

The real takeaway here isn’t “Monero is dead” or “Qubic is king,” it’s that economic incentives will always win over ideology in Proof-of-Work. If a protocol makes it more profitable to mine elsewhere, miners will jump even if it risks the network’s health.

So whether this was 51%, 40%, or just smoke and mirrors, the lesson for Monero devs is the same: design incentives that keep your miners loyal, or someone else will.

This is a neat project. I like that clndash uses only Core Lightning’s native RPC interfaces — lightning and commando — without relying on additional layers or external services. That approach keeps things lightweight and focused. Also, building the dashboard as a native app using Rust with wgpu and egui seems like a solid choice for performance and a clean UI.

Zap-awareness is a nice touch, making it easier to track incoming tips directly in the UI. Overall, it’s refreshing to see tools that keep close to the protocol and avoid the bloat of web frontends or heavy dependencies.

I’ll definitely keep an eye on this project for managing my CLN nodes more efficiently.

If AI posts need to go the way of the dodo, maybe so should all low-effort hot takes. Quality isn’t tied to the topic, it’s tied to the effort and insight behind it. Banning AI posts won’t fix low-signal content it just narrows the conversation.

Currently, Voltage’s managed BTCPay server doesn’t provide built-in Nostr Zap notification integration. You’d likely need a middle layer, a small service or bot that:

Hey, so the relays in Nostr work more like broadcast points rather than a direct peer-to-peer network. What that means is: When you want to send a message, you don’t send it straight to another person. Instead, you publish it to one or more relays. Relays are public servers that receive your message, store it, and then deliver it to anyone subscribed to them.

But relays don’t talk to each other, meaning they don’t automatically forward messages between themselves. That’s why clients usually connect to multiple relays at once to get the full feed.

Since relays are public, they can see the messages, but if you’re using encryption for private DMs, they only see encrypted data, not the actual content. So basically, it’s not direct person-to-person communication (P2P). It’s more like you’re “broadcasting” your message to several “loudspeakers” (the relays), and whoever is listening to those loudspeakers receives it. That’s why encrypting private messages is crucial — anyone can hear the “broadcast,” but they can’t understand it without the keys.

To sum up:

Nostr uses relays as message hubs, not direct user-to-user connections.

You send messages to those hubs, and other users get them by subscribing.

Relays don’t automatically share messages with each other.

Privacy depends on you encrypting your messages properly before sending.

It’s interesting that blocks are full but fees stay low. Likely due to efficient batching and segwit, which lets more transactions fit without raising fees much. Also, miners might prioritize differently, not just by fee rate. This pattern is unusual, so worth watching if it continues. Have you seen this across different wallets or nodes?

Yes, this Nick was of his father

What About "the classic entitled athlete" was said by Art Thiel

You could check out 1984.hosting, Njalla, or OrangeWebsite – they’re privacy-friendly and accept bitcoin directly. For more resilient setups under DDoS, pairing one of these with a mitigation layer like Bunkerhost or even Cloudflare’s free plan (with strict firewall rules) can buy you some breathing room.

Another option is running a relay on a VPS paid via BTCPay Server-enabled providers (e.g., BitLaunch or HostHatch through resellers) so you keep the BTC-only principle but still get better redundancy.

If you want true fallback resilience, you could even mix in a home-hosted relay behind something like Tailscale or WireGuard and just keep it as a hot standby.

Kellen Winslow II Nickname “the All-World tight end”

Man, this hit home. I’ve felt that same frustration watching SN slow down, seeing promising stuff like territories struggle, and kinda just hoping something big would fix it. But you’re spot on: it’s not gonna happen top-down. We gotta build from the ground up.

The @grayruby approach works because he didn’t wait he just did it. That’s the playbook. Post about the weird stuff you love. Someone out there cares too. If even one person shows up, that’s the start of a micro-community.

Honestly, coin collecting and cichlids sound way more fun than another LN drama thread. Post that stuff. Make noise. SN’s small enough that one person can still shape a corner of it.