Skip to content
Platonx99 edited this page May 25, 2018 · 98 revisions

Webchaind is a Go language implementation of Webchain, supporting the original blockchain and its philosophy of immutability, censorship-resistance, and resilient distributed applications.

🔭 For general information related to Webchain including:

  • whitepaper
  • protocol and interface specs
  • affiliated APIs
  • DAPP development guides

Webchaind

The main Webchain client is called webchaind (the old english third person singular conjugation of "to go". Quite appropriate given webchaind is written in Go. Webchaind is a multipurpose command line tool that runs a full Webchain node. It offers three interfaces:

Platforms: Supported Platforms are Linux, Mac, and Windows. In order to install Webchaind, please vist our Releases Page. Please consider reviewing our Disclaimer Notice before use.

License: The Webchain Core Protocol licensed under the GNU Lesser General Public License 3.0. All frontend client software (under cmd) is licensed under the GNU General Public License.

By installing and running webchaind, you can take part in the Webchain live network and

  • mine WEB coins
  • transfer funds between addresses
  • create contracts and send transactions
  • explore block history
  • and much, much more

Basic Use Case Documentation

Install dependencies and build

Building and testing webchaind requires both Go >=1.8 and a C compiler.

Installing Go Wiki page

Get set up:

# Go get it! (get it? ;-)
go get github.com/webchain-network/webchaind/...

# Install binary 'webchaind' to $GOPATH/bin:
# Note: You can run this command from $cwd.
# Note: Ensure $GOPATH/bin is added to your $PATH.
go install github.com/webchain-network/webchaind/cmd/webchaind
# Or, install all executables, including webchaind:
go install github.com//webchain-network/webchaind/cmd/...

# check it out!
webchaind --help

Testing

See the Testing Wiki page for information on unit, integration, and external tests.

Logging

Webchaind outputs stderr to the console. Output from the console can be logged or redirected:

webchaind 2>>webchaind.log

Additionally, you may can use --log-dir=PATH to specify a directly in which webchaind will write it's logs to a timestamped file.

You can also use webchaind attach to begin a Javascript console session with an already-running instance of webchaind; just use a second terminal.

Further

Issues and Support

Please browse our FAQ Wiki page to see if there's already an answer to your question. If there isn't, please file an issue or get in touch with us on Slack (#help or #development channels, preferably).

Reporting

Security issues are best sent to splix@etcdevteam.org, isaac.ardis@gmail.com, or shared in PM with devs on one of the Slack channels.

Non-sensitive bug reports are welcome on Github. Please always state the version (on master) or commit of your build (if on develop), give as much detail as possible about the situation and the anomaly that occurred. Provide logs or stacktrace if you can.

Clone this wiki locally