> 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
saylor seems to be advocating for a hard fork that forces people to move coin.
burning those who do not comply.
this breaks the fundamental social contract and value prop of bitcoin: sovereign ownership and property rights.
it must be opposed. strongly.
https://blossom.primal.net/09bdeb018313b0eeeca3d178fb0b183bd4fb75bb29df30bb7d0dfe79d12402ed.mp4
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.
> I have my own lightning node for the first time
This is how we win
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
nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyxhwumn8ghj7cnjvghxjme0qqswen6sdv8chdl605h78vqvp48jxhx84hlkx8nt9luyczcv744u5ncvrgcsu nostr:nprofile1qyghwumn8ghj7cn0dank2u3wwpex7tcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qpqf4www6qjx43mckpkjld4apyyr76j3aahprvkduh9gc5xec78ypms54r72v
https://blossom.primal.net/b645ffd78b6714bcf28a17276744bb523feb0e034865678af5b6a3c03b9df334.mp4
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.
Ok that's more clear, thanks for explaining. "Type" really nails it, Schema may be good too, either would be a more concise label for the tag than categories.
Discoverability is a good argument for `w`, I'm sold.
Nice work 👍
it just uses the `name`
I see the new metadata, you're now the proud occupant "pip" 🎉
The formatting here is a little hard to grasp fully, if this could be a proposed diff on the github PR that would be ideal for review
What I do grasp I think I agree with, the NIP as currently constructed is mostly a registry... I don't think its a good idea to hard code a bunch of possible metric tags into the NIP itself... Mani's arbitrary string give it more forward-utility without future changes.
An example expansion in my case would be, if I want my paid services to signal that a user paid for something, or was invited/sponsored by another user, I might arbitrarily want to use NIP-85 to publish a paid_user attestation from that service so other services might whitelist them as a non-bot without their yet having a broader WoT in the form of followers etc.
(open to suggestions for a paid_user/invitation NIP or NIP-85 adaptation to bootstrap WoT)
I'm not sure I see the value in the W tag, seems superfluous with the kind and the fact I'd be looking for a specific tag anyway, but perhaps i'm missing something.
I also think the categories themselves being part of the NIP is the same flaw as the registry, unless they're just meant as examples for a top/bottom leveling tags. This may be where formatting of the site as opposed to git makes things unclear. Basically if I were to make a diff the NIP would be half the size or less.
Unfortunately can't make the call tomorrow but look forward to discussing further and reviewing a diff.
your kind 0 metadata shows as this, and I just re-ran it against your listed relays
"profile": {
"name": "pippellia",
"nip05": null,
"lud16": "whitebat1",
partial match only applies to the name field, and demarcated by spaces... we wouldn't want "pip" to also occupy "pi" for example... but would want someones first name to hit if they used name as First Last
Partial matches do not count in the lud16/nip05's prefixes since those wouldn't have spaces... but neither your nip05 or lud16 are populated with "pip"
Since your name field is "pippellia" that's what you occupy
This is the copy pasted messages:
"M0:
Influye en el diseño y las nuevas funciones de ShockWallet
ShockWallet es una billetera impulsada por Lightning diseñada para empoderar a los usuarios, no solo para incurrir en costos por experimentar. Buscamos personas para probar la usabilidad y consultarnos para mejorar la incorporación y otros flujos. Se te pedirá que intentes varias tareas, navegues por la experiencia y compartas tus pensamientos a medida que avanzas. Tu opinión dará forma a ShockWallet para que sea no solo la billetera más fácil, sino también la más potente jamás creada.
Cómo puedes participar
Hay dos formas de involucrarse:
🔓 Pruebas no moderadas
Sumérgete y explora la billetera a tu propio ritmo, no te llevará más de 5 a 10 minutos. Prueba funciones, navega libremente por la interfaz y ve qué funciona (o qué no). Tu opinión honesta es muy valiosa.
- Empieza a probar ahora: https://hotjar.com/l/wDMWeP
🗓 Sesiones de UX moderadas
Programa una sesión privada de 30 minutos con nuestro equipo para discutir conceptos de diseño, validar ideas y compartir tus pensamientos en tiempo real. Esta es tu oportunidad de influir directamente en la hoja de ruta del producto: Haz clic en el enlace de abajo para empezar → Reserva tu franja horaria → Espera la confirmación por correo electrónico.
- Programa tu sesión: https://hotjar.com/l/8gbQYl
Por qué tu opinión importa
Cada función, cada botón, cada palabra, cada interacción importa. Sé parte de hacer que ShockWallet sea realmente genial.
Nota: la applicación y las preguntas serán en ingles. Podemos hablar Español por la sessión moderadas si es preferido."
yep that's him on telegram
I haven't lied about anything, unlike those scam project founders I can handle the thunderdome. You on the other hand are intentionally obtuse.
Ark Labs specifically on the lies, but Second is flirting with much of the same with their lightning affinity positioning. Ark Labs is already pivoting to defi, because they can't back up their bullshit.
> Wut
You know what anonymity set is? No? Then sit down.
> Lightning how many people can use Bitcoin
First not retarded thing you've said, that's true.
> Because of block space
Now you've undone it, it has nothing to do with block space... Only supply distribution.
> Federation
You know what a SPOF is? No?
> Nostr
Only exists because of GUN and ShockWallet v1 
> Different trust models
Centralization if trust is all one model.
Got countless receipts of Ark lying on Twitter, Spark bills itself as non-custodial... Lies. Cashu is privacy larp, privacy implies anonymity set, therefore at scale centralization.
Specifically addressed lightning first mover advantage. Since statechains were there, and went nowhere, it proves lightning isn't a success because it was first.
You're only here on nostr because of things I built. My design with gun and lightning is nostr's prehistory.
Pub/Wallet is a recent sidequest, because lightning tooling sucks too much for me to continue on lightning video.
Lightning doesn't have limitations beyond the physics of the chain, statechains don't fix those, centralizing trust is not an option, statechains are cryptobrained nonsense. There's no such thing as a federation either, it's all a central point of failure, you're brainwashed by crypto marketing material.
Unilateral exit is a hoax, if users could afford it they could just open a channel, these systems appeal to users with dust.
Nothing changes the physics of the chain, only lightning embraces that reality. If you think you can improve upon it without trust and centralization you're delulu and should go work for an ETH company.
Luke himself had CTV on his roadmap post the other day.
The fight is fake, Core vs. Knots is a psyop for Jack's money vs. Jack's money.
Swap-fee based fake-L2's are driving development priorities in both cases.
Active development is cover for activist development.
It's already doing that, there's no round-trip to a tracker required before hitting the webseed directly to get the mov atom and first chunks.
It's just a client that makes use of additional data.
That's exactly what WebTorrent does by using webseeds. It's providing a redundant source for chunks while maintaining the raw performance of a traditional source.
An array of webseeds in the magnet also allow it to download chunks from disparate CDN's without a load balancer to handle that in the back-end, if one gets rugged your links still *just work*
Nevermind just cropped
More educational materials soon to come, but to the early tinkerers, we value your feedback!
If you're not already running ShockWallet with your own node and sharing it with friends and family, you'll love Lightning.Pub
We pushed a major update to ShockWallet with a number of fixes and enhancements ⚡️
Most notably, a callback builder for nostr-based offers 🦤
Easily notify an external application when you receive a payment, vibe-code your heart out. 🫰
New slur for fake L2's:
Trustodial.