文件列表:

.cargo (0, 2023-05-25)
.cargo\config.toml (1578, 2023-05-25)
.dockerignore (2952, 2023-05-25)
.editorconfig (350, 2023-05-25)
CODE_OF_CONDUCT.md (5482, 2023-05-25)
CONTRIBUTING.md (6364, 2023-05-25)
Cargo.lock (353981, 2023-05-25)
Cargo.toml (20925, 2023-05-25)
LICENSE (35149, 2023-05-25)
Makefile (185, 2023-05-25)
... ...

 Astar Network is an interoperable blockchain based the Substrate framework and the hub for dApps within the Polkadot Ecosystem. With Astar Network and Shiden Network, people can stake their tokens to a Smart Contract for rewarding projects that provide value to the network. For contributing to this project, please read our [Contribution Guideline](./CONTRIBUTING.md). ## Building From Source > This section assumes that the developer is running on either macOS or Debian-variant operating system. For Windows, although there are ways to run it, we recommend using [WSL](https://docs.microsoft.com/en-us/windows/wsl/install-win10) or from a virtual machine for stability. Execute the following command from your terminal to set up the development environment and build the node runtime. ```bash # install Substrate development environment via the automatic script $ curl https://getsubstrate.io -sSf | bash -s -- --fast # clone the Git repository $ git clone --recurse-submodules https://github.com/AstarNetwork/Astar.git # change current working directory $ cd Astar # compile the node # note: you may encounter some errors if `wasm32-unknown-unknown` is not installed, or if the toolchain channel is outdated $ cargo build --release # show list of available commands $ ./target/release/astar-collator --help ``` ### Building with Nix ```bash # install Nix package manager: $ curl https://nixos.org/nix/install | sh # run from root of the project folder (`Astar/` folder) $ nix-shell -I nixpkgs=channel:nixos-21.05 third-party/nix/shell.nix --run "cargo build --release" ``` ## Running a Collator Node To set up a collator node, you must have a fully synced node with the proper arguments, which can be done with the following command. ```bash # start the Shiden collator node with $ ./target/release/astar-collator \ --base-path \ --name \ --port 30333 \ --ws-port 9944 \ --rpc-port 9933 \ --telemetry-url 'wss://telemetry.polkadot.io/submit/ 0' \ --rpc-cors all \ --collator ``` Now, you can obtain the node's session key by sending the following RPC payload. ```bash # send `rotate_keys` request $ curl -H 'Content-Type: application/json' --data '{ "jsonrpc":"2.0", "method":"author_rotateKeys", "id":1 }' localhost:9933 # should return a long string of hex, which is your session key {"jsonrpc":"2.0","result":"","id":1} ``` After this step, you should have a validator node online with a session key for your node. For key management and validator rewards, consult our [validator guide online](https://docs.astar.network/build/validator-guide/configure-node). ## Run RPC Tests RPC tests suite can be run for any release. To run tests go to https://github.com/AstarNetwork/Astar/actions/workflows/rpcTest.yml. Click Run workflow, in the dropdown input the release version tag you want to run the test suite. Then click the green Run workflow button to start the test suite.  ## Workspace Dependency Handling All dependencies should be listed inside the workspace's root `Cargo.toml` file. This allows us to easily change version of a crate used by the entire repo by modifying the version in a single place. Right now, if **non_std** is required, `default-features = false` must be set in the root `Cargo.toml` file (related to this [issue](https://github.com/rust-lang/cargo/pull/11409)). Otherwise, it will have no effect, causing your compilation to fail. Also `package` imports aren't properly propagated from root to sub-crates, so defining those should be avoided. Defining _features_ in the root `Cargo.toml` is additive with the features defined in concrete crate's `Cargo.toml`. **Adding Dependency** 1. Check if the dependency is already defined in the root `Cargo.toml` 1. if **yes**, nothing to do, just take note of the enabled features 2. if **no**, add it (make sure to use `default-features = false` if dependency is used in _no_std_ context) 2. Add `new_dependecy = { workspace = true }` to the required crate 3. In case dependency is defined with `default-features = false` but you need it in _std_ context, add `features = ["std"]` to the required crate. ## Further Reading * [Official Documentation](https://docs.astar.network/) * [Whitepaper](https://github.com/AstarNetwork/plasmdocs/blob/master/wp/en.pdf) * [Whitepaper(JP)](https://github.com/AstarNetwork/plasmdocs/blob/master/wp/jp.pdf) * [Subtrate Developer Hub](https://substrate.dev/docs/en/) * [Substrate Glossary](https://substrate.dev/docs/en/knowledgebase/getting-started/glossary) * [Substrate Client Library Documentation](https://polkadot.js.org/docs/)

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：