mirror of
https://github.com/ethereum/go-ethereum.git
synced 2026-08-20 02:42:27 +00:00
All wiki pages have a title
This commit is contained in:
Adam Schmideg
parent
937adb59ce
commit
fa23987ec8
69 changed files with 203 additions and 13 deletions
|
|
@ -3,7 +3,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
|
||||
<title>Go Ethereum</title>
|
||||
<title>{% if page.title %}{{ page.title }} | {% endif %}Go Ethereum</title>
|
||||
{% if site.google_analytics %}
|
||||
<!-- Google Analytics -->
|
||||
<script>
|
||||
|
|
|
|||
|
|
@ -39,7 +39,6 @@ common-js:
|
|||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
{{ content }}
|
||||
<hr/>
|
||||
<footer>
|
||||
|
|
|
|||
|
|
@ -15,8 +15,11 @@ layout: default
|
|||
{% endfor %}
|
||||
</div>
|
||||
<div class="col-md-9" id="content">
|
||||
{% if page.title %}
|
||||
<h1 class="featurette-heading">{{ page.title }}</h1>
|
||||
{% endif %}
|
||||
|
||||
{{ content }}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Accounts
|
||||
---
|
||||
**THIS PAGE IS PARTLY OUTDATED! TODO: REFACTOR OR DELETE**
|
||||
|
||||
# Accounts / key storage specification
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Achieving Darkness
|
||||
---
|
||||
Whisper is designed to be a building block in the next generation of unstoppable ÐApps. It was designed to provide resilience and privacy at considerable expense. At its most secure mode of operation Whisper can theoretically deliver complete darkness. Whisper should also allow the users to configure the level of privacy (how much information it leaks concerning the ÐApp content and ultimately, user activities) as a trade-off for performance. In this article we will discuss the strategy of achieving complete darkness.
|
||||
|
||||
### Adversary
|
||||
|
|
|
|||
|
|
@ -1,4 +1,7 @@
|
|||
# Direction of development until the end of 2018
|
||||
---
|
||||
title: Active go-ethereum projects
|
||||
---
|
||||
## Direction of development until the end of 2018
|
||||
|
||||
- Clef: move account management out of geth to clef
|
||||
- Constantinople - Tools for testing
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Backup & restore
|
||||
---
|
||||
**DO NOT FORGET YOUR PASSWORD** and **BACKUP YOUR KEYSTORE**
|
||||
|
||||
# Backup & restore
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Building Ethereum
|
||||
---
|
||||
## Installation Instructions
|
||||
|
||||
Follow the appropriate link below to find installation instructions for
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Code Review Guidelines
|
||||
---
|
||||
The only way to get code into go-ethereum is to send a pull request. Those pull requests
|
||||
need to be reviewed by someone. This document is a guide that explains our expectations
|
||||
around PRs for both authors and reviewers.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Commandline options
|
||||
---
|
||||
```
|
||||
$ geth help
|
||||
NAME:
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Connecting to the network
|
||||
---
|
||||
## How Peers Are Found
|
||||
|
||||
Geth continuously attempts to connect to other nodes on the network
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Contract tutorial
|
||||
---
|
||||
## Introduction
|
||||
|
||||
Now that you mastered the basics on how to get started and how to send ether, it's time to get your hands dirty in what really makes ethereum stand out of the crowd: smart contracts. Smart contracts are pieces of code that live on the blockchain and execute commands exactly how they were told to. They can read other contracts, make decisions, send ether and execute other contracts. Contracts will exist and run as long as the whole network exists, and will only stop if they run out of gas or if they were programmed to self destruct.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Creating your own Ethereum apps using Eth go
|
||||
---
|
||||
The modular nature of Go and the Ethereum Go implementation, [eth-go](https://github.com/ethereum/eth-go), make it very easy to build your own Ethereum native applications.
|
||||
|
||||
This post will cover the minimal steps required to build an native Ethereum application.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Cross-compiling Ethereum
|
||||
---
|
||||
**Note: All of these and much more have been merged into the project Makefile.
|
||||
You can cross build via `make geth-<os>-<platform>` without needing to know any
|
||||
of these details from below.**
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Developer guide
|
||||
---
|
||||
### Native DApps
|
||||
|
||||
[Introduction and packages](Native:-Introduction)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Developers' guide
|
||||
---
|
||||
**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](Building-Ethereum)**
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Diagnostic tool wnode
|
||||
---
|
||||
## Wnode
|
||||
|
||||
Wnode (whisper node) is a command-line diagnostic tool. It does not have a nice user interface, because its main purpose is diagnostic, and it's meant to be very light-weight rather than beautiful. Wnode might be used for different purposes, including:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Disclaimer
|
||||
---
|
||||
title: Disclaimer
|
||||
---
|
||||
|
||||
Safety caveats
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Ethereum specification
|
||||
---
|
||||
Specifications of all ethereum technologies, languages, protocols, etc.
|
||||
|
||||
### Whitepapers and design rationale
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Ethereum on Android
|
||||
---
|
||||
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](Cross-compiling-Ethereum).
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: FAQ
|
||||
---
|
||||
***
|
||||
**Q.** I noticed my peercount slowly decrease, and now it is at 0. Restarting doesn't get any peers.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Gas price oracle
|
||||
---
|
||||
The gas price oracle is a helper function of the Geth client that tries to find an appropriate default gas price when sending transactions. It can be parametrized with the following command line options:
|
||||
|
||||
- gpomin: lower limit of suggested gas price. This should be set at least as high as the "gasprice" setting usually used by miners so that your transactions will not be rejected automatically because of a too low price.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: How to Whisper
|
||||
---
|
||||
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](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.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Installation Instructions for ARM
|
||||
---
|
||||
title: Installation instructions for ARM
|
||||
---
|
||||
|
||||
Geth is built for ARM using cross-compilation. See [Cross compiling Ethereum](Cross-compiling-Ethereum) for more details.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installation instructions for Arch
|
||||
---
|
||||
## Installing using pacman
|
||||
|
||||
The `geth` package is available from the [community repo](https://www.archlinux.org/packages/community/x86_64/geth/).
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installation instructions for FreeBSD
|
||||
---
|
||||
## Building from source
|
||||
|
||||
### Installing binary package
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installation instructions for Mac
|
||||
---
|
||||
## Installing with Homebrew
|
||||
|
||||
By far the easiest way to install go-ethereum is to use our
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installation instructions for Ubuntu
|
||||
---
|
||||
## Installing from PPA
|
||||
|
||||
```shell
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installation instructions for Windows
|
||||
---
|
||||
# Binaries
|
||||
|
||||
## Download stable binaries
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installing Geth
|
||||
---
|
||||
The Go implementation of Ethereum can be installed using a variety of ways. These include obtaining it as part of Mist; installing it via your favorite package manager; downloading a standalone pre-built bundle; running as a docker container; or building it yourself. This document will detail all of these possibilities to get you quickly joining the Ethereum network using whatever means you prefer.
|
||||
|
||||
* [Install from a package manager](#install-from-a-package-manager)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Installing Go
|
||||
---
|
||||
### Windows
|
||||
|
||||
Download and run the installer found at http://golang.org/doc/install
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Issue handling workflow
|
||||
---
|
||||
### (Draft proposal)
|
||||
Keep the number of open issues under 820
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Contracts and transactions (Japanese)
|
||||
---
|
||||
THIS WIKI IS BEING EDITED AND REVIEWED NOW. PLEASE DO NOT RELY ON IT.
|
||||
|
||||
# Account types and transactions
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: JavaScript console
|
||||
---
|
||||
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](JavaScript-Console#javascript-console-api).
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Management APIs
|
||||
---
|
||||
Beside the official [DApp APIs](https://github.com/ethereum/wiki/wiki/JSON-RPC) interface go-ethereum
|
||||
has support for additional management APIs. Similar to the DApp APIs, these are also provided using
|
||||
[JSON-RPC](http://www.jsonrpc.org/specification) and follow exactly the same conventions. Geth comes
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Managing your accounts
|
||||
---
|
||||
**WARNING**
|
||||
Remember your password.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Metrics and monitoring
|
||||
---
|
||||
Geth has quite a nice logging system, capable of creating leveled log entries tagged with various parts of the system. This helps enormously during debugging to see exactly what the system is doing, what branches it's taking, etc. However, logs are not particularly useful when the system does work correctly, just not very optimally: one - or even a handful - of logged events is not really statistically relevant, and tracing more in log files can quickly become unwieldy.
|
||||
|
||||
The goal of the Geth metrics system is that - similar to logs - we should be able to add arbitrary metric collection to any part of the code without requiring fancy constructs to analyze them (counter variables, public interfaces, crossing over the APIs, console hooks, etc). Instead, we should just "update" metrics whenever and wherever needed, and have them automatically collected, surfaced through the APIs, queryable and visualizable for analysis.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Mining
|
||||
---
|
||||
* [Introduction to Ethereum mining](https://github.com/ethereum/wiki/wiki/Mining#introduction) _(main wiki)_
|
||||
|
||||
# CPU Mining with Geth
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Mobile Clients
|
||||
---
|
||||
**This page has been obsoleted. An new guide is in the progress at [[Mobile: Introduction]]**
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Mobile / Account management
|
||||
---
|
||||
To provide Ethereum integration for your mobile applications, the very first thing you should be interested in doing is account management.
|
||||
|
||||
Although all current leading Ethereum implementations provide account management built in, it is ill advised to keep accounts in any location that is shared between multiple applications and/or multiple people. The same way you do not entrust your ISP (who is after all your gateway into the internet) with your login credentials; you should not entrust an Ethereum node (who is your gateway into the Ethereum network) with your credentials either.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Mobile / Introduction
|
||||
---
|
||||
The Ethereum blockchain along with its two extension protocols Whisper and Swarm was originally conceptualized to become the supporting pillar of web3, providing the consensus, messaging and storage backbone for a new generation of distributed (actually, decentralized) applications called DApps.
|
||||
|
||||
The first incarnation towards this dream of web3 was a command line client providing an RPC interface into the peer-to-peer protocols. The client was soon enough extended with a web-browser-like graphical user interface, permitting developers to write DApps based on the tried and proven HTML/CSS/JS technologies.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Native DApps / Go bindings to Ethereum contracts
|
||||
---
|
||||
**[Please note, events are not yet implemented as they need some RPC subscription
|
||||
features that are still under review.]**
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Native / Account management
|
||||
---
|
||||
To provide Ethereum integration for your native applications, the very first thing you should be interested in doing is account management.
|
||||
|
||||
Although all current leading Ethereum implementations provide account management built in, it is ill advised to keep accounts in any location that is shared between multiple applications and/or multiple people. The same way you do not entrust your ISP (who is after all your gateway into the internet) with your login credentials; you should not entrust an Ethereum node (who is your gateway into the Ethereum network) with your credentials either.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Native / Introduction
|
||||
---
|
||||
The Ethereum blockchain along with its two extension protocols Whisper and Swarm was originally conceptualized to become the supporting pillar of web3, providing the consensus, messaging and storage backbone for a new generation of distributed (actually, decentralized) applications called DApps.
|
||||
|
||||
The first incarnation towards this dream of web3 was a command line client providing an RPC interface into the peer-to-peer protocols. The client was soon enough extended with a web-browser-like graphical user interface, permitting developers to write DApps based on the tried and proven HTML/CSS/JS technologies.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Peer-to-peer
|
||||
---
|
||||
The peer to peer package ([go-ethereum/p2p](https://github.com/ethereum/go-ethereum/tree/develop/p2p)) allows you to rapidly and easily add peer to peer networking to any type of application. The p2p package is set up in a modular structure and extending the p2p with your own additional sub protocols is easy and straight forward.
|
||||
|
||||
Starting the p2p service only requires you setup a `p2p.Server{}` with a few settings:
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Private network
|
||||
---
|
||||
An Ethereum network is a private network if the nodes are not connected to the main
|
||||
network nodes. In this context private only means reserved or isolated, rather than
|
||||
protected or secure.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Provisional JS API
|
||||
---
|
||||
The *provisional* JavaScript API is a purposed API for all things JavaScript. JavaScript technologies can be embedded within Qt(QML) technologies, local web and remote web and therefor the purposed API is written in a ASYNC fashion so that it may be used across all implementations. Hereby it should be known that all functions, unless explicitly specified, take a callback as last function argument which will be called when the operation has been completed.
|
||||
|
||||
Please note that the provisional JavaScript API tries to leverage existing JS idioms as much as possible.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: RPS pub-sub
|
||||
---
|
||||
# Introduction
|
||||
|
||||
From version 1.4 geth has **_experimental_** support for pub/sub using subscriptions as defined in the JSON-RPC 2.0 specification. This allows clients to wait for events instead of polling for them.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Running in Docker
|
||||
---
|
||||
title: Running in Docker
|
||||
---
|
||||
|
||||
We keep a Docker image with recent snapshot builds from the `develop` branch [on DockerHub](https://hub.docker.com/r/ethereum/client-go/). In addition to the container based on [Ubuntu](http://www.ubuntu.com) (158 MB), there is a smaller image using [Alpine Linux](https://alpinelinux.org) (35 MB). To use the alpine [tag](https://hub.docker.com/r/ethereum/client-go/tags), replace `ethereum/client-go` with `ethereum/client-go:alpine` in the examples below.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Sending ether
|
||||
---
|
||||
title: Sending ether
|
||||
---
|
||||
|
||||
The basic way of sending a simple transaction of ether with the console is as follows:
|
||||
```js
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Setting up Ethereum Native
|
||||
---
|
||||
## Dream API
|
||||
|
||||
i.e., something I'm envisioning for *soon*(tm)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Setting up monitoring on local cluster
|
||||
---
|
||||
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,3 +1,6 @@
|
|||
---
|
||||
title: Setting up private network or local cluster
|
||||
---
|
||||
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).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Swarm TODO
|
||||
---
|
||||
# Sprint plan
|
||||
|
||||
# scope
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Swarm - distributed preimage archive
|
||||
---
|
||||
# Resources
|
||||
|
||||
## Swarm, the name
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Swarm channels, namereg-resolution draft
|
||||
---
|
||||
# Channels and streams
|
||||
|
||||
a *swarm chain* is an ordered list of content that are linked as a forkless chain.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Swarm contract
|
||||
---
|
||||
This one contract regulates the incentive structure of Swarm.
|
||||
|
||||
The corresponding solidity code can be browsed [here](https://github.com/ethersphere/go-ethereum/blob/bzz/bzz/bzzcontract/swarm.sol).
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Tracing / Introduction
|
||||
---
|
||||
There are two different types of transactions in Ethereum: plain value transfers and contract executions. A plain value transfer just moves Ether from one account to another and as such is uninteresting from this guide's perspective. If however the recipient of a transaction is a contract account with associated EVM (Ethereum Virtual Machine) bytecode - beside transferring any Ether - the code will also be executed as part of the transaction.
|
||||
|
||||
Having code associated with Ethereum accounts permits transactions to do arbitrarilly complex data storage and enables them to act on the previously stored data by further transacting internally with outside accounts and contracts. This creates an intertwined ecosystem of contracts, where a single transaction can interact with tens or hunderds of accounts.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: URL Scheme
|
||||
---
|
||||
# URLs in DAPP browsers
|
||||
|
||||
URLs should contain all allowable urls in browsers and _all_ `http(s)` urls that resolve in a usual browser must resolve the same way.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Whisper overview
|
||||
---
|
||||
## Whisper Overview
|
||||
|
||||
Whisper is a pure identity-based messaging system. Whisper provides a simple low-level API without being based upon or influenced by the low-level hardware attributes and characteristics. Peer-to-peer communication between the nodes of Whisper network uses the underlying [ÐΞVp2p Wire Protocol](https://github.com/ethereum/wiki/wiki/%C3%90%CE%9EVp2p-Wire-Protocol). Whisper was not designed to provide a connection-oriented system, nor for simply delivering data between a pair of particular network endpoints. However, this might be necessary in some very specific cases (e.g. delivering the expired messages in case they were missed), and Whisper protocol will accommodate for that. Whisper is designed for easy and efficient broadcasting, and also for low-level asynchronous communications. It is designed to be a building block in next generation of unstoppable ÐApps. It was designed to provide resilience and privacy at considerable expense. At its most secure mode of operation, Whisper can theoretically deliver 100% darkness. Whisper should also allow the users to configure the level of privacy (how much information it leaks concerning the ÐApp content and ultimately, user activities) as a trade-off for performance.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Javascript example
|
||||
---
|
||||
title: Whisper JavaScript example
|
||||
---
|
||||
|
||||
[This link](https://github.com/gballet/whisper-chat-example) contains a full-fledged example of how to use Whisper in a small chat application.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Whisper RPC API 5.0
|
||||
---
|
||||
title: Whisper RPC API 5.0
|
||||
---
|
||||
|
||||
This is the proposed API for whisper v5.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Whisper RPC API 6.0
|
||||
---
|
||||
title: Whisper RPC API 6.0
|
||||
---
|
||||
|
||||
This is the proposed API for whisper v6.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
## Whisper v6
|
||||
---
|
||||
title: Whisper v6
|
||||
---
|
||||
|
||||
[Whisper Overview](Whisper-Overview)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Geth
|
||||
---
|
||||
`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://ethereum.gitbooks.io/frontier-guide/content/frontier.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Documentation
|
||||
---
|
||||
* User documentation can be found at our [Ethereum User Guide and reference manual](http://ethereum.gitbooks.io/frontier-guide/content/).
|
||||
* For the API reference and developer documentation head over to the auto generated [GoDoc](https://godoc.org/github.com/ethereum/go-ethereum) documentation.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Other documents
|
||||
---
|
||||
- [Accounts key-storage specification](/docs/Accounts---key-storage-specification)
|
||||
- [Connecting to the network](/docs/Connecting-to-the-network)
|
||||
- [Creating your own Ethereum apps using Eth go](/docs/Creating-your-own-Ethereum-apps-using-Eth-go)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
---
|
||||
title: Swarm POC series
|
||||
---
|
||||
now project features and POC milestones are managed under
|
||||
https://github.com/ethereum/go-ethereum/projects/6
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
layout: default
|
||||
title: Downloads
|
||||
css:
|
||||
- /static/styles/custom/downloads.css
|
||||
js:
|
||||
|
|
|
|||
Loading…
Reference in a new issue