forked from openethereum/parity-ethereum
-
Notifications
You must be signed in to change notification settings - Fork 0
Importing a Chain from Geth
bittylicious edited this page Sep 20, 2016
·
4 revisions
When coming from Geth, be aware that the --geth
option provides you with the highest degree of compatibility to Geth's behaviour, even at the cost of speed, security, functionality and standardisation.
If you don't care about historical transaction information, just use our [state-snapshotting](Getting Synced) to get synced really fast.
On 1.2 and above, use Geth's export feature along with Parity's import:
mkfifo /tmp/chain.rlp && geth export /tmp/chain.rlp &;
sleep 1 && parity import /tmp/chain.rlp
Prior to 1.2, you need to run Parity and then have Geth connect to it. First run Parity without peer discovery and with a simple node key:
echo 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 > /tmp/nodekey
parity --no-discovery --bootnodes "" --node-key $(cat /tmp/nodekey)
Then run Geth telling it to connect to Parity:
geth --bootnodes "enode://$(cat /tmp/nodekey)@127.0.0.1:30303" --nodiscover --maxpeers 1
- [With Mist](Using parity with mist)
- For Mining
- [For Private Chains](Private Chains)
- [For PoA Chains](Proof of Authority Chains)
- [Coming from Geth](Importing a chain from Geth)
- Backing-up & Restoring
- Ethereum Classic