Native RUB difficulty
UnavailableWaiting for difficulty data
Pool overview
Network-wide values, native pool accounting and merged-mining telemetry remain clearly separated.
Merged RUB difficulty
UnavailableWaiting for difficulty data
The two mining modes have separate block difficulties. Share difficulty is the work threshold assigned to a miner.
MERGED MINING
Loading activation status
Ruble and Bitcoin block results are independent. A reward on one network does not require a block on the other.
StatusUnavailable
Merged hashrate—
Active workers · accepted ≤3m—
RUB merged blocks—
BTC blocks—
Last merged share—
Mining profiles
Loading profilesLive Stratum telemetry will appear here.
Accounting health
Open public API →Event consistency—
Financial consistency—
Accepted share records—
Miner accounts—
Worker names recorded—
Latest native blocks
RUB · Native
Loading block history…
Latest merged blocks
RUB · Merged
Loading block history…
BTC
Loading block history…
Native Ruble financial totals
Attributed block rewardsPPLNS + SOLO—
PPLNS accounting only
The rows below cover General and MRR. Direct SOLO rewards are included only in the total above.
Allocated by PPLNSMiners + pool fee—
Available for PPLNS batches—
Committed to PPLNS batchesAll time · includes sent and confirmed batches—
PPLNS · broadcast or paidRecipient amounts after network fees—
Merged mining financial totals
Allocated by PPLNSMiners + pool fee—
Available for payouts—
Reserved in payout batches—
Settled allocationsBefore network fees · finalized batches—
Mining
Choose a mining mode, compare live performance and get connection settings.
Native RUB profiles
General and MRR use shared PPLNS accounting. Solo pays the block finder directly.
Native RUB difficulty
UnavailableWaiting for difficulty data
PPLNS
LoadingGeneral
For direct SHA-256 miners.
Hashrate · 5m average—
- 1m estimate
- —
- 15m average
- —
- 1h average
- —
- 24h average
- —
- Connected workers
- —
- Connected users
- —
Waiting for the first update.
Work and share counters
- Accepted difficulty
- —
- Rejected difficulty
- —
- PPLNS share records · all time
- —
Difficulty is weighted work, not a share count or a reward. These are cumulative counters, not the hashrate averaging periods above.
Shared block rewards
Shares contribute to the shared PPLNS window. Mature rewards are paid in pool batches.
Stratum · port 3333
stratum+tcp://pool.rublecore.org:3333PPLNS
LoadingMiningRigRentals
For MiningRigRentals connections.
Hashrate · 5m average—
- 1m estimate
- —
- 15m average
- —
- 1h average
- —
- 24h average
- —
- Connected workers
- —
- Connected users
- —
Waiting for the first update.
Work and share counters
- Accepted difficulty
- —
- Rejected difficulty
- —
- PPLNS share records · all time
- —
Difficulty is weighted work, not a share count or a reward. These are cumulative counters, not the hashrate averaging periods above.
Shared block rewards
The same PPLNS accounting as General, through a dedicated connection profile.
Stratum · port 3334
stratum+tcp://pool.rublecore.org:3334SOLO
LoadingSolo
For miners seeking their own block reward.
Hashrate · 5m average—
- 1m estimate
- —
- 15m average
- —
- 1h average
- —
- 24h average
- —
- Connected workers
- —
- Connected users
- —
Waiting for the first update.
Work and share counters
- Accepted difficulty
- —
- Rejected difficulty
- —
Difficulty is weighted work, not a share count or a reward. These are cumulative counters, not the hashrate averaging periods above.
Direct block reward
The finder receives the reward directly in the coinbase transaction, after the pool fee. No PPLNS payout threshold.
Stratum · port 3335
stratum+tcp://pool.rublecore.org:3335Native reward rules
General, MRR and Solo
Additional blocks after discovery
General + MRR · difficulty weighted
General + MRR · automatic pool batches
Solo rewards mature in the finder’s wallet. They are not credited to a pool PPLNS balance.
ONE SHA-256 CONNECTION · TWO INDEPENDENT RESULTS
Merged RUB + BTC
Use compatible SHA-256 hardware to participate in Ruble and Bitcoin mining through one dedicated Stratum profile.
Merged RUB difficulty
UnavailableWaiting for difficulty data
Rolling merged-mining telemetry
Awaiting telemetryShare-based estimate · 1mUnavailable
Hashrate · 1hUnavailable
Rejected difficulty · 1hUnavailable
Stale difficulty · 1hUnavailable
Best difficultyUnavailable
Last accepted shareUnavailable
How rewards are accounted
RUB
Ruble merged blocks
Eligible work is evaluated for a Ruble block independently.
BTC
Bitcoin blocks
A Bitcoin reward appears only when an accepted Bitcoin block is found.
A Ruble block may be found without a Bitcoin block, and a Bitcoin block may be found without a Ruble block.
Recent merged-mining blocks
Latest 12 events from up to 200 public records; exact lifetime totals are shown above. RUB and BTC amounts are never combined.
| Asset | Type | Merged # | Network height | Found | Status | Maturity proof | Reward | Attribution | Block hash |
|---|---|---|---|---|---|---|---|---|---|
Awaiting merged-mining telemetryVerified blocks will appear here after merged mining becomes active. | |||||||||
MERGED STRATUMmerge.rublecore.org:3340PPLNS · 1.5% fee · Automatic Vardiff
Pool blocks
Native Ruble, merged Ruble and Bitcoin blocks are identified by asset and mining type.
| Asset | Mining type | Merged # | Network height | Profile | Found | Status | Maturity proof | Reward | Attribution | Block hash |
|---|---|---|---|---|---|---|---|---|---|---|
Loading pool blocksWaiting for the public accounting API. | ||||||||||
Miner dashboard
Use your public RUB address to view native and merged mining activity, blocks, balances and payouts.
Choose a section; your selection can be remembered in this browser.
Account
——Mining mode right now
Checking live Stratum…
The exact mode is resolved from this public RUB address.
Hashrate · 5m—Exact address across active profiles
Active workers—Live Stratum connections
Last live share—Most recent accepted worker share
YOUR MERGED-MINING STATISTICS
STATUS UNAVAILABLEUnavailable
Waiting for an authoritative merged-mining status.
Stable hashrate · 5mUnavailable
Share-based estimate · 1mUnavailable
Hashrate · 1h—
Hashrate · 24h—
Active workers · accepted ≤3m—
Accepted difficulty · 1hUnavailable
Best difficulty—
Last share—
RUB — personal balance
Maturing · estimated
UnavailableLoad a public RUB address to view its reward estimate.
Awaiting allocation · estimated
UnavailableYour share of each PPLNS reward after the pool fee. Estimates become credited only after the pool completes allocation.
- Reserved for payout
- —
- Available
- —
- Paid
- —
- Total credited
- —
BTC — no receiving address selected
Selected addresses are remembered only in this browser.
This account includes all pool work paid to the selected BTC address, including work using another RUB address.
Maturing · estimated
UnavailableLoad a BTC receiving address to view its reward estimate.
Awaiting allocation · estimated
UnavailableThis BTC address’s share of each PPLNS reward after the pool fee. Estimates become credited only after the pool completes allocation.
- Reserved for payout
- —
- Available
- —
- Paid
- —
- Total credited
- —
Payout rules
Only credited, available funds count toward the payout threshold. Maturing estimates are excluded.
RUB
Policy unavailable
BTC
Policy unavailable
RUB maturing reward details
Your PPLNS share after the fee, including rewards from blocks found by other pool participants. These estimates are separate from credited funds.
Load a RUB address to view its reward details.
| Height | Stage | Estimated share | Maturity | Confirmation data recorded | Block hash |
|---|
BTC receiving-account reward details
PPLNS estimates for the selected BTC receiving address, including work using any RUB address. These amounts are separate from RUB rewards and credited BTC funds.
Load a BTC receiving address to view its reward details.
| Height | Stage | Estimated share | Maturity | Confirmation data recorded | Block hash |
|---|
BTC receiving-account allocations
Latest credited rewards for the selected BTC receiving address. The balances above include its complete account totals.
| Height | Found | Credited amount | Block hash |
|---|
BTC receiving-account payouts
Latest payment records for the selected BTC receiving address. Open a transaction for current blockchain confirmations.
| Created | Status | Recipient amount | Transaction ID |
|---|
Merged workers
Only fresh telemetry for this RUB address is shown. The primary worker connects with the address and no suffix; all other worker names are hidden.
| Worker | Status | Hashrate 1m | Hashrate 5m | Hashrate 1h | Hashrate 24h | Accepted difficulty · 1h | Last share |
|---|---|---|---|---|---|---|---|
Awaiting verified merged statisticsEnter a RUB address to view its workers. | |||||||
Blocks and credits for this RUB address
The latest 100 API records for this address are shown. Your own find is labeled ‘Your worker’; PPLNS credit from a block found by someone else is labeled ‘Another pool participant’. Public payout addresses and worker names stay hidden. ‘Block reward’ is the amount before the fee; ‘Distribution share’ is the percentage distributed to miners after the pool fee. Personal amounts appear only after a confirmed calculation.
Latest shown (max. 100)0
Among shown · last hour0
Your finds awaiting allocation—
Credited among shown0
| Asset | Height | Found | Worker | Status | Progress 0–100 | Block reward | My credit | My work | Pool window work | Distribution share | Block hash |
|---|---|---|---|---|---|---|---|---|---|---|---|
Awaiting verified merged statisticsPersonal block records will appear here. | |||||||||||
Personal RUB merged-mining payouts
Personal RUB payout records confirmed by pool accounting are shown, with each operation stage in its status. BTC payments are shown separately for the selected BTC receiving address.
| Asset | Created | Status | Recipient amount | Confirmation | Transaction ID |
|---|---|---|---|---|---|
Awaiting verified merged statisticsPersonal RUB payout records will appear here. | |||||
Native payout rules
Waiting for the current payout policy.
Waiting for verified account balances.
Maturing PPLNS estimates are separate from credited funds. Solo rewards are paid directly in the block and do not enter PPLNS payout batches.
Next personal maturity——
PPLNS credited—
Reserved in batch—
Mature Solo coinbase—
PPLNS share records—
Pool payout batches—
Live mining profiles for this address
A profile is marked live only when fresh telemetry confirms connected workers for this address.
Live workers
Live estimates are reported by each native mining profile. Accepted work is the live profile counter; PPLNS share records are listed separately below.
| Worker | Mode / port | Status | Hashrate 1m | Hashrate 5m | Hashrate 1h | Hashrate 24h | Accepted work · live counter | Last share |
|---|
Blocks found by this address
PPLNS finder attribution and direct Solo rewards are shown separately.
| Height | Mode | Found | Status | Maturity | Your amount | Payment | Block / transaction |
|---|
Pending PPLNS earnings
Estimated rewards mature after 100 following network blocks and become credited after pool allocation. Your reward share is based on accepted work in each block’s PPLNS window.
| Height | Profile | Found | Estimated amount | Your reward share | Calculation | Maturity | Block hash |
|---|
Credited PPLNS allocations
| Height | Profile | Reward type | Received | Calculation | Block hash |
|---|
PPLNS worker history
Accepted share records remain visible when a worker becomes inactive. These accounting estimates and live profile estimates come from different sources and may differ.
| Worker | Profile | Recent | Hashrate 5m | Hashrate 1h | Hashrate 24h | Accepted share records | Last share |
|---|
Pool payout history
Solo rewards are paid directly in the found block and appear above. Payment status is the pool’s last recorded stage; open the transaction for current blockchain confirmations.
| Created | Status | Gross amount | Net amount | Confirmed height | Transaction ID |
|---|
Global reward allocation
Pool-wide block reward allocations after settlement. Global records, not your personal balance or payment history.
| Asset | Mining type | Height | Profile | Block time | Recipient accounts | To miners | Pool fee | PPLNS window work | Block hash |
|---|---|---|---|---|---|---|---|---|---|
No global allocations yetAllocations appear only after authoritative block settlement. | |||||||||
Global pool payout batches
Pool-wide settlement batches and payment outputs. These are global records, not your personal payment history.
| Asset | Mining type | Profile | Created | Status | Payment outputs | Amount to recipients | Network fee | Settlement proof | Transaction ID |
|---|---|---|---|---|---|---|---|---|---|
No global payout batches yetVerified pool settlement transactions will appear here. | |||||||||
Separate settlement
BTC payout information appears only with verified parent-chain telemetry. Missing global or personal finance is never displayed as zero.
Connect a miner
Choose the profile that matches your mining mode. Native profiles use password x; merged mining uses your public Bitcoin reward address.
GENERAL PPLNS:3333
Direct ASIC mining
Automatic difficulty for ordinary persistent public hashrate.
URL
stratum+tcp://pool.rublecore.org:3333Username
YOUR_RUB_ADDRESS.workerPassword
xMin diff
50,000MININGRIGRENTALS:3334
Rented ASICBoost hashrate
High-difficulty profile for the MiningRigRentals SHA256 ASICBOOST market.
URL
stratum+tcp://pool.rublecore.org:3334Username
YOUR_RUB_ADDRESS.workerPassword
xMin diff
262,144SOLO:3335
Direct finder reward
98.5% goes directly to the finder address; 1.5% is paid as the pool fee.
URL
stratum+tcp://pool.rublecore.org:3335Username
YOUR_RUB_ADDRESS.workerPassword
xMin diff
1,000,000MERGED MINING · PPLNS:3340
STATUS UNAVAILABLE
Ruble + Bitcoin
One dedicated SHA-256 connection with independent RUB and BTC block results.
URL
stratum+tcp://merge.rublecore.org:3340Username
YOUR_RUB_ADDRESS.workerPassword
btc=YOUR_BTC_ADDRESSMin diff
50,000 · Automatic VardiffFee
1.5% · PPLNSActivation
Loading from APIMERGED-MINING SETUP
Build the exact connection settings
Enter public receiving addresses only. Nothing entered here is saved by the builder.
- Use your RUB address before the worker suffix.
- Choose a short worker name such as
asic01. - Use your BTC receiving address after
btc=.
URL
stratum+tcp://merge.rublecore.org:3340Username
YOUR_RUB_ADDRESS.asic01Password
btc=YOUR_BTC_ADDRESSAutomatic activation status
Merged-mining work and rewards are available only while the authoritative API status shows LIVE.
Standard Stratum TCP
This endpoint uses standard Stratum TCP. Use only public receiving addresses; network intermediaries may be able to correlate the RUB username and BTC payout address.
Account and payment safety
The pool needs only public receiving addresses. Never paste a seed phrase, private key, WIF, wallet backup or wallet password into a miner, rental service or dashboard.