But with multiple parties involved, who has the rights to read and write to the postgres instance? How do we make sure transactions were not forged? How do we know data at rest is not being tampered with?

Blockchain solves that. Newer blockchain protocols especially an L1 is much faster, easier on the environment, and provides all the immutability, transparency, and traceability benefits.

▲

oblio 6 days ago | parent | next [-]

You know you can just use regular cryptography to validate data, right?

Also, you always have to trust someone, in this case Stripe.

Regarding L1 blockchains, how exactly do they solve the speed problem for a distributed global database that needs to be replicated everywhere for the security guarantees to actually work?

What do they forgo out of https://en.m.wikipedia.org/wiki/CAP_theorem ?

▲

packetlost 6 days ago | parent | next [-]

Pretty much always A. In systems like this, it's better to deny transactions than allow inconsistencies.

▲

jekrb 5 days ago | parent | prev [-]

non-potatoe hardware and elbow grease in the software https://github.com/anza-xyz/agave

	▲	oblio 4 days ago \| parent [-]
		Is there a white paper for what would be a revolutionary discovery in the field of software?

▲

topranks 4 days ago | parent | prev [-]

We need to trust those running the system.

Societies cannot function without trusted intermediaries, in finance and many other things.

If we are in a democracy then the government regulates such organisations and should punish those who do not comply.

Blockchain doesn’t scale as a replacement so the point is moot.