<unnamed>

Public Key

npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa

Profile Code

nprofile1qqsrx9hrd9k7wnfejkgj0wwcgt0400wut5w8479qfudu0tkcpdz9pzqpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqpz4mhxue69uhhyetvv9ujumn0wd68ytnkv46qzxnhwden5te0wd68yenj0yh8x6r0vd4jumn9w3mk7unth9ezqk

Publishing to

Last Notes

2026-09-04 19:24:04 CEST

Bumped the testflight build, bigger released slipped for this week... but should ship next week.
It'll be worth the wait, especially for node operators running a Pub
https://cdn.nostrcheck.me/e38203b024fe1836ef7217ab7035a7168f69ff2e5749bd4a7e4e1e78d6dea5ea.png
#nevent1q…f47g

2026-09-02 18:27:12 CEST

https://blossom.primal.net/0a2ec3a637bcacd6ad3096a7da37dbc7e085f9dde319acf1fa43b1b953a89707.mp4

2026-09-02 17:13:12 CEST

CLINK fixes the LN-address privacy hole — no HTTP third party fetching your invoice.
https://stacker.news/items/1559801

2026-08-26 22:51:56 CEST

🟡 Notice
There's a zero-day CLN vuln that has operators keeping their nodes down until a patch is released. As a result several of our channel peers are offline temporarily until they release a patch which is expected in the next few days.
Liquidity on sends may be tight until then, but is safe.

2026-08-22 18:40:12 CEST

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-16 20:17:24 CEST

https://cdn.nostrcheck.me/f988e356ee54f7826b6012e1b2ed50f478a7b2b1f207c3c12f0d75f60ef2a079.png

2026-08-05 04:50:57 CEST

Make a mental note of who's engaging in the "casino" dice cargo-cult purity spiraling
Shitty dice are fine
https://cdn.nostrcheck.me/f13c7e0555fe0ecca767a9392fa21fd2c8297ee6fe27001960879930f82d4216.png

2026-08-01 18:29:53 CEST

- reply

https://stacker.news/items/1536996/r/justin_shocknet?commentId=1537350

2026-08-01 06:07:34 CEST

https://cdn.nostrcheck.me/aacc4db717c38475ae51cf531e23a1499a842f4c9b3c8d377c01d1e5449fb225.jpeg

2026-08-01 01:36:49 CEST

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

2026-08-01 00:42:05 CEST

- reply

Can promptly ignore anyone pushing more shit op_codes, they wouldn't solve the issue, attacker would now have your vault recovery key and wait to RBF

2026-07-31 20:11:10 CEST

- reply

Highly speculative theory and seems unlikely, if anything the BIP110 theory is more plausible... but also could just be hot wallet de-risk since they're a fake L2 client now anyway.

2026-07-31 08:59:02 CEST

- 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 08:52:26 CEST

Key management is an intractable problem that goes back as far as computers using cryptography at all, engineers in the 70s and 80s recognized that the ultimate vulnerability of any cryptographic system was not the strength of the mathematical cipher, but the fragility of the human interfaces required to use it.
Every email challenge, 2FA token, username/password, biometric, or even SSL sites you've interfaced with is an abstraction or workaround the difficulty in managing keys.
Seed phrases are hardly an improvement over post-it notes on monitors in the 90s, most disks are volatile storage, and memory is lossy.
Large custodians with geographically dispersed enterprise-class HSMs behind policy engines are going to be the inevitable conclusion for most until we start thinking outside of the box rather than tinkering with toys and treating bad BIPs as canonical.
#nevent1q…5eq6

2026-07-31 07:25:00 CEST

HWW maxis becoming ETF maxis was not on my bingo card for this week
https://cdn.nostrcheck.me/e706984382a8746849dd89d6b2e1d39aa95aa8bb345c966c4462c2511f7351fc.png

2026-07-31 05:31:54 CEST

- reply

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

2026-07-30 18:42:29 CEST

- reply

A number of reasons.
Speed: No chain provides instant settlement, waiting for a block confirmation is untenable for simple API calls.
Granularity: No chain can support micropayments that are cost-effective.
Atomicity: You can accept fiat or shitcoins for payments, but then still have to sell those to buy Bitcoin which incurs its own trusted swaps and fees.
Businesses already run servers for websites, email, etc. A sovereign internet requires sovereign servers, the notion that you don't need a server is an NGO psyop. Lightning is simply the payments protocol for sovereign servers, no different than SMTP or HTTP.
Will most people use the Gmail or Godaddy of Lightning? Likely. It's the optionality not to that is what matters. Lightning.Pub and CLINK simply make that option easier to exercise than the status quo, that doesn't mean it has to be easier than not giving a fuck and letting the middleman do it for you.

