Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/elastos/elastos.ela.sidechain.esc


https://github.com/elastos/elastos.ela.sidechain.esc

Last synced: 4 months ago
JSON representation

Awesome Lists containing this project

README 

        
## Elastos.ELA.SideChain.ESC



Elastos Sidechain implementation based on Go Ethereum.



## Building the source



For prerequisites and detailed build instructions please read the

[Installation Instructions](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Building-Ethereum)

on the wiki.



Building `geth` requires both a Go (version 1.20 or later) and a C compiler. You can install

them using your favourite package manager. Once the dependencies are installed, run



```shell

export GO111MODULE=on

go mod tidy

make geth

```



or, to build the full suite of utilities:



```shell

export GO111MODULE=on

go mod tidy

make all

```



## Executables



The Elastos.ELA.SideChain.ESC project comes with several wrappers/executables found in the `cmd`

directory.



| Command    | Description |

|:----------:|-------------|

| **`geth`** | Our main ELA-Ethereum CLI client. It is the entry point into the ELA-Ethereum  network (main-, test- or private net), capable of running as a full node (default), archive node (retaining all historical state) or a light node (retrieving data live). It can be used by other processes as a gateway into the Ethereum network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. `geth --help` and the [CLI Wiki page](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Command-Line-Options) for command line options. |

