Network status
Announcement Official Record is live on-chain — Scrypt mining planned next

Published

HobbyHash Coin now publishes an Official Record — an append-only public ledger of project statements sealed with SHA-256 and anchored on the HOBC chain with one OP_RETURN transaction per seal (prefix HOBCOR1 + content hash).

• Browse the Official Record: https://hobbyhashcoin.com/official-record/

Tri-PoW (SHA256d + KawPow + RandomX) remains live. Scrypt is planned work and is not active yet.

— HobbyHash Coin
Linux node

Linux Node

Install and run a HOBC full node safely on Linux.

What a full node is

A full node downloads, verifies, and relays HobbyHash Coin blocks and transactions — including SHA-256d, KawPow GPU, and RandomX CPU blocks in the Tri-PoW race. Nodes matter because they independently validate the chain instead of trusting a third-party server. Inbound nodes also help other peers find and sync the network.

Outbound-only nodes can still sync, but inbound nodes help more because other peers can connect to them.

Download status

The requested AL9 Linux package path is:

/downloads/linux/HobbyHash-Linux-Node-AL9-x86_64.tar.gz

Download AL9 / RHEL 9 Linux Node

Checksums are available only when published on the downloads page. Do not invent or trust checksums from unofficial sources.

Build from GitHub source

The official node source repository is public (no GitHub login). It includes hobbyhash-clean/src only. Copy the block below as-is — commands are chained with && so a single paste works. Compiled binaries are not stored in Git — build them yourself after cloning.

git clone https://github.com/HobbyHash-Coin-LLC/HobbyHash.git &&
cd HobbyHash/hobbyhash-clean/src &&
./autogen.sh &&
./configure --without-gui &&
make -j"$(nproc)"

Recommended setup

  • Use a stable Linux server, home server, or always-on machine.
  • Use reliable storage with enough free disk space for chain growth.
  • Use a firewall.
  • Forward only mainnet P2P port 18761 if you want inbound peers.
  • Keep RPC bound to localhost and never expose RPC to the internet.
  • Use the Tri-PoW Linux node package from downloads to validate SHA-256, KawPow, and RandomX blocks.

Example mainnet config

Use this as a starting point and replace the RPC credentials before running a node.

server=1
listen=1
daemon=1
rpcuser=CHANGE_THIS_USERNAME
rpcpassword=CHANGE_THIS_LONG_RANDOM_PASSWORD
rpcbind=127.0.0.1
rpcallowip=127.0.0.1
port=18761
rpcport=18762
addnode=hobbyhashcoin.com:18761

Basic install flow

  1. Download a prebuilt package from hobbyhashcoin.com/downloads when available, or build from the official GitHub source.
  2. Verify checksums when available.
  3. Extract the package into a directory you control.
  4. Create the config file with private RPC settings.
  5. Start hobbyhashd.
  6. Watch logs until the node begins syncing.

Firewall and router

  • Forward 18761/tcp only if you want inbound mainnet peers.
  • Do not forward 18762.
  • For simple Linux firewalls, allow inbound TCP 18761 only.
  • RPC should remain reachable only from the same machine: 127.0.0.1.

Useful commands

hobbyhashd -conf=/path/to/hobbyhash.conf
hobbyhash-cli -conf=/path/to/hobbyhash.conf getblockchaininfo
hobbyhash-cli -conf=/path/to/hobbyhash.conf getnetworkinfo
hobbyhash-cli -conf=/path/to/hobbyhash.conf stop

Use getblockchaininfo to check height and sync status. Use getnetworkinfo to check peer count and network details. Stop the daemon safely with hobbyhash-cli stop.

Logs, resync, and bootstrap

View the node debug log in the configured data directory when troubleshooting startup, peers, or sync. The exact data directory path depends on how the node is installed and configured.

For resync basics, stop the node cleanly first, keep wallet backups safe, and only remove chain/index data when you understand what each directory contains. Never delete wallet files while troubleshooting chain sync.

Bootstrap snapshot: Coming soon. No official bootstrap snapshot is confirmed in the current site.