2026-07-29 07:52:20 CEST

Excited to add 3 new Apps to the CLINK ecosystem list:
Dark Wisp Nostr Client
BTCPay CLINK Plugin
Vendure CLINK Plugin
https://clinkme.dev/apps.html

2026-07-27 22:08:54 CEST

- reply

Took your reply and pasted into Cursor and one-shotted it into NAK
Gave me some other ideas though... more to come

2026-07-23 19:59:13 CEST

https://cdn.nostrcheck.me/37709cc72acab702f40e7502ae656c318677d58c50eb4e1dfa39e2668936f193.png

2026-07-20 08:02:58 CEST

Less BIP wars. More BOLT wars.
https://cdn.nostrcheck.me/56a6ba4f3ae7c812f58ddde01e71cb9d8fc895e907ab1212f4cd30e0eaf9bdb0.png

2026-07-17 21:03:16 CEST

- reply

It's speaking to a lack of first-principles thinking In Lightning generally

2026-07-17 20:47:49 CEST

- reply

Routing discovery is proportional to the destination, routes through you are discovered often by payments being made TO you.
The foolish notion that any rando, not offering any services for which they receive payments, should incur hot wallet risk to race to the bottom chasing routing yield... has been poisonous to the Lightning ecosystem.
Routing fees exist to make the network function, not to generate yield for larps... and all you should hope for is to break even while saving on chain fees making payments to *economic* peers.
https://stacker.news/items/1525752

2026-07-16 19:29:17 CEST

- reply

End receiver has to share that invoice though I assume? so it's still a trusted serve, and may be less efficient route and more failure prone than just 3 distinct invoices
Interesting concept though if I'm wrong

2026-07-15 16:42:41 CEST

- reply

Could possibly add a split payload to CLINK offers responses that loads n additional invoices or offers for other parties. The primary offer publisher is still trusted to serve those though, but, never holds the funds themselves.
Alternatively, chain n offers together into one string, with a delimiter where clients sequentially pay each. Biggest issue I see with that would be the strings become extremely long and ugly and it wouldn't work with QR codes
The latter would probably work fine in shops UX's specifically though, assuming there was a debit wallet connection to handle the long strings without QR scanning/copypasta
The issue is that Lightning itself can't natively split payments so it's ultimately always going to be some hacky way of sequencing multiple payments that aren't atomic.
Open to other thoughts, the latter is a trivial CLINK/SDK addition with no work on the reference server and I can tinker with it in our in progress shops UI on Bxrd.

2026-07-10 20:11:20 CEST

- reply

Cline seems to be the go-to for VSCode extension
Zed is another option worth investigating

2026-07-08 21:18:38 CEST

It is a great day for Lightning, and therefore, the world.
Added 2 new projects to the list of CLINK Apps
Woo-CLINK, a WooCommerce plugin, and Electrum CLINK by @npub10uv…vxel
https://cdn.nostrcheck.me/1080d0760888a68d8e030389ea72cbad565fd494d51731ddca6b4220f9b17cdb.png

2026-07-08 21:11:48 CEST

- reply

Don't get me started on covenants

2026-07-08 21:10:26 CEST

- reply

Would probably be too little too late, for years now they've astroturfed these things as self-custodial L2 / Lightning wallets to gain adoption and mindshare
If they came up with a mea culpa PR push saying they've been full of shit for years now, that'd be laudable, but would be the end of their businesses and isn't going to happen.
Since these things are far more custodial then Samourai or Tornado Cash were there's only 2 possible outcomes.
1) they get prosecuted as MSBs
or
2) the gov goes so soft on small-amount custodians they don't need to pretend anymore
That's the most charitable I can be with them, perhaps they aren't out to scam users, but the user was collateral damage as they try to scam the regulator.

2026-07-08 19:39:38 CEST

- reply

Esse cara é um palhaço que não tem resposta.

2026-07-08 19:35:25 CEST

- reply

Yes the issues go deeper the further you go... since these are billed as Lightning wallets (since its pointless to use them with chain deposits) the swaps ingress is entirely trusted place because the operator is the swap provider (prior owner colluding with itself)
There's no free lunch, no levers left to pull... Lightning that they claim to address issues with is emergent of real constraints. So these fake L2's scam and pretend they've created solutions, hoaxes to fool unsophisticated users / cryptophile idiots

