Skip to content

Docs question: self-hosted pool assumptions for a Bitcoin-derived testnet #153

Description

@obtc-maintainer

Hi, I maintain OBTC, a separate Bitcoin-derived PoW experiment. I have a narrow documentation question for self-hosted Public Pool-style setups; this is not a support or listing request.

For a Bitcoin-derived node with getblocktemplate, ordinary SHA256d PoW, and submitblock, what assumptions should a testnet runbook state before a reviewer tries a local pool path? I am mainly thinking about coinbase value/output handling, template mutation boundaries, share difficulty vs block target, and solved-block submission.

Public refs:

This is not a request for endorsement, promotion, investment coverage, miner support, pool support, or hashrate, and there is no miner revenue claim. If this tracker is not the right place for this interface question, feel free to close.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions