Final tweaks for PoC-2 runtime upgrade (#348)

* Final tweaks for PoC-2 runtime upgrade

* Address grumble

* Avoid slow wasm

* New poc-2-era bootnodes

* Fix warning

* Typo

* Fix for allocation in wasm

* Fix & runtimes.

* PoC-1 should be default.

* Name testnet Krumme Lanke, update README

* YML update

* Use the right port
This commit is contained in:
Gav Wood
2018-07-17 18:55:28 +02:00
committed by GitHub
parent 428682d3b5
commit 07fbd871d9
22 changed files with 76 additions and 51 deletions
+17 -17
View File
@@ -12,15 +12,26 @@ curl https://sh.rustup.rs -sSf | sh
sudo apt install make clang
```
Then, install Polkadot PoC-1:
Then, install Polkadot PoC-2:
```
cargo install --git https://github.com/paritytech/polkadot.git --branch v0.1
cargo install --git https://github.com/paritytech/polkadot.git --branch v0.2
```
You'll now have a `polkadot` binary installed to your `PATH`. You can drop the
`--branch v0.1` or run `cargo install --git https://github.com/paritytech/polkadot.git polkadot`
to get the very latest version of Polkadot, but these instructions will not work in that case.
`--branch v0.2` or run `cargo install --git https://github.com/paritytech/polkadot.git polkadot`
to get the very latest version of Polkadot, but these instructions might not work in that case.
### Krumme Lanke Testnet
You will connect to the global Krumme Lanke testnet by default. To do this, just use:
```
polkadot
```
If you want to do anything on it (not that there's much to do), then you'll need
to get some Krumme Lanke DOTs. Ask in the Polkadot watercooler.
### Development
@@ -28,22 +39,11 @@ You can run a simple single-node development "network" on your machine by
running in a terminal:
```
polkadot --chain=dev --validator --key Alice
polkadot --dev
```
You can muck around by cloning and building the http://github.com/paritytech/polka-ui and http://github.com/paritytech/polkadot-ui or just heading to https://polkadot.js.org/apps.
### PoC-1 Testnet
You can also connect to the global PoC-1 testnet. To do this, just use:
```
polkadot --chain=poc-1
```
If you want to do anything on it (not that there's much to do), then you'll need
to get some PoC-1 testnet DOTs. Ask in the Polkadot watercooler.
## Local Two-node Testnet
If you want to see the multi-node consensus algorithm in action locally, then
@@ -99,5 +99,5 @@ cargo test --all
You can start a development chain with:
```
cargo run -- --chain=dev --validator --key Alice
cargo run -- --dev
```