shocknet_justin

https://shock.network

Head of building shit | Lightning.Pub | ShockWallet.app | Lightning.Video/thecto

Public Key

npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsrx9hrd9k7wnfejkgj0wwcgt0400wut5w8479qfudu0tkcpdz9pzqpp4mhxue69uhkummn9ekx7mqs5lugx

Publishing to

nos.lol

Author Public Key

npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa

Show more details

Last Notes

2026-05-26 17:14:46 CEST

nostr wouldn't exist, nevermind have the traction it does, if not for lightning

2026-05-21 20:53:16 CEST

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=noffer1qvqsyqjqvcurjdm9x5uxydrzvcer2wrp8q6x2ef58pnryv3c893ngen98qerwvmrxuunqde5vgcnvc35vg6nydpnxfjrgetzv4snwd3exsungwgprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fc4vx4hj
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.

2026-05-17 19:29:41 CEST

- reply

These same people probably use fake L2's for convenience
More virtue signaling than thinking

2026-05-17 00:55:15 CEST

- reply

These fake L2 scams don't offer anything beyond what a regular custodial SQL database does
They do it to evade the regulators and scam unsuspecting noobs with crypto theatrics
... but when the regulators eventually squeeze their heads, they'll have ton of Lightning Network deanonymization data to hand over because of their central swaps
#nevent1q…99l2

2026-05-17 00:19:11 CEST

- reply

And that's terrible news for all
834411e240bb762dbb823d7f0a3471290be095d779cefbea18e4749120b6144f

2026-05-16 18:54:56 CEST

Just think about all the swaps running through a single Lightning node, fake L2's are a coordinated surveillance apparatus.
All the virtue signaling larps in Bitcoin were easily one-shotted by trust and centralization as soon as a fake Bitcoin company re-marketed it as convenient. Sad!

2026-05-12 07:32:27 CEST

- reply

SQL makes onboarding easier too if thats all you care about

2026-05-12 07:24:17 CEST

- reply

Install a non-shitcoin lightning wallet
I don't understand the confusion, neither spark or ecash are solving anything

2026-05-12 07:07:33 CEST

- reply

Lightning

2026-05-12 05:52:28 CEST

Curating a suggested follow list for new users, but it's hard once you filter out anyone legitimizing Spark or ECash

2026-05-07 06:53:46 CEST

- reply

Lightning is emergent of real world constraints of trustless decentralization and the physics of Bitcoin.
Nothing can be better, trust and centralization are the only levers one can pull.
Ark and Spark are both crypto theater, scams just rebranding trust and centralization.
Bolt12 is just tor-wrapped nonsense peddled by NGOs and LSP salesmen milking anyone naive enough to waste sats on a mobile "node".
CLINK and Lightning.Pub accept the reality that node runners are the new elite, that trust must be locally distributed instead of hidden, and that Lightning needs a robust protocol to connect services, nodes, and the web. All via Nostr of course.

2026-05-02 21:22:10 CEST

- reply

basically yeah

2026-05-02 21:13:03 CEST

- reply

should be able to just have the client replay the history on refresh, with each move appending to a thread

2026-04-30 19:03:45 CEST

- reply

https://media1.tenor.com/m/QgTx6fv4IpAAAAAd/el-risitas-juan-joya-borja.gif

2026-04-15 18:10:33 CEST

- reply

just zapped this via CLINK connection to ShockWallet in BXRD

2026-04-04 07:47:50 CEST

running bxrd

2026-04-02 05:02:37 CEST

I've come around to implementing a Fake L2
https://stacker.news/items/1463647/r/justin_shocknet

2026-03-29 18:49:43 CEST

- reply

🫡

2026-03-15 13:33:09 CET

- reply

Have considered it since nostr apps have been slow to update to CLINK
I think we can add an adapter in the Linked Apps screen, will look more into it

2026-02-26 20:40:16 CET

- reply