2026-07-07 08:01:37 CEST

- reply

https://clinkme.dev

2026-07-06 17:16:36 CEST

- reply

Pub just fetches quotes from Zeus and Boltz so it can use the most competitive, they're not generated on our side

2026-07-04 21:23:55 CEST

- reply

on chain spending? that can be done by the admin on the dashboard via swaps.. its in wallet for users but hidden, should reveal it next wallet release been making sure its stable first
will probably add utxo management for admins in dashboard soon too

2026-07-02 23:33:38 CEST

- reply

Dm*

2026-07-02 23:33:29 CEST

- reply

Sent me but I can't sync until Sunday probably

2026-07-02 23:33:06 CEST

- reply

Yea, you can chain deposit to your pub whenever and open channels from the dashboard from there.

2026-07-02 14:15:18 CEST

- reply

NGO paychecks likely a factor too

2026-07-02 14:13:07 CEST

- reply

Semi and JB are just coping and seething that NWC was too retarded and backwards to replace LNURL... Textbook NIH syndrome
https://bxrd.app/note/e7ead18e6b2078a50c3819e14a01b9507e54bbfe928d0602ebc1acae81382e6c

2026-07-02 14:07:13 CEST

- reply

Onion messages are too slow/unreliable for payments, adds a whole round trip where each hop adds latency and failure probability and turns nodes into arbitrary data relays
Doesn't work in browsers without wasm payload because it doesn't use http, even then interactivity with web apps is limited
Limited payer context for products/commerce
Conflates payments identity with comms identity
This also ties it to node vs user unless implementations scope creep to line of business apps
Mindshare was from the ground up astroturfed by NGOs that control almost all dev funding, to support hacky mobile node implementations with minor network share (which is a separate rant about the inanities of mobile nodes)
Astroturf relied on false privacy claims, blinded paths work fine in bolt11 (CLINK offers also support them)
It's even worse than keysend, which has been available for years yet remains unused... Assigned Bolt number was just for affinity scamming
Doesn't address other common LNURL shapes
LND rightly rebuffed it as retarded for a long time but eventually caved to astroturf
... Probably more I'm forgetting

2026-07-02 02:51:41 CEST

- reply

Not FUD, just facts. Bolt12 sucks which is why creating CLINK was necessary.

2026-07-01 23:50:55 CEST

- reply

True but it's still a key fumble which the phish site is trying to exploit

2026-07-01 23:44:33 CEST

- reply

The secret string is the nsec for the connection

2026-06-29 22:04:11 CEST

With CLINK you don't have to share an nsec.
#nevent1q…m5e6

2026-06-29 19:30:48 CEST

- reply

All good, you were right up until about 2 weeks ago... I think the new K1 addition should serve this use-case well.
Feel free to hit me in the cals for if you want to ideate and work through it over zoom or whatever.

2026-06-29 17:30:55 CEST

- reply

nOffers (lnurl-pay equivalent) are payable by any npub, the keys in the offer are just that of the receivers node service, it's designed to be ad-hoc
nDebits (lnurl-w) started as npub-bound, a budget was allocated to the remote key by the wallet for claim. The new `k1` field makes it now so that the claiming npub doesn't need to be known in advance, so for someone to claim a prize they would just need the static ndebit pointer (relay uri and key of the service) and the one-time use claim code `k1`
So in this case the k1 could roll to match the desired cooldown

2026-06-29 16:19:44 CEST

- reply

Can you explain a little more what you mean by the open offers?
CLINK can do LNURL-w use-cases, actually just a couple weeks ago added `k1` support for session based withdrawals

2026-06-29 02:54:56 CEST

- reply

Nostr wouldn't exist if not for lightning specifically, historical fact, not opinion.

2026-06-28 19:05:00 CEST

- reply

https://youtu.be/bdcS2InQI8I?si=ERwYmGhrE_UNtw3i&t=31

2026-06-28 17:26:33 CEST

- reply

Ran the numbers and it's possible to get $1500 or so worth of API tokens out of a $20 GPT Plus subscription with codex auth
Makes no sense
Composer-maxxing for $60 with included credit to other models still the best deal though

2026-06-27 22:10:08 CEST

Bxrd backfill:author-feed-heads done: 4499 author heads
Translation:
4,499 users in the Web-of-Trust posted in the last week
There are 32,747 in-WoT keys with >1 follow
This could be an interesting KPI for Nostr to keep track of, let me know if you'd like to see these kind of reports published regularly.

