Ir al contenido principal
securestamp.org/nodes
Node Operator Program — Beta

Run a SecureStamp Node

SecureStamp is designed as a federated protocol. Independent node operators run trust registry replicas and participate in the IBFT 2.0 consensus ledger, ensuring no single entity controls the global trust graph.

Node Types

Registry Mirror

Entry

Read replica of the trust registry. Serves lookup requests from a region. No write access.

2 vCPU · 4 GB RAM · 50 GB SSD

Validator Node

Full

Participates in IBFT 2.0 consensus. Writes to the Hyperledger Besu ledger. Requires staking.

4 vCPU · 8 GB RAM · 200 GB SSD · 1 Gbps

Anchor Node

Root

Anchors a geographic zone. Runs both registry and validator roles. Invited by foundation only.

8 vCPU · 16 GB RAM · 500 GB NVMe · 10 Gbps

Setup Guide — Registry Mirror

01

Prerequisites

Install Docker 24+ and docker-compose. A static IP or stable DNS hostname is recommended for production operation.

shell
# Verify docker
docker --version        # >= 24.0
docker compose version  # >= 2.20
02

Clone the node configuration

shell
git clone https://github.com/sergioortizlatorre2/securestamp-protocol.git
cd securestamp-protocol/node
03

Configure environment

Copy the template and fill in your node credentials (provided by the SecureStamp foundation after node application approval).

shell
cp .env.example .env
# Edit .env:
#   NODE_ID=your-node-id
#   NODE_SECRET=your-node-secret
#   REGION=us-east-1          # or eu-west-1 / ap-southeast-1
#   SYNC_ENDPOINT=https://registry.securestamp.org/sync
#   BESU_BOOTNODES=...        # provided on approval
04

Start the node

shell
docker compose up -d

# Monitor sync progress
docker compose logs -f registry-sync

# Health check
curl http://localhost:8080/health
# {"status":"syncing","progress":"42%","ledgerBlock":18420}
05

Register with the foundation

Once your node is synced and healthy, send your node ID and public endpoint to nodes@securestamp.org. The foundation will add your node to the public registry of active operators.

Operator Obligations

99% monthly uptime for registry sync
Keep node software updated within 30 days of release
Report security incidents to security@securestamp.org within 24h
Participate in quarterly operator calls
Store or log queried email addresses or domain lookups
Modify trust scores outside the published algorithm
Sell or share access to sync credentials
Operate under a jurisdiction with data-localization laws without disclosure

Active Nodes

OperatorRegionTypeStatusSince
SecureStamp Foundationus-east-1AnchorOnline2025-01
More operators joining — apply at nodes@securestamp.org

Ready to run a node?

The operator program is in beta. We review applications manually and onboard new operators in batches of 5.

Apply: nodes@securestamp.org
Run a Node — SecureStamp Protocol | SecureStamp Foundation