Explore the Developer Architecture Stratum V2 and ARM integration proposals

Bitcoin proof-of-work integration for phones, Pi-class devices, and ASIC fleets. Integration runs through the verified dashboard: signed releases, a documented stack, and connection details issued once your access is approved.

API proposal License to be published Deployment model in review

Access Status

Builders and integration teams can request access now. Public pages describe what is live today.

Configured onboarding
Verify an email to open your dashboard. Connection details are private and are issued there once your access is approved.
Alpha
Developer access is documented at the concept level while private interfaces remain gated.
Separate services
Mining rewards, payout records, and protocol support are operated as separate services.

Integration Planning

The routes and components below are proposed documentation, not a public developer service.

Review the proposal

A future service may use REST or WebSocket interfaces for status and configuration. No client may submit work or receive mining statistics today.

Proposed routes

Plan hardware

Discuss custom devices during verified onboarding. ARM libraries, device registration, and MSBX integrations are not publicly distributed or connected.

Follow development

Public code, a license, contribution workflow, and developer count have not been published. Use Support to register integration interest.

Research

GET /api/v1/miner/<address> — no key. Returns hashrate, shares and best share for one address. Rig names are never returned, and no endpoint lists miners.

The explorer separately publishes opt-in opaque share profiles, which carry no address at all.

Explorer roadmap

Proposed API Surface

None of the following is implemented. These route names reserve documentation space, and no client library has been published to any package registry.

GET /v1/status
Network status.
GET /v1/stats/public
Aggregate statistics.
POST /v1/device/register
Device registration.
GET /v1/earnings/{address}
Reserved for a future opt-in accounting view. No earnings or payout records exist behind it.

Client libraries are planned for Python and JavaScript, with Rust on a research track and Go a concept only. The one endpoint that is live and keyless is GET /api/v1/miner/<address>, described above.

Proposed System Architecture

1

User Devices

Potential Click, Mobile, MSBX, and ASIC client classes

2

Edge / Network

Managed proxy and collaborative-network design. Connection details are private and are issued in an approved dashboard.

3

Blockchain

Rewards settle on-chain in the block’s own coinbase — 97% miner, 3% platform. Melanin holds no balances.

Planned Protocol & Connectivity

Encrypted

Stratum V2 is under consideration for a future encrypted connection path; no public path is enabled.

Efficient

A binary protocol can reduce bandwidth compared with JSON (Stratum V1); implementation remains future work.

Version Rolling

Version rolling is a protocol feature being evaluated for future clients.

Job Negotiation

Job negotiation is a future protocol consideration, not a currently exposed feature.

Edge Proxies

Local gateways are a future design option; none are publicly available.

Managed Defaults

Safe defaults and scheduling are design work; what ships lands in the release registry.

Engineering Roadmap

Now

Release notes and a simple stack diagram. Integration happens through the verified dashboard rather than a public API.

Next

A public RFC index and fuller reliability notes, once the service is ready to run them.

Later

Chaos-testing summaries, audit artifacts, public maintenance windows.

Where to go next

Onboarding, device planning and integration requests all start in the same place: Support. The concept material is on this page — the proposed API surface and the system architecture — and energy feasibility is reviewed through Energy.

Support

Integration and onboarding questions

GitHub

Published repositories

Security

Responsible disclosure

FAQ

Common developer questions

Non-custodial by construction: your share is written into the block's own coinbase, 97/3 to miner and platform. Bitcoin is the public path and the pool is accepting work. Onboarding needs a verified email, private endpoints stay off public pages, and public code is reviewed before release.