Hercules

> lot of testing work that happens on Core

It can be done on another repo that doesn't usurp the legacy, but would also need less testing if it didn't churn as much as a frivolous app... Bitcoin's value is derived from it being stable and resistant to change.

> compartmentalize

Indeed, it'd be better if Bitcoin was looked at as distributions moreso than implementations. Libbitcoin is an effort to make it libraries, HORNET, and at least one other I scrolled by recently... also BTCD is a great example of a stable alt-implementation that powers a ton of nodes, but as a library, via LND.

> Knots

Unfortunately controlled opposition that's making a clown show of otherwise justified Core resentment

> avoid chain splits

A default distribution in Core is actually a bigger risk, most updates are downloaded blind. This presents a risk of widely distributing a bad version that splits with older versions. With more diversified distributions, the impact of a bad update/alt would be small... more frequent issues with individual, less severe as they'd be irrelevant to the broader network... like a controlled burn.

Core exists at this point only to turn Bitcoin into a Politburo that can be captured by the Courtier

There's zero excuse for there to still be a "default" repo in Bitcoin that undiscerning people turn to on account of its legacy

The only Pro-Bitcoiner move the Core repo can make is to archive itself and force the uninitiated to actively choose a distribution #ArchiveCore

That's the Core position, Loops bip has overwhelming support and dissent is banned or shadow edited

Next time you see someone spreading Quantum fud, call them a scammer.

https://eprint.iacr.org/2025/1237.pdf

Glad to see this, an issue I've been running into is that nostr-tools isn't really up to the task of long-running services. Zig is the perfect choice for an alt implementation... and most notably isn't beholden to the politics of the NIP repo.

@nevent1qvz...

> I have my own lightning node for the first time

This is how we win


@nevent1qqs...

Oh no! then who will fund the NGO's that attack Bitcoin? 😭

No web-hooks

No LNURL server

No lame etrash or fake L2 shitcoins

Just a static page, with a Nostr static offer embedded, and nostr-native receipts powered by CLINK on a self-hosted Lightning.Pub

@nprofile1q... @nprofile1q...

We don't have an NWC adapter either

The W would disambiguate the kind if there's any collision, so you could reasonably query for the NIP-85 structure and find attestations that might be available where you don't necessarily know or care exactly what types they contain

zap_sats_sent would be a good type in my view, rather than just value, zap_sats_sent would be better having values under it... perhaps things like week month year. So yea to your point I don't think value is itself is a good top-level type example, I mostly like eliminating the registry in the NIP.