developer-roadmap VS substrate

Roadmap.sh as guidance

I’d direct you towards this instead: https://github.com/kamranahmedse/developer-roadmap

Repo was first but they also have the site https://roadmap.sh

Developer Roadmaps : Step by step guides and paths to learn different tools or technologies

What do I know? I know easy LeetCode pretty well and can give a medium question a good try on an interview. I know HTML, CSS, JavaScript, and React better than most. I've built multiple fullstack projects as a hobby, many of which I attempted to get communities to actually used. I can hold a conversation about most things on roadmap.sh for frontend. If asked on an interview, I can talk about testing, accessibility, SEO, CSR/SSR/SSG, state management, security, databases, etc. I do NOT have a CS degree but I DO have a college and a medical degree.

Free code camp is a great resource, but you might also appreciate roadmap.sh, as a general roadmap for the things you should learn. It might look overwhelming at first, but remember that these roadmaps are usually completed over years.

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

Of course, like most things in Polkadot, this can be adjusted via governance, and thus a vote of the DOT holders. So if this were seen as a major problem by DOT holders, they can create a new runtime with a modified inflationary model (by changing the parameters here) and vote on it to replace the current one.

Polkadot, Kusama, Substrate and ink!

Solidity is language for smart contacts originally designed for Ethereum. If you want to execute your Solidity smart contract in a blockchain whose VM interprets WASM, then you need to compile Solidity into WebAssembly. Currently, we target Substrate (https://github.com/paritytech/substrate) and Ewasm (https://ewasm.readthedocs.io/en/mkdocs/) that need WebAssembly. This is the project's repo: https://github.com/hyperledger-labs/solang

However, this exercise sets the stage for the topic, explaining some of the basics and showing them off in Rust, so that we can continue this journey by looking at how we would go about building a blockchain application that could actually be used in practice with a framework such as Substrate.

I'd love to see the M1Max times for https://github.com/paritytech/substrate

As mentioned by the Staking team on this message, Polkadot currently has 22500 nominators and the configuration of the staking system prevents further nominators to join. The team suggests to update the staking parameters as soon as the next runtime upgrade happens today. The proposal has the goal to increase the minimum bond to allow new nominators above the threshold to participate in the network’s security mechanism, and for less staked nominators to be chilled. Note that after 9080, the existing nominators can always update their preference at all conditions. The proposal the team suggested will change the staking parameters to allow more nominators with higher backing stake be able to join the staking system. The existing parameters as as follows: minimum validator bond: None maximum validator count: 1200 minimum nominator bond: 40 DOTs maximum nominator count: 22500 The new proposed parameters will update one value: new minimum nominator bond: 80 DOTs and set a new parameter that did not existed before: chill-threshold: 90% The reasoning behind the new minimum nominator bond: Polkadot onboards ~150 nominators per day. That means if the network has 4500 empty slots, they will be filled in 30 days. The team aims to increase the limit enough so that we won't need to do another tweak for at least a month. Changing this parameter to 80 will almost expose 4500 nominators. The new chill-threshold will ensure that the permissionless chill_other  can only be used when more than 90% of "maximum nominator count" is used. note that to ensure polkadot's stability until the parachains launch, this motion does not yet include an increase in the total count of nominators. Multiple tracks of optimization are ongoing by the development team, and you can read more about them in this issue. Please note that doubling the value of the parameter to 80 DOTs will hopefully give the team more time until the new threshold is reached and we have made progress on a more permanent solution. Please leave your comments and feedback on the proposal. Keep in mind these measures are temporary, and the overall goal is the stability and security of the overall network.

The larger picture (having any limit) is an issue that the team is working on resolving. You may track this here: https://github.com/paritytech/substrate/issues/9511