shocknet_justin
Justin (shocknet) ⚡

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 18:11:20 UTC

- reply

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

2026-07-08 19:18:38 UTC

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 19:11:48 UTC

- reply

Don't get me started on covenants

2026-07-08 19:10:26 UTC

- 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 18:46:21 UTC

- reply

I don't see "self-custody" claims on the website, so that's good.
I do see this:
"Ark protocol is a second layer on the bitcoin network"
That is a lie, Ark is not an L2.

2026-07-08 18:45:06 UTC

- reply

Not true, see other reply about the use-case being Lightning receiving.
The problem is not that Ark/Spark are custodial, the problem is that they lie about it and affinity scam as Lightning wallets.
Better an honest custodian than a dishonest one. Fake L2's are a regression, custody with a crypto-theater scamming.

2026-07-08 18:42:33 UTC

- reply

Perhaps density can get refresh pricing down, but users are still bearing an ongoing cost for idle coins.
Ark/Spark exist to affinity scam as Lightning wallets, so people can receive without a node/channel liquidity. Their product market fit is receiving via Lightning swap.
You could use an on-chain onboarding, but that's also pointless, because if you're already on-chain you don't need a coordinator.

2026-07-08 17:39:38 UTC

- reply

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

2026-07-08 17:35:25 UTC

- 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-08 17:25:53 UTC

- reply

Ark is one of the worst Bitcoin affinity scams to date for sure... Total slop to keep noobs paying 50bps points every few weeks for idle funds that still used custodial swaps to be credited in the first place

2026-07-08 16:14:13 UTC

- reply

You needed the operator to give you the leaves in the first place
#nevent1q…90mm

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-07-06 15:16:36 UTC

- 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 19:23:55 UTC

- 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 21:33:38 UTC

- reply

Dm*

2026-07-02 21:33:29 UTC

- reply

Sent me but I can't sync until Sunday probably

2026-07-02 21:33:06 UTC

- reply

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

2026-07-02 12:15:18 UTC

- reply

NGO paychecks likely a factor too

2026-07-02 12:13:07 UTC

- 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 12:07:13 UTC

- 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 00:51:41 UTC

- reply

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

2026-07-01 21:50:55 UTC

- reply

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

2026-07-01 21:44:33 UTC

- reply

The secret string is the nsec for the connection

2026-06-29 20:04:11 UTC

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

2026-06-29 17:30:48 UTC

- 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 15:30:55 UTC

- 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 14:19:44 UTC

- 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-27 05:50:03 UTC

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 04:18:17 UTC

- reply

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

2026-06-21 20:19:28 UTC

- reply

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

2026-06-20 14:31:07 UTC

- 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 14:23:30 UTC

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

2026-06-18 22:06:35 UTC

- reply

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

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

- 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 01:18:54 UTC

- 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-17 23:11:19 UTC

- 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-17 22:01:25 UTC

- 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 21:55:05 UTC

- reply

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

2026-06-17 20:15:24 UTC

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

2026-06-17 01:04:05 UTC

- reply

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

2026-06-17 00:55:08 UTC

- 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 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:38:23 UTC

- 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-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-16 23:21:28 UTC

- 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-16 23:17:03 UTC

- 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-16 00:53:44 UTC

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-15 22:39:25 UTC

- reply

https://bxrd.app

2026-06-15 22:39:10 UTC

- reply

https://bxrd.app

2026-06-13 21:25:07 UTC

- reply

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

2026-06-13 21:22:16 UTC

- 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 18:48:29 UTC

- 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 15:56:25 UTC

- 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 15:31:33 UTC

- 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 15:17:48 UTC

- 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-11 23:49:26 UTC

- 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-11 23:29:05 UTC

- reply

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

2026-06-11 15:14:34 UTC

- 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 15:02:40 UTC

- 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 14:51:28 UTC

- 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 14:10:53 UTC

- reply

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

2026-06-10 20:49:37 UTC

- reply

Rarely, exit nodes typically trigger fail2ban because they DoS constantly

2026-06-10 20:40:36 UTC

- reply

Looks ok with nos2x, we'll set up an alby to try and repro, thanks for the report
There's no social features hooked up yet so you can just generate a throwaway key in local storage for testing

