DATUM preferredTIDESCoinbase payouts
Bitcoin was meant for node + mine in one place. Classic pools split hashing from what goes in the block — that concentrates template power. DeeperGuard uses TIDES to spread coinbase payouts while you keep block creation when you run Knots + DATUM.
Live stats refresh every 15 seconds.
BLAKE2b ASICs (Goldshell SC-series, Antminer A3, iBeLink BM-K…). Username bc1q…address.worker, password x. No account.
1 · Point your miner
| Goldshell / Sia firmware | stratum+tcp://stratum.pool.deeperguard.com:5555 |
|---|---|
| iBeLink | stratum+tcp://stratum.pool.deeperguard.com:7777 |
| Worker | bc1q…yourpayoutaddress.rig1 |
| Password | x |
Shares show up on your worker page within a minute: pool.deeperguard.com/miner/<your address>.
2 · Cut your fee to 0%
Sync Bitcoin Knots (BLAKE2b), run a DATUM gateway with our pre-filled gateway.json, point the ASICs at the gateway instead. Your node builds the block.
| Prime | stratum.pool.deeperguard.com:28915 |
|---|---|
| Window | Same TIDES window — use the same payout address as gateway pool_address and your work carries over. |
One username rule: bc1q…address.worker · password x. Same TIDES window for DATUM and stratum.
Hashing with block creation
You choose transactions on Knots. We only set the coinbase split and verify shares. Miners never talk to Prime directly.
datum section below into gateway.json.stratum+tcp://127.0.0.1:23334 (or your gateway host).| Prime | stratum.pool.deeperguard.com:28915 |
|---|---|
| Pubkey | 6db619d1ec1fa7a323b03ba88a6483ccc3a915c0afa7364f84a085b3df096be46633274e21a624e320488ba80de099526509c24779a882b95beca551d8d6da42 |
| Gateway fee | 0% of window share |
"datum": {
"pool_host": "stratum.pool.deeperguard.com",
"pool_port": 28915,
"pool_pubkey": "6db619d1ec1fa7a323b03ba88a6483ccc3a915c0afa7364f84a085b3df096be46633274e21a624e320488ba80de099526509c24779a882b95beca551d8d6da42",
"pool_pass_workers": true,
"pool_pass_full_users": true,
"pooled_mining_only": true
},
"stratum": {
"vardiff_min": 4096
}
Download starter gateway.json Prime host, port and pubkey filled in; set mining.pool_address and your bitcoind RPC.
Hashing without block creation
Our node builds the template. Use only if you cannot run Knots + a gateway.
| Goldshell / Sia firmware | stratum+tcp://stratum.pool.deeperguard.com:5555 |
|---|---|
| iBeLink | stratum+tcp://stratum.pool.deeperguard.com:7777 |
| Fee | 3% of window share |
Solo bet
No window. Whole block to the finder, minus fee. Not in the TIDES payout table.
| URL | stratum+tcp://stratum.pool.deeperguard.com:3334 |
|---|---|
| Fee | 2% of block reward |
Deducted in the coinbase. No balance, no withdrawal step. Window shares below 546 sats in a block are not paid out (dust floor) and stay with the pool.
Your node, your template.
Convenience path.
Block reward only.
| DeeperGuard | Lazarus | RIPTIDE | B2Pool | |
|---|---|---|---|---|
| DATUM gateway | 0% | 0% | 0% | 1% |
| Public stratum | 3% | 3% | ~1% | 1% |
| Stratum → DATUM rebate | — | 1% | ~0.5% | — |
| Solo | 2% | 2% | — | port |
Other pools’ fees are as published by them and may change; we check them periodically. Our column is read live from Prime.
Prime stats and connected workers.
| Worker | Address | Endpoint | Hashrate | Accepted |
|---|
| Address | Work | % |
|---|
| Address | % | Work |
|---|
Collecting samples…
| Gateway | Accepted | Rejected | Uptime |
|---|
| Height | Kind | Detail |
|---|
Pools are not the problem — separating hashrate from who builds the block is. We label both paths honestly.
Recommended · DATUM gateway · your Knots node
You run a synced Bitcoin Knots node and a DATUM gateway. Your node chooses transactions and builds the template; your ASICs hash that work. Our Prime only sends the coinbase split for the TIDES window and verifies shares — we do not hand you a pre-built block to rubber-stamp.
Convenience · public stratum · our node
You point a miner at our public stratum (:5555 / :7777). You hash, but we (via our pool node and pool-hosted gateway) choose what goes in the block template. That is the classic pool trade-off: easier onboarding, less decentralization of construction.
Our pool-hosted gateway speaks DATUM to Prime on the wire, but your hashrate on public stratum still does not choose transactions — only a your-node gateway does.
Solo mining (:3334) is separate: you keep the whole block if you find it; no TIDES window share. Solo with your own node needs no pool at all — we offer a port only if you want solo without running infrastructure.
Your Knots node builds the block template; your DATUM gateway serves work to your ASICs; our Prime only coordinates who gets paid in the coinbase. That restores the original idea: run a node and mine, with the pool helping on reward variance, not on picking transactions for you.
Public stratum on :5555 / :7777: you hash pool-provided jobs. We choose the template. It is the same separation classic pools introduced — convenient, but a few operators end up constructing most blocks. We charge more for this path so the DATUM path is always the cheaper one.
Not if they only redistribute rewards (TIDES, coinbase splits, no custodial balance). They become a problem when hashrate is pooled but block construction is centralized at the pool. We want most work on the DATUM path; public stratum is optional and clearly labeled.
No. Username is your payout address plus a worker name. Rewards are coinbase outputs when the pool finds a block (100 confirmations to spend).
Only the coinbase dust floor: if your share of the TIDES window is worth less than 546 sats in a given block, Prime cannot place an output for you and that amount stays with the pool. Everything above the floor is paid in that block’s coinbase. Keep enough hashrate in the window that your share clears it.
ratum-gateway 0.1.23+ or CONVOY with the largest-coinbase patch for BLAKE2b. Set stratum.vardiff_min to 4096 so small ASICs are not stuck at 16384.
Yes on :5555 / :7777, at the public stratum fee. Same window — you can move to a gateway later and keep accumulated work, as long as the address stays the same: window credit is keyed by payout address, so use the same bc1 as stratum username and as your gateway’s pool_address. Existing credit keeps the fee class it was earned at; new shares from your gateway are billed at the DATUM rate.
pool.deeperguard.com/miner/<your bc1 address> shows your TIDES window share, projected payout in the next block, hashrate and connected workers. JSON at /api/miner/<address>.
Yes. Blocks are Poisson: with the pool’s current hashrate the dashboard shows the expected interval between blocks. Shares accepted and workers online are the live health signals; the block count is luck over that interval.
BLAKE2b on Bitcoin Knots — not Handshake blake2bsha3, not SHA-256d.
Gateway setup help or listing questions.