Hi. with some key parameters needed to run PARITY, which would connect to the network EXPANSE?
--chain=expanse
nice thanks
I have version 1.3.8 PARITY with this key --chain=expanse produces an error
Download the expanse.json from
parity github repo. copy it into your parity directory and add -chain ./expanse.json to the start command
The buildin flag -chain expanse will come with next version.
Command promt:
Parity.exe --chain c:/blockchain exp/expanse.json .... right?
I'm not sure if its integrated into parity 1.3.8 but I know its in 1.4
where to download 1.4.0?
this bat file parity :
parity.exe --geth --rpcaddr "192.168.0.36" --rpcport 9657 --port 42787 --reserved-peers C:\SLAVA_NODA\Parity_EXP\nodes.json --author "0x704EE3dFD9B2aF0cfB71064E6e8EF4ED314993AC" --chain expanse.json --dapps-port 8082 --db-path C:\SLAVA_NODA\Parity_EXP\blockchain
pause
View this:
C:\SLAVA_NODA\Parity_EXP>parity.exe --geth --rpcaddr "192.168.0.36" --rpcport 9657 --port 42787 --reserved-peers C:\SLAVA_NODA\Parity_EXP\nodes.json --author "0x704EE3
4ED314993AC" --chain expanse.json --dapps-port 8082 --db-path C:\SLAVA_NODA\Parity_EXP\blockchain
2016-10-25 00:33:21 Starting Parity/v1.3.9-beta-e9987c4-20161021/x86_64-windows-msvc/rustc1.12.0
2016-10-25 00:33:21 Using state DB journalling strategy fast
2016-10-25 00:33:21 Configured for Expanse using Ethash engine
2016-10-25 00:33:21 Your chain is an alternative fork. TRANSACTIONS MAY BE REPLAYED ON THE MAINNET!
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Error { repr: Os { code: 5, message: "Oткaзaнo в дocтyпe." } })', ../src/libcore\result
2016-10-25 00:33:23 Public node URL: enode://ad5ba1019019c3311b04653f0c33fa484fda442f30258ce17660b639c876876fb79ff65d9ab2980ffe5ada1f58e14c967c785c482f410f85c4049d10a
stack backtrace:
0: 0x1406b346e - <unknown>
1: 0x1406b1363 - <unknown>
2: 0x1406b1e2d - <unknown>
3: 0x1406b1c76 - <unknown>
4: 0x1406b1bd4 - <unknown>
5: 0x1406b1b6b - <unknown>
6: 0x1406bedb5 - <unknown>
7: 0x1400c27d7 - <unknown>
8: 0x1400c22f0 - <unknown>
9: 0x1406b5631 - <unknown>
10: 0x1400c2f75 - <unknown>
11: 0x1406af15e - <unknown>
12: 0x775d59cc - BaseThreadInitThunk
2016-10-25 00:33:53 0/ 0/25 peers 6 KiB db 7 KiB chain 0 bytes queue 4 KiB sync
2016-10-25 00:34:48 0/ 0/25 peers 6 KiB db 7 KiB chain 0 bytes queue 4 KiB sync
2016-10-25 00:34:54 0/ 0/25 peers 6 KiB db 7 KiB chain 0 bytes queue 4 KiB sync
2016-10-25 00:35:24 0/ 0/25 peers 6 KiB db 7 KiB chain 0 bytes queue 4 KiB sync
2016-10-25 00:35:54 0/ 0/25 peers 6 KiB db 7 KiB chain 0 bytes queue 4 KiB sync
2016-10-25 00:36:24 0/ 0/25 peers 6 KiB db 7 KiB chain 0 bytes queue 4 KiB sync
where is the mistake