shocknet_justin
Justin (shocknet) ⚡

Lightning Maxi. Building Lightning.Pub | ShockWallet.app | CLINKme.dev | Lightning.Video | Bxrd.app

Public Key

npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa

NIP-05 Address

Profile Code

nprofile1qqsrx9hrd9k7wnfejkgj0wwcgt0400wut5w8479qfudu0tkcpdz9pzqpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyqyt8wumn8ghj7cnfw33k76twv4ezuum0vd5kzmqs0rur6

Publishing to

Author Public Key

npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa

Show more details

Last Notes

2026-10-26 15:47:08 UTC

Been thinking about this as an unintended feature of Nostr.
Phone numbers and email have become little more than a vector for spam and phishing. They'd be more valuable if literally 99% of activity disappeared.
Nostr just needs to lean into it with WoT, but that implies infrastructure in direct opposition to trends like White Noise / NIP17
#nevent1q…903u

2026-10-20 21:22:11 UTC

Bxrd's following feed now surfaces notes by cumulative engagement, not just a reverse chron of posts or reposts of your follows.
Nostr clients as only as good as the infrastructure that powers them, these simple enhancements are made possible by a shared graph using a lot of memory.
https://npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa.blossom.band/48a84e16ddd27cea604f387993d12b9b9540a9b2112772172112f0f9ac2bac83.png

2026-10-01 04:29:35 UTC

CLINK disrespectors just having NIH syndrome. Embarrassed they've wasted time on dying protocols because they couldn't solve the most basic use-cases of getting invoices and receipts reliably where they belong without a bunch of extra trad-web infrastructure.
#nevent1q…5ewy

2026-09-29 19:11:48 UTC

CLINK Offers: Lightning payments without a web serve
https://cdn.lightning.video/2e46a6cc78d41d2f7212e240c3dffac2bbeb66ad7dd43c0e07c1e2e78c6b98d9/98a9pKkZY2.mp4

2026-09-22 19:06:57 UTC

Welcome @npub1car…f0dd to the CLINK ecosystem
https://cdn.nostrcheck.me/cab7285a8e0dba3447b0084c6752f0d04fee9b118ee7867d2db03ad1d21f3faa.png
#nevent1q…xv9x

2026-09-18 07:07:55 UTC

Welcome Circl and SkateSpots to the CLINK ecosystem
https://clinkme.dev/apps.html
@npub15yp…mpcx @npub1e2a…8a4l

2026-09-17 18:26:11 UTC

Good poll for Bithereum crypto-kids to out themselves.
#nevent1q…573d

2026-09-13 18:54:07 UTC

Got to the bottom of the Ark astroturf, an "anon" fighting me over it accidentally revealed a little too much about themselves.
Big-stablecoin is behind it, that's why all the paid fluffers are out.
All makes sense now since it's Centralized/Surveilable, double-spendable, and results in negative yield via rounds.
Also doubt that it's being proposed shortly after Taproot Assets is a coincidence.

2026-09-11 15:35:47 UTC

The Liquid hacker could send the remaining coin to Spark and Ark and shatter illusions of those being non-custodial at the same time
Kill three fake L2's in one hack

2026-09-08 16:38:23 UTC

https://cdn.nostrcheck.me/7471d12067457ad7504d2b28aaa05143d655133081e407eac8ed36f4caf542b6.png
#nevent1q…uz2f

2026-09-07 05:53:49 UTC

I suggest fixing your nostr metadata to occupy a nym/slug, and adding a noffer for zaps.. Might drop a little something this week
(see https://nymrank.dev if you're unfamiliar with nym optimization)

2026-08-24 16:13:34 UTC

NIP-22 now implemented on Bxrd and it will pick up both kinds for a transition period
https://Bxrd.app
#nevent1q…0vvv

2026-08-22 16:40:12 UTC

Pretty sure this is just plebs that hardware wallets and punch plates are wastes of money when you can just back up wallet.dat to mdisc
https://cdn.nostrcheck.me/8fb676363a2c9f5d469a2e8bd970fa9a59087cb8f56ada2c484c086069183246.png

2026-08-13 16:08:57 UTC

- reply

just got the logs and replied on telegram 👀

2026-08-09 05:13:21 UTC

If you think BIP-110 failed you never understood the objective. It was extremely successful controlled opposition.
Core's influence has been consolidated, solidified.
Resistance shattered and demoralized.
"Spam" is now a good thing, pre-excusing more Bithereum scope creep.

2026-08-07 17:09:47 UTC

Looking at the patch commits it seems that an attacker could glean connection details to the backing node.
Even if there's no evidence you were hit yet and have no funds hot, you wouldn't want to receive a payment with an attacker lying in wait,
Rotate the connection credentials to the backing node.
#nevent1q…3yxv

2026-08-03 17:22:51 UTC

Checked a repo not our own for calibration last night with GPT 5.6 Sol
Critical hit first try, a fairly popular software wallet. Disclosed to publisher just now.
You may want to consider checking and building stuff from source yourself until the ecosystem has time to catch up.
https://cdn.nostrcheck.me/d1c72e3b87b2cf5f43e5aa02aa3ac1152d79d40c9a49576a1280822d7c60739d.png

2026-08-03 17:16:21 UTC

Silver lining here is that fake L2 wallets built exclusively on swaps are facing their comeuppance.
They were warned about these single points of failure.
#nevent1q…knan

2026-07-31 23:36:49 UTC

Do not bin your Coldcards
https://cdn.nostrcheck.me/da24ad3d8f84513cfc1dc6ccc936cb694810eb545ab38037cb808d4bfd2740e9.png

2026-07-31 06:59:02 UTC

- reply

ESP32 seeds are vulnerable if they're created with Wifi/Bluetooth not on
None of these toys are a silver bullet
https://insomnihack.ch/talks/breaking-the-random-exploiting-esp32s-rng-vulnerabilities-in-offline-applications/

2026-07-31 03:31:54 UTC

- reply

https://cdn.nostrcheck.me/79c8ae163395c7c0f41252672e65f14dec6c906de603464768a4424b87a448ca.png

2026-07-30 20:21:43 UTC

- reply

> Over this past decade people are increasingly abandoning Bitcoin as a store of value
Fastest growing ETF's ever and countless ATHs over the last 10y show otherwise
Gravity pulls towards 21M Bitcoin, not 21M fly-by-night new shitcoins constantly shopping for narratives
> cultish ideological demands
> Everything else is secondary
... to being the world reserve currency.
Says the guy virtue signaling about privacy and buying t-shirts
You don't even use a more private chain, you use sybil honeypot Monero... lol

2026-07-30 19:50:36 UTC

- reply

You mentioned being in Europe, so I suppose you must be confusing surrender as virtue.

2026-07-30 17:54:34 UTC

- reply

> if the problems of ledger privacy could be solved
Big if, still hasn't been solved. Monero is a sybil honeypot chain for larps that's less private from the state than Bitcoin simply because the anonset is shit and attracts lazy dumbs that can't do proper UTXO management.
> Tantalum-180m
Is there a decentralized ledger, near-costless verification, and most importantly, a deeply liquid market for this? Yes you could clone Bitcoin bit for bit today and have an equally scarce base unit, but the scarcity of the conception and resultant gravity-well cannot be replicated. Every shit-chain reinforces this, shit-chains are not scarce.

2026-07-30 16:30:51 UTC

- reply

> There is zero room in a payment network for the kind of error rates and half-assedness of implementations that we see in Lightning products.
I agree with this and it's also why I'm out on a limb relative to most lightning devs. The same clowns pushing Bolt12 also push things like mobile nodes, the idea of routing for profit, hold invoices, and other half-baked stupidity.
These aren't Bitcoiners for Bitcoin's sake, they're shills for NGO's that control most of the funding, and bandwagon jumping hipsters.
> We’ve had a decade of LN development and there is only one thing that is “normie-friendly” and production grade
If you watch some of my interviews I specifically go in to why I pivoted back to wallet/node dev from my video site, because Lightning tooling had gotten worse instead of better... for the same reasons described above.
> Peer to peer payments networks have to fit all major real world
The definitions of peer and real world do a lot of heavy lifting. I assure you that your definition of peer and real world are different than mine.
> people on the street want USDT on TRON
Lightning or Bitcoin doesn't exist to beat fiat on UX, no one uses Gold for payments either, yet its 10x the market vs. Bitcoin
> all you have is a PWA
Lightning.Pub is a headless server with an SQL database and an RPC that installs on pretty much any OS in less than a minute.
> CLINK is not ready for the real world
The reference server hasn't even hit 0.1.0 yet.
> you want to convince me to start using this other Lightning thing
I don't want to convince you of anything, if you want to use fiat shitcoins for better UX while others go right ahead. The Lingua Franca of 21M will continue to spread fine without you. Anything worth doing is hard.
> current leadership
I have no leaders, only sheep need a shepherd. Is Lightning full of sheep? Sure is. That leaves plenty of green field for me on the other side of the hill.

2026-07-29 07:08:31 UTC

- reply

Happy to talk through it some time

2026-07-22 18:19:43 UTC

- reply

If you think Taproot is bad wait until you see Covenants

2026-07-08 15:54:09 UTC

Surprised that people are still surprised how bad these fake L2 scams are.
Actually, Grubles may not even realize he pointed out something much deeper.
See, it doesn't matter if clients don't cache recovery info from the server... It's the fact that you need it served after every tx to begin with.
It's not self-custody, its a data availability dependency the server can simply withhold.
https://cdn.nostrcheck.me/f0043a3c04e2677df3e36f06d0cea14862223d5dee9e44472a7c38091aaa63d2.png

2026-06-18 18:20:25 UTC

- reply

CLINK author here, I like keysend, its actually been one of my arguments against Bolt12... Bolt12 should have never happened, add that to the diagram and CLINK is dead simple by comparison.
Couple limitations though with keysend that CLINK addresses though:
1) Web friendliness, if Lightning is to be the money on the web it needs to work in websites, which nostr does
2) CLINK keys are de-coupled from the node itself, so are available per-user rather than per-node in shared node contexts
3) Arbitrary payer_dater for commerce, product sku's etc in the payload (also receipt payloads which also enable interactivity on webapps)

