Go to file
obscuren 10b252dd05 WIP RPC interface 2014-10-21 13:24:48 +02:00
ethchain Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
ethcrypto Renamed Sha3Bin to Sha3 2014-10-08 12:06:39 +02:00
ethdb Removed old code 2014-08-23 11:00:33 +02:00
ethlog ethlog: fix typo in documentation 2014-10-17 17:23:29 +02:00
ethminer Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
ethpipe Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
ethrpc add pushtx to api 2014-09-09 21:27:34 -07:00
ethstate Use the state instead of the state object directly. 2014-10-16 13:38:21 +02:00
ethtrie Added generic big to 256 method. Implemented new iterator 2014-10-10 17:00:06 +02:00
ethutil Using proper naming scheme. Fixes #63 2014-10-18 13:23:01 +02:00
ethwire New block message 2014-10-08 12:29:49 +02:00
event event: panic for duplicate type 2014-10-16 18:59:28 +02:00
pow/ar Implemented AR PoW 2014-10-10 22:44:20 +02:00
rpc WIP RPC interface 2014-10-21 13:24:48 +02:00
tests Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
types Working on new (blocking) event machine. 2014-09-29 12:57:51 +02:00
ui Moved Filter's wrapping functions to their own util package. Fixes #61 2014-10-18 13:20:06 +02:00
vm Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
websocket Implemented WebSocket package 2014-09-30 23:26:52 +02:00
.gitignore Merge branch 'feature/keys' of https://github.com/ethersphere/go-ethereum into ethersphere-feature/keys 2014-07-01 13:45:39 +02:00
.travis.yml Travis bumped to 1.3 2014-10-18 14:20:51 +02:00
LICENSE MIT -> LGPL 2014-08-21 15:43:14 +02:00
README.md Re-enabled Travis 2014-10-18 13:50:48 +02:00
block_pool.go Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
ethereum.go Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00
events.go all: use (blocking) event package instead of ethreact 2014-10-16 18:50:48 +02:00
nat.go Implemented support for UPnP 2014-02-02 19:22:39 +01:00
natpmp.go Implemented POST 2014-08-25 11:29:42 +02:00
natupnp.go Fixed Upnp bug 2014-05-01 22:14:20 +02:00
peer.go Renamed block_chain to chain_manager 2014-10-20 11:53:11 +02:00

README.md

Ethereum

Master: Build Status Develop: Build Status

Ethereum Go Development package (C) Jeffrey Wilcke

Ethereum is currently in its testing phase. The current state is "Proof of Concept 0.6.5". For build instructions see the Wiki.

Ethereum Go is split up in several sub packages Please refer to each individual package for more information.

  1. eth
  2. ethchain
  3. ethwire
  4. ethdb
  5. ethutil
  6. ethpipe
  7. ethvm
  8. ethtrie
  9. ethreact
  10. ethlog

The eth is the top-level package of the Ethereum protocol. It functions as the Ethereum bootstrapping and peer communication layer. The ethchain contains the Ethereum blockchain, block manager, transaction and transaction handlers. The ethwire contains the Ethereum wire protocol which can be used to hook in to the Ethereum network. ethutil contains utility functions which are not Ethereum specific. The utility package contains the patricia trie, RLP Encoding and hex encoding helpers. The ethdb package contains the LevelDB interface and memory DB interface.

This is the bootstrap package. Eth-go contains all the necessary code to get a node and connectivity going.

Build

This is the Developer package. For the Ethereal client please see Ethereum(G).

go get -u github.com/ethereum/eth-go

Contribution

If you'd like to contribute to Eth please fork, fix, commit and send a pull request. Commits who do not comply with the coding standards are ignored (use gofmt!). If you send pull requests make absolute sure that you commit on the develop branch and that you do not merge to master. Commits that are directly based on master are simply ignored.

To make life easier try git flow it sets this all up and streamlines your work flow.

Coding standards

Sources should be formatted according to the Go Formatting Style.

Unless structs fields are supposed to be directly accesible, provide Getters and hide the fields through Go's exporting facility.

When you comment put meaningfull comments. Describe in detail what you want to achieve.

wrong

// Check if the value at x is greater than y
if x > y {
    // It's greater!
}

Everyone reading the source probably know what you wanted to achieve with above code. Those are not meaningful comments.

While the project isn't 100% tested I want you to write tests non the less. I haven't got time to evaluate everyone's code in detail so I expect you to write tests for me so I don't have to test your code manually. (If you want to contribute by just writing tests that's fine too!)