riscv-zkt-list VS solana

> all branchless code runs in constant time

No - e.g. division is not constant time.

You have to have branchless code and only use certain instructions.

E.g. here is the list for RISC-V.

https://github.com/rvkrypto/riscv-zkt-list/blob/main/zkt-lis...

Most things except div/rem, branches and floating point are ok. Oh and obviously store/load.

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.