Indeed, to be practical we need to understand the psychology... and that's seeing is believing. A certain cohort cannot be told, they must be shown... and so we can explain the obsession with MoE as being because its more visible.

I think this explains why negotiating people into getting just a few bucks worth has been so successful historically, eventually they "see" green percentages in whatever app... the ever important show me part.

Yes, it's a statechain implementation Lightspark uses to obfuscate their custodial relationship with users allowing them to distribute SDK's to wallet devs who won't KYC users.

The one thing i'll give them is is that they openly admit its trusted in their docs.

The problem is they're lying when they market it as an L2 as if its not trustodial.

Lightning is the only L2

Ark and Statechains have to refer to Lightning as "glue" because they are not L2's themselves

L1 = Payments L2 = Payment Channels

Fin.

Every countries GDP is fake

Reality and the matrix.

This touches on something that I think is the problem with people that expect Bitcoin to be a ubiquitous MoE... It's literal savings technology, yet, the insistence that it be used in the meatspace for coffee to be successful is the Coca-Cola mindset.

Everyone is aware of and uses this pointless cornsyrup water, not because it is useful, but because they spend billions on signage.

Moths to a flame.

No sacred cows

There'd be much, much less.

It's already live in Lightning Pub and ShockWallet, but in a mostly POC state as real users haven't battle-tested it, just internal tinkering.

Feel free to play with it, any and all feedback helps with direction.

The SDK should make it easy enough to make an app that uses it, dev feedback on that would be extremely valuable as well.

The source for the demo is on gh too: https://github.com/shocknet/clink-demo

You didn't base your decision to use it on data that refutes it

You mean operatives and front organization "NGOs"... you don't know who any of these people actually are or who's funding they work for.

SIGINT stops at the border? Client states, intelligence sharing, proxies, fields ops. etc... demonstratively naive to intentionally misleading this is ever mentioned.

Sure about that? you're implying now that it's centralized/censored, and such whitelisting is its own vulnerability.

Literally anything, or nothing in most common LARPy cases.

SSH jumps and SSL tunnels are common for hiding in plain sight in Enterprise/Gov Info/Op Sec.

Blackhats have been known to distribute backdoor tunneling malware.

VPN's are turnkey examples of the former, slightly better incentives with paid services, but ultimately just as likely to be pwned. Really only good for soft-threats like geo-fencing.

Nesting VPNs is doable to resemble Tor with the better incentives, some Bitcoiner actually made Obscura which specializes in that... not an endorsement, I still think its silly.

Good old fashioned wardriving? Burner sims? Whatever street degens do these days.

All that left for Tor is midcurves that think downloading a browser fork or TAILS makes them elite. It's where ego meets laziness.

They're just users, they actually generate on-chain activity when they acquire or liquidate... imagine how much less activity there would be without them.

Assume that roughly half are controlled by Langley and the other half by Ft. Meade, who also has telemetry in your ISP's networking equipment.

There's no reason to believe the middle node and exit node aren't colluding, there's no sybil resistance whatsover, and the fact that it only exists as a "privacy" tool ensures that its a honeypot under constant surveillance.

Anything marketed or spread through the virtue of privacy is inherently less private. This is the privacy paradox.

lol... you mean the laziest

All the events for methods are ephemeral, its like an RPC to simply transport the invoices. Relays that don't offer storage are therefore viable.

(Offer based Lightning addresses are still subject to NIP-05 stored events though)

Yes the offers spec provides an alternative to Bolt12 for use-cases where a static QR code or string is desired, but this is more useful since it's trivially used on the web and Nostr is actually reliable. There's no dependence on Bolt12 at all, in fact, I hate Bolt12 :)

Yes this was designed with subscriptions in mind (push payments), hense the pricing types encoded into the offer which allow for pricing to change over time for scheduled payments. I'll eventually demo the tooling we're building into the wallet and wallet server for this.

The debit side of the spec facilitates a service requesting a payment (pull payments) and give the user one-click ruleset approval.

yo!

I'm actually working on materials for this a bit today, any requests for what more should be in the demo/readme/future videos or otherwise I'd appreciate

First I need to stick this somewhere:

They announced on twitter at somepoint but search is awful, could only find this

Might just be an API endpoint you can switch out for boltz

No, just connecting to it is getting your IP flagged for additional scrutiny

Nothing good can come from using it. Rat poison.

Lightning has always been giant coinjoin, that's why it's so hated by spooks harvesting your xpub through centralized mixers and their privacy larp useful idiots.

As far as your list, I believe Zeus/Olympus now runs its own instance of boltz swaps fwiw.

Delete this, do not connect to Tor for any reason. It's another honeypot by the same spooks harvesting the xpubs of larps.

Yea things like gpt, cursor and Gemini are doing a lot of tricks behind the scenes to make so much functionality available in their bots

I think MCP will eventually enable similarly useful bots to be more distributed and open, but that still has to be built brick by brick

I don't see anything retarded with this follow-up, except from the obvious answer which is that onion messages themselves are retarded. The ending of his post hand-waves that permissionless innovation will solve the "last 20%" and fact it sucks.

Poast.

Would be interested to see a Antonin "The GOAT" Scalia sample for context.

I’m disheartened to see mental cycles as valuable as yours Mr. Beef being used on something like this, onion messages are a terrible thing and beyond saving.

As I have long warned and been vindicated, each hop inherently increases latency and failure probability. This makes OM’s unfit for communication in areas where high reliability and performance are paramount, like payments. Bolt12 has no future because of this.

Anyone who has used Tor can attest to the fact there is no production value to OM’s. To the extent OM’s work on Lightning even conceptually is due only to the nature of the network being a defacto bonding apparatus, any further decoupling from that can only make reliability worse.

Now, Lightning would absolutely benefit from a better overlay network for communication, but that is almost unanimously Nostr. Concerns are properly separated, web comportability allows deprecation of things like LNURL, and identity can be either leveraged trivially or entirely de-coupled based on the use-case.

Better protocols like we’re developing with CLINK solve the node-to-app coordination problem without the unreliable p2p topology. The preceding link demonstrates Nostr static payment offers that retrieve bolt11 invoices from a simple static web page without wasm, and there are also specs for the reverse flow (debits) and a draft for remote management of static offers (app manages offers on a remote node).

The unified interface seems to be it, since a chat bot can manipulate APIs for literally anything, it's becomes the chat bot expands access to otherwise niche algos that couldn't stand alone as there own tool

It's the interface for programs the same way search engines are for the web