2026-06-27 07:50:03 CEST

If it maintains a payment channel, it's a node.
If that payment channel is to a phone, its a waste of chain space and liquidity.
Like a miner that doesn't mine when you sleep.

2026-06-23 06:18:17 CEST

- reply

⚡
https://cdn.nostrcheck.me/decd55fb6c6cd3ca7d136804f51fb3c86f04d7bb21eb96b2df2288a8a2593485.png

2026-06-22 18:38:45 CEST

Bxrd now features an indexed posts search, de-noised by the Web of Trust
https://cdn.nostrcheck.me/fc045f5c48251dbf5d77fdedac1bba09e637b0bc795e7591658e59b033843aa6.png

2026-06-21 22:19:28 CEST

- reply

Will have to look into what this is, should be easy to extend balance/budget limits

2026-06-20 16:31:07 CEST

- reply

It's most powerful for aspiring receivers/merchants, since you can stand up a lightning node without additional networking to receive payments from Web Apps...
Lightning.Pub is the reference server and stands up in under a minute, wallet connects remotely to it via nprofile
Since it's a static address that fetches regular bolt11 invoices, users can generally pay it without additional wallet support, but for wallets that do support it you can add that to an address book etc.
We'll be doing more with payment pages that use it, example here: https://pay.shockwallet.app/?noffer=noffer1qszqqqqqzspszqqzg3jxzv3evccngdryx33kyct9v5ukyenrv4jk2vesv3jnscfcv5mnzerrxpjkxce3xajnzef3xvenqvn98qcxxvfkxucnzerzxyervvnrvvekyvsprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcqxs9tw

2026-06-20 16:23:30 CEST

https://cdn.nostrcheck.me/3c42a2fcdc3a95dc87e7bc314dc5cd84066e34f86be8f6e7333c9ab6281ede96.png

2026-06-19 00:06:35 CEST

- reply

Clink 🍻
It's an onomatopoeia for the sound of coins changing hands

2026-06-18 23:15:25 CEST

- reply

ShockWallet supports CLINK Debit, superior to NWC
As for Nostr clients, Amethyst and Bxrd.app support debits for zap spending...
Unsure of support status yet on Wisp/Dark Wisp
#nevent1q…jt50

2026-06-18 20:20:25 CEST

- 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-18 18:40:33 CEST

- reply

It should be doing that already, but seems to get lost in some cases, state has been tricky to manage... theres a few other navigation bugs i'm hunting.
Best place for now is telegram t.me/shockbtc

2026-06-18 03:18:54 CEST

- reply

Connect to and manage your node over nostr to avoid network setup
Manage clink offers for products services
Accept and manage debit requests
Sync across devices
Invite guests to your node
Automate payments
Uses nostr for identity/device sync
Multi connection multi identity
Static payment pages (payges) over nostr
Reference client and management dashboard for Lightning.Pub
Probably more I'm forgetting

2026-06-18 01:11:19 CEST

- reply

That's for connecting to a lightning.pub node
If you just want to tinker you can use bootstrap mode to connect to ours

2026-06-18 00:01:25 CEST

- reply

Pretty much, once you paste the ndebit into your client and try to use it wallet will prompt for approval and let you said a budget... thats it

2026-06-17 23:55:05 CEST

- reply

Works for Zap's, but CLINK instead of NWC... Amethyst now supports CLINK

2026-06-17 23:39:59 CEST

- reply

ty sir, will keep grinding through til the global economy runs on nostr and lightning 🫡

2026-06-17 22:19:27 CEST

- reply

remedied
#nevent1q…ntnl

2026-06-17 22:15:24 CEST

ShockWallet is now published in the @npub10r8…t2p8
https://cdn.nostrcheck.me/1ef5788b8c08e276fab7c0737c2227aa2074e324a41b9499d8ad39d8fba8d245.png

2026-06-17 04:16:56 CEST

- reply

Yea IP traffic is at a much lower level than is in scope, even the underlying lightning node still has to squawk over its native port. Need some kind of tunnel to obfuscate a residential IP
I usually suggest a cheap VPS and just use its IP through SSH -R
Much better reliability

2026-06-17 03:04:05 CEST

- reply

Hmm, that might be clock skew, may need to loosen tolerance

2026-06-17 02:55:08 CEST

- reply

