Creating your own OmegaCases Mining Pool

A mining pool lets many miners combine hashpower and split OmegaZites rewards proportionally to the shares they contribute. You do not need much custom code to run one. OmegaCases handles listing, uptime checks, the join flow, and splitting the reward, all automatically.

Prerequisites

You need a VPS or a machine you control (even a home computer works) with a public IPv4 or IPv6 address and an open port that miners and OmegaCases can reach. You can create an unlimited number of pools.

fetch("https://omegacases.com/api/mining/pools", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    owner_id:    "your-user-id",
    name:        "My Pool",
    host:        "203.0.113.10",
    port:        3333,
    ip_version:  "auto",       // "ipv4", "ipv6", or "auto"
    description: "Low fee pool, PPLNS payouts"
  })
})

{
  "success": true,
  "pool":    { "id": "pool-uuid", "status": "testing", ... },
  "api_key": "a3f9c2...",
  "warning": "Save this API key now, it will not be shown again."
}

Authenticating pool API calls

Calls your pool makes to OmegaCases (like submitting a found block) are authenticated with your API key, not a normal user session, since your pool is an unattended server rather than a logged in browser. Send it as a bearer token.

Authorization: Bearer a3f9c2...

The 30 second liveness check

After you register, OmegaCases's own server starts connecting to the host and port you gave it. It sends a short message, PING, and expects PONG back. This repeats for about 30 seconds. If enough of those checks succeed, your pool's status changes fromtesting to active and it appears on the public pool list at/mining. If it fails, your pool goes back to pending and you can fix whatever is blocking the connection (a firewall rule, for example) and try again by editing the pool, which restarts the check.

Ongoing uptime checks

OmegaCases keeps re-checking active pools the same way, roughly every few minutes, for as long as you are listed. A pool that stops answering PING for several checks in a row gets marked offline until it responds again. You do not need to call anything yourself for this, OmegaCases always initiates the check.

fetch("https://omegacases.com/api/mining/pools/{id}/submit-block", {
  method: "POST",
  headers: {
    "Content-Type":  "application/json",
    "Authorization": "Bearer a3f9c2..."
  },
  body: JSON.stringify({
    nonce: 918234,
    hash:  "0000abc...",
    shares: [
      { "user_id": "uuid-of-participant",       "shares": 1500 },
      { "user_id": "uuid-of-another-participant", "shares": 800 }
    ]
  })
})

{
  "success": true,
  "block":   { "height": 1234, "reward_zites": 64 },
  "payouts": [
    { "user_id": "...", "shares": 1500, "zites_credited": 41.7391 },
    { "user_id": "...", "shares": 800,  "zites_credited": 22.2609 }
  ]
}

PPLNS and payout logic is your responsibility

OmegaCases does not care how you decide share weights internally, whether that is PPLNS, PPS, simple proportional, or anything else. It only takes the shares list you submit at block-found time and splits that block's OmegaZites reward proportionally among those numbers. All internal accounting, minimum payout thresholds, and fairness between your own miners is entirely up to you.

Getting listed and letting users join

Once active, your pool appears on /mining showing its uptime, blocks found, and member count so prospective miners can evaluate it before joining. When a user presses Join Pool, OmegaCases simply records them as a participant, so the site can show that they are a member and so your submit-block calls can credit their user_id. The user still needs to separately configure their own mining software with your pool's host and port to actually start contributing hashpower, joining on the site does not connect them to your server for you.

Endpoints at a glance