• v0.1.0 65f47066dd

    agorise released this 2026-08-14 00:52:52 +00:00 | 9 commits to main since this release

    Signed by agorise
    GPG key ID: 53524E1F1017EB9C

    hidden-rpc v0.1.0

    First public release.

    hidden-rpc turns an ordinary computer — an old laptop is plenty — into a
    censorship-resistant Blurt RPC node, reachable privately over Tor (.onion v3) and
    I2P (.b32.i2p). No public IP, no port-forwarding, no DNS, no registrar, no hosting
    company.

    One-step setup

    From the repository folder:

    ./installer/hidden-rpc-setup.sh
    

    That's the whole thing. It downloads everything it needs, loads a presynced blockchain
    snapshot, starts the node bound to localhost, turns on the Tor and I2P hidden services,
    and prints your two addresses. It is safe to run again anytime — it never undoes finished
    work and never changes your addresses.

    Highlights

    • One command, no fuss. No prompts beyond your password once. Calm, reassuring output
      designed so a first-time operator never sees a scary error.
    • Downloads everything automatically — including the ~27 GB presynced chain (resumable),
      with a live progress bar and time estimates, plus spinners and elapsed timers on the
      longer steps.
    • Private by design. The RPC is bound to 127.0.0.1 only — reachable through Tor and
      I2P, never exposed on your local network or the clear net. Outbound-only hidden services
      mean no CGNAT/ISP problems.
    • Fast, multi-peer catch-up from current Blurt seed nodes.
    • Resilient. Auto-restarts after a reboot; graceful on hiccups — if anything is
      interrupted, just run it again and it continues.
    • Wraps the official upstream blurtd — no forks, no re-implementation.

    Requirements

    • 64-bit Linux (Debian / Ubuntu / Mint family), amd64.
    • About 100 GB of free disk space.
    • Docker, Tor, and i2pd are installed automatically if missing.

    Good to know

    • After setup, the node keeps catching up to the current block in the background. This can
      take a while and is completely normal. Watch it calmly with
      ./installer/hidden-rpc-setup.sh --watch.
    • Your I2P address takes a couple of minutes to become reachable on the first run. Re-run
      ./installer/hidden-rpc-setup.sh --show-addresses to print it once it's ready.
    • If you ever look at the raw node logs, lines like Error when pushing block ... too old
      during catch-up are normal and harmless — duplicate blocks from multiple peers being
      rejected. The chain keeps advancing right through them.

    Important: what this does and does not do

    Tor and I2P hide where you read, not whether what you read is true. Reaching a node
    does not make its data trustworthy — cross-checking answers across independent nodes is the
    reader's job. This release is RPC-only (no witness / block production).

    Downloads