Blockchain / DePIN / HB-TEP

Blockchain and federated infrastructure.

Explore the immutable legacy ledger, follow HVM testnet finality and inspect the infrastructure behind HashBurst.

Live API availability

Availability is checked independently. An API response does not prove that every node is online.

Explore HashBurst

Explorer

Chain 1337 is a terminal archive. Historical blocks and transactions remain readable; mining and spending are disabled.

Read the archive

DNS Nodes

Inspect node discovery with explicit data sources. TEP peers are not proof of on-chain registration.

Inspect nodes

HB-TEP

Inspect transport peers and reported connectivity. Transport identity remains distinct from validator consensus identity.

View transport

Sovereign Storage

Read reported storage capacity and node availability. Capacity is derived from the storage API, not estimates.

View storage

HVM Network

Testnet chain 4735490. Follow finalized height, observer connectivity and EVM RPC availability. This section and the HVM dashboard are in English.

Open HVM Network

Mainnet

Chain 4735489 is not activated. Publication of this website does not activate a network or import legacy balances.

Inspect implementation

External pool mining, APoW submissions and finalized HVM rewards are separate measurements. No private keys or wallet signatures are requested by this website.

Participate in the federation

You can apply to join the HashBurst federation for free. This participation process does not require a joining payment. You remain responsible for hardware, energy, connectivity and node administration. Technical admission and private-network credentials are arranged with the maintainers.

A public installer does not provide automatic admission. Legacy archive 1337 does not accept registrations. DePIN participation, running an HVM observer and becoming a validator are separate processes.

Choose your node role

Edge storage node

Contributes replicas while online. Edge capacity is best-effort and does not automatically increase sellable capacity.

Stable storage node

Offers capacity and sustained availability. Maintainers verify identity, reachability and replication policy before including it in committable capacity.

Compute or mining worker

Participates in workloads configured by the coordinator. External pool mining and native APoW use separate configuration and accounting; returns are not guaranteed.

HVM observer

Reads and verifies the network without signing consensus. Requires configuration for the selected network, a verified checkpoint and separate identities.

HVM validator

Signs consensus. Requires signed public registrations, approved protocol parameters and the network economic requirements. Installing a storage node does not grant this role.

How to add a node for free

Prepare the system
The documented installer target is Ubuntu x86_64 with systemd, Python 3, curl and administrative access. Check disk space, time synchronization, connectivity and system updates. Review any machine hosting critical services before installation.
Submit a node proposal
Provide the role, OS version, CPU, RAM, offered storage, availability and NAT status. Use the downloadable template below and open a request in the installer repository. The template stays on your device until you submit it.
Receive admission parameters
Agree on release and checksum, node identifier, rendezvous, bootstrap peers and storage role. The IPFS federation key must be delivered through a private channel, never through a public issue.
Install the approved profile
The documented v2.1.6 installer includes legacy registration that is incompatible with the frozen archive. Use only an onboarding profile verified by maintainers for the current network. Do not create a new federation with the primary option when joining the existing one.
Verify identity and services
The node generates or preserves its keys locally. Maintainers verify its public Peer ID and X25519 public key. A key file alone does not prove federation membership. Complete TEP and storage checks and confirm inclusion in the authorized inventory.

Open a request with the maintainers

Do not attach private keys, passwords, swarm.key or complete environment files. Before submitting, remove information you do not want to make public.

Local node checks

From an Ubuntu shell, these commands read available resources without installing software.

uname -m
cat /etc/os-release
free -h
df -h
timedatectl status

After approved onboarding, check TEP locally. The response should report AES-256-GCM and app_ready=true; peer acceptance must be checked separately.

systemctl --no-pager status hashburst-tep.service
curl --fail --max-time 10 http://127.0.0.1:47778/

Services and network boundaries

HB-TEP handles authenticated transport; HB-Files handles sovereign storage; private IPFS distributes admitted content. HA coordination assigns the operational master and applies fencing. HVM handles blockchain execution and consensus; these services are not interchangeable.

Service	Port and access
HB-TEP	47777 UDP
TEP IPC	127.0.0.1:47778
HB-Files / storage summary	8091
Mining aggregator	8093
Storage network aggregator	8094
Private Kubo RPC	127.0.0.1:5011

Local IPC and Kubo ports must not be publicly exposed. Do not open every port in this table: apply only the rules for the agreed role. Private keys remain on the node.

Public data and APIs

Inspect API responses directly. External pool mining is distinct from HVM rewards; an available master does not prove rewarded work.

Node installer | Blockchain source