News for hackers. Stuff that matters.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by NelsonMinar on Saturday February 05, 2022 @10:50AM (#30222223)
I admire aphyr's ability to dive into a new and complex distributed systems technology and understand it enough to evaluate it for correctness. I hope the Radix developers have ears to listen, the comment in the report "RDX Works informed Jepsen that the blockchain/DLT community had developed idiosyncratic definitions of safety and liveness" is not encouraging.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by daenney on Saturday February 05, 2022 @11:23AM (#30222619)
> To Jepsen’s surprise, RDX Works asserted that phenomena such as aborted read, intermediate read, and lost writes do not constitute safety violations (in the blockchain sense). RDX Works claims that to describe these errors as safety violations would not be understood by readers from a blockchain background; this report is therefore “factually incorrect”. On these grounds, RDX Works requested that Jepsen delete any mention of our findings from the abstract of this report.

That certainly does not inspire any confidence.

> Jepsen respectfully declines to do so.

Thank you for sticking to that.

Re:Jepsen: Radix DLT 1.0-Beta.35.1 by Mleekko 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.

Re:Jepsen: Radix DLT 1.0-Beta.35.1 by daenney on Saturday February 05, 2022 @12:33PM (#30223452)
Sure. But they could have asked for the additional clarifications or context to be added to make this clear, instead of requesting a bunch of stuff be removed because they’re concerned it’ll paint them in a bad light.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by faraz85 on Saturday February 05, 2022 @12:36PM (#30223484)
As I understand from the report, no request was made to remove the content but to leave terms like "liveness break" and "safety break" out of the abstract until those terms were defined in the main report.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by aphyr on Saturday February 05, 2022 @12:45PM (#30223574)
You understand incorrectly.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by exdsq on Saturday February 05, 2022 @07:09PM (#30227786)
Did you even read the report aphyr?

/s

Re:Jepsen: Radix DLT 1.0-Beta.35.1 by moby_click on Sunday February 06, 2022 @07:18AM (#30231851)
I don't think readers with any kind of computational background expect to read FAILED writes. Apparently, neither does RDX Works - claiming to have fixed most of the issues.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by belter on Saturday February 05, 2022 @02:10PM (#30224661)
Jepsen is the Carl Jung of Distributed Systems...
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by faraz85 on Saturday February 05, 2022 @12:13PM (#30223236)
Pleased they ignored that request too, although I can see where RDX are coming from. In a distributed ledger it's all about state. The consensus layer of the architecture is rock solid according to this report.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by aphyr on Saturday February 05, 2022 @12:37PM (#30223491)
The core ledger system lost committed transactions by choosing not to write them to disk before acknowledgement.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by Mleekko 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 by NelsonMinar on Saturday February 05, 2022 @12:52PM (#30223643)
Well, Radix says it is fixed now. That's the gist of their response to this report, "we fixed a lot of things and no one's tested the new code but trust us!"
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by Mleekko 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 by Too on Sunday February 06, 2022 @01:55AM (#30230115)
Isn't this is a rather common configuration for a distributed DB? Given one node dies before flush, you trust that the remaining nodes in the system will not die at the same time and live long enough to flush to their respective disks. It's a gamble yes, but depending on your environment the risk can be smaller than the benefits. For a blockchain ledger, you might want to choose the safer corner of CAP in that equation.
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by zbentley on Monday February 07, 2022 @12:58AM (#30240967)
> Isn't this is a rather common configuration for a distributed DB?

In my experience it is not. Rather, aggressive fsyncing/O_DIRECT usage are common. The rationale for this is usually partition risk: better to durably log a write before propagating it than to potentially fail in propagating it and then be left in a position of having to either reactively fsync or hope that automatic flush-to-disk will persist your unexpectedly-sole possession of that update.

Re:Jepsen: Radix DLT 1.0-Beta.35.1 by Smaug123 on Saturday February 05, 2022 @01:41PM (#30224274)
> The consensus layer of the architecture is rock solid according to this report.

That's quite a stretch. The report states explicitly a) the usual proviso that they can only prove the presence of bugs, not their absence, but more pertinently b) that their methodology is more usually applied to lower-latency databases, with the implication that they are less confident of their conclusions in this new regime:

> Radix’s low throughput and high latency may have masked safety violations. In particular, our tests required several hours to reproduce e.g. aborted read (#13).

Note also that they didn't even attempt to test what happens in the presence of malicious nodes!

Re:Jepsen: Radix DLT 1.0-Beta.35.1 by smw on Saturday February 05, 2022 @12:57PM (#30223705)
Are you (new account) failing to disclose your conflict of interest here?
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by faraz85 on Saturday February 05, 2022 @01:04PM (#30223783)
Happy to share I'm an advocate of this project and follow its developments closely
Re:Jepsen: Radix DLT 1.0-Beta.35.1 by xwolfi on Sunday February 06, 2022 @04:07AM (#30230697)
You're also financially involved, akin to a franchisee or a "member" in an MLM, and make money on providing staking services on this blockchain. It's fine, but it's important to put your comments in context: you will always tend to defend your overweight investment in this pyramid, while I never heard of it til today.

One of your recent-ish blog article for instance, that contrast (commercial vs technical) with the Jepsen report: https://www.radstakes.com/post/airdrops-incoming-radstakes-p...

And your statement of the 2% fee you seem to take on every staking: https://www.radstakes.com/post/radstakes-year-end-report

This report will not help your business, but you should pressure RDX Works into doing a new one on the next version rather than convince us we didn't read properly some quite shocking things in the first one :s