21 sats \ 0 replies \ @justin_shocknet 3h \ on: Troubled waters - more events impacting our access to water 📊 charts
I remember the climate change psyop in public school decades ago now where they once brought in a touring speaker to tell us that India and Pakistan would go to war over water...
And that we should be extra scared because both are nuclear armed countries...
My dad being a Navy veteran, I asked why they don't just use nuclear-powered desalination like are used on Navy vessels...
CLASS DISMISSED
I believe in that scenario, the current state is up to the task,
Digressing, I also think that's the case now and not a hypothetical. My thesis is Bitcoin is a white-hat psyop by NSA/military intelligence to save America from the Triffin dilemma and inevitable global reserve collapse. We're just watching this op, among many others, like a movie🍿
In any event, US adoption ends in it becoming a foreign reserve backing the dollar, the US Treasury and it's foreign peers basically becoming giant ECash mints (see ECash Act)
Why is this path inevitable? Because anything else requires destroying Bitcoin as we know it. No scaling proposal can accommodate the ridiculous hypotheticals of ~8BN people using it to buy coffee self-custodially and remain Bitcoin. At best, we're talking a peg, with a weaker form of consensus.
We already have pegs without destroying the base layer, so there's no rationale to add risk to the base layer because a peg is inherently a downgrade.
Reasonable scaling improvements (optimization within current design space) are marginal by comparison so they tend to not be as exciting. They are also unquantifiable until they are actually needed- and we have the real data necessary to quantify them.
Scalooors like Paul and the CTV clowns do a disservice by taking resources away from projects that want to get us to that very achievable milestone of 1BN users.
"At all costs" means introducing a new consensus that is not Bitcoin, basically a shitcoin "pegged" to Bitcoin that introduces unknown incentives into Bitcoin itself through a potentially deleterious fork.
The counter-evidence is the fact that fees are still only 10% of block subsidy, and they're not even in an up-trend despite FUD over things like jpegs.
There's also nearly 0 new demand for self-custody relative to adoption. This is evidence we've reached a self-custody maximum, not because it's expensive, but because Bitcoin isn't here to obviate credit.. it's a measuring stick against the Cantillon effect of central banks with added systemic optionality.
Anyone interested in self-custody has had ~15 years to decide that. Hell, even the fake maxi's on Nostr are mostly ECash simps these days. New adoption is going to off-chain governance, like ETF's and Corporate Treasuries.
Even 10s of millions in Liquid astroturf marketing can't find a meaningful userbase.
Reality is Bitcoin is NGU tech first and foremost, as much as Agorist-minded folks like myself would like to see more means of exchange.
Now, hopefully the observations supporting a self-custody maximum are misleading, and new tools (like those I'm working on for that matter) re-accelerate self-custody and make it viral as MoE... But even then Bitcoin could still onboard a billion to Lightning with existing batching tech. The knocks on Lightning today are largely downstream of the high-time-preference stupidity and wastefulness of mobile nodes. Just imagine how much more efficient Lightning will get when bozo's aren't buying unstable channels tied to one mobile device.
At the end of the day, the scale ceiling is nowhere in sight, so the conclusion we must draw is that it's a red herring being exploited by scammers with the help of of their virtue-signaling useful idiots.
PS is a one-man cult, many analogues to the CTV cult but at least CTV'rs generally admit they're grug brains shilling something too esoteric for them to understand themselves.
Scaling frauds like Paul somehow stay in the roadmap conversation anyway because there's some built-in virtue signaling element to saying we must scale at all costs, despite a preponderance of counter-evidence.
But clearly, these scalooors must love Bitcoin and poor people more than anyone.
Fact is that every scaling proposal requires baseless assumptions about demands and wild speculation on utility. It's sad how much attention this recycled garbage gets any time someone has to pay a slightly higher fee than they did a few weeks prior.
bug bounties or processes
I think this is more cultural than needing to be specifically outlined in OSS. The majority of eyes on decentralized/oss are the users of it.
Is this person equally concerned with the supply chain as well? libs, operating sytems, and so on?
a red team sponsored for the lightning network
Based on all the Lightning FUD that comes from grantees, competing initiatives to Lightning are that by default.
There's disincentives at work in a sponsored red team model... at least a bounty or successful attack is based on results
Implementations are also not the network, who's to say whom Lightning Labs or Blockstream hire for review in private?
more projects like lnsploit being sponsored
Maybe because no one uses this one in the first place?
concept of a red team was new to me
Probably because it's antiquated, was more of a closed-source commercial thing. Who needs it more? Microsoft or Debian?
real attackers are already incentivized
That and not just from he honeypot aspect, FUD as mentioned above is incentivized by competition... and its already a david .v goliath battle.
best preparation for a war is being attacked by your enemy
The only alternative is fighting the last war
We want well financed good guys attacking bitcoin, right? Is that a bad idea for some reason, or is it just not necessary?
Seems like the wrong question unless we assume resources are infinite? Assuming not, should it be a higher priority? Empirically there seems to be little to no justification for it.
Federated Lightning Addresses for Mutiny+ Users
Hoax. There's no such thing, the webserver serves any invoice it pleases... makes you wonder what else they misrepresent
You could run your own server, but that's pointless, just run a real node instead of some constantly offline mobile nonsense
Imagine being clued in enough to know about lightning and not know Tor is a useless honeypot probably run by Intel agencies
The same people that fall for traps like Tor fell for traps like Samourai... Enjoy your FISA warrants
If you really cared about obfuscating your IP address you wouldn't flag yourself by using something so stupid, there are countless better ways
Considered writing up something but I can't think of any pros...
Proponents will say it's more private, but that's a hoax since all the privacy features are already happening separately
It can obviate lnurl-pay web servers, but so does nostr via lightning.pub or AMP
I guess it's good if you're a Neobank/shitcoiner since it's really meant for ECash
I guess it's good if you're the state and want to bifurcate the network effect of lightning as a means of exchange (attack)
The retro-futurism is on-point...
Retro because it's basically a re-implementation of Tor
Futurism because it's destined for the same fate, slow and unreliable and overrun with shitcoiners
That's solid, id consider that stationary still.. they both use LND, you've found a nice workaround for hardware... Battery safe like a laptop but low footprint like a raspi 🤌
It can work but only with lightning.pub or LNC to a stationary node, mobile nodes will be extinct soon™️
taxes on production is bad for production
inflation forces savings into production which produces the wrong things
taxes on consumption slows velocity (good for inflation) but is bad for government revenues
So, I'd go with the unlisted option, lock down the economy with a fake pandemic to save the currency for an election cycle through inflating away some debt without increasing velocity
31 sats \ 0 replies \ @justin_shocknet 28 Apr \ parent \ on: Idea for future "Bitcoin businesses" bitcoin
💯 plebification WIP
Thanks for the mention.
Lightning.Pub isn't packaged up nicely for people averse to the command line quite yet, given the stage of development, but we are looking at packaging and distribution over the next month or so. Folks should stay tuned!
As you mentioned, the goal of the project is to make running Lightning infrastructure for your friends/family/customers easier than previously thought possible.
It may come as a surprise that the biggest hurdle to more Uncle Jim's hasn't been with Bitcoin/Lightning node management itself, that's easily automated as illustrated by bad patterns like mobile nodes.
It's the legacy baggage of traditional web infrastructure, things like IP4 reverse proxies, DNS, Firewalls and SSL certificates, all which require a personal configuration that is a hurdle for most.
We've solved that with a Nostr native RPC, and have some reverse SSH services in the works for backward compatibility with LNURL.
ShockWallet (also a dev alpha) is our reference client, you can experiment with today and not just with a Pub back-end. LNURL accounts can be added to the wallet as well.
Any would-be tinkers should feel free to reach out if they need some help getting started, helping you helps us to know where frictions lay.
There's nothing I want to see more than millions of family lightning nodes (not on a damn phone!) causing the deep state a fit as Bitcoin becomes the dominant world-wide Means of Exchange.
Ignoring the law for a moment... as a business you should not want custody just because we're dealing with hot wallets... customer funds WILL be stolen or otherwise lost because software isn't perfect. WHEN (not if) that happens, it could end your business or worse, your reputation.
Custodial is in the end, and the only business in it is regulatory arbitrage based on faulty risk assumptions.
Everything about the service they were running was bad, he's probably lucky he was spooked off of it before something really bad happened.
We had a similar exploitation of new features last month with Lightning.Pub, drainage attacks are constantly being attempted on any public facing Lightning API. This has set us back several months (not to mention runway from what was looted) focusing on additional hardening.
Such attacks usually cost something to attempt (deposit first then over-withdraw), and so this is yet another reason you should to self-host because obscurity can be a last line of defense.
The higher profile a service is, the more likely it is where new vulns will be found.