stateright VS solana

stateright - which is meant for distributed state machines and includes a full on model checker

Stateright.

Author seems to be using https://github.com/ailidani/paxi for actual implementation and proof.

I'm more of a python/rust guy. There have been some attempts to make model checkers in rust: https://github.com/stateright/stateright

The issue is that rust is a very large language and it's hard to get it right.

I have a python implementation of raft over here:

https://github.com/adsharma/raft/tree/master/raft/states

That's small enough to be self contained and perhaps run through a model checker some day and transpiled to many statically typed languages.

The issue with TLA+ proofs such as:

https://github.com/fpaxos/raft.tla

is that it's hard to tell if a particular C++ or Rust implementation conforms to the spec.

So how do we check and transpile?

* https://www.philipzucker.com/Modelling_TLA_in_z3py/

Why make memory safety the exception? For example, https://github.com/stateright/stateright implements model checking for distributed systems at the library-level. If you could achieve the same effect with memory safety through the ecosystem, why wouldn't you?

Regarding the last point — correct, Stateright aims to verify both.

It’s important to clarify that this doesn’t provide a proof of correctness, but it can dramatically improve confidence in both the design and implementation compared with fuzz testing, for example. This is done by exhaustively enumerating possible nondeterministic outcomes (e.g. due to message reordering) within specified constraints (e.g. up to S servers and C clients performing X operations…).

Examples:

SD Paxos: https://github.com/stateright/stateright/blob/master/example...

ABD (linearizable register algorithm): https://github.com/stateright/stateright/blob/master/example...

I believe they meant this: https://github.com/stateright/stateright

Solana (9700 GitHub Stars) https://github.com/solana-labs/solana

EIP Core standards: Changes to Solana’s core code go through “feature gates” in the Solana repo. Yes, it’s much less organized than the EIP pages you are used to, and a headache to understand or keep up with. A cost of the speed of development, I’m told.

I visited the project on github (https://github.com/solana-labs/solana), and tried to get an overview of the ~800 open issues and ~100 open PRs.

Solana

With the introduction of new and advanced blockchain platforms in the Web 3.0 scene, the narrative around Ethereum has slowly shifted towards its younger “Ethereum Alternatives”. Solana, Avalanche, and MultiversX (former Elrond) are some of the crypto blockchains that are given this terminology, as they share similar features but are comparatively cheaper and better than Ethereum.

I understand this initiative is connected with Solana network [1] in some way?

[1] https://solana.com/

They do, actually: https://github.com/solana-labs/solana/security/policy

Not sure I understand your question, but if you want the source code you can find it on github (https://github.com/solana-labs/solana)

Some topics that may be discussed in the next call include @ShinobiSystems Timely Vote Credits proposal (https://github.com/solana-labs/solana/blob/master/docs/src/proposals/timely-vote-credits.md), @elusivprivacy new built-in cryptographic operations to accelerate ZK verification (for privacy tech), and feature activation coordination standards.