Mining Vivuscoin

Vivuscoin is SHA-256d proof of work with a 240-second block target and a 50 VVC reward. The project runs a solo stratum endpoint: point any SHA-256d miner at it with your VVC address as the username, and a block you find pays the reward straight to that address. No account, no pool balance, nothing to withdraw.

Get a wallet address
Network
Difficulty current target
Block height on both seed nodes
Last block date of the latest block
Block reward 50 VVC every 240 s at target

Live stats unavailable — see Network status.

Proof of work in Vivuscoin

Vivuscoin uses SHA-256d, the same double SHA-256 hash as Bitcoin, on Bitcoin-derived code. The rules that matter to a miner:

  • Block target: 240 seconds. Difficulty is set so that the whole network finds one block every four minutes on average.
  • Reward: 50 VVC per block, halving every 210,000 blocks. Transaction fees in the block go to the miner as well.
  • Coinbase maturity: 100 blocks. A reward can be spent after 100 further blocks; the wallet shows it as immature until then.
  • Difficulty today: about 132.6 (as of 2026-09; live value in the tiles above). At that difficulty the network needs roughly 2.4 GH/s in total to keep 240-second blocks (difficulty × 232 ÷ 240 s). That is tiny by SHA-256 standards, and it shapes the hardware advice below.

Difficulty has not moved since 2021-09-22 because no block has been found since. Why that happened, and what v1.1 changes about it, is explained below.

Solo mining through our stratum endpoint

Any SHA-256d stratum miner can connect. Your VVC address is the username, the password is x.

The endpoint runs in solo mode: the block template's coinbase pays the address you authorise with, so a block you find pays its full 50 VVC reward directly to your wallet. There is no pool wallet, no share accounting that turns into payouts, no minimum, no fee and nothing to withdraw. It also means there is no smoothing: you earn a whole block or nothing.

Use an address that starts with A from the Vivuscoin wallet. Bech32 vvc1 usernames have not been tested against the endpoint yet, so stick to A addresses for now. A username that is not a valid VVC address is rejected at login.

Blocks only count once the network is producing them again.

Until the v1.1 restart your miner will connect, receive work and submit shares, but the chain may not advance. Watch Network status and the roadmap.

Solo stratum
Pool URL:  stratum+tcp://pool.vivuscoin.com:3333
Username:  your VVC wallet address (e.g. A... from the Vivuscoin wallet)
Password:  x

Example:   -a sha256d -o stratum+tcp://pool.vivuscoin.com:3333 -u <YOUR_VVC_ADDRESS> -p x

Your miner sends work to the stratum endpoint; when a block is found, its reward is paid by the block itself to the address you used as the username.

Step by step

  1. Get a VVC address

    Install Vivuscoin Core, let it sync to 24,092, and create a receiving address in the Receive tab. It starts with A. Back up wallet.dat: the block rewards land in this wallet and nowhere else.

  2. Pick mining software

    Any miner that speaks stratum and hashes SHA-256d will do. For a first connection test a CPU miner such as cpuminer (-a sha256d) is enough; for actually finding blocks see the hardware notes. Vivuscoin has no miner of its own and recommends none.

  3. Run the miner

    Three example command lines. They are examples; check your miner's own flags, in particular how it selects the algorithm.

    cpuminer / cpuminer-multi
    cpuminer -a sha256d -o stratum+tcp://pool.vivuscoin.com:3333 -u <YOUR_VVC_ADDRESS> -p x
    cgminer
    cgminer -o stratum+tcp://pool.vivuscoin.com:3333 -u <YOUR_VVC_ADDRESS> -p x
    bfgminer
    bfgminer -o stratum+tcp://pool.vivuscoin.com:3333 -u <YOUR_VVC_ADDRESS> -p x

    Replace <YOUR_VVC_ADDRESS> with the address from step 1. cgminer and bfgminer hash SHA-256d by default; other miners need the algorithm named. A working connection shows a subscribe, an accepted authorisation and a new job every 30 seconds or so.

  4. Watch for your block

    Your miner reports accepted shares; a share that meets the network difficulty is a block. The network status page shows the block height and the time of the last block, and your wallet shows the reward as an immature balance. To inspect a block, open it on the block explorer: each block page shows the coinbase and the address it paid.

  5. Wait for the reward to mature

    A block reward becomes spendable after 100 further blocks. At the 240-second target that is about 6 hours and 40 minutes, but only once blocks are flowing at the target rate.

