Bless Node Reference
This reference page documents the native Bless worker that was installed on a Linux VPS, verified through Docker, and connected to the Bless boot node network.
Node Reference
Last checked from the VPS on May 2, 2026 at 02:22 UTC. The public page was verified over TLS 1.3 with a Let's Encrypt certificate, the container was running, TCP port 9527 was published, Docker showed network I/O, and recent logs showed health-check messages from the Bless boot node.
Native Docker Worker
The worker is installed as a Docker container with a persistent identity folder, so normal container restarts keep the same peer identity.
container: blessnetwork-node image: ghcr.io/blessnetwork/b7s:0.6.6.patch3 status: Up 2 hours at last check public port: 9527/tcp restart policy: unless-stopped network io: 7.61MB in / 2.03MB out health checks: 34 in the last 2 minutes peer id: 12D3KooWLekK2RbJadBDUJCdtCKxQg7zTYymRQRpteu3hV2AWHnJ
Live Traffic Monitor
Current service traffic is sampled from each Bless Docker container and its network namespace. BlessNet CLI/runtime status is sampled from the WireNets web VPS, and the rows below are scoped to Bless listeners and tunnel interfaces only.
| Node | State | From | To | Direction |
|---|---|---|---|---|
| Waiting for live connection sample. | ||||
Operational Notes
The page is a public operational reference for the WireNets Bless node setup. It confirms that the native worker was installed and connected, while keeping the distinction between running a node and qualifying for network rewards.
The Bless worker is deployed with Docker and set to restart automatically unless it is manually stopped.
The node identity files are stored outside the container, keeping the same peer ID through container rebuilds.
TCP port 9527 is published for the native node listener and was reachable during setup checks.
Bless documentation says VPS usage is not rewarded. This reference is proof of operation, not a reward guarantee.
Use the Bless dashboard link with referral code DQZ3FF, then compare the dashboard node IDs with the live peer IDs shown here.
Native node setup follows the official Bless Docker guidance and the public b7s worker image.
WireNets can document, monitor, and maintain Linux service deployments like this one.
References
These are the public references used for the native Linux worker install and policy note.