"Transformers are necessary to make the AC system work."
This isn't quite wrong but the motivation is backwards: AC is necessary to make transformers work.
1. All grids need to move energy at high voltage and low current to minimize losses.
2. This requires a mechanism to step voltages up and down for transmission.
3. In 1890 the only such mechanism was the transformer.
4. Transformers only work on AC, not DC.
Hence our legacy grid is AC.
Nowadays we have an additional mechanism: Power electronics. Power electronics work on both AC and DC, so transformers with their huge requirements for copper and steel are no longer necessary.
We need to accelerate the transition of our grid to DC because DC grids are simpler and cheaper than AC grids.
Grid-scale power electronics are also extremely niche and expensive, perhaps moreso than transformers. HVDC is used where it has a significant advantage, but ease of conversion is not one of those.
> so transformers with their huge requirements for copper and steel are no longer necessary.
smelting some copper and steel and wounding it up is far, far, far, far cheaper than replacing it with power silicon(which might be smaller, but overall needs tons more of energy to produce)
It will be also less reliable. Transformers deal with any overload far better and routinely run for like 50+ years
Exactly. Your rocket can escape the earth at the speed of a slow elevator if you burn the engines continuously and you can carry an infinite amount of fuel and your fuel weighs nothing.
Since those constraints are impossible to meet in the real world, we have to get going fast enough to coast most of the trip on inertia after the fuel runs out.
I call this odious practice "profit maximization titration" and almost all companies do it now. They continually enshittify the product a little at a time until they notice a dip in profits and then they dial back the shittiness a bit. Or if they're really sophisticated they will enshittify the product by a large amount and then do a binary search to restore product functionality in logarithmically smaller steps until the balance between profits and customer dissatisfaction re-stabilizes. They 'git bisect' the product's shittiness, as it were.
There was a strong corporate cultural component to Fukushima as well. Tepco had spent decades telling the Japanese public that nuclear power was completely safe. A tall order in Japan obviously, but by and large it worked.
During the operation of Fukushima Daiichi, various studies had been done that recommended upgraded safety features like enlarging the seawall, moving the emergency generators above ground so they couldn't be flooded, etc.
In every case, management rejected the recommendations because:
1. They would cost money.
2. Upgrading safety would be tantamount to admitting the reactors were less than safe before, and we can't have that.
It amazes me that companies are developing proprietary IP with somebody else's cloud-based AI that ingests and learns from everything that they type and it generates.
These companies are paying for the privilege of having their IP stolen.
With the Lightning network, L2 is basically a database between only 2 parties that are required to be online during the transaction. It's not possible to double spend in that situation.
There's the possibility of double spending by committing to the bitcoin blockchain an old version of your "database", but then you would face the penalty of having your entire balance confiscated by the other party.
> but then you would face the penalty of having your entire balance confiscated by the other party.
Only if the other party notices in time that you did this. You are reliant on active monitoring of the blockchain to know that your transactions actually happened. And the more you want to scale (i.e. the more transactions you do on a single Lightning channel without settling it on the BTC blockchain), the bigger the risk becomes.
Yes, but as long as you monitor, double spending is not possible. And it's possible to use tools to do that somewhat passively.
There are conditions on every payment system. With bitcoin you also have something to do to prevent double spending: wait for some number of confirmations (and making sure you're on the right chain).
And "double-spend protection guarantees of blockchains" is very dependent on the cost of doing a 51% attack, so it's not strong by itself. It's very strong in bitcoin only because the quantity of hashrate/money required to do one is astronomical. It's not so strong on small blockchains.
And I fail to see how the risk increases with more transactions on a single lightning channel.
My point is that Lightning has additional failure modes that BTC does not, and Lightning in itself does not offer the guarantees that Bitcoin does. It of course also suffers from all of BTC's failure points - if someone successfully does a 51% attack on BTC, they can implicitly also steal any Lightning funds as well. If you close a Lightning channel and then don't wait for enough confirmations, or you broadcast your cheating transaction and don't wait for enough confirmations, you can clearly lose your money.
The risk doesn't increase with the number of transactions on a channel, that was a wrong statement from my side. What I was thinking of is that the risk increases the more your transact through Lightning instead of regular BTC. Basically, the more of your BTC is caught up in Lightning channels, the higher the value of attacking you with a double spend attempt.
This is automated, no one is proposing to manually look at BTC blocks to see if you are getting cheated. The problem is that you need to explicitly run code constantly to check if this happens - which means that if your monitoring agent goes offline for any reason (which an attacker could perhaps force), your BTC that you received in a Lightning channel may be stolen.
Okay, so it's an attack vector but one that can be mitigated against by implementing redundancy.
I would argue that Lightning's biggest security issue is having to store your private keys on an Internet connected device. I don't know if further improvements can be made in this area, for example allowing for some kind of 2FA, like multi-sig on the base layer.
I thought it was interesting that BSV seemed to scale just fine, and you could also store entire files on it, including JSON, HTML or even music or videos.
This seemed like an amazing innovation to me, made even more amazing by the fact that it was, by all accounts, the original protocol.
You could do some pretty amazing stuff with it, for example store a SPA on chain and then store individual posts on chain, and have the SPA read the app.
Unfortunately, the ecosystem was completely greed focused, and nobody is interested in technological advancement in the slightest.
>BSV seemed to scale just fine, and you could also store entire files on it, including JSON, HTML or even music or videos
This doesn't pass the sniff test. Everyone must store the full blockchain in order to verify it. So to run a full node you would have to store everyone's JSON, HTML, music, videos. Full mirroring for every node in a distributed system is about as close as you can get to the definition of doesn't scale.
I should note, the scaling I was referring to was transaction processing. Data storage is a little different.
The architecture which I heard described or hypothesized was more akin to Amazon deep storage. More frequently accessed data would be more accessible on "hot" nodes.
Full nodes would effectively, under this paradigm, become cloud storage providers. As a bonus, the problem of how to charge for access is basically already solved, and does not require a complex corporate payment scheme.
Indeed. Bitcoin's blockchain grows with a laughable 3kB/s, yet is an unwieldy 700 GB.
A blockchain that allowed you store one song per second would be hundreds of TB before long. There are other architectures for that sort of thing for a reason.
Looks like BSV is about 7TB and grows at about 4GB a day. I have no clue what those guys are up to these days. This may be unweildy for a home PC but really is still pretty trivial for a data center.
500 hours of video is uploaded to YouTube per minute which is... If my napkin math is right, about a petabyte a day.
Looks like the max they've done is something like 22k TPS. No idea how accurate this is, I don't follow the ecosystem. There's a lot of different numbers like "maximum theoretical potential" that probably ly mean nothing.
> Note to oligarchs: a post-apocalyptic world is no fun. Not even for you in your bunkers.
It's amusing to me that oligarchs don't seem to understand that if the economy goes to hell, their private security forces will just leave (or worse!). What do they think they will pay salaries with? Bitcoin? Do they really think an army of robot dogs is going to protect them?
Warlords exist in the poorest of economies. They have made the calculation that they should hedge for collapse and attempt to establish themselves for that situation.
Could you please stop posting unsubstantive comments and flamebait? You've unfortunately been doing it repeatedly. It's not what this site is for, and destroys what it is for.
Here in New Mexico there's a long tradition of flat-roofed adobe house construction; the materials are abundant and it insulates fairly well (by the standards of the 1700s). But the roofs always leak because snow and rain don't immediately run off. Yet even though we now have modern building materials readily available, a lot of faux adobe still gets built especially in wealthy neighborhoods.
We have a saying: "New Mexico is a place where poor people want to live in a modern house with a pitched roof and rich people want to live in mud huts."
The only one I found that was truly battery-powered was the Makita [0]. The $99 Cuisinart I found seems to be a standard electric kettle. Lots of kettles describe themselves as cordless but that does not mean battery-powered; it just means the kettle itself can be removed from a corded base.
I also found a ton of AI-generated link spam pages purporting to be about battery-powered kettles that are all clearly not battery-powered (e.g. [1]). Some of these are 12v powered, but they still contain no batteries. Apparently the adjective cordless confuses AI just like it does people.
Side note: Boiling water takes a lot of energy. You need a big battery; not just a couple of AAs. Any truly battery-powered kettle is going to require a battery at least as big as one for a contractor-grade power tool, and that battery is going to deplete after roughly one boiled pot.
This isn't quite wrong but the motivation is backwards: AC is necessary to make transformers work.
1. All grids need to move energy at high voltage and low current to minimize losses.
2. This requires a mechanism to step voltages up and down for transmission.
3. In 1890 the only such mechanism was the transformer.
4. Transformers only work on AC, not DC.
Hence our legacy grid is AC.
Nowadays we have an additional mechanism: Power electronics. Power electronics work on both AC and DC, so transformers with their huge requirements for copper and steel are no longer necessary.
We need to accelerate the transition of our grid to DC because DC grids are simpler and cheaper than AC grids.
reply