AnnouncementOfficial 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
Wallet
Wallet Guide
Receive, send, back up, and protect HOBC wallet keys safely.
What a wallet does
A HOBC wallet stores the keys needed to receive and spend HobbyHash Coin. The blockchain records transactions, but the wallet controls the keys that authorize spending. If the keys are lost, the coins controlled by those keys can become permanently inaccessible.
A wallet can create receiving addresses, track balances, build transactions, and broadcast payments through a synced node or wallet backend.
Linux desktop wallet
Download the Linux AppImage or .deb from the official downloads page. The AppImage is portable: save it, run chmod +x on the file, then launch it. The .deb installs through sudo dpkg -i and adds HobbyHash Wallet to your applications menu.
Both packages bundle the same HOBC full node and wallet UI as Windows. RPC stays on 127.0.0.1 only — do not expose port 18762 to your LAN or the internet.
If hobbyhashd is already running for mining on this machine, the wallet adopts the existing node on 127.0.0.1:18762 when it can connect. Stop the external node first if you want the wallet to manage its own bundled copy exclusively.
Prefer the AppImage on mining rigs and portable setups; use .deb on Ubuntu/Debian desktops.
AppImage automatic updates work when you launch the wallet from the same AppImage file path.
Verify SHA256 checksums from the downloads page before installing.
Give only the public receiving address to the sender or miner.
Wait for the transaction to appear and gain confirmations.
For mining, use the address before the dot in the worker name: HOBC_ADDRESS.WORKERNAME.
Sending HOBC
Check the destination address carefully before sending.
Send a small test amount first when using a new address or tool.
After broadcast, use the transaction ID in the explorer when available.
Do not send funds from a wallet you cannot back up or unlock.
Confirmations
A confirmation means a transaction is included in a block. More blocks after that block add more confirmations. Services may require different confirmation counts before treating a transaction as final. Confirmation policy for any specific service is To be confirmed unless that service publishes it.
Encryption and backups
Encrypt wallets when the wallet software supports encryption.
Use a strong password that you can store safely. If you lose the wallet password, support cannot recover it for you.
If the desktop/core wallet uses a wallet.dat file, back up that file after creating or changing wallet keys.
Store backups offline in more than one safe place.
Never email wallet files or upload private wallet backups to random cloud links.
Cold storage
Cold storage means keeping wallet keys offline so they are not exposed to an internet-connected machine during normal use. A cold wallet can be useful for larger balances, but it requires careful backup handling and a clear process for signing transactions.
Private keys and recovery phrases
Never share private keys. Never paste private keys into websites. If a wallet gives you a seed or recovery phrase, treat it like the wallet itself. Current public docs do not prove that every HOBC wallet build uses a recovery phrase, so follow the exact backup method shown by the wallet you are using.
If you cannot explain your wallet backup and recovery process, do not hold larger balances yet.
The public web wallet is custodial. For local key control, use the official desktop wallet (Windows installer or Linux AppImage/.deb) from the downloads page. Long-term holdings should use local wallet software with encrypted backups.