Team Mining · non-custodial

Your own mining pool, without running a pool server

You mine as one team against the network. When you find a block, its coinbase pays every member directly, in proportion to their work. You set the rules, we run the server.

Who it's for

Communities Meetups, Telegram or Discord groups that want to pool their hashrate and find blocks together.
Several farms Farms that join forces instead of handing their hashrate to one of the big pools.
People who know each other A few miners with serious hashrate who want to mine together without a shared wallet.

A single farm with one address doesn't need a team. It just mines solo.

Team Mining vs. the other ways

Blitzpool Team MiningAn admin splits itYour own pool server
PayoutEvery member gets an output of their own in the coinbaseThe admin splits the reward by hand after the blockDepends on the pool software
Who holds the moneyNobody, not even usThe admin or a multisig, and it holds the whole blockDepends on the pool software
RulesCounting method, finder bonus, member limit: a few clicksWhatever the admin saysWhatever you build yourselves
Running itNothing to run: point your miners at the pool, doneNo server, but bookkeeping after every blockNode, pool software, monitoring, updates, around the clock
Block templateYour own, with Job Declaration (sv2-ui build with 0x0003)The template of whichever pool you mine onYour own

Your rules

  • Counting method: A PROP round of any length, reset after every block found if you like, or a sliding window over the last 1 to 365 days. The choice is fixed once the team is created.
  • Finder bonus: Whoever finds the block gets a share up front that you set. The rest is split as usual.
  • Member limit: You decide how many can join. Once the team is full, it takes no more members.
  • Public or private: Either listed in the team directory with join requests, or invite links only, which expire after 1 hour to 30 days.
  • Confirmed joins only: Every member confirms their own address, by email or by signature. Nobody can pull someone else's address into a team.
  • The admin only organizes: inviting, accepting, keeping the rules. They can't touch the sats.

Your block, your template

With Stratum V2 and Job Declaration your team picks the transactions in the block itself, on your own node. For farms in particular this means your hashrate doesn't end up in the big pools' templates.

Blitzpool sv2-ui: Job Declaration for Team Mining

Our sv2-ui build speaks Coinbase Transaction Payouts (extension 0x0003): your miner declares its own template, and the coinbase still pays your team. It is a fork Blitzpool maintains until 0x0003 lands officially in the SRI software. Spec draft

Start it with:docker run --rm --name sv2-ui \ -p 8080:8080 \ -e HOST_HOME=$HOME \ -v /var/run/docker.sock:/var/run/docker.sock \ -v sv2-config:/app/data/config \ ghcr.io/warioishere/sv2-ui:0x0003

In sv2-ui: Pool → Custom Templates → preset “Blitzpool” (description: Team Mining).

Requirement: your own Bitcoin Core node, version 30 or newer; a pruned node is enough.

What you should know

Variance You only get paid when your team finds a block. How often that happens depends on nothing but your combined hashrate. A team of a few small miners can wait a very long time. Expected time per block at today's network difficulty:
Minimum payout A member whose share of a block would fall below the minimum payout gets no output. That share goes to the pool. Teams have no credit that gets paid out later.
Room in the coinbase The coinbase only has room for a limited number of payouts. With more members, the smallest shares drop out of that block, and their share goes to the pool. Your team's admin page shows the limit.

Don't need a team of your own? In the PPLNS pool you mine together with everyone else: the same coinbase payout, the same Stratum V2 setup with Job Declaration. Go to the PPLNS pool