Mleekko
Re:Jepsen: Radix DLT 1.0-Beta.35.1
on Saturday February 05, 2022 @03:37PM (#30225707)
It's not a secret at all.
The response from the Radix CEO: "We re-used the part of his testing harness, and then re-created the other critical tests to determine if the errors detected where still present. He is fantastically expensive and booked 3-6 months in advance on average. We'll definite re-deploy this kind of testing again, but we'll save it for another bigger release, rather than a patch where the identified errors can be tested against."
Re:Jepsen: Radix DLT 1.0-Beta.35.1
on Saturday February 05, 2022 @01:04PM (#30223782)
nope, if you read it one more time, for this particular issue Jepsen confirms the fix.
Re:Jepsen: Radix DLT 1.0-Beta.35.1
on Saturday February 05, 2022 @12:42PM (#30223544)
Yeah, the issue is serious but at the same time:
"This problem occurred only in cases where every node was killed at roughly the same time".
And there are 100 nodes on the network.
(and it is fixed now)
Re:Jepsen: Radix DLT 1.0-Beta.35.1
on Saturday February 05, 2022 @12:13PM (#30223231)
What Radix say is true though.
In private DBs, reads from the DB node are considered transactions and need to follow the same rules as writes. But on public blockchains(ledgers) only state manipulation is what matters. For example, Metamask obtaining an address balance would be a transaction, but no one calls it that way because it doesn't modify the state.