2026-06-17 00:17:11 UTC

- reply

People interact via the web, http/https, so for lightning to be the money of the web it needs to work on the web.
Fortunately Nostr picks up where lightning failed since it uses http and can get invoices there. CLINK exists for this reason.
Lightning having its own p2p layer necessitates native apps on mobile, stands out on militarized networks, and couples communication and monetary identity.
Pubky has a few high level concepts right directionally but relies on DHT which doesn't work, after 20 years the torrent world still uses trackers because DHT is so slow and unreliable.
https://pay.shockwallet.app/?noffer=noffer1qszqqqqqzspszqqzg3jxzv3evccngdryx33kyct9v5ukyenrv4jk2vesv3jnscfcv5mnzerrxpjkxce3xajnzef3xvenqvn98qcxxvfkxucnzerzxyervvnrvvekyvsprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcqxs9tw demonstrates static pages just using nostr to fetch invoices, no galaxy brain p2p required.

2026-06-16 23:29:05 UTC

- reply

Bolt12 does nothing for privacy, blinded paths maybe do (debatable) but exist outside of Bolt12 (LND has had them for a long time already)
CLINK is better for static addresses, and more private since it's decoupled from the node, allows for HA, and is out of band on a web port.
(static addresses are a misnomer because Lighting is inherently synchronous, they're just pointers to a live endpoint)
Bolt12 is literally just invoice passing over Tor-like onion messages, fortunately LND has an option to disable them. Since you can't inspect them you can't block non-invoice data, Bolt12 is a vulnerability pushed by the minor implementations who went all in on phones-are-servers. Dumbest thing ever.

2026-06-13 21:25:07 UTC

- reply

I'm the anti-Bolt12 guy
It's retarded for many reasons

2025-12-10 21:31:11 UTC

- 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-07-17 17:07:42 UTC

- reply

iiuc, this wouldn't have been possible if the default open was 1 conf?