substrate VS validator-stats

Substrate — a framework for building application-specific blockchains (written in Rust);

frame-benchmarking = { version = "4.0.0-dev", default-features = false, optional = true, git = "https://github.com/paritytech/substrate.git", branch = "polkadot-v1.0.0" }

To offer some perspective outside of the typical "all crypto is a scam", Parity is doing some cool stuff with a rust modular blockchain library called Substrate https://github.com/paritytech/substrate.

Rust takes the cake in the blockchain space: Substrate, Cosmos (CosmWasm), and Solana. All of the zero knowledge cryptography libraries used for layer 2 solutions are written in Rust, compiling to Wasm (see arkworks, Risc0). Ethereum's next version of smart contracts will even use a restricted subset of Wasm ("Ewasm") instead of EVM.

Verifying NPoS election solution graph and its score is a memory-intensive operation that needs to be performed within a single block time. Under the current runtime constraints, a solution graph with 22,500 nominators can be verified well within the block production time on Polkadot. There are plans to improve on this and implement multi-block election solution verification, after which, the NPoS system can scale to incorporate more nominators.

Fast-unstake is now available on Kusama. This allows instant unstaking if you have not participated in staking in the last 28 eras. https://github.com/paritytech/substrate/pull/12129

First, any outstanding multisig calls (ones where one signatory has signed, but not the threshold) will not be able to execute. Please either finish your multisig calls before this upgrade, or wait until after it is completed. https://github.com/paritytech/substrate/pull/12072

Github: https://github.com/paritytech/substrate

It's not part of the current Polkadot runtime, so you won't see the minimum stake at this point. You could calculate it out approximately what it will be by e.g. running https://github.com/w3f/validator-stats, parsing out all nominator amounts, sorting, and looking for spot #20_000.

This number fluctuates every era, and the most recent and up to date version can be found out using this community-developed tool or through these scripts which you can run on your machine. See the Election Solution Set section on the Nominator page for more details.

To see these figures and more on your own, you can run the validator-stats script here: https://github.com/w3f/validator-stats

Right now you have to run the validator-stats script and look for "Lowest minimal nominator". https://github.com/w3f/validator-stats