NETWORK PULSE
0 samplesPool hashrate · live session
—Waiting for valid telemetry
Chart begins collecting after the first valid pool sample.
SHA-256d · BTC SOLO + VMESH AUXPOW
YOUR BITCOIN HASHRATE, ANOTHER MINING TARGET
Bitcoin SOLO.
More from each hash.
Mine Bitcoin solo while the same SHA-256d work also targets VargaMesh (VMESH) blocks. One ASIC connection, two independent proof-of-work targets. No extra hashrate split.
Hashpower marketplace
Mining Rig Rentals
Explore available mining hashrate
Solo mining has no guaranteed blocks or profit. VMESH mining does not increase your chance of finding a BTC block.
MERGED SOLO CONSOLESHA-256d · AuxPoW
ONE WORKSTREAMYOUR ASICStratum V1 · Port 3950
PARENT CHAINBitcoinSOLO target
CHILD CHAINVargaMeshAuxPoW target
Checking pool…Same hashes, separate block chances
BITCOIN · SOLO0.1%
BTC developer fee · 99.9% of a found BTC block to the miner
VARGAMESH · AUXPOW1%
VMESH developer fee · 99% of a found VMESH block to the miner
Separate chain-specific fees, charged only on a found block of that chain. Rates are set in the deployed pool code; actual coinbase outputs govern the payout. BCSIG: /VargaMesh-MergedSolo/.
PUBLIC FEE DISCLOSURE
Developer fees & destination addresses
Two independent block rewards. No Bitcoin fee is taken from VMESH rewards and no VMESH fee is taken from Bitcoin rewards. Fees apply only when a valid block is found on the respective chain.
BITCOIN · BTC0.1%
Miner payout: 99.9%, subject to satoshi rounding.
Developer destination:
bc1qdw2puj3g4ypqyxql7dy3jw2f29u5q7fkvd584mVARGAMESH · VMESH1%
Miner payout: 99%.
Developer destination:
vm1qsfsgj70pdv86nguvexzvsflmcknz4lrsj87wx9Original coinbase signature (BCSIG): /VargaMesh-MergedSolo/. These are developer-fee addresses, not deposit addresses. A blank VMESH password for an unbound BTC miner routes the VMESH miner share to the Ecosystem Treasury; an existing binding always takes priority. Explicitly invalid VMESH addresses are rejected.
TRANSPARENT FEES
Bitcoin: 0.1% developer fee (99.9% miner). VMESH: 1% developer fee (99% miner). Fees apply independently to found blocks. For a new BTC address, a blank VMESH password donates the 99% VMESH miner share to the Treasury. Existing bindings are preserved; malformed nonblank addresses are rejected.
Read policy LIVE MINING NETWORKWaiting for live API…
StratumChecking…
Pool hashrate—
BTC miners—
Workers—
Connections—
Accepted shares / sec—
Start difficulty—
AuxPoW coordinatorChecking…
REAL-TIME INTELLIGENCE
Mining operations at a glance.
Live endpoints, active miner estimates and session-only hashrate history. No invented historical data.
Awaiting first sample
WHY BTC MINERS CHOOSE MERGED SOLO
Keep your Bitcoin focus. Add a VMESH target.
No altcoin purchase, no second ASIC, no second pool connection required.
Bitcoin stays SOLO
A found BTC block pays 99.9% (subject to satoshi rounding) to your supplied Bitcoin payout address and 0.1% to the published developer fee address.
Same SHA-256d work
AuxPoW commits VMESH child-chain data to the BTC parent work. Your ASIC does not split hashrate across two algorithms.
Mine VMESH too
Accepted parent work can independently reach the VMESH target. Found VMESH child blocks follow a 99% miner / 1% pool reward split.
START IN THREE STEPS
Need a VMESH wallet? ↗Connect your SHA-256d ASIC
Compatible with standard Stratum V1 SHA-256d miners. No account registration.
Copy these settings into your miner
STRATUM V101 · Pool URL
stratum+tcp://mergedsolo.vargamesh.com:395002 · Username (Bitcoin payout address)
YOUR_BTC_ADDRESS.worker03 · Password (VMESH address or blank for Treasury)
YOUR_VMESH_ADDRESSUse BTC and VMESH addresses you control. A blank VMESH password on a new BTC miner routes the VMESH reward to the ecosystem Treasury; a malformed nonblank password is rejected. Optional
Already mining here? View your stats →
.worker suffix names your machine. Your BTC address may be bound to the first recorded VMESH payout address; changing it may require operator assistance.
WHAT IS VARGAMESH?
An independent SHA-256d proof-of-work network
VargaMesh (VMESH) is a separate blockchain with its own mainnet, nodes, wallets and block rewards. It supports AuxPoW merged mining: the Bitcoin parent work can also serve as proof for a VMESH child block. VMESH is not Bitcoin, and its price or block rewards are not guaranteed.
CLEAR PAYOUT RULES · NO SURPRISES
Understand your payout route.
BTC payouts and VMESH child rewards are separate. For an unbound BTC username, leaving the VMESH password blank selects the ecosystem Treasury. VMESH donations cannot be reversed.
VMESH PAYOUT DECISIONFALLBACK ACTIVE
Stratum passwordVMESH payout address
To keep your VMESH miner reward, enter your own valid vm1 address. An empty password with no prior BTC binding sends the VMESH miner share to Treasury. Existing bindings remain protected; a non-empty invalid address is rejected.
PUBLIC ECOSYSTEM TREASURY
Support the VargaMesh ecosystem
Active policy: a new BTC miner that deliberately leaves the VMESH password blank sends the 99% VMESH miner reward to the Ecosystem Treasury; the separate 1% VMESH developer fee remains unchanged. Existing BTC-to-VMESH bindings always take priority. Non-empty malformed addresses are rejected.
Treasury destination for blank-password fallback
vm1qmh7cnjshtxyrqdfefzs2k7g6r7pd7ma9ntrlegPublic treasury information ↗Active only for blank VMESH passwords on unbound BTC usernames
EDUCATIONAL TOOL · BITCOIN SOLO
Estimate your BTC block probability
Based on the live BTC network difficulty when available. An estimate, not a payout forecast.
Chance of ≥1 Bitcoin block—
Waiting for a verified BTC difficulty figure.
Poisson estimate using independent hashes; excludes downtime, fees and changing network difficulty. VMESH block probability is separate.STRAIGHT ANSWERS
Bitcoin merged SOLO mining FAQ
What is the Bitcoin pool fee?
0.1% of the Bitcoin block coinbase goes to the developer address bc1qdw2puj3g4ypqyxql7dy3jw2f29u5q7fkvd584m; 99.9% goes to the miner, subject to satoshi rounding. Charged only if a BTC block is found. The signature is /VargaMesh-MergedSolo/.
What is the VMESH mining fee?
1% of a found VMESH block coinbase goes to the developer address vm1qsfsgj70pdv86nguvexzvsflmcknz4lrsj87wx9; 99% goes to the miner's valid, registered VMESH address. Fees on BTC and VMESH are separate.
Does merged mining split my ASIC hashrate?
No. Merged mining uses the same SHA-256d parent mining work to evaluate the Bitcoin and VargaMesh proof-of-work targets. It does not improve your Bitcoin block odds.
Do I need a VMESH wallet?
Yes. Supply your own Bitcoin payout address as the Stratum username and your own VMESH address as the Stratum password. Create or open a VMESH wallet ↗.
What if I leave the VMESH password blank or enter an invalid address?
Enter a valid VMESH mainnet payout address. An existing BTC-to-VMESH binding is reused when the password is blank. For a new BTC username, leaving the password completely blank donates the VMESH miner share (99%) to the Ecosystem Treasury; a non-empty invalid address is rejected. To receive VMESH yourself, enter your valid vm1 address.
Is a BTC or VMESH block guaranteed?
No. SOLO mining is probabilistic. Neither network guarantees a block find, a payout, profitability or a stable market price. Electricity and hardware costs remain your responsibility.
⌕
Miner statistics by BTC payout address
Public views mask payout addresses and worker identifiers; address-specific lookups remain limited to the entered BTC address.
Privacy: only masked addresses are rendered in public tables. Lookups may reach the pool backend; do not enter private keys or recovery phrases.
Live miner overview
Public pool activity with BTC and VMESH payout addresses masked.
Loading…
Active / recently active miners
5m and 15m estimates from accepted pool shares| BTC payout | VMESH binding | 5m hashrate | 15m hashrate | Active workers | Last share |
|---|---|---|---|---|---|
| Loading miner telemetry… | |||||
How pool statistics are calculated
Transparent estimates based on accepted share difficulty — not miner-advertised speed.
HASHRATE
Accepted-work estimate
Hashrate is estimated from accepted share difficulty over each displayed time window. Short windows react quickly but can fluctuate more.
PRIVACY
Masked payout addresses
Public miner tables never expose full BTC or VMESH payout addresses. The full BTC address is supplied only for the requested lookup.
SOLO
No outcome guarantee
SOLO mining is probabilistic. Hashrate, shares and previous block finds do not guarantee future blocks, payouts, profitability or economic value.
VARGAMESH · MERGED SOLO INTELLIGENCE
On-chain results & BestShare
BTC parent chain + VMESH AuxPoW. Explore actual network history, cumulative share records and Coinbase payouts — with verified findings clearly separated from unverified matches.
Connecting to SQLite…
BTC node checking
VMESH node checking
SQLite/WAL
Waiting for first reading
POOL BEST SHARE ALL TIME
—
Highest cumulative share difficulty reported by CKPool
Waiting for pool telemetry
BTC TARGET LIVE DIFF
—
Current network difficulty
—
VMESH TARGET LIVE DIFF
—
Current network difficulty
—
VERIFIED POOL FINDS BTC / VMESH
— / —
Requires matching pool-submission proof, not only a Coinbase address
Verification pipeline not ready
POOL TELEMETRY
Observed BestShare evolution
Historical snapshots of the cumulative record, not the time a share was actually mined.
Waiting for the first SQLite observation…
COINBASE ANALYSIS
VMESH payout classification
Your VMESH wallet is also the fee wallet. A 1% output must never be mistaken for a full solo reward.
1% fee-sized outputs—
Full-amount payouts—
1% sized Full payout Other
FEE / MINER WALLET
—Full reward output ≠ independently verified pool submission.
CHAIN SCANNER
BTC history indexing
—Checking scan checkpoint…
No verified pool block count available
CHAIN SCANNER
VMESH history indexing
—Checking scan checkpoint…
Existing candidates survive scans and service restarts.
TRANSPARENT ON-CHAIN RECORDS
Recent Coinbase payout observations
Coinbase matches are candidates only. They are not reported as verified mining results.
Swipe sideways to see amounts, payout type and proof →
| Chain / height | Time | Receiver | Matched amount | Coinbase total | Type | Proof |
|---|---|---|---|---|---|---|
| Loading indexed Coinbase records… | ||||||
Showing most recent observations onlyChain confirmations are not a pool-submission proof
Index stateWaiting for SQLite results…
Current-target comparison is informational, not a historical block proof. Wallet-based payout detection cannot determine which Stratum pool submitted the winning block.