Practical overview
When it fits
Use it as a code reference when configuring an ORE pool’s account initialization, webhook-based event processing, and ore-cli-facing server.
Who it is for
- Operators setting up ORE mining-pool infrastructure.
- Rust developers adapting pool logic while retaining the HTTP paths used by ore-cli.
Documented uses
- Initialize the pool and member accounts required by the server.
- Process mining events delivered through a Helius webhook.
- Run an HTTP service exposing paths used by ore-cli.
- Start a local database with the documented Docker Compose setup.
Requirements & limits
The repository is public and described as open source; no license is specified in the supplied repository details.
- Admin initialization must create the pool and member accounts before the server starts.
- Mining-event processing depends on a manually created raw Helius webhook and an authentication token supplied to the server.
- The repository is marked deprecated and describes itself as a reference implementation subject to breaking changes.
- Forks that change pool logic must preserve the HTTP paths used by ore-cli to follow the documented customization approach.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Initialize the pool accounts before starting the server
Create the on-chain pool and member accounts that the Ore Pool server expects.
Before you start
- The repository and Rust Cargo environment used by its documented cargo commands.
- An RPC URL, keypair path, and pool URL for the admin initialization command.
Steps
Run the admin application with
COMMAND="init",RPC_URL,KEYPAIR_PATH, andPOOL_URLconfigured.Use the admin application's
proof-accountcommand to obtain the pool proof-account public key.Configure the server environment, including RPC_URL, KEYPAIR_PATH, DB_URL, ATTR_EPOCH, HELIUS_AUTH_TOKEN, and OPERATOR_COMMISSION, then start the server.
Expected outcome
The pool and member accounts are initialized before the server starts, and the server has its documented configuration inputs.
Guide limitations
- The repository is marked deprecated and describes the implementation as a reference project subject to breaking changes.
- Mining-event processing also depends on a manually created raw Helius webhook; this guide does not configure or verify that webhook.
Configure webhook inputs for mining-event processing
Set up the Helius webhook inputs the server uses to parse mining events asynchronously.
Before you start
- A running Ore Pool server configuration with a Helius authentication token.
- The pool proof-account public key, obtainable using the admin application's
proof-accountcommand. - Access to the Helius dashboard to create a webhook.
Steps
Create a webhook manually in the Helius dashboard and select type
raw.Specify the pool proof-account public key among the account addresses to listen for.
Configure the webhook to include an auth token in POST requests and pass that token to the server as an environment variable.
Expected outcome
The server has the documented webhook type, account filter, and authentication-token input for asynchronous mining-event parsing.
Guide limitations
- The repository does not automate webhook creation.
- The webhook’s live delivery and server processing are not verified by this setup description.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- regolith-labs/ore-pool · Official homepage title · retained in its source language