Nice, that overlaps nicely with some of my disdain for L402... http introduces domains/ssl/reverse proxies etc and that's a big friction with p2p markets: https://stacker.news/items/1435085/r/justin_shocknet?commentId=1435245
I think some of the concerns you raise boil down more directly to credit vs. Lightning, Cashu just being an implementation of credit. CLINK (and the Lightning.Pub reference server for it) can also be used for credit since it can be used in reverse (for debits).
When using Lightning you're right that there's latency that would make sub-second exchanges impractical without direct peering. CLINK is better at this than Bolt12 since it's not using onion messages that add a slow and fragile round trip, but still the payment itself unless directly channel peered will often exceed the desired time and fee threshold.
The Cashu tokens may be claimable in a disconnect, but if the issuing is offline they're also worthless, so it's not really solving anything. If the service or client goes offline with CLINK, it's literally just request response, no different than an REST API... the receiver would fail to sweep or the sender would fail to emit the referenced transaction. Nothing in limbo.
In your scenario I'd do a hybrid approach with CLINK, a minutes worth of credit with the service which debits a local account per-second, and then the customer can either top-up that credit every minute OR the service sends a debit request to the payer to complete or deny every minute based on the prior minutes debits meeting their criteria.

2026-02-26 16:31:32 CET

- reply

Correct that L402 is retarded, it's a sheepish meme because of an abandoned HTTP status code
But Cashu is just as sheepish, Nostr as a Lightning transport doesn't need shitcoins
https://CLINKme.dev

2026-02-12 17:09:06 CET

https://stacker.news/items/1432435/r/justin_shocknet?commentId=1432491

2026-02-12 17:08:35 CET

- reply

https://stacker.news/items/1432435/r/justin_shocknet?commentId=1432491

2026-01-30 19:20:28 CET

- reply

I see you're still aiding the communist NGO's and confusing their takes with your own.

2026-01-30 18:04:18 CET

- reply

BRCA is a trojan horse and weaponized virtue signaling.
It's purpose is to create conditional law that Big Fintech with leagues of lawyers can use to crush actual self-custodial competition. This is pushed by NGO's who are funded by big fintech.
Total scam.

2025-12-27 14:52:18 CET

- reply

Hercules

2025-12-26 17:08:42 CET

https://blossom.primal.net/4eb8d80ad32ad8127118ab18eb5228d9bdd6c13494b834e6eabd9e6f1fcf883f.png

2025-12-20 04:57:36 CET

- reply

> 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.

2025-12-19 19:24:52 CET

- reply

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

2025-12-19 18:46:16 CET

- reply

That's the Core position, Loops bip has overwhelming support and dissent is banned or shadow edited
https://image.nostr.build/b225935f733a2601727c340c1d4f04204425677a4161f0524d76f1b384c7f64b.jpg

2025-12-18 18:36:26 CET

Next time you see someone spreading Quantum fud, call them a scammer.
https://eprint.iacr.org/2025/1237.pdf
https://blossom.primal.net/16b5166abbc92e62bd38ff154aff8fbf0deac87c75bb6ff4c01d931b56fef73c.png

2025-12-18 04:23:57 CET

- reply

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.
#nevent1q…42yu

2025-12-16 02:10:32 CET

> I have my own lightning node for the first time
This is how we win
#nevent1q…64k0

2025-12-12 22:50:18 CET

- reply

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

2025-12-12 22:28:19 CET

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
@nprofile…gcsu @nprofile…r72v
https://blossom.primal.net/b645ffd78b6714bcf28a17276744bb523feb0e034865678af5b6a3c03b9df334.mp4

2025-12-11 15:18:38 CET

- reply

We don't have an NWC adapter either

2025-12-10 22:31:11 CET

- reply

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.

2025-12-10 19:34:01 CET

- reply

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 👍

2025-12-10 18:59:53 CET

- reply

it just uses the `name`
I see the new metadata, you're now the proud occupant "pip" 🎉
https://blossom.primal.net/6f307c016d7c51c0000116d3f2b6421701b7f2d26d6739956f6eaba1a692eaa0.png

2025-12-10 18:47:22 CET

- reply

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.

2025-12-10 18:00:16 CET

