[dartos]

At the end of the day, web3 is just the web with a new payment processor (a blockchain)

That payment processor just has no support, no UX team, no security team, and nobody to hold accountable.

It’s actually a more trust based system than what we have. Instead of trusting a single payment provider, you need to trust a wallet extension, the website you’re on, and the contract you’re interacting with.

Any failure in judgement is also irreversible.

It’s just a really bad solution to a problem most people don’t even know exists.

[hnbad]

Web3 is more than that because some people genuinely thought the future was running actual code on the blockchain and using that as part of the backend. Of course that works reasonably well as long as your code is terse, straightforward, trustworthy, easy to read, bug-free and you have no performance requirements for execution speed or deployment speed.

[dartos]

> thought the future was running actual code on the blockchain and using that as part of the backend

What did that code do besides process transactions and distribute tokens?

Almost nothing.

It’d be the payment gateway layer of any backend. Processing payments and returning proof of purchase.

[zelphirkalt]

So almost never?

[hnbad]

That's the joke.

[zcw100]

...and the crypto it's based on. ...and it's implementation.

I can't wait for the biggest bank heist in history due to an exploit in a crypto algorithm.

[javier2]

I suppose one could argue that has already happened multiple times?