I'll look at how that works, must be nip-30... I've been sticking to the basics just to make a stable canvas but have nothing against more expressiveness
The first goal of bxrd is the infrastructure behind it, just making it the best functioning basic nostr client available so that nostr doesn't feel broken.
With that stable, combined with CLINK, Lightning.Video will be able to be moved on top of it and be non-custodial
Products/Business pages will then be layered to, decentralized Shopify / WooCommerce.

2026-06-17 02:17:11 CEST

- 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-17 01:44:25 CEST

- reply

Since the CLINK keys are decoupled from the Lightning node you can roll them without losing channels, you could have multiple for different apps/users/use-cases to break correlation, or use blinded paths to obfuscate the destination node
Relay observers can see DM metadata of course, but since they're scoped only to these ephemeral kinds there's little to glean particularly where the payer is typically using an ephemeral key.

2026-06-17 01:38:23 CEST

- reply

Payments are already onioned, but tied to an htlc, all the middle node can see is entry and exit... bolt12 doesn't change that, it just adds a round trip for the invoice over that shitty onion network. (onions are slow and unreliable, Lightning should have been web-based not p2p but that's a separate matter)
Utreexo doesn't change the fact that phones are not servers and that the internet is synchronous. Mobile nodes only exist for you to lose money to LSP's on overpriced channels.
Lightning is for earning money while you sleep, which means, a server (or an old laptop, rpi, vps, whatever)

2026-06-17 01:29:05 CEST

- 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-17 01:21:28 CEST

- reply

It displays them in notifications / reactions modals, but doesn't compose them
I recall vaguely seeing some chatter about standardizing on just likes as primal does
I don't have a strong opinion this either way... can do if desired.

2026-06-17 01:17:03 CEST

- reply

I know, they're adding Bolt12, they capitulated to retards that cried for it despite knowing better.
Completely moronic to use Lightning nodes for arbitrary data onion messages.

2026-06-17 01:04:37 CEST

- reply

There's def an AI bubble, but in breadth not height. Lots of garbage benefiting from it. SpaceX is the pin... much tougher row to hoe with them beating OAI and Anthropic, and the next Starship milestone pulls the orbital datacenter narrative even further forward.

2026-06-16 18:58:51 CEST

- reply

Easy
Elon derangement syndrome, trillionionare envy, and Chinese/globalist propaganda are keeping SpaceX under valued while index funds over value dying companies.

2026-06-16 02:53:44 CEST

Bxrd.app now tracks relay signaling from the user graph via NIP-65, runs tests a few times per hour, and fans out as appropriate
... without choking your phone to death.
https://cdn.nostrcheck.me/24a1bc44b1ed6b6d41fa616596fb63dd9712a0c7df22f9f0e75bb57ad61b2603.png

2026-06-16 00:39:25 CEST

- reply

https://bxrd.app

2026-06-16 00:39:10 CEST

- reply

https://bxrd.app

2026-06-13 23:25:07 CEST

- reply

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

2026-06-13 23:23:44 CEST

- reply

Yea missed the fact this was a Monero bot

2026-06-13 23:22:16 CEST

- reply

There's Nostr CLI tools written in go or rust if that's your thing... or even websocat if you're elite
But if channels are so hard that you're shitcoining with a low-anonset clown chain then there's nothing more that can be done to help you, you've got privacy larper syndrome

2026-06-13 20:48:29 CEST

- reply

Wtf you talking about Willis?
Since CLINK is Nostr, it works literally everywhere.
bxrd.app and shockwallet are both PWA's
The reference server is a nodejs app that sets up in a minute and can run on any VPS or whatever box you have at home... but because it uses nostr it obviates the network setup.
You can even use a noffer as a url param to a web site:
https://pay.shockwallet.app/?noffer=noffer1qszqqqqqzspszqqzg3jxzv3evccngdryx33kyct9v5ukyenrv4jk2vesv3jnscfcv5mnzerrxpjkxce3xajnzef3xvenqvn98qcxxvfkxucnzerzxyervvnrvvekyvsprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcqxs9tw

2026-06-12 19:35:43 CEST

- reply

Yep, may disable entirely for the default offer
Found some other small bugs in Pub around error handling too that should make debugging more straightforwared for testers/implementers

2026-06-12 17:56:25 CEST

- reply

