substrate-open-working-groups VS crates.io

Polkadot Developer Community - Official community forum to discuss Substrate, PolkadotJS, and building cross-chain dApps.

And of course you can always develop your own blockchain with Substrate to support it.

A great framework for building your own blockchain, and use numerous off-the-shelf modules, with Substrate - https://substrate.dev/

If you're interested in developing yourself, check out substrate.dev.

Assuming you are working through the substrate.dev tutorials I have just had this same problem as worked around it by reverting the node template to the `polkadot-v0.9.25` tag.

Well. Polkadot created substrate (substrate.dev) which is a framework for building a blockchain, with a lot of general components to make it easy to "plug-and-play" your customizable blockchain. I tried using their "Getting Started" guide to spin up "my own blockchain", it was done within an hour or so.

Check out https://substrate.dev/ !

Substrate is not a chain; it's the default address style, named after the Substrate development framework which virtually all (if not all) parachains are currently built with. https://substrate.dev/

Do contact the Substrate project (basis of the Polkadot/Kusama project), which is based in Berlin. You can contact them on their channel (see their website on http://substrate.dev), they're friendly and many of them are native German speakers.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.

So this is my question: Which way was the right to find it out? There is no info about this feature on crates.io. I also have no clue what exactly it does and why it is named rwh_05.

Rust does it so much better with https://crates.io . I don't know why Go can't (or won't) do something similar.