Crates.io | ore-pool-types |
lib.rs | ore-pool-types |
version | 1.0.0 |
source | src |
created_at | 2024-10-11 19:15:51.529993 |
updated_at | 2025-01-11 01:22:53.181837 |
description | Types for interacting with the API of a pool server |
homepage | https://ore.supply |
repository | https://github.com/regolith-labs/ore-pool |
max_upload_size | |
id | 1405734 |
size | 8,951 |
Infrastructure for operating ORE mining pools.
Must cargo run
the admin application before starting server.
Creates the pool and member accounts on-chain which the server expects to exist upon starting. A member account is created because we need an account to write the pool commissions to. You can manage this member account (balance, claim, etc.) from the ore-cli
.
# cd ./admin
COMMAND="init" RPC_URL="" KEYPAIR_PATH="/my/path/id.json" POOL_URL="" cargo run --release
Start the server. Parameterized via env vars.
# cd ./server
RPC_URL="" KEYPAIR_PATH="/my/path/id.json" DB_URL="" ATTR_EPOCH="60" HELIUS_AUTH_TOKEN="" OPERATOR_COMMISSION="" RUST_LOG=info cargo run --release
The server depends on a Helius webhook, for parsing the mining events asynchronously.
raw
.proof-account
command in the admin server.ore-cli
.ore-cli
is interfacing with. If you do that, people should be able to participate in your pool with no additional installs or changes to their client.To spin up the database locally:
docker-compose up