Verify Your Bitcoin Onboarding. One dashboard: wallet, worker, connection details.

The pool is running and accepting work. Verify an email, add a wallet and worker, and your dashboard issues connection details once access is approved. The direct-payment policy allocates rewards through the block’s coinbase: 97% to you, 3% to the platform.

Worker configuration 97/3 in the coinbase Non-custodial by design

Access Status

Bitcoin is the only public mining project. Verify an email, then use your dashboard for wallet, worker, and connection details.

Bitcoin onboarding
Verify an email to open the Bitcoin dashboard. Connection details are private and are issued there once your access is approved.
Alpha
The verified dashboard keeps wallet, worker, and connection details private.
Workforce only
Workforce-only projects require a verified @melanin.engineering account in the dashboard.

Verify → Configure → Connect

1

Verify

Bitcoin is the public project. Verify any email address to open your dashboard, then request access. It is granted by review rather than instantly, so a person sees every request.

2

Configure

Add the Bitcoin wallet you want paid to, and a worker for the hardware you have. Your wallet address is your username at the pool; the password field is ignored.

3

Connect

Once an operator approves you, your dashboard shows the exact connection details for the tier and mode you chose. They live there and are never published on a public page. The direct-payment policy allocates rewards through the block’s coinbase — 97% to you, 3% to the platform.

Configure Your Bitcoin Onboarding

Email verification opens your Bitcoin dashboard, where you register a wallet and worker. Endpoints are never published on a public page — your dashboard issues the exact connection details once access is approved.

Prefer to talk first? Ask Melanie, join the Telegram group, or email company@melanin.engineering.

What is available today

The pool is running and accepting work. Solo and collaborative models are both live for Bitcoin, and the choice you record in your dashboard is the one your connection uses.

Melanin’s non-custodial architecture is designed to send rewards through the block’s own coinbase transaction, without a platform-held withdrawal balance. Keep your wallet keys under your control.

The split is 97% miner / 3% platform, under the direct-payment policy. Confirm actual receipt in your wallet; the dashboard alone does not verify the pool’s outputs or prove payment.

Connection details are private. Your dashboard shows the exact endpoint for your tier and model once your access is approved, and those details are never printed on a public page. Anyone can start that process with an email verification.

If you want your rig seen, the public explorer is live at explorer.melanin.global — opt-in only, one address at a time. A published profile shows its wallet address, the same figure the blockchain already carries; your email, your rig names, and the list of who mines here are never published.

Mining economics

This is an educational topic, not a projected payout. Melanin’s fee is published — 97% miner, 3% platform, allocated through the coinbase under that policy — but no earnings estimate is offered, and none should be inferred from the figures below.

BTC
Bitcoin market reference Unavailable Market reference only · not a Melanin payout or explorer

Enter an example gross reward in BTC to see how it is split.

Where to go next

Start on hardware you own

The hobbyist front door: a computer, a Pi, or a phone, and what actually happens before you register anything.

Academy track

Pool Mining & Payouts — how a share becomes a payout, and what Solo trades away.

Public explorer

Pool statistics are public, and a miner can opt one address in. Nobody can download the list of miners, and rig names are never published.

Non-custodial by construction is the direct-payment design. The published fee policy is 97/3 to miner and platform. Bitcoin is the public path. Confirm actual payment in your wallet; a dashboard record alone is not proof. Onboarding needs a verified email, private endpoints stay off public pages, and public code is reviewed before release.