How to Set Up Hashrate Splitting on 0xStratix

Hashrate Splitting means distributing hashrate across multiple pools and accounts by exact percentages. Instead of sending all of a miner's hashrate to a single pool, you define rules — for example, 99% of the hashrate to your main pool and 1% to a separate account as a fee (Hotel Fee).

0xStratix does this in the cloud. You don't reflash miners or install anything: you create a proxy, configure the routing rules in the dashboard, and then point your miners at your endpoint over the Stratum protocol. Because the logic runs on the 0xStratix side, you can change percentages, pools, and destination accounts in real time — without touching the miners.

One key principle: configure first, connect miners second. That's the order we'll follow here.

Key concepts

Proxy (configuration) — a set of routing rules tied to a coin (e.g. Bitcoin). On an existing proxy, the tabs Overview, Configuration, and History are available at the top.
Account and worker — a miner's connection string takes the form account.worker: everything before the dot is the account, everything after is the worker. The proxy uses this string to identify whose traffic arrived.
Incoming account — a rule for incoming traffic. The first rule is always Any incoming (a fallback) — it applies to any account. You can additionally create a rule for a specific account.worker.
Destination (route) — where hashrate goes: the destination pool and a percentage. One incoming account can have several destinations, and their percentages must add up to exactly 100%.
Keep same — pass-through mode. When the toggle is on, the value (Account, Worker, or Password) is forwarded from the miner unchanged. When off, the value you enter manually is used instead. When all three are on, the route shows as Keep incoming.
History — every save creates a new version of the configuration; previous versions remain available on the History tab.

Step 1 — Create a proxy

Open the proxy creation screen and fill in:

Proxy name — any label you like (e.g. My BTC Proxy #1).
Coin — e.g. Bitcoin.

The Incoming Accounts block appears below, with a first rule already in place: Any incoming. Before you can create the configuration, this rule needs at least one destination — until a pool is selected, a "Select a pool" error is shown and the Create configuration button stays disabled.

Configure the destination (see Step 2), then click Create configuration.

Step 2 — Configure the route for "Any incoming"

Work from general to specific: first define the rule that handles all incoming traffic.

Next to the Any incoming rule, click Add destination — the Edit destination dialog opens:

Account — with Keep same on, the account is taken from the miner; with it off, you enter one manually.
Worker — same logic: keep it as is, or set your own worker name.
Password — usually left on Keep same (often x).
% — the share of hashrate that goes to this destination.
Pool — the destination pool from the list (e.g. viabtc-btc).

Click Save destination.

In the basic scenario, all three Keep same toggles are on, % = 100, and a pool is selected — so all hashrate is forwarded to the pool exactly as received, unchanged.

Important: the percentages of all destinations within one incoming account must add up to exactly 100%. If the total isn't 100, the configuration can't be saved.

Step 3 — Fine-tune for a specific account (optional)

If the rule for general traffic is enough, you can skip this step. If you need a separate rule for a specific account.worker, click Add account — the Add incoming account dialog opens:

Incoming account — a specific name (e.g. account1) or the Any account toggle.
Incoming worker — a specific name or the Any worker toggle (*).

Click Save account, then define destinations for this rule the same way as in Step 2.

Step 4 — Common route scenarios

A few frequent destination setups:

No fee (pass-through). A single destination: all Keep same toggles on, 100%, pool selected. Hashrate reaches the pool exactly as it arrived from the miner.
Fee / Hotel Fee. Two destinations under one incoming account:
- the main one — Keep same, e.g. 99%, to the customer's pool;
- the fee one — turn off Keep same on Worker (and on Account if needed), enter your own worker/account, set 1%, and choose a pool.
Different fee percentage. Same setup, but the fee destination's percentage changes (e.g. 5%), with the main destination taking the remainder up to 100%.

Hotel Fee example with real values: the main route receives 99% of the hashrate, while a second destination with a substituted worker (fee) — 1% — goes to the account dddddvv on the viabtc-btc pool.

Destination	Account / Worker	%	Pool
Main	Keep same	99	viabtc-btc
Fee (Hotel Fee)	`dddddvv` / `fee`	1	viabtc-btc
Total		100

Step 5 — Verify in Preview

The Preview block shows the routing as a graph: INCOMING → % → EXIT. It shows how many routes are configured and how many are active, and exactly where the hashrate goes. This is handy for checking before you save.

Step 6 — Save the configuration

When everything is set up correctly, save:

On first creation — the Create configuration button.
On an existing proxy — the Save new version button (a new version is created).

All previous versions remain available on the History tab, and you can roll back to them at any time.

Step 7 — Connect your miners

Now that the rules are saved, point your miners at your proxy. In the miner's pool settings, enter:

Pool URL:   btc.0xstratix.com:PORT
Worker:     account.worker
Password:   x

Port. 3333 is the shared port. Each customer has a dedicated proxy and their own personal port — take it from the dashboard and use that one.
Worker name — in account.worker format. The proxy uses it to match traffic against the rules in Incoming Accounts.
No firmware change is required — miners stay on their current firmware.

FAQ

What order should I set things up in? Create and configure the proxy first, then point your miners at the endpoint. You can't create a configuration without at least one destination that has a pool selected.

Do I need special firmware? No. 0xStratix works over standard Stratum — your miners stay on their current firmware.

Which port do I use? 3333 is the shared port. Each customer has their own proxy and personal port; take it from the dashboard.

Do the percentages have to add up to 100? Yes. Within a single incoming account, all destination percentages must total exactly 100% — otherwise the configuration can't be saved.

What does "Keep same" mean? It forwards the value from the miner unchanged. Turn the toggle off to substitute your own Account, Worker, or Password — that's how a fee (Hotel Fee) is set up.

Can I roll back changes? Yes. Every save is a new version, and all previous versions are available on the History tab.

Get started

Dashboard: app.0xstratix.com
Website: 0xstratix.com