pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-06-15 22:01:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Node template love (#6560)

Browse Source 
* Node template love

Better description in node/Cargo.toml
Example dispatchables should have non-zero weights
Changes to README to bring in line with current DevHub Node Template

* Update README.md

cleaned up, reworked text, ready for round 2

* Add DbWeight

* Update README.md

* Consistent Playground buttons

* "setup" -> "set up"

Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>

* Import `Get` trait to fix build

Co-authored-by: Addie Wagenknecht <addie@nortd.com>
Co-authored-by: Ricardo Rius <ricardo@parity.io>
Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
This commit is contained in:
Dan Forbes
2020-07-10 00:29:39 -07:00
committed by GitHub
parent bf4e5d4d2c
commit f39f404c22
3 changed files with 72 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
substrate/bin/node-template/README.md
+68 -21
View File
@@ -1,54 +1,76 @@
[![Substrate Playground](https://img.shields.io/badge/Playground-node_template-brightgreen?logo=Parity%20Substrate)](https://playground-staging.substrate.dev/?deploy=node-template)
# Substrate Node Template # Substrate Node Template
A new FRAME-based Substrate node, ready for hacking. A new FRAME-based Substrate node, ready for hacking :rocket:
## Build ## Local Development
Install Rust: Follow these steps to prepare a local Substrate development environment :hammer_and_wrench:
### Simple Setup
Install all the required dependencies with a single command (be patient, this can take up
to 30 minutes).
```bash ```bash
curl https://sh.rustup.rs -sSf | sh curl https://getsubstrate.io -sSf | bash -s -- --fast
``` ```
Initialize your Wasm Build environment: ### Manual Setup
```bash Find manual setup instructions at the [Substrate Developer Hub](https://substrate.dev/docs/en/knowledgebase/getting-started/#manual-installation).
./scripts/init.sh
```
Build Wasm and native code: ### Build
Once the development environment is set up, build the node template. This command will build the
[Wasm](https://substrate.dev/docs/en/knowledgebase/advanced/executor#wasm-execution) and
[native](https://substrate.dev/docs/en/knowledgebase/advanced/executor#native-execution) code:
```bash ```bash
cargo build --release cargo build --release
``` ```
## Playground [![Substrate Playground](https://img.shields.io/badge/Playground-node_template-brightgreen?logo=Parity%20Substrate)](https://playground-staging.substrate.dev/?deploy=node-template)
[The Substrate Playground](https://playground-staging.substrate.dev/?deploy=node-template) is an
online development environment that supplies a pre-configured container with pre-compiled build
artifacts :cartwheeling:
## Run ## Run
### Single node development chain ### Single Node Development Chain
Purge any existing developer chain state: Purge any existing dev chain state:
```bash ```bash
./target/release/node-template purge-chain --dev ./target/release/node-template purge-chain --dev
``` ```
Start a development chain with: Start a dev chain:
```bash ```bash
./target/release/node-template --dev ./target/release/node-template --dev
``` ```
Detailed logs may be shown by running the node with the following environment variables set: `RUST_LOG=debug RUST_BACKTRACE=1 cargo run -- --dev`. Or, start a dev chain with detailed logging:
### Multi-node local testnet ```bash
RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/node-template -lruntime=debug --dev
```
If you want to see the multi-node consensus algorithm in action locally, then you can create a local testnet with two validator nodes for Alice and Bob, who are the initial authorities of the genesis chain that have been endowed with testnet units. ### Multi-Node Local Testnet
Optionally, give each node a name and expose them so they are listed on the Polkadot [telemetry site](https://telemetry.polkadot.io/#/Local%20Testnet). To see the multi-node consensus algorithm in action, run a local testnet with two validator nodes,
Alice and Bob, that have been [configured](/bin/node-template/node/src/chain_spec.rs) as the
initial authorities of the `local` testnet chain and endowed with testnet units.
You'll need two terminal windows open. Note: this will require two terminal sessions (one for each node).
We'll start Alice's substrate node first on default TCP port 30333 with her chain database stored locally at `/tmp/alice`. The bootnode ID of her node is `QmRpheLN4JWdAnY7HGJfWFNbfkQCb6tFf4vvA6hgjMZKrR`, which is generated from the `--node-key` value that we specify below: Start Alice's node first. The command below uses the default TCP port (30333) and specifies
`/tmp/alice` as the chain database location. Alice's node ID will be
`12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp` (legacy representation:
`QmRpheLN4JWdAnY7HGJfWFNbfkQCb6tFf4vvA6hgjMZKrR`); this is determined by the `node-key`.
```bash ```bash
cargo run -- \ cargo run -- \
@@ -60,17 +82,42 @@ cargo run -- \
--validator --validator
``` ```
In the second terminal, we'll start Bob's substrate node on a different TCP port of 30334, and with his chain database stored locally at `/tmp/bob`. We'll specify a value for the `--bootnodes` option that will connect his node to Alice's bootnode ID on TCP port 30333: In another terminal, use the following command to start Bob's node on a different TCP port (30334)
and with a chain database location of `/tmp/bob`. The `--bootnodes` option will connect his node to
Alice's on TCP port 30333:
```bash ```bash
cargo run -- \ cargo run -- \
--base-path /tmp/bob \ --base-path /tmp/bob \
--bootnodes /ip4/127.0.0.1/tcp/30333/p2p/QmRpheLN4JWdAnY7HGJfWFNbfkQCb6tFf4vvA6hgjMZKrR \ --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp \
--chain=local \ --chain=local \
--bob \ --bob \
--port 30334 \ --port 30334 \
--ws-port 9945 \
--telemetry-url 'ws://telemetry.polkadot.io:1024 0' \ --telemetry-url 'ws://telemetry.polkadot.io:1024 0' \
--validator --validator
``` ```
Additional CLI usage options are available and may be shown by running `cargo run -- --help`. Execute `cargo run -- --help` to learn more about the template node's CLI options.
## Generate a Custom Node Template
Generate a Substrate node template based on a particular commit by running the following commands:
```bash
# Clone from the main Substrate repo
git clone https://github.com/paritytech/substrate.git
cd substrate
# Switch to the branch or commit to base the template on
git checkout <branch/tag/sha1>
# Run the helper script to generate a node template. This script compiles Substrate, so it will take
# a while to complete. It expects a single parameter: the location for the script's output expressed
# as a relative path.
.maintain/node-template-release.sh ../node-template.tar.gz
```
Custom node templates are not supported. Please use a recently tagged version of the
[Substrate Developer Node Template](https://github.com/substrate-developer-hub/substrate-node-template)
in order to receive support.
substrate/bin/node-template/node/Cargo.toml
+1 -1
View File
@@ -2,7 +2,7 @@
name = "node-template" name = "node-template"
version = "2.0.0-rc4" version = "2.0.0-rc4"
authors = ["Anonymous"] authors = ["Anonymous"]
description = "Substrate Node template" description = "A new FRAME-based Substrate node, ready for hacking."
edition = "2018" edition = "2018"
license = "Unlicense" license = "Unlicense"
build = "build.rs" build = "build.rs"
substrate/bin/node-template/pallets/template/src/lib.rs
+3 -3
View File
@@ -9,7 +9,7 @@
/// For more guidance on Substrate FRAME, see the example pallet /// For more guidance on Substrate FRAME, see the example pallet
/// https://github.com/paritytech/substrate/blob/master/frame/example/src/lib.rs /// https://github.com/paritytech/substrate/blob/master/frame/example/src/lib.rs
use frame_support::{decl_module, decl_storage, decl_event, decl_error, dispatch}; use frame_support::{decl_module, decl_storage, decl_event, decl_error, dispatch, traits::Get};
use frame_system::ensure_signed; use frame_system::ensure_signed;
#[cfg(test)] #[cfg(test)]
@@ -75,7 +75,7 @@ decl_module! {
/// Just a dummy entry point. /// Just a dummy entry point.
/// function that can be called by the external world as an extrinsics call /// function that can be called by the external world as an extrinsics call
/// takes a parameter of the type `AccountId`, stores it, and emits an event /// takes a parameter of the type `AccountId`, stores it, and emits an event
#[weight = 0] #[weight = 10_000 + T::DbWeight::get().writes(1)]
pub fn do_something(origin, something: u32) -> dispatch::DispatchResult { pub fn do_something(origin, something: u32) -> dispatch::DispatchResult {
// Check it was signed and get the signer. See also: ensure_root and ensure_none // Check it was signed and get the signer. See also: ensure_root and ensure_none
let who = ensure_signed(origin)?; let who = ensure_signed(origin)?;
@@ -91,7 +91,7 @@ decl_module! {
/// Another dummy entry point. /// Another dummy entry point.
/// takes no parameters, attempts to increment storage value, and possibly throws an error /// takes no parameters, attempts to increment storage value, and possibly throws an error
#[weight = 0] #[weight = 10_000 + T::DbWeight::get().reads_writes(1,1)]
pub fn cause_error(origin) -> dispatch::DispatchResult { pub fn cause_error(origin) -> dispatch::DispatchResult {
// Check it was signed and get the signer. See also: ensure_root and ensure_none // Check it was signed and get the signer. See also: ensure_root and ensure_none
let _who = ensure_signed(origin)?; let _who = ensure_signed(origin)?;