https://github.com/diodechain/diode_node

Diode Relay Node
https://github.com/diodechain/diode_node

Last synced: about 2 months ago
JSON representation

Diode Relay Node

• Host: GitHub
• URL: https://github.com/diodechain/diode_node
• Owner: diodechain
• License: other
• Created: 2024-05-17T12:10:46.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2025-04-08T10:27:42.000Z (2 months ago)
• Last Synced: 2025-04-08T11:29:48.629Z (2 months ago)
• Language: Elixir
• Homepage:
• Size: 2.02 MB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
![diode logo](https://diode.io/images/logo-trans.svg)

> ### Secure. Super Light. Web3. 

# Diode Network Relay Node

Relay nodes are at the heart of Diodes decentralized infrastructure network. Each node helps devices to communicate securely and efficiently through the Diode network. More nodes in more regions mean more available bandwidth for a growing network.

When deploying a node it should be setup on publicly reachable interfaces with a public IP. If the Node is not reachable from other nodes it might eventually get blocked and not receive any traffic. Nodes are gaining reputation over time when they stay up and available.

# Getting Started

To get started with the diode node install the latest snap release:

[![Get it from the Snap Store](https://snapcraft.io/en/dark/install.svg)](https://snapcraft.io/diode-node)

```bash

sudo snap install diode-node

```

## Snap Configuration

After installation all configuration values are available via the snap config system:

```bash

sudo snap get diode-node

```

# Linux Kernel optimization

To optimize Linux for maximum network performance we advise to enable tcp bbr:

```/etc/sysctl.conf

net.core.default_qdisc=fq

net.ipv4.tcp_congestion_control=bbr

```

```/etc/modules-load.d/modules.conf

tcp_bbr

```

And then reboot or 

```bash

sudo modprobe tcp_bbr 

sudo sysctl --system

```

# Operations

## See last service restart reason

When running the snap installation then it's a two step process to see the last service restart reason:

1. Get the timestamp of the last service restart

2. Read the logs around that timestamp

```bash

> systemctl show -p ActiveEnterTimestamp snap.diode-node.service.service

ActiveEnterTimestamp=Mon 2024-12-30 02:57:06 UTC

> journalctl -u snap.diode-node.service.service --since "2024-12-30 02:50:00"

```