[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

Search:


View post   

>> No.54329317 [View]
File: 223 KB, 2048x1447, HBAR_LAMBO.jpg [View same] [iqdb] [saucenao] [google]
54329317

>> No.52843201 [View]
File: 223 KB, 2048x1447, HBAR_LAMBO.jpg [View same] [iqdb] [saucenao] [google]
52843201

>> No.49722021 [View]
File: 223 KB, 2048x1447, HBAR_LAMBO.jpg [View same] [iqdb] [saucenao] [google]
49722021

>>49720362
Now listen because I'm only doing to explain this once.
Consider the following query:
UPDATE TABLE accounts WHERE number=123456789 SET balance=0;
The problem with that query is that it destroys the prior information about the balance of account #123456789.
That's all fine and dandy until you run into the situation where this query was not supposed to happen: bug, human error, hacking, whatever.
Because once this query is done, there is no way to to prove that account #123456789 ever had a non-zero balance.
So this is why the blockchain(*) is interesting, because it can give you STATE PROOFS. All it takes is taking a hash of the table or some rows, and submitting a blockchain transaction.
Also it logically follows, that the more fine-grained a state proof is, the more useful it is.
(E.g. a state proof generated for each transaction is more useful than a state proof generated once per hour and so on.)
And the only blockchain (*) which can provide a large number of state proofs affordably is Hedera.

(*) Yes, I know Hedera is a hashgraph, not a blockchain, fuck off.

Navigation
View posts[+24][+48][+96]