1
- # Libre currency based on Substrate framework
1
+ # Duniter v2s
2
2
3
- A FRAME- based [ Substrate] ( https://www.substrate.io/ ) libre currency implementation .
3
+ A rewriting of duniter based on [ Substrate] ( https://www.substrate.io/ ) framework .
4
4
5
5
## Setup
6
6
@@ -13,15 +13,15 @@ NOTE: You must first follow the instructions in the [Setup] section (#setup).
13
13
Use the following command to build the node without launching it:
14
14
15
15
``` sh
16
- cargo build --release
16
+ cargo build
17
17
```
18
18
19
19
## Run
20
20
21
21
Use Rust's native ` cargo ` command to build and launch the node:
22
22
23
23
``` sh
24
- cargo run --release -- --dev --tmp
24
+ cargo run -- --dev --tmp
25
25
```
26
26
27
27
## Contribute
@@ -34,27 +34,27 @@ Once the project has been built, the following command can be used to explore al
34
34
subcommands:
35
35
36
36
``` sh
37
- ./target/release/lc-core -h
37
+ ./target/release/duniter -h
38
38
```
39
39
40
40
## Single-Node Development Chain
41
41
42
42
This command will start the single-node development chain with persistent state:
43
43
44
44
``` bash
45
- ./target/release/lc-core --dev
45
+ ./target/debug/duniter --dev
46
46
```
47
47
48
48
Purge the development chain's state:
49
49
50
50
``` bash
51
- ./target/release/lc-core purge-chain --dev
51
+ ./target/debug/duniter purge-chain --dev
52
52
```
53
53
54
54
Start the development chain with detailed logging:
55
55
56
56
``` bash
57
- RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/lc-core -lruntime=debug --dev
57
+ RUST_LOG=debug RUST_BACKTRACE=1 ./target/debug/duniter -lruntime=debug --dev
58
58
```
59
59
60
60
## Connect with Polkadot-JS Apps Front-end
@@ -74,15 +74,15 @@ If you want to see the multi-node consensus algorithm in action, refer to
74
74
### Purge previous lacal testnet
75
75
76
76
```
77
- ./target/release/lc-core purge-chain --base-path /tmp/alice --chain local
78
- ./target/release/lc-core purge-chain --base-path /tmp/bob --chain local
77
+ ./target/debug/duniter purge-chain --base-path /tmp/alice --chain local
78
+ ./target/debug/duniter purge-chain --base-path /tmp/bob --chain local
79
79
80
80
```
81
81
82
82
### Start Alice's node
83
83
84
84
``` bash
85
- ./target/release/lc-core \
85
+ ./target/debug/duniter \
86
86
--base-path /tmp/alice \
87
87
--chain local \
88
88
--alice \
@@ -96,7 +96,7 @@ If you want to see the multi-node consensus algorithm in action, refer to
96
96
### Start Bob's node
97
97
98
98
``` bash
99
- ./target/release/lc-core \
99
+ ./target/debug/duniter \
100
100
--base-path /tmp/bob \
101
101
--chain local \
102
102
--bob \
@@ -150,7 +150,7 @@ After the node has been [built](#build), refer to the embedded documentation to
150
150
capabilities and configuration parameters that it exposes:
151
151
152
152
``` shell
153
- ./target/release/lc-core --help
153
+ ./target/debug/duniter --help
154
154
```
155
155
156
156
### Runtime
@@ -210,15 +210,15 @@ Then run the following command to start a single node development chain.
210
210
```
211
211
212
212
This command will firstly compile your code, and then start a local development network. You can
213
- also replace the default command (` cargo build --release && ./target/release/lc-core --dev --ws-external ` )
213
+ also replace the default command (` cargo build && ./target/debug/duniter --dev --ws-external ` )
214
214
by appending your own. A few useful ones are as follow.
215
215
216
216
``` bash
217
- # Run Substrate node without re-compiling
218
- ./scripts/docker_run.sh ./target/release/lc-core --dev --ws-external
217
+ # Run duniter node without re-compiling
218
+ ./scripts/docker_run.sh ./target/debug/duniter --dev --ws-external
219
219
220
220
# Purge the local dev chain
221
- ./scripts/docker_run.sh ./target/release/lc-core purge-chain --dev
221
+ ./scripts/docker_run.sh ./target/debug/duniter purge-chain --dev
222
222
223
223
# Check whether the code is compilable
224
224
./scripts/docker_run.sh cargo check
0 commit comments