2026-06-10 20:32:45 UTC

- reply

Bizarre... whats the offer? I'll try to repro
Fixed something potentially related the other day, what's the version code in the bottom of the nav bar?

2026-06-10 20:19:27 UTC

- reply

ShockWallet or Zeus
ShockWallet has as PWA if you want to test on the fly and not install an app: https://my.shockwallet.app
If you already have a wallet connected via NWC it shouldn't matter though, just use the noffer in-app to get the invoice and pass the invoice along.

2026-06-10 19:59:48 UTC

- reply

Indeed, the problem with L2 security is that it is inherently dependent on liveness, since they are multi-party and the chain is the adjudicator that needs to be reached.
If you fight liveness, you sacrifice security, and such a solution is back to being just re-branded trust.
This is why I laugh at these fake L2s, it's not about the L2, the L1 is all that matters, and people beefing on Lightning just don't like Bitcoin.

2026-06-10 18:50:53 UTC

- reply

Yea my framing is in a hypothetical scaling scenario to entertain the "we must scale to 8BN people that don't have any money" virtue signals people use to justify shitcoining.
I personally think that's retarded, but it undercuts these fake L2s re-branding trust and centralization.

2026-06-10 18:04:45 UTC

- reply

Unilateral chain exit is subject to the constraints of the chain itself, not the L2. The gripes about Lightning are because of this, not Lightning itself, beefing with Lightning is beefing with how the chain works underneath it.
Since supply being the only real scaling limitation if we're talking about billions of users, L2's cannot scale sovereignty until the chain does.
You can't unilateral exit millisats if the chain does not recognize millisats for example. No L2 can solve this.

2026-06-10 17:55:39 UTC

- reply

> We can arbitrarily divide on any L2
But you can't offer the chain's security with those, so all roads lead back back to trust and centralization.

2026-06-10 17:49:23 UTC

- reply

Now I feel dumb at math. Great post.

2026-06-10 17:23:17 UTC

- reply

I'll try to use words you can understand.
Bitcoin doesn't cut into smaller pieces. It's uses whole units.

2026-06-10 17:21:04 UTC

- reply

Would you like to get into how Satoshi was an NSA operation and nothing about it's design was just an educated guess? I'm using this thread as an opportunity to fix nextjs bugs on Bxrd.

2026-06-10 17:07:25 UTC

- reply

It 10x's the base unit because Bitcoin doesn't have floating point

2026-06-10 17:06:37 UTC

- reply

Have fun with that.

2026-06-10 17:05:08 UTC

- reply

Yes it does. Bitcoin is the sum of its base units.

2026-06-10 17:04:50 UTC

- reply

Again, Bitcoin doesn't have decimal places or floating point precision.
It's not a math question. It's the reality of how the protocol works.

2026-06-10 17:02:57 UTC

- reply

It is an increase in supply, because Bitcoin is 2.1q.
An increase in base units is not necessarily dilutive.
These are not incongruent.

2026-06-10 17:00:04 UTC

- reply

Those were soft forks, a base unit change i'm fairly certain would need to be a hard one. I could be wrong on that, popcorn ready either way.

2026-06-10 16:52:14 UTC

- reply

I literally just said I'm not talking about dilution.
Dilution was projected by you and low-attention-span guy.
How is this for clarification, "scaling requires a supply increase, but that supply increase doesn't have to be dilutive."
Point remains, it's not going to happen but I got popcorn ready if you want to try.

2026-06-10 16:45:39 UTC

- reply

> could be changed
via a *supply increase* of the base unit
You're talking about *dilution*, like the other guy, which I never said. I'm being literal, factual.

2026-06-10 16:44:13 UTC

- reply

Your short attention span is probably why you don't know Bitcoin's basic properties yet feel compelled to opine.
Must be tough.

2026-06-10 16:40:59 UTC

- reply

It is an inflation of supply, 2.1q base units to 21 210 or whatever is an increase.
You said dilution, not me. Comprehension fail.

2026-06-10 16:37:00 UTC

- reply

Bitcoin does not have millisats.

