
Justin (shocknet) ⚡
Lightning Maxi. Building Lightning.Pub | ShockWallet.app | CLINKme.dev | Lightning.Video | Bxrd.app
What point is that?
Ok so it's not inaccurate, I'm open to hearing stylistic preferences. I'm for improvement.
No you weren't, it was a 1:1 DM about GUN... ShockWallet predates nostr by 2 years.
https://x.com/i/status/1329817308378882048
https://cdn.nostrcheck.me/514d1d5e4b7cd62038ba01e778715a2…
https://x.com/i/status/1329817308378882048
https://cdn.nostrcheck.me/514d1d5e4b7cd62038ba01e778715a2…
On the first, you mean like personalized graphs? Graphs need to be hosted, could be a compelling premium option.
On the second, Sanctum policy engine integration in the works, with self hosted signer.
On the second, Sanctum policy engine integration in the works, with self hosted signer.
A system that allows bots to DoS or drown out users with noise is censorship by other means
Transparent WoT removes the developer skew, gives users the upper hand over bots
Bxrd flock is ascendant
Transparent WoT removes the developer skew, gives users the upper hand over bots
Bxrd flock is ascendant
bxrd.app
ELI5 / TLDR:
CLINK gives you a permanent Lightning payment code (noffer1...) that works like a Bitcoin address, but smarter.
Old way (LNURL, Lightning Addresses):
Requires a web server, domain, SSL, public IP — very complicated setup.
CLINK way:
Everything happens over normal Nostr DMs. Just share one static string. Wallets and websites use that to fetch invoices.
It also sends a payment receipt back so the website can react (success animation, unlock content, etc.) and you can attach extra data (SKU, order info, etc.).
Try it by pasting this:
noffer1qvqsyqjqvcurjdm9x5uxydrzvcer2wrp8q6x2ef58pnryv3c893ngen98qerwvmrxuunqde5vgcnvc35vg6nydpnxfjrgetzv4snwd3exsungwgprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fc4vx4hj
... into https://pay.shockwallet.app
As a receiver, you can include that string in a web link: https://pay.shockwallet.app/?noffer=noffer1qvqsyqjqvcurjd…
That's a fully static web site, and you'll get a success animation once paying the invoice. The node you're paying doesn't need any fancy networking setup.
Bolt12 achieves some of this static payment code stuff through Tor-like onion messages, which are therefore slow and unreliable. It's also not web friendly, making its utility limited. Some might even say that it's retarded.
CLINK gives you a permanent Lightning payment code (noffer1...) that works like a Bitcoin address, but smarter.
Old way (LNURL, Lightning Addresses):
Requires a web server, domain, SSL, public IP — very complicated setup.
CLINK way:
Everything happens over normal Nostr DMs. Just share one static string. Wallets and websites use that to fetch invoices.
It also sends a payment receipt back so the website can react (success animation, unlock content, etc.) and you can attach extra data (SKU, order info, etc.).
Try it by pasting this:
noffer1qvqsyqjqvcurjdm9x5uxydrzvcer2wrp8q6x2ef58pnryv3c893ngen98qerwvmrxuunqde5vgcnvc35vg6nydpnxfjrgetzv4snwd3exsungwgprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fc4vx4hj
... into https://pay.shockwallet.app
As a receiver, you can include that string in a web link: https://pay.shockwallet.app/?noffer=noffer1qvqsyqjqvcurjd…
That's a fully static web site, and you'll get a success animation once paying the invoice. The node you're paying doesn't need any fancy networking setup.
Bolt12 achieves some of this static payment code stuff through Tor-like onion messages, which are therefore slow and unreliable. It's also not web friendly, making its utility limited. Some might even say that it's retarded.
Lightning
Curating a suggested follow list for new users, but it's hard once you filter out anyone legitimizing Spark or ECash
Been working on some graph infrastructure for Nostr to enable more features in our Lightning suite, so I slopped together a general nostr client to test its performance and comprehensiveness vs. standard bearers like primal and to use in the Nosfabrica hackathon demo
Rather than connecting directly to relays, BXRD uses a shared graph so any user activity makes it more performant for all users. This graph also comes in handy for computing web-of-trust scores.
The architecture of BXRD also makes it useful for external linking, clean namespace links based on nymrank which work for opengraph cards and server side rendering without an intermediary service like njump
https://cdn.lightning.video/eb5b0f038fba733b50cec1c8b48ed…
Also this allowed for web-push notifications for the PWA
CLINK wallet connections sync across devices via NIP78, and use your own nostr key to pair to your shockwallet
It's in a good enough state that it's now my primary nostr client, only thing missing of note is uploading rich media (todo: with Lightning.Video's forthcoming api v2).
DM's are there, just not the nip17 giftwrap nonsense, but i'll look at that more closely eventually...
DM's from outside the WoT show in a spam folder
https://cdn.lightning.video/eb5b0f038fba733b50cec1c8b48ed…
**Caveats:**
Will get better as I keep using it and finding things I need/want, or send me reports if you use it. It may get bounced frequently as I deploy changes.
Content is only indexed if the author passes the WoT threshold, which is currently about 200k keys... so if you don't have an established nostr presence and want to use it let me know and I'll throw you a follow
Rather than connecting directly to relays, BXRD uses a shared graph so any user activity makes it more performant for all users. This graph also comes in handy for computing web-of-trust scores.
The architecture of BXRD also makes it useful for external linking, clean namespace links based on nymrank which work for opengraph cards and server side rendering without an intermediary service like njump
https://cdn.lightning.video/eb5b0f038fba733b50cec1c8b48ed…
Also this allowed for web-push notifications for the PWA
CLINK wallet connections sync across devices via NIP78, and use your own nostr key to pair to your shockwallet
It's in a good enough state that it's now my primary nostr client, only thing missing of note is uploading rich media (todo: with Lightning.Video's forthcoming api v2).
DM's are there, just not the nip17 giftwrap nonsense, but i'll look at that more closely eventually...
DM's from outside the WoT show in a spam folder
https://cdn.lightning.video/eb5b0f038fba733b50cec1c8b48ed…
**Caveats:**
Will get better as I keep using it and finding things I need/want, or send me reports if you use it. It may get bounced frequently as I deploy changes.
Content is only indexed if the author passes the WoT threshold, which is currently about 200k keys... so if you don't have an established nostr presence and want to use it let me know and I'll throw you a follow
Clinkme.dev
Fake L2's don't scale anything
There's two factors in scaling
1) Transaction throughput: Lightning already scales transactions infinitely
2) Ownership: Distribution is the real bottleneck, there's a minimum amount of Bitcoin needed to not be dust and even at sub-sat fees today there's not enough Bitcoin for everyone to trustlessly transact (unilateral exit)... a few hundred million people at most... likely less as big accumulators like institutions continue to accumulate
There's two factors in scaling
1) Transaction throughput: Lightning already scales transactions infinitely
2) Ownership: Distribution is the real bottleneck, there's a minimum amount of Bitcoin needed to not be dust and even at sub-sat fees today there's not enough Bitcoin for everyone to trustlessly transact (unilateral exit)... a few hundred million people at most... likely less as big accumulators like institutions continue to accumulate
There's a new wave of Lightning FUD hitting the wires, but that's noise. What no one else is talking about is the signal.
Reality is that Lightning faces a massive incentive problem, one it inherits from Bitcoin itself.
The great wave of shitcoins in the early years highlighted this problem way back then, but it's manifesting itself in a new, potentially even more dangerous way today.
Since Bitcoin, and its only real L2 in Lightning, are emergent, truly decentralized, disintermediated and "just work" as money, the profit motive for companies looking to benefit from a growing industry skews towards "inventing" things beyond them; there must always be something "new" to re-brand non-solutions or introduce middlemen.
Enter the newest attack by fake L2s, or shitcoins 2.0 as they should be more appropriately framed. Shitcoining 1.0 has lost its novelty, as over time people realize there is one true coin. Scammers have thus adapted, and are now affinity scamming as Bitcoin projects.
Ark, Spark, Citrea, Stacks, and countless others now... with their astroturf for Covenants that would lend them some perceived legitimacy... solve nothing.
These are all means not to solve problems or enhance UX, but to smuggle trust and centralization for profit.
Lightning wallets can very easily introduce trust and centralization with the same exact trade-offs; fake L2s are no different than zero-conf channels, but this isn't sexy and won't raise a bunch of money or generate hype. Actually enhancing UX is tedious, hard work, to which I can attest, and inherently requires scarce creativity, otherwise the challenges would be solved already.
This is a perfect storm for the scammer class. Unsophisticated users that lack technical discernment, combined with hipsters always ready to jump on the current thing bandwagon, magnify the scammer astroturf. This reinforces investment theses, then more investment yields more scams, which amp up hipsters and the unsophisticated; it's a downward spiral.
**Unlike Shitcoins 1.0, Shitcoins 2.0 presents a Bitcoin contagion.**
Never before have so many disparate scams sought to change Bitcoin itself to pervert the incentives further.
Shitcoins 1.0 sold you a new coin... Shitcoins 2.0 want to exploit YOUR coin.
Shitcoins 1.0 sold your friends and family a new investment thesis; Shitcoins 2.0 stand on the back of your hard-fought orange-pilling.
Covenants are the force multiplier of this attack.
These apps are in chorus over how it enhances the security of their centralized apps, and given their affinity scam nature, the security of Bitcoin. In reality, it has no monetary purpose, only to enable delegation to these centralized middlemen.
If you control your Bitcoin today, you control your Bitcoin, period. Covenants offer you nothing.
Covenants scammers want you to believe, however, that you can control your Bitcoin while someone else, via their fake L2 centralized application, controls your Bitcoin.
New OP_ Codes like CTV, CAT, DRIVECHAIN, and others represent a new era where changes to Bitcoin aren't argued on the merits of Bitcoin as money, but its use as an Ethereum-like stack for centralized applications.
> But aren't VAULTs a monetary use of covenants?
No, just as covenants are a push for centralized remote control, vaults are to CLAW BACK that control. This leaves 2 mutually exclusive scenarios:
* Bitcoin loses its utility as money, as merchants can no longer simply rely on confirmations to conclude a payment is settled.
* A merchant can ensure funds are not encumbered through certain output types, but then so can an attacker, rendering the vault pointless from the start.
> What do?
Incentives are a bitch; we couldn't stop shitcoins... but we did grind them down over time.
The question is whether we can grind down these fake L2s and covenants scammers; fortunately, Bitcoin being hard to change buys us time.
It's imperative that if you value Bitcoin as hard money and wish to defend it as such, you present the same show of force we showed against shitcoins.
Let every investor and user know, in every comment on every blog or Twitter post, that these applications are not Bitcoin, that Covenants are an attack by the Bithereum Industrial Complex, and that whoever advocates them is either a scammer, a paid shill, or a hipster moron.
https://blossom.primal.net/ab6e91b0046ae25498294861e5708d…
Reality is that Lightning faces a massive incentive problem, one it inherits from Bitcoin itself.
The great wave of shitcoins in the early years highlighted this problem way back then, but it's manifesting itself in a new, potentially even more dangerous way today.
Since Bitcoin, and its only real L2 in Lightning, are emergent, truly decentralized, disintermediated and "just work" as money, the profit motive for companies looking to benefit from a growing industry skews towards "inventing" things beyond them; there must always be something "new" to re-brand non-solutions or introduce middlemen.
Enter the newest attack by fake L2s, or shitcoins 2.0 as they should be more appropriately framed. Shitcoining 1.0 has lost its novelty, as over time people realize there is one true coin. Scammers have thus adapted, and are now affinity scamming as Bitcoin projects.
Ark, Spark, Citrea, Stacks, and countless others now... with their astroturf for Covenants that would lend them some perceived legitimacy... solve nothing.
These are all means not to solve problems or enhance UX, but to smuggle trust and centralization for profit.
Lightning wallets can very easily introduce trust and centralization with the same exact trade-offs; fake L2s are no different than zero-conf channels, but this isn't sexy and won't raise a bunch of money or generate hype. Actually enhancing UX is tedious, hard work, to which I can attest, and inherently requires scarce creativity, otherwise the challenges would be solved already.
This is a perfect storm for the scammer class. Unsophisticated users that lack technical discernment, combined with hipsters always ready to jump on the current thing bandwagon, magnify the scammer astroturf. This reinforces investment theses, then more investment yields more scams, which amp up hipsters and the unsophisticated; it's a downward spiral.
**Unlike Shitcoins 1.0, Shitcoins 2.0 presents a Bitcoin contagion.**
Never before have so many disparate scams sought to change Bitcoin itself to pervert the incentives further.
Shitcoins 1.0 sold you a new coin... Shitcoins 2.0 want to exploit YOUR coin.
Shitcoins 1.0 sold your friends and family a new investment thesis; Shitcoins 2.0 stand on the back of your hard-fought orange-pilling.
Covenants are the force multiplier of this attack.
These apps are in chorus over how it enhances the security of their centralized apps, and given their affinity scam nature, the security of Bitcoin. In reality, it has no monetary purpose, only to enable delegation to these centralized middlemen.
If you control your Bitcoin today, you control your Bitcoin, period. Covenants offer you nothing.
Covenants scammers want you to believe, however, that you can control your Bitcoin while someone else, via their fake L2 centralized application, controls your Bitcoin.
New OP_ Codes like CTV, CAT, DRIVECHAIN, and others represent a new era where changes to Bitcoin aren't argued on the merits of Bitcoin as money, but its use as an Ethereum-like stack for centralized applications.
> But aren't VAULTs a monetary use of covenants?
No, just as covenants are a push for centralized remote control, vaults are to CLAW BACK that control. This leaves 2 mutually exclusive scenarios:
* Bitcoin loses its utility as money, as merchants can no longer simply rely on confirmations to conclude a payment is settled.
* A merchant can ensure funds are not encumbered through certain output types, but then so can an attacker, rendering the vault pointless from the start.
> What do?
Incentives are a bitch; we couldn't stop shitcoins... but we did grind them down over time.
The question is whether we can grind down these fake L2s and covenants scammers; fortunately, Bitcoin being hard to change buys us time.
It's imperative that if you value Bitcoin as hard money and wish to defend it as such, you present the same show of force we showed against shitcoins.
Let every investor and user know, in every comment on every blog or Twitter post, that these applications are not Bitcoin, that Covenants are an attack by the Bithereum Industrial Complex, and that whoever advocates them is either a scammer, a paid shill, or a hipster moron.
https://blossom.primal.net/ab6e91b0046ae25498294861e5708d…
Didn't you drag Saylor for avoiding that same trap?
Maybe should have listened a little closer.
Maybe should have listened a little closer.
But [they] are *supportive* of at least CTV
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.
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*
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*
Haven't been able to reproduce the lightning address issue but hold up at this point we'll have a push hopefully this week and can sneak some logs in for the address problem
Can't get guests balance to 0 but I'll send to your new address
Can't get guests balance to 0 but I'll send to your new address
No lightning address enrolled? If your on android is it the latest apk?
Prod bootstrap node is ahead of wallets with a breaking change for history /balance updates.. known issue ... trying to get the new build shipped in the next few days but it's been a monster
Prod bootstrap node is ahead of wallets with a breaking change for history /balance updates.. known issue ... trying to get the new build shipped in the next few days but it's been a monster
I see drivechains as a silly distraction, but if I'm proven wrong eventually that's fine too.
Much of the ECash scam comes from the fact that any major custodian is already "MultiSig" with varied stakeholders, and that this somehow makes it a layer upon Bitcoin.
Coinbase Custody uses a MultiSig vault with several overseeing stakeholders including regulators. Is that a Bitcoin layer if we also ECash on it?
Is it really any more private when they're a in and out hop in your coin movements?
All you've done with software is codify a fiat political system that's still inherently susceptible to human weakness.
These ECash projects aren't getting tens of millions in sus VC money, and backesld by "Russia Man Bad" NGO spooks like the HRF.
Think logically. Just skim the ECash act. Connect the dots to Bolt12 and Blockstream.
These projects are astroturfing the next CBDC/Digital Dollar and attacking/exploiting lightnings traction to do it.
Don't give up on Uncle Jim.
Coinbase Custody uses a MultiSig vault with several overseeing stakeholders including regulators. Is that a Bitcoin layer if we also ECash on it?
Is it really any more private when they're a in and out hop in your coin movements?
All you've done with software is codify a fiat political system that's still inherently susceptible to human weakness.
These ECash projects aren't getting tens of millions in sus VC money, and backesld by "Russia Man Bad" NGO spooks like the HRF.
Think logically. Just skim the ECash act. Connect the dots to Bolt12 and Blockstream.
These projects are astroturfing the next CBDC/Digital Dollar and attacking/exploiting lightnings traction to do it.
Don't give up on Uncle Jim.