- reply

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
https://blossom.primal.net/503cfc849a110fec8e8c796cb8cda651cc50b595d1487ee361a73f9369ffc5bf.png

2025-12-10 08:48:12 CET

- reply

yep that's him on telegram

2025-12-10 01:46:10 CET

- reply

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 https://image.nostr.build/bf21817afd0c45e6d7d1ef3d7eedc9eff70d64aa3cf99e0686b35a7dd89ca2f5.jpg
> Different trust models
Centralization if trust is all one model.

2025-12-10 01:21:20 CET

- reply

Will check it out 👍

2025-12-10 00:51:26 CET

- reply

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.

2025-12-10 00:14:02 CET

- reply

Their design is built around scale centralization, it's shit design no matter what their incentives.
> Statechains never took off
That is being laughed off the stage.
Lightning is.
> Until spark cane along
And Spark is laughable, so by your own admission statechains only use-case is pretending to be lightning.

2025-12-10 00:02:02 CET

- reply

I literally make a lightning node distribution, made for people to run, and decentralize the network.
I do not provide any centralized custodial service, Pubs use any other Pub to bootstrap peer.
Even the built-in LSP automation uses an array of different LSP's, zeus-olympus, voltage, megalithic, flash sats.
I don't run one.
YOUR NODE shops rates and peers when running a Lightning.Pub
I've made all this a 1 line install and Start9 bundle.
I shit on Ark Spark and Cashu because they are shit, their entire premise is at-scale centralization, handwaving that neobanker dogshit as open source doesn't make it any less shit.
You know nothing.

2025-12-09 23:40:24 CET

- reply

No need to reserve, just set your metadata... Added a faq to explain https://nymrank.dev/faq

2025-12-09 23:36:37 CET

- reply

For ShockWallet there is yes, @nprofile…prsj is running it

2025-12-03 22:48:01 CET

- reply

Yep, I think it's just a few tweaks away from accommodating breadth. Biggest limiter may be current nostr event kinds.
Things like invitations and receipts in a commercial setting will really boost signal.

2025-12-03 22:31:49 CET

- reply

Yep, the impersonators that show under permissive only show up to be adjacent for comparison... in an API setting only the real Odell would show as that's the account occupying the name.

2025-12-03 21:15:05 CET

- reply

You're already perfectly set up to defend your nym, NO IMPOSTERS!
https://blossom.primal.net/08d209dfee9d027943d06cae7d101210386474d07868f0bad4361ae7fcc3c03e.png

2025-12-03 20:33:05 CET

Got Nymrank.dev in a pretty good place, this week, predictable namespace across nostr apps has been a big need for us to offer trustless and customized ShockWallet Lightning Addresses, and Lightning Video channel names.
Ingesting Trusted Assertions from @nprofile…waas 's GrapeRank and layering on affinity calculations makes for very solid decentralized namespace secured by #WoT
May talk about it on the #wotathon @nprofile…pnlv call tomorrow if I don't manage to break it before then.
https://blossom.primal.net/e7834688ef31aca853e7c9f2383df2e53becb27c10ad45f5482e94aa9b7cb927.png

2025-11-29 07:57:22 CET

- reply

yea some standard GFY codes that could infer scope would probably help, looks like there's a human readable but is only appended after a single ambiguous prefix

2025-11-29 07:39:43 CET

- reply

hmm, they'd have to send some event in any case in order to be ack'd, otherwise the relay can't know who's socketing... only alternative I could think of is pro-active auth, fail/retry is probably the simplest

2025-11-29 07:16:03 CET

- reply

Auth? I'm intrigued. Describe what you have in mind

2025-11-29 04:26:00 CET

- reply

Needs a total rewrite for the handshake, not to mention the server handlers, it's literally leftover browser extension slop that never considered the bigger picture of ad-hoc and service connections
Keep letting that NIP repo access go to your head though, muh numbers...

2025-11-29 03:28:49 CET

- reply

NWC is a nerfed persistent connection that requires manual user pre-provisioning and doesn't even offer static payment codes or budget requests
If you want better UX's you need to use better protocols, not browser extension slop