Hardware

The honest version: the network needs about 2.4 GH/s in total today, and difficulty follows whatever hash rate shows up. So the question is not "what is fastest" but "what matches the network". No profitability claims are made here; VVC has no market price.

HardwareTypical SHA-256d rateAgainst today's ~2.4 GH/s needMakes sense for
CPUtens of MH/smany hours to days per block on its ownTesting the connection
Single GPUabout 1–3 GH/sroughly the whole networkActually mining; throttle it if blocks come too fast
SHA-256 ASICtens of TH/s and uptens of thousands of times more than neededNot this network today (see below)

Why an ASIC is the wrong tool right now

Until v1.1 activates, the 2021 difficulty rules are still in force: difficulty is recalculated only every 5,040 blocks and can move at most four times up or down per retarget. Aim an ASIC at that and it finds the next 5,040 blocks in minutes, difficulty rises only fourfold, and it repeats. When the ASIC leaves, difficulty is stuck far above what anyone else can serve and the chain stalls again. That is exactly how it got stuck at 24,092 in 2021. The next retarget under the old rules comes at block 25,200, and because five years have passed since the previous one it will lower difficulty to about 33, the largest drop the clamp allows.

v1.1 changes this: difficulty is recomputed every block from the last 60 blocks, so it tracks the real hash rate within an hour or two, and a bounded emergency rule brings it back down if blocks stop. An ASIC would then just push difficulty up as fast as it mines, which harms only its owner when it leaves and everyone else until difficulty falls back. Even under v1.1, a duty-cycled or throttled device is the considerate choice on a network this size.

A single GPU is about the right magnitude today. If you run one and blocks come faster than every four minutes, throttle it; the goal after the restart is steady 240-second blocks, not the most blocks in the shortest time.

Why the chain stopped and how v1.1 changes mining

The chain has been paused at block 24,092 since 2021-09-22. In 2021, difficulty retargeted every 5,040 blocks with a ±4× clamp, the way early Bitcoin did. Hash power came, pushed difficulty up at a retarget, and left; nobody could serve difficulty 132.6 at the time, and with no block found there was no retarget to bring it down. A rule that only adjusts after 5,040 blocks cannot recover from zero blocks.

v1.1 replaces that rule and adds guard rails. For a miner it means:

  • Per-block difficulty (LWMA-1 over a 60-block window): difficulty responds to your hash rate within blocks, not after thousands of them.
  • Emergency rule: if no block arrives for a long time, difficulty is lowered step by step within bounds, so a stall recovers within hours.
  • Timestamps: a block may be at most 12 minutes ahead of network time (was 2 hours), which removes the room for timestamp tricks against the difficulty algorithm.
  • Reorg limit: reorganisations deeper than about 10 blocks are refused and checkpoints are kept, so a burst of hash power cannot rewrite history.
  • Activation: v1.1 activates at a set height shortly after mining resumes. Wallets and nodes must upgrade before that height; the height is published with the release and is not set yet.

Until v1.1 activates, the old 5,040-block retarget applies.

Blocks found before the activation height are mined under the 2021 rules, including the ±4× clamp. Keep hash rate modest until difficulty is being set per block.

The restart plan in order

Mining FAQ

Is there a fee?

No. The endpoint runs in solo mode with no fee and no donation: the whole 50 VVC reward plus the block's transaction fees go to your address in the block itself. The pool never holds coins, so there is nothing to deduct.

Can I use a normal pool?

We know of no third-party pool for VVC, and this endpoint does not do shared payouts. If you want to run your own, we run a solo-mode ckpool against a Vivuscoin full node; how to run a node is on the Developers page. A pool that promises VVC payouts is not affiliated with this project.

What about the old pool instructions?

The host and port have not changed: pool.vivuscoin.com:3333. The old homepage line with -p c=VVC is obsolete; the password is now simply x, and the username is your address rather than an account name.

Where do I see my blocks?

In your wallet, as an immature balance that matures after 100 blocks, and on the network status page as a rising block height. Open the block on the block explorer to see the coinbase and the address it paid, or use a full node's getblock.

All network and mining questions