2026-06-10 16:36:16 UTC

- reply

Chain transactions are done in sats. There are no decimals in Bitcoin, it does not have floating point precision. The base unit is sats, there are 2.1q of them.
A UI rendering 100 sats as .00000100 Bitcoin does not change the fact Bitcoin is using sats, not decimals.

2026-06-10 16:34:46 UTC

- reply

Bitcoin doesn't have decimal places, understand this. Division is not at thing in Bitcoin.

2026-06-10 16:32:40 UTC

- reply

No, you are. I never said dilution.
I said a supply increase. The base unit is 2.1Q, if you want *more* base units, thats a *supply increase*.
More = supply increase
Very simple concept to grasp.

2026-06-10 16:30:14 UTC

- reply

Bitcoin doesn't divide, shitcoiner education is failing them.

2026-06-10 16:27:50 UTC

- reply

Bitcoin doesn't have decimals, it has sats. "Whole coins" are an abstraction, a Bitcoin is 100M base units, sats.
You can't add abstracted decimal places without a supply increase of the base unit, which would break every piece of Bitcoin software ever created... it's not going to happen.
2.1q sats -> 21q usats or whatever is a 10x supply increase. The hardest fork imaginable.

2026-06-10 16:23:25 UTC

- reply

Not on-chain they don't, you don't seem to understand the difference between internal accounting and actual Bitcoin, maybe why you think a shitcoin like Liquid is Bitcoin...

2026-06-10 16:21:17 UTC

- reply

No you can't. Adding decimals in Bitcoin is a supply increase, a change in the base unit, not going to happen.
msats in Lightning aren't resolvable on chain, they're shitcoins used for internal accounting/rounding... they aren't units of actual Bitcoin.
You really don't know what you don't know...

2026-06-10 16:13:38 UTC

- reply

This is Bitcoin 101 fella, it's not divisible at all.
2.1quadrillion sats.

2026-06-10 16:12:40 UTC

- reply

There's no capital requirement, its literally just re-usable transactions you'd already make.
Lightning nodes have faced traditional web server friction, Pub solves that, there's a lot more people using them today than there were yesterday because CLINK doesn't have the friction of LNURL.
You can bitch about Lightning as much as you want, that's fine, but it doesn't change the fact there are no solutions to be had. Smuggling trust and centralization are not solutions. Understand this.

2026-06-10 16:07:54 UTC

- reply

It's a mathematical fact 8BN cannot use Bitcoin, they have to trust someone to use it for them, because it's not divisible and chain representation has a minimum.
Ark is a scam from the bottom up.
What you believe and what are true can be separate things. I acknowledge reality and focus my energy on what is possible, not cope and virtue signals.

2026-06-10 15:59:08 UTC

- reply

Actually if you dont have a CLINK Debit string it should just show the invoice for scanning... just confirm you're auth'd...

2026-06-10 15:58:14 UTC

- reply

In settings add a CLINK Debit string to connect to a spending wallet. It will take the invoice from the noffer and pipe it over to the debit connection.
If you already did that, are you signed in with an extension? there was a bug with those but was fixed...

2026-06-10 15:55:38 UTC

- reply

> There are no solutions. Only tradeoffs
Exactly. Those trade-offs are trust and centralization, which are all fake L2's can offer.
You cannot handle 8 billion people without trust and centralization, that's a function of the supply cap / dust + non-zero fee required for chain security. Bitcoin scales to 100-200M at most, less as large accumulators remove float, that's purely on lack of divisibility alone and has nothing to do with tx density.
8BN is also not the goal, that's retarded. Not even 8BN have internet or phones. There are only 300MN businesses and maybe 1BN households.
The only tradeoff lightning makes is liveness, which is how the internet works. That's a hard requirement for anything but the base chain.
It's a fact that trust and centralization are the only levers, but if you want to beat your head against the wall denying reality like shitcoiners do have fun I guess.

2026-06-10 15:40:26 UTC

- reply

Based, let me know when I should add it to the apps lists.

2026-06-10 15:34:33 UTC

- reply

I personally recommend an old laptop, but if someone chooses to use a VPS that's still better than Blockstreams centralized swap API.