> Because literally the only point is to avoid the existing banking system and you can do that with a postures database with much less cpu involved.

Ethereum is actually very low resource intensive nowadays.

You can run a validator node on a RPI, a full sync node on a Intel N100 minipc with a big fast SSD and the "light clients" can probably run on something very small.

I have seen banks having to bring semi-trailers full of diesel generators to plug them to their mainframe because the current requirements were too high for the grid during big batch jobs.

▲

ChadNauseam 5 days ago | parent | next [-]

I like crypto (I'm formerly in the industry), but that's not quite a fair comparison.

1. Running a validator is inexpensive in terms of compute, but there are 1,000,000 validators or something, which adds up to a lot of CPU usage. Of course, I think it's insanely awesome that you can run some code on Ethereum and it'll be replicated on 1,000,000 independently-operated machines, but it's not a very CPU-efficient strategy. 2. Banks doing those batch jobs probably had much higher TPS than ethereum.

	▲	sunshine-o 5 days ago \| parent [-]
		> Banks doing those batch jobs probably had much higher TPS than ethereum. Yes the platform running in most banks, usually built on what we call "mainframes", is still mind blowing and with incredible performance. Also just one of those CPU is about the price of a house... Also the requirements I cited is for running an Ethereum mainnet "Layer 1" node. And most "TPS" happens on the layer 2s anyway. So it is hard to compare technically. But one thing for sure is becoming an active participant in the Ethereum mainnet has a very low barrier. They got rid of the whole intensive "Proof of work" part about 5 years ago. For a full sync node the waste is more at the bandwidth and disk levels.

▲

topranks 4 days ago | parent | prev [-]

Just because they ditch the proof-of-work doesn’t make it efficient.

The blockchain structure, the validation mechanism etc are still a very inefficient way to do general compute or database type functions.