Silent Payments coinbase

The current system where most miners use a custodial pool to manage payouts has seen some evolution with the introduction of Ocean, which allows approximately 2% of miners to receive payments directly from the coinbase transaction. In this model, despite the pool having control over the payout amounts and the coinbase outputs, there is an opportunity for increased autonomy by letting miners build their own blocks through Datum. This implementation uses a Bitcoin address as a unique identifier for payouts which, however, leads to several privacy and security issues such as address reuse and the potential for tracking miners' spending habits.

The concept of silent payments could potentially mitigate these drawbacks by enhancing privacy and unlinking subsequent payments to individual miners. Implementing this change would primarily affect entities involved in receiving transactions, including libraries, scanner services, and wallets. Conversely, sending transactions would be handled by specialized mining-related software or general-purpose silent payment libraries. The feasibility of integrating this feature into the existing BIP-352 (Bitcoin Improvement Proposal) or whether a new proposal is necessary remains a point of discussion.

Furthermore, the role of solo pools in this ecosystem is notable. These pools, characterized by a smaller collective hash rate but a higher count of individual miners, also use the payout-bitcoin-address-as-user-ID scheme. Adapting the silent payment mechanism to suit solo pools might impose additional requirements on solo miners. However, the benefits, particularly in terms of enhanced privacy by concealing the details of block reward spending, could outweigh these challenges. Such adaptations would need careful consideration of the specific needs and current practices within solo pools. The proposed changes and the underlying technology, including the input/nonce solution, though not detailed, appear plausible for achieving the desired privacy enhancements.