Frequently asked

The box. Firmware is always stratum.routehash.com:23335. Never 28915.

On RouteHash, a Miner is the person with the ASIC. A Node Runner books that hash. Knots uses miner for the person who runs the node that builds the block. You can be both: ASIC on 23335, when not rented dest = your DATUM.

A hasher is work sent to someone else’s DATUM. They choose the transactions. You are a named dest on their one node. Hashing into House Pool or a listed node is hashing. Join our coordinator with your DATUM and you stay a miner.

RouteHash’s mining pool — our DATUM node. Connecting here is joining our pool. When not rented dest = House Pool, or a node runner’s rental dest = House Pool, hashes into our gateway. Dual paycheck: coinbase here plus BTC escrow when a listing is booked. See House Pool.

Listed DATUM nodes. You join that operator’s pool — hasher on their one node. Hash stays spread. Catalog: Node Marketplace.

A Node Runner pays the Miner BTC escrow for listed hours. That is not pool coinbase. The ASIC stays on stratum.routehash.com:23335; work goes to the Node Runner’s dest until the lease ends.

A segment is a DATUM node you run, with Pool Host pointed at a coordinator (ours, Terminus, or another). You build the template and submit the block. Ten boxes on that gateway are still one segment. Ten dests in your split are hashers on that segment, not ten segments.

Example: RouteHash DATUM with ten dests, Pool Host = Terminus Prime → RouteHash is one segment on Terminus. When a block is found, the finding gateway’s Knots broadcasts. The coinbase is a flat list of payees the coordinator dictated (TIDES-style window) — not Terminus’s split stacked on top of RouteHash’s split. With Pool Pass User = On, dest usernames can show as identities in that window.

RATUM is the coordinator software. Prime is that process. RouteHash Prime is pool.routehash.com:28915. Type that in DATUM Config → Pool Host (plus the pubkey on Connect). ASICs stay on your miner port. House Pool is joining our DATUM node on 23335 — a different product.

A template is the candidate block your Knots node builds. DATUM serves that work to your miners. When it finds, the coinbase (first transaction in the block) pays payout addresses. A dest is a payout address, and the upstream the proxy sends work to. Dest weight is that address’s cut of the coinbase — we say extra payout address and cut. A slice is that cut of one coinbase. A share is submitted proof of work, not a coinbase cut. A modifier is a named payout address in the DATUM split. House Pool writes the split for you. You do not fill a split form on our gateways.

The cut (percentage) of the coinbase split for a payout address. We say extra payout address and cut. A share is submitted proof of work, not that cut.

Ask is luck-and-split at the listed coinbase take (0 is FREE). Your payout address is named; the block pays by work. No BTC escrow.

Fill is a BTC hire on RouteHash for an extra payout address and a larger coinbase cut. The node runner names the address and sets the percentage on their node. RouteHash holds the hire. ASIC stays on stratum.routehash.com:23335.

The miner wants the rental credit as spendable XBT. The listing price stays BTC/TH/day. The renter can pay BTC or XBT. This is not “priced in XBT,” and it is not House Pool coinbase.

OCEAN’s (and similar) rolling window: each found block’s coinbase pays recent work. Listed OCEAN nodes on Node Marketplace use TIDES. House Pool is a DATUM split on our node, not TIDES. Joining our coordinator, you get paid in the coinbase whenever this group finds, in proportion to your work.

Knots is the node (XBT / Blake2b). DATUM is the gateway that builds templates from that node. Keep the Knots you already run.

