d0wn3d/gobyted repository overview

| | | |

⁠GOBYTE CORE DOCKERIZED

⁠Production-ready Docker image for seamless GoByte full-node deployment, with integrated Python Sentinel for automated Masternode health management.

⁠🖥️ System Requirements

• Architecture: x86_64 (AMD/Intel) or ARM64 (Raspberry Pi 4/5, AWS Graviton).
• OS: Linux with Docker 24.0+.
• Storage: 40 GB HDD/SSD/NVMe.
• Memory: 4 GB RAM is the sweet spot. If using 2 GB, a 2 GB swap file on an SSD is mandatory.
• Network: Stable internet with at least 5 Mbps upload and port 12455 (13455 for testnet) OPEN for optimal peer connectivity.

⁠🚀 Key Features

• Multi-Arch Support: Native binaries for linux/amd64 (PC/Servers) and linux/arm64 (Raspberry Pi/Apple Silicon).

• Image Types:

  :latest (Debian-Slim): Maximum stability and compatibility (glibc), compatible with most Linux distributions and cloud providers.

  :develop (Debian-Slim): Unstable. Pre-release versions for testing new features. Expect frequent changes and potential bugs.

• Security First: Runs as a non-root user (gobyte) with stripped binaries.

• Masternode Ready: Optimized for 24/7 uptime and low latency, with minimal resource usage.

⁠📦 What's Inside:

• gobyted: The backbone of the operation. This is the full-node daemon that handles blockchain synchronization, block validation, and network connectivity.
• gobyte-cli: Your command-line remote control. Use this to interact with the daemon, manage your wallet, and query the blockchain without breaking a sweat.
• gobyte-tx: The surgical tool for power users. It allows for the creation, handling, and signing of raw transactions—perfect for those who like to look under the hood.

⁠🏗️ Quick Start

⁠1. Create a Persistent Volume

First, create a gobyted-data volume. This ensures your blockchain data persists even if the container is updated or recreated:

    docker volume create --name=gobyted-data

⁠2. Launch the Node

Run the container in detached mode. This maps the necessary P2P and RPC ports and attaches the volume you just created:

    docker run -d \
    --name gobyted-node \
    -v gobyted-data:/home/gobyte \
    -p 12455:12455 \
    -p 127.0.0.1:12454:12454 \
    d0wn3d/gobyted

⁠3. Verify the Status

Check if the container is running and the node is successfully downloading the blockchain:

    docker ps

Expected Output:

    CONTAINER ID   IMAGE             COMMAND            STATUS          PORTS
    d0e1076b2dca   d0wn3d/gobyted    "gobyte_oneshot"   Up 2 seconds    127.0.0.1:12454->12454/tcp, 0.0.0.0:12455->12455/tcp

⁠4. Monitor Logs

    docker logs -f gobyted-node

⁠⚙️ Configuration & Usage

Running in Testnet

If you want to join the testnet instead of the mainnet, simply pass the TESTNET=1 environment variable.

[!NOTE] Testnet typically uses different ports. Ensure your port mappings match the testnet requirements if you are connecting from outside the container.

    docker run -d \
      --name gobyted-node-testnet \
      --env TESTNET=1 \
      -v gobyted-data:/home/gobyte \
      -p 13455:13455 \
      -p 127.0.0.1:12454:12454 \
      d0wn3d/gobyted

Interacting with the Node

Once the container is running, you don't need to enter the container to use the CLI tools. You can use docker exec to run commands directly:

• Get Node Info:

    docker exec gobyted-node gobyte-cli getblockchaininfo
  

  Copy

• List Wallet Addresses:

    docker exec gobyted-node gobyte-cli listaddressgroupings
  

  Copy

Stopping the Daemon

To safely shut down the node and ensure the blockchain database is flushed to the volume correctly:

    docker stop gobyted-node

Additional documentation in the docs folder⁠.

⁠💎 Credits

Original work by Kyle Manna https://github.com/kylemanna/docker-bitcoind⁠. Modified to use GoByte Core instead of Bitcoin Core.

⁠💎 Donations

GBX: GT6XDe4RsS8vGpqW5mU3nywkCAanZZ1bT8 BTC: