Deployment of Bitcoind can be done in many ways, depending on the requirements of your deployment, it could be fairly minimal, or very involved.
Before undertaking such a process, it is important to consider if you really need a Bitcoin node. Services such as mAPI provide transaction processing and informational services to merchants, exchanges and anyone else who needs to interact with the blockchain without the encumbrance of running a Bitcoin node themselves.
If you are a Miner, at the bare minimum you will need to setup your Bitcoin node by running bitcoind.
Further to this, you may wish to run Miner ID (and/or mAPI alongside your Bitcoin Node. These can be run on the same machine, or connected over LAN/WAN.
Miner Id is an optional addition to running bitcoind which allows you as a Miner to build a reputation in the Bitcoin SV ecosystem.
It also allows Miners a verifiable opportunity to list their services, contact, and other relevant information to their customer base without the risk of impersonations on their behalf.
In a similar vein to Miner ID, mAPI is an interface Miners can offer on Bitcoin SV to provide personalised fee pricing and service guarantees to partners and/or the general public. In accordance with the SPV protocol, a user or merchant interacting with mAPI provides all of the assurances required to safely transact on BSV without needing to maintain a full local copy of the blockchain. Double spends and other risk factors often cited when using Bitcoin are alleviated by creating an active communication channel between Merchants and Miners.
A positive response from a Miner via mAPI is a reputationally backed promise that Miner will attempt to mine your transaction and won’t accept a double spend of it unless they see it in a block, the merchant will be notified near instantly at the time of processing.
Please refer to the mAPI setup guide for deploying mAPI
GMC is an improved API for Miners, ensuring they can scale with the Bitcoin network, by mining large blocks without the limitations of the RPC interface interfering as block sizes grow. Based on and credited to the work of Andrew Stone and Johan van der Hoeven, GMC works by removing the list of transactions from the RPC request found in ‘getblocktemplate’ and supplying only the Merkle proof of all the transactions currently in the mempool/blockcandidate.
It is strongly recommended that Miners begin the necessary steps to adapt their mining pool software to use GMC. As block sizes grow, Miners still using GetBlockTemplate will begin to run into issues trying to produce blocks. At best, they will be leaving fees on the table for other Miners, and at worst their mining environment will fall behind the chain tip as they are waiting on block templates to be generated, in some cases bringing block production to a complete stand still.
For Miners wishing to test the limitations of their pool setup it is recommended they start a test deployment on the Scaling Testnet.