| `abigen` | Source code generator to convert Ethereum contract definitions into easy to use, compile-time type-safe Go packages. It operates on plain [Ethereum contract ABIs](https://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) with expanded functionality if the contract bytecode is also available. However it also accepts Solidity source files, making development much more streamlined. Please see our [Native DApps](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts) wiki page for details. |

| `bootnode` | Stripped down version of our Ethereum client implementation that only takes part in the network node discovery protocol, but does not run any of the higher level application protocols. It can be used as a lightweight bootstrap node to aid in finding peers in private networks. |

| `evm` | Developer utility version of the EVM (Ethereum Virtual Machine) that is capable of running bytecode snippets within a configurable environment and execution mode. Its purpose is to allow isolated, fine-grained debugging of EVM opcodes (e.g. `evm --code 60ff60ff --debug`). |

| `gethrpctest` | Developer utility tool to support our [ethereum/rpc-test](https://github.com/ethereum/rpc-tests) test suite which validates baseline conformity to the [Ethereum JSON RPC](https://github.com/ethereum/wiki/wiki/JSON-RPC) specs. Please see the [test suite's readme](https://github.com/ethereum/rpc-tests/blob/master/README.md) for details. |

| `rlpdump` | Developer utility tool to convert binary RLP ([Recursive Length Prefix](https://github.com/ethereum/wiki/wiki/RLP)) dumps (data encoding used by the Ethereum protocol both network as well as consensus wise) to user friendlier hierarchical representation (e.g. `rlpdump --hex CE0183FFFFFFC4C304050583616263`). |

| `puppeth`    | a CLI wizard that aids in creating a new Ethereum network. |



## Running `geth`



Going through all the possible command line flags is out of scope here (please consult our

[CLI Wiki page](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Command-Line-Options)),

but we've enumerated a few common parameter combos to get you up to speed quickly

on how you can run your own `geth` instance.



### Hardware Requirements



Minimum:



* CPU with 2+ cores

* 4GB RAM

* 1TB free storage space to sync the Mainnet

* 8 MBit/sec download Internet service



Recommended:



* Fast CPU with 4+ cores

* 16GB+ RAM

* High-performance SSD with at least 1TB of free space

* 25+ MBit/sec download Internet service



### Full node on the main Ethereum network



By far the most common scenario is people wanting to simply interact with the Ethereum

network: create accounts; transfer funds; deploy and interact with contracts. For this

particular use-case the user doesn't care about years-old historical data, so we can

fast-sync quickly to the current state of the network. To do so:



```shell

$ geth console

```



This command will:

 * Start `geth` in fast sync mode (default, can be changed with the `--syncmode` flag),

   causing it to download more data in exchange for avoiding processing the entire history

   of the Ethereum network, which is very CPU intensive.

 * Start up `geth`'s built-in interactive [JavaScript console](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/JavaScript-Console),

   (via the trailing `console` subcommand) through which you can invoke all official [`web3` methods](https://github.com/elastos/wiki/wiki/JavaScript-API)

   as well as `geth`'s own [management APIs](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Management-APIs).

   This tool is optional and if you leave it out you can always attach to an already running

   `geth` instance with `geth attach`.



### A Full node on the Ethereum test network



Transitioning towards developers, if you'd like to play around with creating Ethereum

contracts, you almost certainly would like to do that without any real money involved until

you get the hang of the entire system. In other words, instead of attaching to the main

network, you want to join the **test** network with your node, which is fully equivalent to

the main network, but with play-Ether only.



```shell

$ geth --testnet console

```



The `console` subcommand has the exact same meaning as above and they are equally

useful on the testnet too. Please see above for their explanations if you've skipped here.



Specifying the `--testnet` flag, however, will reconfigure your `geth` instance a bit:



 * Instead of using the default data directory (`~/.ela_ethereum` on Linux for example), `geth`

   will nest itself one level deeper into a `testnet` subfolder (`~/.ela_ethereum/testnet` on

   Linux). Note, on OSX and Linux this also means that attaching to a running testnet node

   requires the use of a custom endpoint since `geth attach` will try to attach to a

   production node endpoint by default. E.g.

   `geth attach /testnet/geth.ipc`. Windows users are not affected by

   this.

 * Instead of connecting the main Ethereum network, the client will connect to the test

   network, which uses different P2P bootnodes, different network IDs and genesis states.



*Note: Although there are some internal protective measures to prevent transactions from

crossing over between the main network and test network, you should make sure to always

use separate accounts for play-money and real-money. Unless you manually move

accounts, `geth` will by default correctly separate the two networks and will not make any

accounts available between them.*



### Full node on the Rinkeby test network



The above test network is a cross-client one based on the ethash proof-of-work consensus

algorithm. As such, it has certain extra overhead and is more susceptible to reorganization

attacks due to the network's low difficulty/security. Go Ethereum also supports connecting

to a proof-of-authority based test network called [*Rinkeby*](https://www.rinkeby.io)

(operated by members of the community). This network is lighter, more secure, but is only

supported by Elastos.ELA.SideChain.ESC.



```shell

$ geth --rinkeby console

```



### How to topup ELA to ETH

* use compile [ELA-Client](https://github.com/elastos/Elastos.ELA.Client)

* create topup transaction: `./ela-cli wallet -t create --deposit eth_address(ETH address) --amount recharge_value(amount ela units) --fee recharge_fee(fee ela units)`

* sign transaction: `./ela-cli wallet -t sign --file to_be_signed.txn -p yourpassword(your keystore password)`

* send transaction: `./ela-cli wallet -t send --file ready_to_send.txn`



### How to withdraw ETH to ELA

* use node console: `node`

* use contract code:



```

Web3 = require("web3");

// set web3 uri

web3 = new Web3("http://127.0.0.1:20636");

// set withdraw contract

contract = new web3.eth.Contract([{"constant":false,"inputs":[{"name":"_addr","type":"string"},{"name":"_amount","type":"uint256"},{"name":"_fee","type":"uint256"}],"name":"receivePayload","outputs":[],"payable":true,"stateMutability":"payable","type":"function"},{"payable":true,"stateMutability":"payable","type":"fallback"},{"anonymous":false,"inputs":[{"indexed":false,"name":"_addr","type":"string"},{"indexed":false,"name":"_amount","type":"uint256"},{"indexed":false,"name":"_crosschainamount","type":"uint256"},{"indexed":true,"name":"_sender","type":"address"}],"name":"PayloadReceived","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"_sender","type":"address"},{"indexed":false,"name":"_amount","type":"uint256"},{"indexed":true,"name":"_black","type":"address"}],"name":"EtherDeposited","type":"event"}]);

// set eth account address

contract.options.address = deploy_contract_address;

// set account contract keystore info

acc = web3.eth.accounts.decrypt(keystore_content, ketstore_password);   

// call receivePayload function，params：(ELA main chain address，amount(In ela up to convert wei 10000000000)，fee)

cdata  = contract.methods.receivePayload(ELA_address, withdraw_amount, fee).encodeABI();

// gas minimum is 3000000，gasPrice is any value

tx = {data: cdata, to: contract.options.address, from: acc.address, gas: "3000000", gasPrice: "20000000000"};

// send transaction amount(use receivePayload function amount)

tx.value = withdraw_amount;

acc.signTransaction(tx).then((res)=>{

   console.log("coming");

   stx = res;

   console.log(stx.rawTransaction);

   web3.eth.sendSignedTransaction(stx.rawTransaction).then(console)});

```

*Note: ELA testnet server Deploy Contract Address: `0x491bC043672B9286fA02FA7e0d6A3E5A0384A31A`

ELA mainnet server Deploy Contract Address: `0xC445f9487bF570fF508eA9Ac320b59730e81e503`*



### Configuration



As an alternative to passing the numerous flags to the `geth` binary, you can also pass a

configuration file via:



```shell

$ geth --config /path/to/your_config.toml

```



To get an idea how the file should look like you can use the `dumpconfig` subcommand to

export your existing configuration:



```shell

$ geth --your-favourite-flags dumpconfig

```



*Note: This works only with `geth` v1.6.0 and above.*



### Programmatically interfacing `geth` nodes



As a developer, sooner rather than later you'll want to start interacting with Geth and the Ethereum

network via your own programs and not manually through the console. To aid this, Geth has built-in

support for a JSON-RPC based APIs ([standard APIs](https://github.com/ethereum/wiki/wiki/JSON-RPC) and

[Geth specific APIs](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Management-APIs)). These can be

exposed via HTTP, WebSockets and IPC (unix sockets on unix based platforms, and named pipes on Windows).



The IPC interface is enabled by default and exposes all the APIs supported by Geth, whereas the HTTP

and WS interfaces need to manually be enabled and only expose a subset of APIs due to security reasons.

These can be turned on/off and configured as you'd expect.



HTTP based JSON-RPC API options:



  * `--rpc` Enable the HTTP-RPC server

  * `--rpcaddr` HTTP-RPC server listening interface (default: "localhost")

  * `--rpcport` HTTP-RPC server listening port (default: 20636)

  * `--rpcapi` API's offered over the HTTP-RPC interface (default: "eth,net,web3")

  * `--rpccorsdomain` Comma separated list of domains from which to accept cross origin requests (browser enforced)

  * `--ws` Enable the WS-RPC server

  * `--wsaddr` WS-RPC server listening interface (default: "localhost")

  * `--wsport` WS-RPC server listening port (default: 20635)

  * `--wsapi` API's offered over the WS-RPC interface (default: "eth,net,web3")

  * `--wsorigins` Origins from which to accept websockets requests

  * `--ipcdisable` Disable the IPC-RPC server

  * `--ipcapi` API's offered over the IPC-RPC interface (default: "admin,debug,eth,miner,net,personal,shh,txpool,web3")

  * `--ipcpath` Filename for IPC socket/pipe within the datadir (explicit paths escape it)



You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect

via HTTP, WS or IPC to a Geth node configured with the above flags and you'll need to speak [JSON-RPC](http://www.jsonrpc.org/specification)

on all transports. You can reuse the same connection for multiple requests!



**Note: Please understand the security implications of opening up an HTTP/WS based

transport before doing so! Hackers on the internet are actively trying to subvert

Ethereum nodes with exposed APIs! Further, all browser tabs can access locally

running web servers, so malicious web pages could try to subvert locally available

APIs!**



### Operating a private network



Maintaining your own private network is more involved as a lot of configurations taken for

granted in the official networks need to be manually set up.



#### Defining the private genesis state



First, you'll need to create the genesis state of your networks, which all nodes need to be

aware of and agree upon. This consists of a small JSON file (e.g. call it `genesis.json`):



```json

{

  "config": {

    "chainId": ,

    "homesteadBlock": 0,

    "eip150Block": 0,

    "eip155Block": 0,

    "eip158Block": 0,

    "byzantiumBlock": 0,

    "constantinopleBlock": 0,

    "petersburgBlock": 0

  },

  "alloc": {},

  "coinbase": "0x0000000000000000000000000000000000000000",

  "difficulty": "0x20000",

  "extraData": "",

  "gasLimit": "0x2fefd8",

  "nonce": "0x0000000000000042",

  "mixhash": "0x0000000000000000000000000000000000000000000000000000000000000000",

  "parentHash": "0x0000000000000000000000000000000000000000000000000000000000000000",

  "timestamp": "0x00"

}

```



The above fields should be fine for most purposes, although we'd recommend changing

the `nonce` to some random value so you prevent unknown remote nodes from being able

to connect to you. If you'd like to pre-fund some accounts for easier testing, create

the accounts and populate the `alloc` field with their addresses.



```json

"alloc": {

  "0x0000000000000000000000000000000000000001": {

    "balance": "111111111"

  },

  "0x0000000000000000000000000000000000000002": {

    "balance": "222222222"

  }

}

```



With the genesis state defined in the above JSON file, you'll need to initialize **every**

`geth` node with it prior to starting it up to ensure all blockchain parameters are correctly

set:



```shell

$ geth init path/to/genesis.json

```



#### Creating the rendezvous point



With all nodes that you want to run initialized to the desired genesis state, you'll need to

start a bootstrap node that others can use to find each other in your network and/or over

the internet. The clean way is to configure and run a dedicated bootnode:



```shell

$ bootnode --genkey=boot.key

$ bootnode --nodekey=boot.key

```



With the bootnode online, it will display an [`enode` URL](https://github.com/ethereum/wiki/wiki/enode-url-format)

that other nodes can use to connect to it and exchange peer information. Make sure to replace the

displayed IP address information (most probably `[::]`) with your externally accessible IP to get the

actual `enode` URL.



*Note: You could also use a full fledged Geth node as a bootnode, but it's the less recommended way.*



#### Starting up your member nodes



With the bootnode operational and externally reachable (you can try

`telnet  ` to ensure it's indeed reachable), start every subsequent `geth`

node pointed to the bootnode for peer discovery via the `--bootnodes` flag. It will

probably also be desirable to keep the data directory of your private network separated, so

do also specify a custom `--datadir` flag.



```shell

$ geth --datadir=path/to/custom/data/folder --bootnodes=

```



*Note: Since your network will be completely cut off from the main and test networks, you'll

also need to configure a miner to process transactions and create new blocks for you.*



#### Running a private miner



Mining on the public Ethereum network is a complex task as it's only feasible using GPUs,

requiring an OpenCL or CUDA enabled `ethminer` instance. For information on such a

setup, please consult the [EtherMining subreddit](https://www.reddit.com/r/EtherMining/)

and the [Genoil miner](https://github.com/Genoil/cpp-ethereum) repository.



In a private network setting, however a single CPU miner instance is more than enough for

practical purposes as it can produce a stable stream of blocks at the correct intervals

without needing heavy resources (consider running on a single thread, no need for multiple

ones either). To start a `geth` instance for mining, run it with all your usual flags, extended

by:



```shell

$ geth  --mine --miner.threads=1 --etherbase=0x0000000000000000000000000000000000000000

```



Which will start mining blocks and transactions on a single CPU thread, crediting all

proceedings to the account specified by `--etherbase`. You can further tune the mining

by changing the default gas limit blocks converge to (`--targetgaslimit`) and the price

transactions are accepted at (`--gasprice`).



## Upgrade EVM version to London

This section highlights the main breaking changes introduced in Solidity version 0.8.19.

For the full list check [the release changelog](https://github.com/ethereum/solidity/releases/tag/v0.8.19)



## Contribution



Thank you for considering to help out with the source code! We welcome contributions

from anyone on the internet, and are grateful for even the smallest of fixes!



If you'd like to contribute to Elastos.ELA.SideChain.ESC, please fork, fix, commit and send a pull request

for the maintainers to review and merge into the main code base. If you wish to submit

more complex changes though, please check up with the core devs first on [our gitter channel](https://gitter.im/elastos/Elastos.ELA.SideChain.ESC)

to ensure those changes are in line with the general philosophy of the project and/or get

some early feedback which can make both your efforts much lighter as well as our review

and merge procedures quick and simple.



Please make sure your contributions adhere to our coding guidelines:



 * Code must adhere to the official Go [formatting](https://golang.org/doc/effective_go.html#formatting)

   guidelines (i.e. uses [gofmt](https://golang.org/cmd/gofmt/)).

 * Code must be documented adhering to the official Go [commentary](https://golang.org/doc/effective_go.html#commentary)

   guidelines.

 * Pull requests need to be based on and opened against the `master` branch.

 * Commit messages should be prefixed with the package(s) they modify.

   * E.g. "eth, rpc: make trace configs optional"



Please see the [Developers' Guide](https://github.com/elastos/Elastos.ELA.SideChain.ESC/wiki/Developers'-Guide)

for more details on configuring your environment, managing project dependencies, and

testing procedures.



## License



The Elastos.ELA.SideChain.ESC library (i.e. all code outside of the `cmd` directory) is licensed under the

[GNU Lesser General Public License v3.0](https://www.gnu.org/licenses/lgpl-3.0.en.html),

also included in our repository in the `COPYING.LESSER` file.



The Elastos.ELA.SideChain.ESC binaries (i.e. all code inside of the `cmd` directory) is licensed under the

[GNU General Public License v3.0](https://www.gnu.org/licenses/gpl-3.0.en.html), also

included in our repository in the `COPYING` file.