Since distributed blockchains / databases are distributed and therefore need partition tolerance by definition, that leaves consistency or availability for the shortfall in computation.
I'm guessing any "crypto-kinda-currency" is picking eventual consistency as a core mechanic. Think about the word EVENTUAL though.
If the core function of the crypto is a ledger, then it makes sense, it EVENTUALLY gets transacted, and in practical terms you take the faith in the distributed system from a flawless previous record in reconciliation, probably before the actual completion of the transaction.
Now, a distributed major blockchain has ... how many nodes? Thousands or more? That is a long time for reconciliation of the consistency, even with great dedicated internal networks. What? This is over a heterogenous global internet network? That implies EVENTUAL has some bad worst cases.
"Smart contracts" or "distributed trustless computation". Whatever, getting the value of calculation from a node and getting the value stored in the node is essentially the same thing in terms of determining an answer to a query.
It implies a horrendous performance, one you have little control over. I don't think Kubernetes is shaking in its boots.
It's interesting Aphyr never does any crypto analyses, although he makes his bones running a test suite. How do you test a scaled cryptocurrency?
I'm guessing any "crypto-kinda-currency" is picking eventual consistency as a core mechanic. Think about the word EVENTUAL though.
If the core function of the crypto is a ledger, then it makes sense, it EVENTUALLY gets transacted, and in practical terms you take the faith in the distributed system from a flawless previous record in reconciliation, probably before the actual completion of the transaction.
Now, a distributed major blockchain has ... how many nodes? Thousands or more? That is a long time for reconciliation of the consistency, even with great dedicated internal networks. What? This is over a heterogenous global internet network? That implies EVENTUAL has some bad worst cases.
"Smart contracts" or "distributed trustless computation". Whatever, getting the value of calculation from a node and getting the value stored in the node is essentially the same thing in terms of determining an answer to a query.
It implies a horrendous performance, one you have little control over. I don't think Kubernetes is shaking in its boots.
It's interesting Aphyr never does any crypto analyses, although he makes his bones running a test suite. How do you test a scaled cryptocurrency?