Already running DATUM (CONVOY #pow, Ocean, Paulscode, iohzrd)? Keep that one gateway. Paste Pool Host pool.routehash.com, port 28915, and the pubkey from Connect. One DATUM per box.

StartOS (Start9), Knots and no DATUM yet: sideload RouteHash Gateway. Package id routehash-gateway does not replace a service named datum. Umbrel (beta): add community store https://github.com/RouteHash-com/umbrel-store, then install RouteHash Gateway next to Bitcoin Knots 29.4.2. ASICs stay on that gateway’s miner port (23339). Paulscode companion: paste Pool Host into that app. Beta until a live Umbrel install is confirmed.

Keep your pool. Get paid. Keep XBT open. RouteHash is a hashrate marketplace plus a mining pool. House Pool is RouteHash’s mining pool — our DATUM node. Connecting here is joining our pool. ASICs authenticate to stratum.routehash.com:23335. Paid leases go to the node runner’s saved destination (their DATUM node, a listed pool, or House Pool). Between leases, hash into your DATUM node if you run one, a listed pool, or House Pool. List a pool so hash stays spread — XBT stays a money of the plebs. If you run a DATUM node, you can also join our coordinator — that is a different product.

SHA-256 work settles BTC. Blake2b work settles XBT. Marketplace rentals are always priced and escrowed in BTC. You can take that rental credit in BTC, or as spendable circulating XBT (if the renter paid BTC, that send is converted circulating XBT: exchange fee, fill buffer, and you cover the network fee). House Pool pays in the block on the algorithm the ASIC hashed. RouteHash does not pay marketplace credits from House Pool coinbase.

Bech32 does not tell the rails apart. The BTC dest is where BTC rental credits go if you receive BTC, and SHA-256 House Pool / OCEAN identity. The XBT dest is Blake2b House Pool coinbase, and spendable XBT rental credits if you receive XBT. RouteHash never infers the rail from the string.

Three separate paths: (1) Marketplace rentals — priced and escrowed in BTC; you receive BTC or spendable circulating XBT. (2) House Pool — paid in that gateway’s coinbase (XBT DATUM group RouteHashXBT after RATUM; BTC DATUM group RouteHashBTC). (3) Listed DATUM nodes — that pool’s own rules (OCEAN uses TIDES). See How coins move.

Marketplace rental credits send at 0.00000700 BTC or more. Ask us to send a ready balance, or we send twice a day, so escrow stays small. Default receive is BTC. Receive XBT and staff send spendable circulating XBT to your verified XBT dest. If the renter paid BTC, an exchange fee, fill buffer, and network fee apply. If the renter paid XBT, there is no exchange. House Pool and listed-node coinbase pay in the block and do not wait on this queue.

Always stratum+tcp://stratum.routehash.com:23335, password x, Worker = the issued proxy key (optional .Label suffix). Same host:port for Blake2b and SHA-256. Never put the miner on :28915 (RATUM Prime), :25600, or DATUM’s listen port. The proxy rewrites that Worker before it dials you.

No. Worker is the issued key. House Pool Blake2b authorizes as group RouteHashXBT. House Pool SHA-256 authorizes as group RouteHashBTC. A listed OCEAN node uses the verified BTC dest as the upstream username. Do not type a bc1q into the ASIC Worker field.

No. RouteHash does not ping ASICs or DATUM. Online means the miner opened TCP to :23335 and authorized. AxeOS “Loss 100%” is that firmware’s share-reply counter: connected, but no accepted share yet (difficulty still high, or DATUM has not accepted a share). Keep the box on 23335 + issued Worker.

Not from the pool connection. RouteHash sees accepted/rejected shares, difficulty, and live TH inferred from accepted work. Those rings live on the miner’s LAN web UI. We would have to poll that page (usually not reachable from here) or run an agent on the box.

The last 15 minutes of accepted work. Not 5 minutes. Admin 5/15/30 cards are the same math over those windows. A ~ on the miners board means the listed rate is shown because the session is online but that 15-minute window is still empty.

Share luck in a short window. One high-difficulty share in five minutes is a lot of work; zero shares looks dead. Example: difficulty 131072 on a ~6 TH SHA-256 box is about one share every 90s, so 2 shares ≈ 3.75 TH and 5 shares ≈ 9.38 TH. The 15-minute number is the one to compare to the miner UI. Instant 15-second flushes of 13–70 TH are one share in a short slot, not extra hardware.

No. If Share difficulty is left blank, RouteHash stores a d= from advertised TH so the box should prove work about once every 20 seconds. That is written on Save for that rig only. Nothing later retunes it from 5/15/30-minute cards. The proxy asks for that d=; DATUM may still raise it (a 6 TH box requested 32768 and was answered 131072). Share difficulty does not change block odds — only how often the miner proves work to the pool.

No. Advertised TH and share difficulty are per-rig. The averaging formula is global. Changing rig 4’s listing rate or d= does not retune rigs 2 and 3. Smoother 5-minute cards need more shares in the window (pool min-diff closer to the requested d=), not a fudge factor.

Blank still means auto from advertised TH. A typed value is kept unless it is below the floor (Blake2b 4096, SHA-256 1024). DATUM/RATUM min-diff on the XBT box may be lower (e.g. 2048). The miner UI’s current Diff is pool vardiff after connect, not the Add Rig field.

No. DATUM pays one coinbase line per payout address. Two SHA-256 boxes on the same verified BTC dest share that dest’s slice (98% after the House Pool fee). The pie is one slice per Miner. Tables stay one row per rig, with that 98% split by live hash (equal TH → 49% / 49%). The dest report title is the Miner name, not both rig names concatenated.

The disclosed operator fee for that destination: Blake2b House Pool = live XBT take on our DATUM node (Limited-time free until we reach 500.00 TH/s; 0% = FREE); SHA-256 House Pool = RouteHash DATUM take (0.50% until the rail fills, then 2.00%); listed node = listed Ask; a paid lease = lease; Miner node = —.

Three different takes. Super-user platform fee on Admin → Fees is marketplace rental escrow: node runner take on top of the listing, miner take out of the listing (new leases only). RATUM is Blake2b House Pool, taken from Prime, not that slider. SHA-256 House Pool fee is a separate super-user field (0.50% until the rail fills, then 2.00%) as a named coinbase line to the Core treasury. Save a BTC treasury dest so that take is named; otherwise it is Always Pay Self remainder.

No. It is rounding leftover after named modifier lines. RATUM (XBT) or the RouteHash 2% (BTC House Pool) is the operator take. Unallocated remainder is coverage, not a second stacked fee.

That link follows the rig’s algorithm: Blake2b → XBT miners, SHA-256 → BTC miners. Hard-refresh the admin rig page after the app process serving that tree is current.

A DATUM node is the gateway that builds blocks. Pool Host is a field on that gateway, never on the ASIC:

• Join House Pool — ASIC on stratum.routehash.com:23335, idle dest = House Pool. That is joining RouteHash’s mining pool (our DATUM node).
• Solo on your DATUM node — leave Pool Host blank. You keep the coinbase. Same chance of finding a block.
• Join our coordinator — Pool Host pool.routehash.com, Pool Port 28915, Pool Pubkey from Connect. Collaborative reward sharing = prefer. Pool Pass User = On. Pool Pass Workers = Off. You still build the block. You get paid in the coinbase whenever this group finds, in proportion to your work. That is a segment.
• Your own coordinator — Pool Host is your RATUM (or another DATUM pool) and your pubkey. Renting hash to your DATUM node does not require joining us.

Keep the Knots you already run. Never put stratum.routehash.com, :23335, or your miner listen in Pool Host. Guide: Join the coordinator.

House Pool is RouteHash’s mining pool — our DATUM node. Connecting here is joining our pool.

Solo on my DATUM node is your DATUM/Knots with Pool Host blank — you keep the coinbase. List it on Node Marketplace only if you want guests. List the ASIC anyway; rentals override idle, then solo mining resumes.

A listed pool is someone else’s DATUM node on Node Marketplace. You join that operator’s pool. They add your payout address the same way a mining pool names a miner. Many small Knots pools give the network strength. Ask / FREE idle is luck only. Fill is hire: sticker rate, an offer, a ticket, you pay the agreed BTC, they add your dest, you activate when hashing starts, RouteHash holds that BTC until both parties confirm settlement.

Coordinator is optional if you run a DATUM node: Pool Host pool.routehash.com:28915. A paid lease always overrides idle.

Yes. Dest = House Pool. You need no ASIC and no node. That is joining RouteHash’s mining pool — our DATUM node. Your dest gets a coinbase slice equal to live TH / House Pool TH after the rail’s take. The miner is paid from your BTC escrow either way. Want your DATUM node to build the block? Run a gateway and join the coordinator.

Two different payments. When not rented, coinbase follows that dest (your node, a listed pool, or House Pool). While leased, hashrate goes to the Node Runner’s saved dest, and the Miner is paid from BTC escrow — not from that dest’s coinbase. House Pool when not rented plus a live listing is two paychecks. The ASIC never leaves stratum.routehash.com:23335. Binding rules: RouteHash Policy Article 13.

SHA-256 / BTC: RouteHash writes one operator line into the Core DATUM split. Launch window is 0.50% (50 bps); the configured default after that window is 2.00%. Super-user Admin → Fees sets it. It is global for that rail’s next coinbase, not a per-miner “first N TH” meter. Blake2b / XBT: Limited-time free until we reach 500.00 TH/s. The XBT take is the live fee on our DATUM node (0% = FREE). Flask does not override that with a second House Pool take. The 500.00 TH/s figure is a public hash target; it does not rewrite that fee. Idle XBT coinbase plus a marketplace listing still pays rented hours from BTC escrow (take that rental credit in BTC or spendable XBT).

Yes. That is the usual miner setup: ASIC on stratum.routehash.com:23335, when not rented dest = your node, listing on the marketplace. While nobody is renting, you solo mine. When a node runner books, work goes to their destination. When the lease ends, you are solo mining again. You do not unplug the box or leave your node.

No. Point the ASIC at RouteHash and set where hash goes to that pool’s listed node (or list your node and hash into it). RouteHash forwards that hash there. Guests join that operator’s pool — hasher on their one DATUM node. Keep the Knots you already run. Listing the ASIC for rent is extra BTC escrow on top — take that rental credit in BTC or spendable XBT.

No. OCEAN is a listed DATUM node on Node Marketplace (TIDES, about 2% on the public stratum). BTC House Pool is RouteHash’s mining pool on SHA-256 — our DATUM node, Pool Host blank. If that gateway’s Pool Host still points at OCEAN, House Pool work mixes into TIDES. Independent House Pool needs that host blank.

Empty split tables are not submitted (that would wipe the group). SHA-256 House Pool only writes dests when there is live House Pool hash and a verified BTC dest. RouteHash updates the Core DATUM gateway only — never the XBT gateway. You do not fill the gateway’s split form.

Three different sockets. ASICs stay on stratum.routehash.com:23335. RouteHash dials your miner listen (the host:port you type — often 23334, or 23339 if StartOS remapped). Leave DATUM’s listen alone. Allow TCP on that listen only from 165.245.235.36. Do not world-open it on StartTunnel. Config → Pool Host is the uplink (RATUM :28915, TIDES riptide.maveth.ca:28916, or blank for solo). Never put 23335 or miner ports in Pool Host.

Type the listen DATUM already uses. Allow TCP on that port only from 165.245.235.36. Do not publish miner listen on StartTunnel, Gateways, or a socat forward to the whole internet. Coordinator 28915 stays public.

Not kind-1 notes. Listings are NIP-33 parameterized replaceable events: kind 30078 (application-specific listing JSON: listing id, rig, algo, advertised TH, price, min hours, directory endpoint) and kind 30079 (signer revocation). Tags: d = listing id (replaceable coordinate), expiration. Nothing here signs payments or on-chain transactions. Events expire (~24h) unless republished.

Damus/Primal/Amethyst look for notes and will show nothing. Use a filter client (nak, Nostrudel, a websocket console). Subscribe kinds 30078 and 30079 and this instance’s marketplace npub (Admin → Relay Health). If the relay’s Authorized Pubkeys list is a write ACL, add that npub; leave NIP-05 disabled. Other RouteHash nodes only accept events if the pubkey is on Admin → Directory Signers. Discover in-app does not turn those events into rentable local listings.

No. RouteHash Policy is the binding description of rails. This page is operational Q&A. In-flight rentals keep price and SLA locked at checkout.

Yes. Marketplace balances, rentals, and House Pool coinbase are live. Hashrate, luck, and uptime are not guaranteed. Starting a lease does not kill the existing TCP session — the miner keeps the old destination until it reconnects.