2025-11-29 01:12:33 CET

- reply

https://CLINKme.dev

2025-11-22 17:11:53 CET

- reply

Disgraceful

2025-11-19 18:04:20 CET

"Complexity is fraud"
-PJ O'Rourke on Fake L2's

2025-11-18 21:38:33 CET

- reply

Fortunately this isn't about wallet connections, its about getting invoices (and pre-images) to the web without every Lightning node needing to set up a web server.

2025-11-18 21:37:30 CET

- reply

Rusty did afaik yes, while Spiral did much of the NGO-level astroturf. Both representing minor implementations focused on the mobile node fantasy.
I recall one such use-case in the repo discussion being Fedimint/Liquid related shitcoinery. Solving the transport of bolt11's would have been adequate if that wasn't their priority, not a whole new BOLT to poison the protocol-level.
The shit that comes out of the NGO's and Blockstream have been a reliable counter-signal in every regard.

2025-11-18 21:28:11 CET

- reply

1) It mimics Tor, each hop is added latency and failure probability, whereas Nostr being a web server is the same performance people expect from any website
2/3) Bi-direction needs to be at the app layer if its to be used in commerce, payments often have additional context... you're not firing the zap receipt from Lightning for example
4) That appears to be a middleware plugin to talk websockets, since the browser requires websockets... nostr is just json and websockets already

2025-11-18 21:10:52 CET

- reply

It's a solved problem if you don't outsource your thinking to Spiral
https://blossom.primal.net/7f07c7ed0e2c3c11652c0620be73fb992c0c5c5193363115503de2fd6ef7d242.png

2025-11-18 20:59:07 CET

- reply

I don't like many aspects, it was completely contrived from a lack of principles by the minor implementations pushing the mobile node fantasy.
Even if I didn't care about jpegs on Lightning:
- The performance/reliability are a non-starter
- It doesn't do bi-direction for commercial applications
- It puts the concern at the wrong layer, the payments layer protocol versus the Line-of-Business Application
- My underlying principle is that Lightning is the native money of the internet, so things MUST work in a browser
(but not reliant on on that web tech you can still QR code a noffer with just a relay ip and node pubkey)
- If you want to add functionality, the SDK doesn't touch your underlying node implementation or the BOLT specs and can work with any of them
Nostr offers checks all those boxes, with the added benefit of having an identity layer that can be optionally leveraged along side it.

2025-11-18 20:39:26 CET

- reply

LN stuff is payments.
Bolt12 is arbitrary data on LN, may as well be jpegs on chain.
We'll let Nostr handle arbitrary data.

2025-11-18 20:36:51 CET

- reply

They're centralizing in social contexts because they're used for discovery and feed subscriptions, but as an RPC transport they're encoded in each noffer and only for ephemeral interactivity, not passively.
They're also not reliant on TLS since you can run a relay without SSL and just address it by IP
From a privacy standpoint, all the keys used in CLINK are wrapped as to not keep a social identity tied or hot on a service endpoint. A node can use as many as it wants for disparate offers/users.
The payloads themselves are encrypted so it's only the kind metadata viewable, but yea NIP42 would be a good add here, actually got a PR for that I need to review on our reference server.

2025-11-18 20:19:37 CET

- reply

They don't need to care about Nostr anymore than they cared about http to use LNURL, as long as it just works.
Bolt12 simply doesn't work, only a few privacy larps really cared, and they were completely wrong about blinded paths. It was always just astroturf by Spiral and minor implementations jealous of LND's market share.
The separation of concerns is key, not having to trust a nostr relay because of the encryption/signing already provides an instant transport network with the same accessibility of LNURL.
Nostr is also bi-directional, it's not just noffers, but ndebits and nmanage for offers. Offers themselves provide flexible arbitrary data payloads for product details. (t-shirt sizes, sku's, zap receipts etc)

2025-11-18 19:58:04 CET

- reply

