mirror of
https://github.com/ethereum/go-ethereum.git
synced 2026-08-19 18:32:23 +00:00
hardcoded absolute links replaced with relative links
This commit is contained in:
Adam Schmideg
parent
079be26803
commit
6fc291a44e
25 changed files with 88 additions and 88 deletions
|
|
@ -13,9 +13,9 @@ The default data directory locations are platform specific:
|
|||
|
||||
Accounts are stored in the `keystore` subdirectory. The contents of this directories should be transportable between nodes, platforms, implementations (C++, Go, Python).
|
||||
|
||||
To configure the location of the data directory, the `--datadir` parameter can be specified. See [CLI Options](https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options) for more details.
|
||||
To configure the location of the data directory, the `--datadir` parameter can be specified. See [CLI Options](Command-Line-Options) for more details.
|
||||
|
||||
_**Note:** The [Ethash DAG](https://github.com/ethereum/go-ethereum/wiki/Mining#ethash-dag) is stored at `~/.ethash` (Mac/Linux) or `%APPDATA%\Ethash` (Windows) so that it can be reused by all clients. You can store this in a different location by using a symbolic link._
|
||||
_**Note:** The [Ethash DAG](Mining#ethash-dag) is stored at `~/.ethash` (Mac/Linux) or `%APPDATA%\Ethash` (Windows) so that it can be reused by all clients. You can store this in a different location by using a symbolic link._
|
||||
|
||||
## Upgrades
|
||||
|
||||
|
|
|
|||
|
|
@ -3,15 +3,15 @@
|
|||
Follow the appropriate link below to find installation instructions for
|
||||
your platform.
|
||||
|
||||
* [Installation Instructions for Mac OS X](https://github.com/ethereum/go-ethereum/wiki/Installation-Instructions-for-Mac)
|
||||
* [Installation Instructions for Windows](https://github.com/ethereum/go-ethereum/wiki/Installation-instructions-for-Windows)
|
||||
* [Installation Instructions for Mac OS X](Installation-Instructions-for-Mac)
|
||||
* [Installation Instructions for Windows](Installation-instructions-for-Windows)
|
||||
* Installation Instructions for Linux/Unix
|
||||
* [Ubuntu](https://github.com/ethereum/go-ethereum/wiki/Installation-Instructions-for-Ubuntu)
|
||||
* [Arch](https://github.com/ethereum/go-ethereum/wiki/Installation-Instructions-for-Arch)
|
||||
* [FreeBSD](https://github.com/ethereum/go-ethereum/wiki/Installation-Instructions-for-FreeBSD)
|
||||
* [Ubuntu](Installation-Instructions-for-Ubuntu)
|
||||
* [Arch](Installation-Instructions-for-Arch)
|
||||
* [FreeBSD](Installation-Instructions-for-FreeBSD)
|
||||
* [Setup for Raspberry Pi](https://github.com/ethereum/wiki/wiki/Raspberry-Pi-instructions)
|
||||
* [ARM](https://github.com/ethereum/go-ethereum/wiki/Installation-Instructions-for-ARM)
|
||||
* [Usage instructions for Docker](https://github.com/ethereum/go-ethereum/wiki/Running-in-Docker)
|
||||
* [ARM](Installation-Instructions-for-ARM)
|
||||
* [Usage instructions for Docker](Running-in-Docker)
|
||||
|
||||
## Quick Links
|
||||
|
||||
|
|
|
|||
|
|
@ -141,7 +141,7 @@ the following into `<datadir>/geth/static-nodes.json`:
|
|||
]
|
||||
```
|
||||
|
||||
You can also add static nodes at runtime via the js console using [`admin.addPeer()`](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#addpeer):
|
||||
You can also add static nodes at runtime via the js console using [`admin.addPeer()`](JavaScript-Console#addpeer):
|
||||
|
||||
```js
|
||||
admin.addPeer("enode://f4642fa65af50cfdea8fa7414a5def7bb7991478b768e296f5e4a54e8b995de102e0ceae2e826f293c481b5325f89be6d207b003382e18a8ecba66fbaf6416c0@33.4.2.1:30303")
|
||||
|
|
|
|||
|
|
@ -1,21 +1,21 @@
|
|||
### Native DApps
|
||||
|
||||
[Introduction and packages](https://github.com/ethereum/go-ethereum/wiki/Native:-Introduction)
|
||||
[Introduction and packages](Native:-Introduction)
|
||||
|
||||
[Account management](https://github.com/ethereum/go-ethereum/wiki/Native:-Account-management)
|
||||
[Account management](Native:-Account-management)
|
||||
|
||||
### Mobile platforms
|
||||
|
||||
[Introduction and packages](https://github.com/ethereum/go-ethereum/wiki/Mobile:-Introduction)
|
||||
[Introduction and packages](Mobile:-Introduction)
|
||||
|
||||
[Account management](https://github.com/ethereum/go-ethereum/wiki/Mobile:-Account-management)
|
||||
[Account management](Mobile:-Account-management)
|
||||
|
||||
### Transaction tracing
|
||||
|
||||
[Introduction and basics](https://github.com/ethereum/go-ethereum/wiki/Tracing:-Introduction)
|
||||
[Introduction and basics](Tracing:-Introduction)
|
||||
|
||||
[Custom in-node tracers](https://github.com/ethereum/go-ethereum/wiki/Tracing:-Custom-tracers)
|
||||
[Custom in-node tracers](Tracing:-Custom-tracers)
|
||||
|
||||
[Full blockchain tracing](https://github.com/ethereum/go-ethereum/wiki/Tracing:-Blockchain-tracing)
|
||||
[Full blockchain tracing](Tracing:-Blockchain-tracing)
|
||||
|
||||
[Dependency exfiltration](https://github.com/ethereum/go-ethereum/wiki/Tracing:-Exfiltration)
|
||||
[Dependency exfiltration](Tracing:-Exfiltration)
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
**NOTE: These instructions are for people who want to contribute Go source code changes.
|
||||
If you just want to run ethereum, use the normal [Installation Instructions](https://github.com/ethereum/go-ethereum/wiki/Building-Ethereum)**
|
||||
If you just want to run ethereum, use the normal [Installation Instructions](Building-Ethereum)**
|
||||
|
||||
This document is the entry point for developers of the Go implementation of Ethereum. Developers here refer to the hands-on: who are interested in build, develop, debug, submit a bug report or pull request or contribute code to go-ethereum.
|
||||
|
||||
|
|
@ -7,7 +7,7 @@ This document is the entry point for developers of the Go implementation of Ethe
|
|||
|
||||
### Go Environment
|
||||
|
||||
We assume that you have [`go` v1.8 installed](https://github.com/ethereum/go-ethereum/wiki/Installing-Go), and `GOPATH` is set.
|
||||
We assume that you have [`go` v1.8 installed](Installing-Go), and `GOPATH` is set.
|
||||
|
||||
**Note**:You must have your working copy under `$GOPATH/src/github.com/ethereum/go-ethereum`.
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ go-ethereum exectuables can be built individually. To build just geth, use:
|
|||
go install -v ./cmd/geth
|
||||
```
|
||||
|
||||
Read about cross compilation of go-ethereum [here](https://github.com/ethereum/go-ethereum/wiki/Cross-compiling-Ethereum).
|
||||
Read about cross compilation of go-ethereum [here](Cross-compiling-Ethereum).
|
||||
|
||||
### Git flow
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ for more see [go test flags](http://golang.org/cmd/go/#hdr-Description_of_testin
|
|||
### Metrics and monitoring
|
||||
|
||||
`geth` can do node behaviour monitoring, aggregation and show performance metric charts.
|
||||
Read about [metrics and monitoring](https://github.com/ethereum/go-ethereum/wiki/Metrics-and-Monitoring)
|
||||
Read about [metrics and monitoring](Metrics-and-Monitoring)
|
||||
|
||||
### Getting Stack Traces
|
||||
|
||||
|
|
@ -123,7 +123,7 @@ PRs need to be based on and opened against the `master` branch (unless by explic
|
|||
agreement, you contribute to a complex feature branch).
|
||||
|
||||
Your PR will be reviewed according to the [Code Review
|
||||
Guidelines](https://github.com/ethereum/go-ethereum/wiki/Code-Review-Guidelines).
|
||||
Guidelines](Code-Review-Guidelines).
|
||||
|
||||
We encourage a PR early approach, meaning you create the PR the earliest even without the
|
||||
fix/feature. This will let core devs and other volunteers know you picked up an issue.
|
||||
|
|
@ -131,8 +131,8 @@ These early PRs should indicate 'in progress' status.
|
|||
|
||||
## Dev Tutorials (mostly outdated)
|
||||
|
||||
* [Private networks, local clusters and monitoring](https://github.com/ethereum/go-ethereum/wiki/Setting-up-private-network-or-local-cluster)
|
||||
* [Private networks, local clusters and monitoring](Setting-up-private-network-or-local-cluster)
|
||||
|
||||
* [P2P 101](https://github.com/ethereum/go-ethereum/wiki/Peer-to-Peer): a tutorial about setting up and creating a p2p server and p2p sub protocol.
|
||||
* [P2P 101](Peer-to-Peer): a tutorial about setting up and creating a p2p server and p2p sub protocol.
|
||||
|
||||
* [How to Whisper](https://github.com/ethereum/go-ethereum/wiki/How-to-Whisper): an introduction to whisper.
|
||||
* [How to Whisper](How-to-Whisper): an introduction to whisper.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Specifications of all ethereum technologies, languages, protocols, etc.
|
|||
|
||||
- [JavaScript API](https://github.com/ethereum/wiki/wiki/JavaScript-API#a)
|
||||
- [Generic JSON RPC](https://github.com/ethereum/wiki/wiki/JSON-RPC)
|
||||
- [JSRE admin API](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#console-api)
|
||||
- [JSRE admin API](JavaScript-Console#console-api)
|
||||
- [RLP](https://github.com/ethereum/wiki/wiki/RLP)
|
||||
- [ÐΞVp2p Wire Protocol](https://github.com/ethereum/wiki/wiki/%C3%90%CE%9EVp2p-Wire-Protocol)
|
||||
- [Web3 Secret Storage](https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition)
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Building Geth for Android is a non trivial task, as it requires cross compiling external C dependencies ([GNU Arithmetic Library](https://gmplib.org/)); internal C dependencies ([ethash](https://github.com/ethereum/ethash)); as well as the entire CGO enabled Go code-base to Android. This is further complicated by the Position Independent Executables (PIE) security feature introduced since Android 4.1 Jelly Bean, requiring different compiler and linker options based on the target Android platform version.
|
||||
|
||||
To cope with all the build issues, the [`xgo`](https://github.com/karalabe/xgo) CGO enabled Go cross compiler is used, which assembles an entire multi-platform cross compiler suite into a single mega docker container. Details about using `xgo` can be found in the project's [README](https://github.com/karalabe/xgo/blob/master/README.md), with Ethereum specifics on the go-ethereum cross compilation [wiki page](https://github.com/ethereum/go-ethereum/wiki/Cross-compiling-Ethereum).
|
||||
To cope with all the build issues, the [`xgo`](https://github.com/karalabe/xgo) CGO enabled Go cross compiler is used, which assembles an entire multi-platform cross compiler suite into a single mega docker container. Details about using `xgo` can be found in the project's [README](https://github.com/karalabe/xgo/blob/master/README.md), with Ethereum specifics on the go-ethereum cross compilation [wiki page](Cross-compiling-Ethereum).
|
||||
|
||||
TL;DR
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
|
||||
**Q.** I would like to run multiple geth instances but got the error "Fatal: blockchain db err: resource temporarily unavailable".
|
||||
|
||||
**A.** Geth uses a datadir to store the blockchain, accounts and some additional information. This directory cannot be shared between running instances. If you would like to run multiple instances follow [these](https://github.com/ethereum/go-ethereum/wiki/Setting-up-private-network-or-local-cluster) instructions.
|
||||
**A.** Geth uses a datadir to store the blockchain, accounts and some additional information. This directory cannot be shared between running instances. If you would like to run multiple instances follow [these](Setting-up-private-network-or-local-cluster) instructions.
|
||||
|
||||
**Q.** How do Ethereum syncing work?
|
||||
|
||||
|
|
|
|||
14
docs/Geth.md
14
docs/Geth.md
|
|
@ -1,5 +1,5 @@
|
|||
`geth` is the the command line interface for running a full ethereum node implemented in Go.
|
||||
It is the main deliverable of the [Frontier Release](https://github.com/ethereum/go-ethereum/wiki/Frontier)
|
||||
It is the main deliverable of the [Frontier Release](Frontier)
|
||||
|
||||
## Capabilities
|
||||
|
||||
|
|
@ -15,20 +15,20 @@ By installing and running `geth`, you can take part in the ethereum frontier liv
|
|||
Supported Platforms are Linux, Mac Os and Windows.
|
||||
|
||||
We support two types of installation: binary or scripted install for users.
|
||||
See [Install instructions](https://github.com/ethereum/go-ethereum/wiki/Building-Ethereum) for binary and scripted installs.
|
||||
See [Install instructions](Building-Ethereum) for binary and scripted installs.
|
||||
|
||||
Developers and community enthusiast are advised to read the [Developers' Guide](https://github.com/ethereum/go-ethereum/wiki/Developers%27-Guide), which contains detailed instructions for manual build from source (on any platform) as well as detailed tips on testing, monitoring, contributing, debugging and submitting pull requests on github.
|
||||
Developers and community enthusiast are advised to read the [Developers' Guide](Developers%27-Guide), which contains detailed instructions for manual build from source (on any platform) as well as detailed tips on testing, monitoring, contributing, debugging and submitting pull requests on github.
|
||||
|
||||
## Interfaces
|
||||
|
||||
* Javascript Console: `geth` can be launched with an interactive console, that provides a javascript runtime environment exposing a javascript API to interact with your node. [Javascript Console API](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console) includes the `web3` javascript Ðapp API as well as an additional admin API.
|
||||
* Javascript Console: `geth` can be launched with an interactive console, that provides a javascript runtime environment exposing a javascript API to interact with your node. [Javascript Console API](JavaScript-Console) includes the `web3` javascript Ðapp API as well as an additional admin API.
|
||||
* JSON-RPC server: `geth` can be launched with a json-rpc server that exposes the [JSON-RPC API](https://github.com/ethereum/wiki/wiki/JSON-RPC)
|
||||
* [Command line options](https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options) documents command line parameters as well as subcommands.
|
||||
* [Command line options](Command-Line-Options) documents command line parameters as well as subcommands.
|
||||
|
||||
## Basic Use Case Documentation
|
||||
|
||||
* [Managing accounts](https://github.com/ethereum/go-ethereum/wiki/Managing-your-accounts)
|
||||
* [Mining](https://github.com/ethereum/go-ethereum/wiki/mining)
|
||||
* [Managing accounts](Managing-your-accounts)
|
||||
* [Mining](mining)
|
||||
|
||||
**Note** buying and selling ether through exchanges is not discussed here.
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Moved: [Management APIs](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)
|
||||
Moved: [Management APIs](Management-APIs)
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
Whisper is a pure identity-based messaging system. Whisper provides a low-level (non-application-specific) but easily-accessible API without being based upon or prejudiced by the low-level hardware attributes and characteristics, particularly the notion of singular endpoints.
|
||||
|
||||
This tutorial assumes you've read [p2p 101](https://github.com/ethereum/go-ethereum/wiki/Peer-to-Peer). If you haven't read it I suggest you read it. This tutorial will guide you to setting up a full p2p server with whisper capabilities.
|
||||
This tutorial assumes you've read [p2p 101](Peer-to-Peer). If you haven't read it I suggest you read it. This tutorial will guide you to setting up a full p2p server with whisper capabilities.
|
||||
|
||||
Let's quickly cover some of whisper's basic functionality and discuss it in greater detail later.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Installation Instructions for ARM
|
||||
|
||||
Geth is built for ARM using cross-compilation. See [Cross compiling Ethereum](https://github.com/ethereum/go-ethereum/wiki/Cross-compiling-Ethereum) for more details.
|
||||
Geth is built for ARM using cross-compilation. See [Cross compiling Ethereum](Cross-compiling-Ethereum) for more details.
|
||||
|
||||
## RasPi 2
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ git clone https://github.com/ethereum/go-ethereum
|
|||
```
|
||||
Install latest distribution of Go (v1.7) if you don't have it already:
|
||||
|
||||
[See instructions](https://github.com/ethereum/go-ethereum/wiki/Installing-Go#ubuntu-1404)
|
||||
[See instructions](Installing-Go#ubuntu-1404)
|
||||
|
||||
Building `geth` requires Go and C compilers to be installed:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Ethereum implements a **javascript runtime environment** (JSRE) that can be used in either interactive (console) or non-interactive (script) mode.
|
||||
|
||||
Ethereum's Javascript console exposes the full [web3 JavaScript Dapp API](https://github.com/ethereum/wiki/wiki/JavaScript-API) and the [admin API](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#javascript-console-api).
|
||||
Ethereum's Javascript console exposes the full [web3 JavaScript Dapp API](https://github.com/ethereum/wiki/wiki/JavaScript-API) and the [admin API](JavaScript-Console#javascript-console-api).
|
||||
|
||||
## Interactive use: the JSRE REPL Console
|
||||
|
||||
|
|
@ -71,4 +71,4 @@ In addition to the full functionality of JS (as per ECMA5), the ethereum JSRE is
|
|||
|
||||
Beside the official [DApp API](https://github.com/ethereum/wiki/wiki/JSON-RPC) interface the go ethereum node has support for additional management API's. These API's are offered using [JSON-RPC](http://www.jsonrpc.org/specification) and follow the same conventions as used in the DApp API. The go ethereum package comes with a console client which has support for all additional API's.
|
||||
|
||||
[The management API has its own wiki page](https://github.com/ethereum/go-ethereum/wiki/Management-APIs).
|
||||
[The management API has its own wiki page](Management-APIs).
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ These additional APIs follow the same conventions as the official DApp APIs. Web
|
|||
[extended](https://github.com/ethereum/web3.js/pull/229) and used to consume these additional APIs.
|
||||
|
||||
The different functions are split into multiple smaller logically grouped APIs. Examples are given
|
||||
for the [JavaScript console](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console) but
|
||||
for the [JavaScript console](JavaScript-Console) but
|
||||
can easily be converted to an RPC request.
|
||||
|
||||
**2 examples:**
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ or import). Without it you are not able to unlock your account.
|
|||
Note that exporting your key in unencrypted format is NOT supported.
|
||||
|
||||
Keys are stored under `<DATADIR>/keystore`. Make sure you backup your keys regularly! See
|
||||
[DATADIR backup & restore](https://github.com/ethereum/go-ethereum/wiki/Backup-&-restore)
|
||||
[DATADIR backup & restore](Backup-&-restore)
|
||||
for more information. If a custom datadir and keystore option are given the keystore
|
||||
option takes preference over the datadir option.
|
||||
|
||||
|
|
@ -59,7 +59,7 @@ OPTIONS:
|
|||
--keystore Directory for the keystore (default = inside the datadir)
|
||||
```
|
||||
|
||||
Accounts can also be managed via the [Javascript Console](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console)
|
||||
Accounts can also be managed via the [Javascript Console](JavaScript-Console)
|
||||
|
||||
## Examples
|
||||
### Interactive use
|
||||
|
|
@ -332,7 +332,7 @@ That can then be executed with:
|
|||
|
||||
Since this function will disappear after restarting geth, it can be helpful to store
|
||||
commonly used functions to be recalled later. The
|
||||
[loadScript](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#loadscript)
|
||||
[loadScript](JavaScript-Console#loadscript)
|
||||
function makes this very easy.
|
||||
|
||||
First, save the `checkAllBalances()` function definition to a file on your computer. For
|
||||
|
|
|
|||
|
|
@ -10,11 +10,11 @@ The C++ implementation of Ethereum also offers a GPU miner, both as part of Eth
|
|||
|
||||
_**NOTE:** Ensure your blockchain is fully synchronised with the main chain before starting to mine, otherwise you will not be mining on the main chain._
|
||||
|
||||
When you start up your ethereum node with `geth` it is not mining by default. To start it in mining mode, you use the `--mine` [command line option](https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options). The `-minerthreads` parameter can be used to set the number parallel mining threads (defaulting to the total number of processor cores).
|
||||
When you start up your ethereum node with `geth` it is not mining by default. To start it in mining mode, you use the `--mine` [command line option](Command-Line-Options). The `-minerthreads` parameter can be used to set the number parallel mining threads (defaulting to the total number of processor cores).
|
||||
|
||||
`geth --mine --minerthreads=4`
|
||||
|
||||
You can also start and stop CPU mining at runtime using the [console](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#adminminerstart). `miner.start` takes an optional parameter for the number of miner threads.
|
||||
You can also start and stop CPU mining at runtime using the [console](JavaScript-Console#adminminerstart). `miner.start` takes an optional parameter for the number of miner threads.
|
||||
|
||||
```
|
||||
> miner.start(8)
|
||||
|
|
@ -25,7 +25,7 @@ true
|
|||
|
||||
Note that mining for real ether only makes sense if you are in sync with the network (since you mine on top of the consensus block). Therefore the eth blockchain downloader/synchroniser will delay mining until syncing is complete, and after that mining automatically starts unless you cancel your intention with `miner.stop()`.
|
||||
|
||||
In order to earn ether you must have your **etherbase** (or **coinbase**) address set. This etherbase defaults to your [primary account](https://github.com/ethereum/go-ethereum/wiki/Managing-your-accounts). If you don't have an etherbase address, then `geth --mine` will not start up.
|
||||
In order to earn ether you must have your **etherbase** (or **coinbase**) address set. This etherbase defaults to your [primary account](Managing-your-accounts). If you don't have an etherbase address, then `geth --mine` will not start up.
|
||||
|
||||
You can set your etherbase on the command line:
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ miner.setEtherbase(eth.accounts[2])
|
|||
|
||||
Note that your etherbase does not need to be an address of a local account, just an existing one.
|
||||
|
||||
There is an option [to add extra Data](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#adminminersetextra) (32 bytes only) to your mined blocks. By convention this is interpreted as a unicode string, so you can set your short vanity tag.
|
||||
There is an option [to add extra Data](JavaScript-Console#adminminersetextra) (32 bytes only) to your mined blocks. By convention this is interpreted as a unicode string, so you can set your short vanity tag.
|
||||
|
||||
```
|
||||
miner.setExtra("ΞTHΞЯSPHΞЯΞ")
|
||||
|
|
@ -61,7 +61,7 @@ Header:
|
|||
|
||||
See also [this proposal](https://github.com/ethereum/wiki/wiki/Extra-Data)
|
||||
|
||||
You can check your hashrate with [miner.hashrate](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console#adminminerhashrate), the result is in H/s (Hash operations per second).
|
||||
You can check your hashrate with [miner.hashrate](JavaScript-Console#adminminerhashrate), the result is in H/s (Hash operations per second).
|
||||
|
||||
```
|
||||
> miner.hashrate
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This page describes how to set up a monitoring site, [like this one](http://eth-netstats.herokuapp.com/), for your private network. It builds upon [this wiki article](https://github.com/ethereum/go-ethereum/wiki/Setting-up-private-network-or-local-cluster) and assumes you've created a local cluster using [this script (gethcluster.sh)](https://github.com/ethersphere/eth-utils).
|
||||
This page describes how to set up a monitoring site, [like this one](http://eth-netstats.herokuapp.com/), for your private network. It builds upon [this wiki article](Setting-up-private-network-or-local-cluster) and assumes you've created a local cluster using [this script (gethcluster.sh)](https://github.com/ethersphere/eth-utils).
|
||||
|
||||
The monitoring system consists of two components:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
This page describes how to set up a local cluster of nodes, advise how to make it private, and how to hook up your nodes on the eth-netstat network monitoring app.
|
||||
A fully controlled ethereum network is useful as a backend for network integration testing (core developers working on issues related to networking/blockchain synching/message propagation, etc or DAPP developers testing multi-block and multi-user scenarios).
|
||||
|
||||
We assume you are able to build `geth` following the [build instructions](https://github.com/ethereum/go-ethereum/wiki/Building-Ethereum)
|
||||
We assume you are able to build `geth` following the [build instructions](Building-Ethereum)
|
||||
|
||||
## Setting up multiple nodes
|
||||
|
||||
|
|
@ -112,5 +112,5 @@ I0216 10:01:40.094089 p2p/discover/udp.go:227] Listening, enode://890b6b5367ef60
|
|||
|
||||
[This page](https://github.com/ethereum/wiki/wiki/Network-Status) describes how to use the [The Ethereum (centralised) network status monitor (known sometimes as "eth-netstats")](http://stats.ethdev.com) to monitor your nodes.
|
||||
|
||||
[This page](https://github.com/ethereum/go-ethereum/wiki/Setting-up-monitoring-on-local-cluster) or [this README](https://github.com/ethersphere/eth-utils)
|
||||
[This page](Setting-up-monitoring-on-local-cluster) or [this README](https://github.com/ethersphere/eth-utils)
|
||||
describes how you set up your own monitoring service for a (private or public) local cluster.
|
||||
|
|
@ -28,7 +28,7 @@
|
|||
|
||||
## APIs
|
||||
- DAPP API - js integration (Fabian, Alex)
|
||||
- mist dapp storage scheme, url->hash mapping (Fabian, Alex) https://github.com/ethereum/go-ethereum/wiki/URL-Scheme
|
||||
- mist dapp storage scheme, url->hash mapping (Fabian, Alex) [URL scheme](URL-Scheme)
|
||||
|
||||
# Discuss alternatives
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ every named host defines a timeline,
|
|||
The host part in a bzz webaddress should be resolved with our version of DNS, ie. using both `NameReg` (name registration contract on ethereum) and a simple mutable storage in swarm.
|
||||
|
||||
## signed version store
|
||||
The point of channels (https://github.com/ethereum/go-ethereum/wiki/Swarm---Channels
|
||||
The point of channels (Swarm---Channels
|
||||
) is to have a total order over a set of manifests.
|
||||
|
||||
The typical usecase is that it should be enough to know the name of a site or document to always see the latest version of a software or get the current episode of your favourite series or the consensus state of a blockchain. It should also be possible to deterministically derive the key to future content...
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
## Whisper v6
|
||||
|
||||
[Whisper Overview](https://github.com/ethereum/go-ethereum/wiki/Whisper-Overview)
|
||||
[Whisper Overview](Whisper-Overview)
|
||||
|
||||
[Whisper web3.js API Documentation](http://web3js.readthedocs.io/en/1.0/web3-shh.html)
|
||||
|
||||
[Whisper RPC API 6.0](https://github.com/ethereum/go-ethereum/wiki/Whisper-v6-RPC-API)
|
||||
[Whisper RPC API 6.0](Whisper-v6-RPC-API)
|
||||
|
||||
[Diagnostic Tool wnode](https://github.com/ethereum/go-ethereum/wiki/Diagnostic-Tool-wnode)
|
||||
[Diagnostic Tool wnode](Diagnostic-Tool-wnode)
|
||||
|
||||
[Achieving Darkness](https://github.com/ethereum/go-ethereum/wiki/Achieving-Darkness)
|
||||
[Achieving Darkness](Achieving-Darkness)
|
||||
|
||||
[Javascript Example](https://github.com/ethereum/go-ethereum/wiki/Whisper-js-example)
|
||||
[Javascript Example](Whisper-js-example)
|
||||
|
||||
## Legacy documentation (unsupported)
|
||||
|
||||
Whisper v2 to v5 are no longer supported.
|
||||
|
||||
[Whisper RPC API 5.0](https://github.com/ethereum/go-ethereum/wiki/Whisper-v5-RPC-API)
|
||||
[Whisper RPC API 5.0](Whisper-v5-RPC-API)
|
||||
|
|
@ -10,7 +10,7 @@ Both types of accounts have an ether balance.
|
|||
|
||||
Transactions can be fired from from both types of accounts, though contracts only fire transactions in response to other transactions that they have received. Therefore, all action on ethereum block chain is set in motion by transactions fired from externally controlled accounts.
|
||||
|
||||
The simplest transactions are ether transfer transactions. But before we go into that you should read up on [accounts](https://github.com/ethereum/go-ethereum/wiki/Managing-your-accounts) and perhaps on [mining](https://github.com/ethereum/go-ethereum/wiki/Mining).
|
||||
The simplest transactions are ether transfer transactions. But before we go into that you should read up on [accounts](Managing-your-accounts) and perhaps on [mining](Mining).
|
||||
|
||||
## Ether transfer
|
||||
|
||||
|
|
@ -166,9 +166,9 @@ So how did you pay for all this? Under the hood, the transaction specified a gas
|
|||
|
||||
Gas limit is there to protect you from buggy code running until your funds are depleted. The product of `gasPrice` and `gas` represents the maximum amount of Wei that you are willing to pay for executing the transaction. What you specify as `gasPrice` is used by miners to rank transactions for inclusion in the blockchain. It is the price in Wei of one unit of gas, in which VM operations are priced.
|
||||
|
||||
The gas expenditure incurred by running your contract will be bought by the ether you have in your account at a price you specified in the transaction with `gasPrice`. If you do not have the ether to cover all the gas requirements to complete running your code, the processing aborts and all intermediate state changes roll back to the pre-transaction snapshot. The gas used up to the point where execution stopped were used after all, so the ether balance of your account will be reduced. These parameters can be adjusted on the transaction object fields `gas` and `gasPrice`. The `value` field is used the same as in ether transfer transactions between normal accounts. In other words transferring funds is available between any two accounts, either normal (i.e. externally controlled) or contract. If your contract runs out of funds, you should see an insufficient funds error. Note that all funds on contract accounts will be irrecoverably lost, once we release [Homestead](https://github.com/ethereum/go-ethereum/wiki/Homestead) (see [the rules of the game](https://github.com/ethereum/go-ethereum/wiki/Frontier)).
|
||||
The gas expenditure incurred by running your contract will be bought by the ether you have in your account at a price you specified in the transaction with `gasPrice`. If you do not have the ether to cover all the gas requirements to complete running your code, the processing aborts and all intermediate state changes roll back to the pre-transaction snapshot. The gas used up to the point where execution stopped were used after all, so the ether balance of your account will be reduced. These parameters can be adjusted on the transaction object fields `gas` and `gasPrice`. The `value` field is used the same as in ether transfer transactions between normal accounts. In other words transferring funds is available between any two accounts, either normal (i.e. externally controlled) or contract. If your contract runs out of funds, you should see an insufficient funds error. Note that all funds on contract accounts will be irrecoverably lost, once we release [Homestead](Homestead) (see [the rules of the game](Frontier)).
|
||||
|
||||
For testing and playing with contracts you can use the test network or [set up a private node (or cluster)](https://github.com/ethereum/go-ethereum/wiki/Setting-up-private-networklock-or-local-cluster) potentially isolated from all the other nodes. If you then mine, you can make sure that your transaction will be included in the next block. You can see the pending transactions with:
|
||||
For testing and playing with contracts you can use the test network or [set up a private node (or cluster)](Setting-up-private-networklock-or-local-cluster) potentially isolated from all the other nodes. If you then mine, you can make sure that your transaction will be included in the next block. You can see the pending transactions with:
|
||||
|
||||
```js
|
||||
eth.getBlock("pending", true).transactions
|
||||
|
|
|
|||
|
|
@ -2,42 +2,42 @@
|
|||
|
||||
### Install and build
|
||||
|
||||
[Installing Ethereum](https://github.com/ethereum/go-ethereum/wiki/Building-Ethereum)
|
||||
[Installing Ethereum](Building-Ethereum)
|
||||
|
||||
[Developers' Guide](https://github.com/ethereum/go-ethereum/wiki/Developers%27-Guide)
|
||||
[Developers' Guide](Developers%27-Guide)
|
||||
|
||||
### Usage
|
||||
|
||||
[Managing Accounts](https://github.com/ethereum/go-ethereum/wiki/Managing-your-accounts)
|
||||
[Managing Accounts](Managing-your-accounts)
|
||||
|
||||
[Mining](https://github.com/ethereum/go-ethereum/wiki/Mining)
|
||||
[Mining](Mining)
|
||||
|
||||
[Contract Tutorial](https://github.com/ethereum/go-ethereum/wiki/Contract-Tutorial)
|
||||
[Contract Tutorial](Contract-Tutorial)
|
||||
|
||||
### Interface Documentation
|
||||
|
||||
[Command Line Options](https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options)
|
||||
[Command Line Options](Command-Line-Options)
|
||||
|
||||
[JavaScript Console](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console)
|
||||
[JavaScript Console](JavaScript-Console)
|
||||
|
||||
[Management API](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)
|
||||
[Management API](Management-APIs)
|
||||
|
||||
[JSON-RPC server](https://github.com/ethereum/wiki/wiki/JSON-RPC)
|
||||
|
||||
### Issues
|
||||
|
||||
[FAQ](https://github.com/ethereum/go-ethereum/wiki/FAQ)
|
||||
[FAQ](FAQ)
|
||||
|
||||
[Reporting issues](https://github.com/ethereum/go-ethereum/wiki/geth#reporting)
|
||||
[Reporting issues](geth#reporting)
|
||||
|
||||
[Community and support](https://github.com/ethereum/go-ethereum/wiki/geth#community-and-support)
|
||||
[Community and support](geth#community-and-support)
|
||||
|
||||
[Issue handling workflow](https://github.com/ethereum/go-ethereum/wiki/Issue-handling-workflow) (draft proposal)
|
||||
[Issue handling workflow](Issue-handling-workflow) (draft proposal)
|
||||
|
||||
### Developers
|
||||
|
||||
[Mobile Clients](https://github.com/ethereum/go-ethereum/wiki/Mobile-Clients:-Libraries-and-Inproc-Ethereum-Nodes)
|
||||
[Mobile Clients](Mobile-Clients:-Libraries-and-Inproc-Ethereum-Nodes)
|
||||
|
||||
[Native DApps](https://github.com/ethereum/go-ethereum/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts)
|
||||
[Native DApps](Native-DApps:-Go-bindings-to-Ethereum-contracts)
|
||||
|
||||
[Active go-ethereum projects](https://github.com/ethereum/go-ethereum/wiki/Active-go-ethereum-projects)
|
||||
[Active go-ethereum projects](Active-go-ethereum-projects)
|
||||
|
|
|
|||
|
|
@ -5,13 +5,13 @@ This is the Wiki for the official Ethereum golang implementation. For generic Et
|
|||
|
||||
Main entry points:
|
||||
|
||||
* [Installation Instructions](https://github.com/ethereum/go-ethereum/wiki/Building-Ethereum)
|
||||
* [Developer/Management API](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)
|
||||
* [Managing Accounts](https://github.com/ethereum/go-ethereum/wiki/Managing-your-accounts)
|
||||
* [Command Line Options](https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options)
|
||||
* [JavaScript Console](https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console)
|
||||
* [Private Network](https://github.com/ethereum/go-ethereum/wiki/Private-network)
|
||||
* [Developers' Guide](https://github.com/ethereum/go-ethereum/wiki/Developers'-Guide)
|
||||
* [Whisper v6](https://github.com/ethereum/go-ethereum/wiki/Whisper)
|
||||
* [Installation Instructions](Building-Ethereum)
|
||||
* [Developer/Management API](Management-APIs)
|
||||
* [Managing Accounts](Managing-your-accounts)
|
||||
* [Command Line Options](Command-Line-Options)
|
||||
* [JavaScript Console](JavaScript-Console)
|
||||
* [Private Network](Private-network)
|
||||
* [Developers' Guide](Developers'-Guide)
|
||||
* [Whisper v6](Whisper)
|
||||
|
||||
Sidebar lists all pages.
|
||||
|
|
|
|||
Loading…
Reference in a new issue