💯, LNURL can do this as well just to a lesser degree
Next steps for us are to add products in bxrd, so in addition to your shitpost feed, you'll be able to create products for sale and your profile becomes a storefront
It'll also be going into Lightning.Video so that it becomes fully self-custodial, a noffer on each video will let your Pub trigger paywall unlocks
CLINK manage `nmanage` is a 3rd spec in the suite that will allow bxrd/lightning.video/whatever marketplace apps that use it to create offers from their own UI so you don't have to do that manually in shockwallet... you'll just create a product in the marketplace app, that app will reach into your Pub over Nostr to set up the appropriate offer and use it in the product listing
This is a POC of a static website that parses noffers to pull invoices that demonstrates how product links will work... the beauty of nostr is it works on the web and can just show bolt11... wallets don't need CLINK to work with those, bolt11 is the lingua franca
https://pay.shockwallet.app/?noffer=noffer1qszqqqqqzspszqqzg3jxzv3evccngdryx33kyct9v5ukyenrv4jk2vesv3jnscfcv5mnzerrxpjkxce3xajnzef3xvenqvn98qcxxvfkxucnzerzxyervvnrvvekyvsprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcqxs9tw
@nprofile…gcsu @nprofile…r72v also have a kiosk powered by an offer to let people pay for snacks https://shocknet.github.io/PlebCafe/

2026-06-12 17:31:33 CEST

- reply

Ah, that explains it
Payer_data tells the handler what payload should be expected along with the invoice request and if the shape doesn't match it's rejected
payer_data is arbitrary json that can be used for product info, sku's, an email address, anything you want to pipe back out to another system upon payment (works with the webhook callback)

2026-06-12 17:17:48 CEST

- reply

Server can respond that they expired (as a reason the pointer is no longer valid, code 3)
But I see this is from our Pub, it's logging invalid expected data and responding with a 1 (generally invalid, not expired)
It doesn't recognize the pointer... there was an IPC crash so it might not have stored... investigating that on our end

2026-06-12 02:12:28 CEST

- reply

You're signing for it when you post as something you want people to pay, but yes that still makes it ambiguous for zap payloads

2026-06-12 01:56:32 CEST

Just deployed a massive refactor of Bxrd state management, now using TanStack... should make the UX a lot snappier and reliable. Easily the most performant client, built on a shared WoT graph with AQL.
Probably still lots of edges so please test, CLINK like a mf, and report bugs. Thx.
On-boarding for new to nostr / non-WoT users not complete, but coming soon.
https://bxrd.app
https://cdn.nostrcheck.me/19ce616b47bc9453c73bb35fcc7837838af23c23f86a8cf140c6fdd30d978d10.png

2026-06-12 01:49:26 CEST

- reply

My client isn't treating ones in a note as a zap, it's just fetching the invoice and paying it
But, I also just zapped you from the zap icon which does send the zap payload (prioritizing a published noffer over lud16)
Could treat the post noffers as zappable... just a matter of clients sending the payload they would regularly
https://cdn.nostrcheck.me/b81d9e014625f0652d42ccd3df7e46127110356644eff5249d4b981bdef84763.png

2026-06-12 01:29:05 CEST

- reply

https://cdn.nostrcheck.me/b3f72d3d17184c3e7e9195db5b1bc595f09b8872a6f5e5c2e8feb0961a084192.png

2026-06-11 19:39:25 CEST

- reply

pushed fix... the extension object was being spread, the component Alby injects is most likey a class, that why it was failing to spread, nos2x probably injects an object that can be spread

2026-06-11 17:42:01 CEST

- reply

that makes sense, maybe we can show a toast on first spend that guides users to the preference or does a disclosure
UI polish in the queue, started working with @deSign_r but the internals should make pub/shockwallet the most reliable and likely cheapest option most users have experienced

2026-06-11 17:14:34 CEST

- reply

I had opposing feedback that people wanted to see what they zapped (ex if you send 21, sats show 21 sats, fees in the modal) but that's a good preference toggle we could add to show the total now that you mention it
Bootstrap is for convenience and stacking LSP credit, it's really meant to connect to a self-hosted Pub. Floor 10 is just a safe default for an operation... still much lower than Spark/Ark/Liquid swap services

2026-06-11 17:02:40 CEST

- reply

Paid 12, the floor is 10 or 60bps
Percentage is high because it's small, 1000 sats would have cost 60 sat

2026-06-11 16:51:28 CEST

- reply

Reserve is held for routing fees on LN, amount held must exceed sending since the sender pays
Total fees are shown on the item including service, click one of the outbound payments and you'll see those in the modal there

2026-06-11 16:10:53 CEST

- reply

Should be the fee reserve, it's shown in the send screen