Polkadot Blockchain Developer Bootcamp with Substrate + Rust

Store blockchain data across nodes to maintain decentralization. Coordinate peer-to-peer networking, implement consensus, process transactions, and generate secure block hashes to safeguard integrity.

Understand how blockchain operates as a state machine, where decentralized nodes must agree on a single future state through consensus models like proof of work, from genesis to new blocks.

Explore blockchain economics in the Polkadot blockchain developer bootcamp by examining how processors, memory, and bandwidth power decentralized networks and how node operators are rewarded, primarily through transaction fees.

Explain how blockchains enable submitting and voting on proposals in a semi democratic process, noting currency requirements, and contrast on-chain sunshine governance with off-chain deliberation.

Build and run decentralised apps on a decentralised blockchain by combining front-end technologies like HTML, CSS, and JavaScript with smart contracts that execute transactions under specific conditions.

Start your local substrate node in development mode from the compiled template, verify blocks are being finalized, and use the dev option to wipe keys for a clean restart.

Start the Substrate front-end template to connect the front end to your node, select an account like Alice, view the current block and balances, and transfer funds.

Interact with the front end to transfer funds between accounts using the transfer component, moving one unit from Alice to Dave, then verify the transaction and updated balances in events.

Explore the substrate node architecture in a decentralized network where each node acts as both client and server, using lib p2p for communication, consensus, and runtime execution.

Substrate enables building private networks, solo chains, and parachains like Polkadot, which provide decentralized security through a relay chain; power chains must implement the same consensus as the relay chain.

Polkadot offers three node types: full, archive, light. Full nodes store genesis and most recent 256 blocks; archive nodes hold history; light clients require minimal hardware and cannot validate.

Run two substrate nodes on one computer to form a private network, with Alice and Bob each producing and finalizing blocks, then configure base path and the local chain spec.

Join an existing Polkadot network by launching a second node named Bob, using the running node as reference. Configure ports, keys, and boot node to add Bob as a validator.

Observe Alice and Bob nodes connecting with peers, blocks begin to be produced, and the finalized count increases. Shutting down Alice reduces peers and Bob stops producing blocks.

Explore consensus mechanisms for substrate-based blockchains, weigh trade-offs, and choose or customize a consensus—whether prebuilt or custom—for block authoring and finalization as the source of truth.

Understand block authoring in substrate networks, comparing Aura and Babe validators, round-robin and slot-based scheduling, and proof of work.

Understand how blocks link to their parent, forming a genesis-to-present chain, and compare fork resolution methods like grandpa's longest-chain rule and ghost's most-descendants approach.

Learn how deterministic finality complements block authoring in Substrate, using a finality mechanism, authority votes, and two-thirds thresholds to prevent reversals and guide fork choice.

Generate unique sr25519 and id25519 keys for validator nodes using the substrate node template; create a secret phrase, and derive id25519 keys with inspect, ensuring each node has distinct credentials.

Learn to generate a custom chain specification by exporting the local chain spec, editing the aura and grandpa authorities with sr25519 keys, and saving a named custom spec.

Convert the custom spectre json chain specification to its raw format, enabling the node to reference encoded storage keys in local storage.

Launch the first boot node as the chain authority in your private substrate blockchain, using a custom spec json, ports, telemetry, and unsafe ipc for testing.

Start a local Polkadot Substrate node and view terminal output showing the chain specification, authority status, genesis block, and the local host identity.

Insert Aura Authority keys and Grand Power Authority keys into each node's keystore using the chain specification to enable block production and finalization, then verify the keys.

Add a second blockchain node to join an existing network by configuring a custom spec, boot node, and validator keys, then enable aura and grandpa to produce and finalize blocks.

Understand Substrate accounts, addresses, and keys, including multiple addresses from a single public key. An account can hold funds and transact, with a private key plus seed phrase for recovery.

Substrate derives multiple chain-specific addresses from one public key, enabling interaction with networks; the s58 format encodes network info in base58 with a checksum, and prefixes distinguish Polkadot and Kusama.

Explore specialized accounts in substrate, including stash accounts, controller accounts, and proxy accounts that manage funds and governance, while offline keys secure balances and allow autonomous function calls.

Add the Nicks pallet dependencies to the cargo file, enable the standard feature set, and verify runtime dependencies resolve with cargo check for a successful compile.

Review the config trait to identify the parameters and types the balancers palette requires, then implement them in the runtime, guided by the palette's documentation.

Implement the config trait for the next palette of the balances palette by setting type currency to balance and a 100 reservation fee, wiring Knicks into the construct runtime.

Start the blockchain node in development mode from the Substrate node template and interact with it through the front end. Watch blocks produce and finalize as the terminal stays open.

Open and start the front end template in a new terminal shell, create a new tab, navigate to the substrate front end template folder, and run start.

Interact with the nicks pallet in the runtime to set a nickname by calling the set name extrinsic, using a front-end template, signing transactions, and confirming finalization and events.

Query information for an account using the nicks pallet to read Alice's nickname, showing hex-encoded nickname and reserved amount, and practice set name and name of functions.