Skip to content

Commit 5c13758

Browse files
authored
Merge pull request #127 from ewasm/reorder
Move the writing contracts section
2 parents d1cf1d5 + a83c64a commit 5c13758

1 file changed

Lines changed: 19 additions & 19 deletions

File tree

README.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,25 @@ The primary communication channels for the Ewasm project are GitHub and Gitter.
3535

3636
The team also hosts a (roughly) fortnightly public "Ewasm community hangout" call. Look for the the next scheduled call in [ewasm/pm issues](https://github.com/ewasm/pm/issues). Calls are announced, including dial-in information, in [ewasm/Lobby](https://gitter.im/ewasm/Lobby). Calls are also livestreamed and recorded.
3737

38+
## Differences from mainnet
39+
40+
The Ewasm testnet supports executing EVM 1.0 (Byzantium) bytecode **and** ewasm bytecode. The chain id is set to 0x42 (decimal 66).
41+
42+
There are two further technical differences:
43+
44+
- the code size limit introduced by Spurious Dragon has been lifted and there is no upper limit (as Wasm bytecode is more verbose than the EVM equivalent)
45+
- zero bytes in contract bytecode are not subsidised during deployment (they cost the same as non-zero bytes)
46+
47+
## Transacting
48+
49+
You don't need any special infrastructure to transact on the Ewasm testnet. You may run your own node (see below), or you may use the public node. You may view the list of testnet tools here: http://ewasm.ethereum.org/. Start by requesting test ether from the faucet:
50+
51+
- Configure Metamask to use the public node. Open Metamask, tap the network selector at the top, and click Custom RPC. Enter the following URL and click Save: http://ewasm.ethereum.org:8545.
52+
- Browse to the [faucet](http://ewasm.ethereum.org/faucet), make sure it read your public key correctly from Metamask in the "user" section, then tap "request 1 ether from faucet" in the "faucet" section.
53+
- Click the txid that appears in the "transactions" section and watch your faucet transaction get mined.
54+
55+
Voila! You're now ready to transact on the testnet.
56+
3857
## Writing and compiling smart contracts
3958

4059
### Solidity/EVM
@@ -75,25 +94,6 @@ At present, we've developed support for the following languages and toolchains:
7594

7695
If you're interested in adding support for another language, framework, or toolset, see the Contributing section above and reach out.
7796

78-
## Differences from mainnet
79-
80-
The Ewasm testnet supports executing EVM 1.0 (Byzantium) bytecode **and** ewasm bytecode. The chain id is set to 0x42 (decimal 66).
81-
82-
There are two further technical differences:
83-
84-
- the code size limit introduced by Spurious Dragon has been lifted and there is no upper limit (as Wasm bytecode is more verbose than the EVM equivalent)
85-
- zero bytes in contract bytecode are not subsidised during deployment (they cost the same as non-zero bytes)
86-
87-
## Transacting
88-
89-
You don't need any special infrastructure to transact on the Ewasm testnet. You may run your own node (see below), or you may use the public node. You may view the list of testnet tools here: http://ewasm.ethereum.org/. Start by requesting test ether from the faucet:
90-
91-
- Configure Metamask to use the public node. Open Metamask, tap the network selector at the top, and click Custom RPC. Enter the following URL and click Save: http://ewasm.ethereum.org:8545.
92-
- Browse to the [faucet](http://ewasm.ethereum.org/faucet), make sure it read your public key correctly from Metamask in the "user" section, then tap "request 1 ether from faucet" in the "faucet" section.
93-
- Click the txid that appears in the "transactions" section and watch your faucet transaction get mined.
94-
95-
Voila! You're now ready to transact on the testnet.
96-
9797
## Running a testnet node locally
9898

9999
The testnet currently only supports the [go-ethereum](https://github.com/ethereum/go-ethereum) (geth) client. Support for aleth (formerly, cpp-ethereum) is a work in progress and more information may be found [here](aleth.md).

0 commit comments

Comments
 (0)