You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* build with --locked flag
* init - produces blocks and has balances
* rename SS58Prefix and collator name
* update chain spec ID
* update readme
* disable inflation
**An Ethereum compatible [Parachain](https://polkadot.com/rollups) built with the [Polkadot-SDK](https://github.com/paritytech/polkadot-sdk).**
8
4
9
-
👉 _Discover the Moonbeam project at [moonbeam.network](https://moonbeam.network)._<br>
10
-
👉 _Learn to [use the Moonbeam network](https://docs.moonbeam.network/) with our technical docs._<br>
11
-
👉 _Reference our [crate-level docs (rustdocs)](https://moonbeam-foundation.github.io/moonbeam) to contribute._
12
-
13
-
## Run Moonbeam with zombienet
14
-
```bash
15
-
# Start Polkadot relay with Moonbeam parachain
16
-
make start-zombienet-moonbeam
17
-
# Start Kusama relay with Moonriver parachain
18
-
make start-zombienet-moonriver
19
-
```
20
-
21
-
## Run a Moonbase Alpha (Moonbeam TestNet) Node with Docker
22
-
23
-
Docker images are published for every tagged release. Learn more with `moonbeam --help`.
24
-
25
-
```bash
26
-
# Join the public testnet
27
-
docker run --network="host" moonbeamfoundation/moonbeam:v0.46.0 --chain alphanet
28
-
```
29
-
30
-
You can find more detailed instructions to [run a full node in our TestNet](https://docs.moonbeam.network/node-operators/networks/run-a-node/overview/)
5
+
👉 _Discover the QuStreamNetwork project at [qustream.com](https://qustream.com)._<br>
31
6
32
-
## Run a Local Development Node with Docker
33
-
34
-
Developers who are building dApps to run on Moonbeam, may want a lightweight node to work with
35
-
locally. You can quickly set up a single node without a relay chain backing it using the development service.
7
+
## Run QuStreamNetwork with zombienet for local development
36
8
37
9
```bash
38
-
# Run a dev service node
39
-
docker run --network="host" moonbeamfoundation/moonbeam:v0.46.0 --dev
40
-
```
41
-
42
-
For more information, see our detailed instructions to [run a development node](https://docs.moonbeam.network/builders/get-started/networks/moonbeam-dev/)
43
-
44
-
### Sealing Options
45
-
46
-
The above command will start the node in instant seal mode. It creates a block when a transaction arrives, similar to Ganache's auto-mine. You can also choose to author blocks at a regular interval, or control authoring manually through the RPC.
47
-
48
-
```bash
49
-
# Author a block every 6 seconds.
50
-
docker run --network="host" moonbeamfoundation/moonbeam:v0.46.0 --dev --sealing 6000
51
-
52
-
# Manually control the block authorship and finality
53
-
docker run --network="host" moonbeamfoundation/moonbeam:v0.46.0 --dev --sealing manual
10
+
# Start Polkadot relay with QuStreamNetwork parachain
11
+
make start-zombienet-qustream
54
12
```
55
13
56
14
### Prefunded Development Addresses
57
15
58
-
Running Moonbeam in development mode will pre-fund several well-known addresses that (mostly) contain the letters "th" in their names to remind you that they are for ethereum-compatible usage. These addresses are derived from
16
+
Running QuStreamNetwork in development mode will pre-fund several well-known addresses that (mostly) contain the letters "th" in their names to remind you that they are for ethereum-compatible usage. These addresses are derived from
59
17
Substrate's canonical mnemonic: `bottom drive obey lake curtain smoke basket hold race lonely fit walk`
60
18
61
19
```
@@ -108,26 +66,26 @@ Additionally, the prefunded default account for testing purposes is as follows:
To build Moonbeam, a proper Substrate development environment is required. If you're new to working with Substrate-based blockchains, consider starting with the [Getting Started with a Moonbeam Development Node](https://docs.moonbeam.network/builders/get-started/networks/moonbeam-dev/) documentation.
71
+
To build QuStreamNetwork, a proper Substrate development environment is required. If you're new to working with Substrate-based blockchains, consider starting with the [Getting Started with a Moonbeam Development Node](https://docs.moonbeam.network/builders/get-started/networks/moonbeam-dev/) documentation.
114
72
115
73
If you need a refresher setting up your Substrate environment, see [Substrate's Getting Started Guide](https://substrate.dev/docs/en/knowledgebase/getting-started/).
116
74
117
-
Please note that cloning the master branch might result in an unstable build. If you want a stable version, check out the [latest releases](https://github.com/moonbeam-foundation/moonbeam/releases).
75
+
Please note that cloning the qustream branch might result in an unstable build. If you want a stable version, check out the [latest releases](https://github.com/Asphere-xyz/QuStreamNetwork/releases).
-_EVM Chain Id_: A place to store the chain id for each Moonbeam network
142
+
-_EVM Chain Id_: A place to store the chain id for each QuStream network
189
143
-_EVM_: Encapsulates execution logic for an Ethereum Virtual Machine
190
144
-_Ethereum_: Ethereum-style data encoding and access for the EVM.
191
145
192
-
The following pallets are stored in `pallets/`. They are designed for Moonbeam's specific requirements:
146
+
The following pallets are stored in `pallets/`. They are designed for QuStream's specific requirements:
193
147
194
148
-_Author Inherent_: Allows block authors to include their identity in a block via an inherent.
195
149
-_Parachain Staking_: Minimal staking pallet that selects collators by total amount at stake
196
150
197
151
When modifying the git repository for these dependencies, a tool called [diener](https://github.com/bkchr/diener) can be used to replace the git URL and branch for each reference in all `Cargo.toml` files with a single command. This alleviates a lot of the repetitive modifications necessary when changing dependency versions.
198
152
199
-
## Rustdocs
200
-
201
-
Rustdocs for the Moonbeam codebase are automatically generated and published
0 commit comments