It extends arbitrary data onto Lightning, which is as much of an attack as jpegs on the chain... payment traffic is naturally bonded
But all that aside, it's introducing 2 round trips across all those hops, each hop exponentially increasing failure probability and mean-time-to-payment

2025-11-18 19:55:17 CET

- reply

Right, between the poor performance/reliability/browser-incompatibility Bolt12 is a dead end... meanwhile, CLINK Offers work reliably today... including with blinded paths on LND so bolt12 can't even claim a privacy advantage
#nevent1q…04en

2025-11-18 19:49:31 CET

- reply

Could also use BIP-353 dns text records, but NIP-05 has more traction currently.

2025-11-18 19:47:32 CET

- reply

Bolt12 uses *other nodes* as a relay, problem is Bolt12 is unreliable because it mimics Tor and doesn't work in the browser.

2025-11-13 21:06:59 CET

- reply

🗲 🗲 🗲 🗲 🗲 🗲 🗲 🗲 🗲 🗲 🗲 🗲

2025-11-13 19:17:05 CET

Covenants cope grasps at straws with LN-Symmetry
LN-Symmetry is trash now being leveraged in attack on LN by the fake L2/bithereum/shitcoins 2.0 industrial complex.
Note the increasing correlation with it and former Lightning products, many still engaged in the mobile node fantasy, that burnt out, quit trying to actually innovate on UX, and took the fake-L2 Faustian bargain.
The "feature" of Symmetry is that it removes much of the online-ness incentive for nodes, and the justice disincentive for attackers.
The combined change of these delicate incentives would make the open and disintermediated version of the network unusable, increasing reliance on central coordinators.
Who benefits from that?

2025-11-13 01:43:04 CET

- reply

Bunch of nonsense, they're a little older than the new wave of Fake L2s and have been beaten up already. Ex https://petertodd.org/2023/drivechains
Paul can't even get basic Lightning principles right, shitcoiner clown of the highest order.

2025-11-12 19:45:14 CET

- reply

Can you upload to Lightning.Video? can share a link from that

2025-11-12 19:43:59 CET

- reply

I just got locked out of twitter too, they forced yubi-key re-enrollment and botched it big time
Anyone trying to get hold of me there i'm not ignoring you

2025-11-12 18:39:48 CET

- reply

I get into my solution, Lightning.Pub, a bit on the full interview
It's a recognition that casual users are going to end up trusting somebody, so we need to make the tools that allow that to be distributed to the local extreme of the family/small-biz
#nevent1q…q9ly

2025-11-12 18:34:10 CET

- reply

Indeed, I actually think institutional mining breaking down into decentralized heating appliances is a good thing, but that will be disruptive for any good actors in that industry so they should plan accordingly.
The risk of Fake L2 / Miner co-integration is just another risk Fake L2 users need to keep in mind before they capitulate to centralization for the sake of convenience.

2025-11-12 17:36:48 CET

- reply

Ty Shawn 🫡
#nevent1q…jhw5

2025-11-12 17:26:18 CET

- reply

Fake L2 / centralized coordination creates an incentive problem with miners for sure. With any meaningful scale they'll have incentive to vertically integrate miners and coordinators to start play games where they mine their control transactions and not competing ones or exits.
But that aside, if things remain where they are with sub-sat fees, and price languishes relative to the subsidy with future halvings, the nature of hash rate will inevitably change but not necessarily decrease.
The big industrial miners right now are already starting to pivot to AI, the arb is starting to come out of stranded energy. The subsidy also currently draws in institutional investment that will pay a premium for "uncirculated" coins that have a known provenance and can't in the future be linked to "illicit activity". With each halving this strategy becomes more expensive for these institutional accumulators.
That's not necessarily negative for overall hash rate, ASICS keep coming and each new version is cheaper than the previous one.
Things like Heatbit are a glimpse into where the hashrate will move to once institutional miners start move on, application where heat is the primary output and Bitcoin just subsidizes THAT. Greenhouses, water heaters in your house etc.
This would be better than the status quo today vs. a few very large pools anointed by institutional (nation-state?) capital.

