Frequently asked questions.
Everything you need to know before connecting an ASIC to the planned BCH + VMESH merged SOLO pool.
Is the pool live and accepting miners?
No. BCHN was still synchronizing at the last operator-provided check. The website and status feed are staged separately; public Stratum access will open only after successful BCH/VMESH end-to-end validation.
Can my ASIC mine BCH and VMESH simultaneously?
Yes in principle. The parent-chain BCH hashing work can contain a VMESH AuxPoW commitment. Both chains evaluate solutions against different proof-of-work targets; combined mining does not magically double your hashrate.
Which hardware is supported?
SHA-256d-compatible ASIC hardware. Compatibility with individual ASIC firmware and Stratum clients still requires testing before launch.
How are BCH rewards paid?
The planned solo implementation places the finding miner's BCH CashAddr payout and a fixed 1% developer payout in the BCH coinbase. A BCH block must be accepted by the BCH network and satisfy the coinbase maturity rules.
How are VMESH rewards paid?
A per-miner VMESH child coinbase is constructed using the miner's own VMESH address. Its fixed 1% developer output is separate from the BCH output. Each chain handles its own maturity and confirmations.
Does a VMESH block also pay BCH?
Not necessarily. Finding a VMESH-level solution does not mean its hash satisfies the much harder BCH parent target. The reverse is typically different, but acceptance always depends on each chain's proof validation.
Is the 1% fee mandatory for the entire VargaMesh network?
No. These are pool implementation policies, not consensus requirements imposed on all VMESH miners.
Where can I verify VargaMesh?
See the official project, block explorer and the VargaMesh Core repository.