Parity Rinkeby – Configuring Parity for Rinkeby Testnet

configurationparityrinkebytestnets

Can someone provide me an genesis block configuration json for Parity client here is my setup described:

I've installed the client (version: Parity/v1.6.8-beta-c396229-20170608/x86_64-linux-gnu/rustc1.17.0). Converted my rinkeby genesis block config using this as input:www.rinkeby.io/rinkeby.json and using this tool mentioned on the github wiki page: https://github.com/keorn/parity-spec. Which resulted in this config file: https://gist.github.com/kgcorps/3b67338bc5ea204372f993ed25389e88

When trying to start parity with the following command:

parity --chain=res.json --bootnodes=enode://a24ac7c5484ef4ed0c5eb2d36620ba4e4aa13b8c84684e1b4aab0cebea2ae45cb4d375b77eab56516d34bfbd3c1a833fc51296ff084b770b94fb9028c4d25ccf@52.169.42.101:30303 --identity=foobar --datadir=$HOME/.rinkebyParity

I have hunch I've made stupid mistake somewhere with the config conversion. The source config is good to go since I've used it with geth without any problems.

Thanks for any tips

Edit
As far as I understand parity doesn't support ProofOfAuthority algorithm, does this mean that it is impossible to use parity with rinkeby testnet?

Best Answer

Parity does very well support proof of authority, but it does not implement the Clique engine required to join the Rinkeby test network. It just wont work out.

If you want to join a PoA testnet, you can still use Kovan:

parity --chain kovan

Related Solutions

Parity – How to Set Up Parity Bootnode Role in a Private Network

Bootnodes are the nodes which provide information about other peers, txns, blocks. Once that information is received, bootnode does not need to be online. But bootnodes are always kept online, because new nodes keep coming up and require some of this information. Information of bootnodes can be provided by:

genesis file
list of reserved peers at startup

If your node gets information of other nodes from bootnode, it can get blocks and txns from other too. Even if bootnode goes offline, your chain will sync.

Yes. Bootnode can be validator nodes. It does not matter whether bootnode is validator or non validator. For all other nodes, it is just some node which can be used to get information of other nodes and get previous blockchain data. NOTE: Since the validator node needs to expose its enode address (enode://pubkey1@ip1:port1) and thus the validator node's IP address in order to be a Bootnode, having validator nodes serve as Bootnodes (and advertising this) makes it easier for network attackers (DDOS) to target validator nodes.
Yes. You can provide a list of nodes using a file containing list of enode urls and you can use that file while starting parity. Use this tag to point to the file: --reserved-peers <file_name>. If you want it to be configured in toml file, you can use
```
[network]
reserved_peers: "<filename>"
```
Yes they do. Bootnodes also become a part of the peers and communicate transactions and blocks and if discovery is set to true, they also discover other peers.

[Ethereum] How to connect to Rinkeby without using Geth / Parity

Web3 and Metamask are all you need to connect to Rinkeby. You don't need Infura, Geth, or Parity. For state modifying, check out the method send command:

myContract.methods.myMethod([param1[, param2[, ...]]]).send(options[, callback])

Related Topic

LooksRare Testnets – Does LooksRare Scan Rinkeby Testnet?