2025-11-12 17:13:50 CET

- reply

💯
Yep, that's all covenants do, enable delegation theater to centralized Bithereum-like Fake L2 apps, it's an application stack feature not a monetary one.
I expanded on that a bit here
#nevent1q…he4r

2025-11-12 17:09:56 CET

- reply

Lightning's UX issues are inherited from it being an emergent part of Bitcoin, no "L2" can fix that as the physics of chain security are what they are.
Only centralization and trust mitigate the experience for the casual user, which is what Fake L2's are repackaging with scam narratives.
That being the case, the only honest and philosophically consistent approach is localization of that trust and coordination to family/small-business scale appliances

2025-11-10 22:06:26 CET

- reply

You can use the shockwallet.app lightning address to receive
I don't think @nprofile…x58v has added CLINK Debits yet for spending

2025-11-10 19:41:13 CET

Covenants scaloors live in effete intellectualism.
Lightning for better or worse, what people like and dislike, is scaling that lives in reality.
https://blossom.primal.net/b2e7ae2a7c3e36c1f3db4074255eda0bd0d39b375c762753a1bb66a71eec128f.png

2025-11-10 16:43:46 CET

- reply

Yes, both directions, though there may be a bug with zap receipts publishing when you receive... looking into it

2025-11-09 21:41:03 CET

- reply

From the standpoint that it's much worse and scammier? They've overstepped on marketing worse than anyone
https://stacker.news/items/1275977/r/justin_shocknet

2025-11-08 18:53:51 CET

- reply

> hybrid federated custody
That's a hoax, it's Shroedinger's node, key distribution can't be verified and there's still centralized infrastructure
> Eventually we will have a noncustodial ecash token that is directly redeemable for bitcoin on L1
lol no... thats not how any of this works... anyone claiming that can be done is selling a perpetual motion machine, the physics of the chain are immutable.
Lightning as the only real L2 is how it is because it recognizes this, its just re-usable on chain transactions.

2025-11-08 17:12:25 CET

- reply

lol, feels that way often, but that's the purpose of astroturf... to demoralize and manufacture consensus
scammers spare no expense to appear strong when they are weak

2025-11-08 16:40:31 CET

- reply

Yea they had to pivot away from the competing with Lightning messaging, since Lightning is the only real L2 they have to fall back to it. Now they just affinity scam as powering Lightning wallets.
They're closed networks and Lightning is an open network which gives an Lightning insurmountable advantage. One of their latest pivots seems to be payments between DeFi degens on shitcoin platforms
https://blossom.primal.net/cfb435ca733ae345192d3b3ef1e77dd91b9310dd6c4a0185347015692b1d12f9.png

2025-11-07 22:47:33 CET

- reply

#nevent1q…04en

2025-11-07 22:47:05 CET

- reply

https://clinkme.dev

2025-11-07 22:11:07 CET

- reply

https://clinkme.dev

2025-11-07 21:45:49 CET

- reply

Clinkme.dev

2025-11-07 18:44:43 CET

- reply

forgot Sanctum 😂
auth.shock.network

2025-11-06 21:06:36 CET

- reply

That link is to a second revision to address some of this.
The reality is fake L2's don't do anything differently than custodial solutions. They've just re-branded. There's no changing of the underlying physics, there's no free lunch, no solutions- only tradeoffs, fake L2's are just scamming.
No doubt that Lightning wallets are bad right now, but this is mostly downstream of mobile node fantasy. This is why I have shifted focus completely to ShockWallet and Lightning.Pub, no one else wants to be honest about this reality.
Pub uses trust too for bootstrapping and scale, because again there are no solutions. But, we're decentralizing that to the local extreme, not re-centralizing it.

2025-11-06 19:16:28 CET

- reply

Related reading
https://stacker.news/items/1275977

2025-11-06 16:24:39 CET

https://stacker.news/items/1275977

2025-11-05 15:55:48 CET

- reply

And opening a channel to a big routing node is your choice, Lightning is just infinitely re-usable transactions, you can open a channel to anyone also running a node.