Start Here!

Hi - we're glad you want to start using the Diode Network - you won't be disappointed!

To start consuming content from the Diode Network, or to publish content via the Diode Network, see the sections below.

To read more about the Diode Network and related technologies, see the Useful Links and Articles.

Let us know if you have any questions or suggestions for this content via Telegram!

Consume Public Content via the Internet Gateway

Diode hosts an Internet gateway at diode.link. Public content published via the Diode Network is accessible via this gateway at <client-address>.diode.link. For example, you can type https://pi-taipei.diode.link in a web browser to view streaming video from our Taipei office.

If you want to access Private or Protected content, or just want to access the Diode Network without using the public gateway, install the Diode Client (next section) and see the article about accessing Web 3.0 content.

Publish Content or Consume Private/Protected Content

The Diode Client enables you to quickly publish content to the Diode Network, or to directly access content already published. It is a fast way to start interacting directly with the Diode Network from your local device.

Install the Diode Client

The Diode Client runs on Linux (x86 and ARM), Mac, and Windows. To install, visit our Downloads page or run this command in a terminal window:

curl -Ssf https://diode.io/install.sh | sh

Once installed, type diode in a terminal window to get a list of commands and additional information. The Go Client Commands article also describes the client capabilities.

Manage Your Identities

All addresses on the Diode Network are unique and are used as identities to interact with the network. They can be used to publish content, access private or protected content, manage Fleet Contracts, and reserve a BNS name (domain name).

Addresses (identities) on the Diode Network are Ethereum public addresses. In order to instantiate something persistent on the Diode Network, you must have an address, and you must have access to the addresses' private key - typically stored in a wallet somewhere.

Each Diode Client has its own wallet that it manages on the device the client is running on. However, there are many use cases in which it is valuable to manage aspects of the Diode Network without relying on a specific instance of the Diode Client - for these use cases, we recommend using a browser with a MetaMask plugin and the Diode Network Explorer (docs).

See the article "Configure MetaMask" to get MetaMask setup.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)