Good info from Grok:
Unlike DATUM, Public Pool’s design mimics a lightweight pool structure. It coordinates work distribution so that miners collectively target the same block template, potentially reducing duplicate effort by assigning non-overlapping nonce ranges. This doesn’t mean they solve the block as a unified entity (solo mining still applies), but it optimizes their combined hashrate toward a single goal, which can feel like aggregation...
Public Pool’s protocol borrows from traditional pool mining concepts, where a central server (in this case, your node) orchestrates work to maximize efficiency. This includes aggregating hashrate for display and possibly optimizing nonce distribution, which DATUM avoids to maintain decentralization. DATUM’s focus is on letting each miner operate as a standalone entity with its own template control, while Public Pool treats your setup as a mini-pool
Asaf Fulks
npub1ze…4n8ys
2025-07-28 03:50:03 UTC
in reply to nevent1q…pewu
Author Public Key
npub1zete4tgtqyfns5zavpa882ej9tt2gfhhd97rursq0crztzt2hyhsk4n8ysSeen on
wss://nos.lolPublished at
2025-07-28 03:50:03 UTCEvent JSON
{
"id": "291299cc67e8b3746a6ecc243bbab32d9e881be9fa062213d5cd538ae5bd38b1",
"pubkey": "16579aad0b011338505d607a73ab322ad6a426f7697c3e0e007e0625896ab92f",
"created_at": 1753674603,
"kind": 1,
"tags": [
[
"e",
"d89f3a9564e81152ca85ea18f3d2c74469363e427e2cffdf47ab524edececffb",
"",
"root"
],
[
"p",
"16579aad0b011338505d607a73ab322ad6a426f7697c3e0e007e0625896ab92f"
]
],
"content": "Good info from Grok: \n\nUnlike DATUM, Public Pool’s design mimics a lightweight pool structure. It coordinates work distribution so that miners collectively target the same block template, potentially reducing duplicate effort by assigning non-overlapping nonce ranges. This doesn’t mean they solve the block as a unified entity (solo mining still applies), but it optimizes their combined hashrate toward a single goal, which can feel like aggregation...\n\nPublic Pool’s protocol borrows from traditional pool mining concepts, where a central server (in this case, your node) orchestrates work to maximize efficiency. This includes aggregating hashrate for display and possibly optimizing nonce distribution, which DATUM avoids to maintain decentralization. DATUM’s focus is on letting each miner operate as a standalone entity with its own template control, while Public Pool treats your setup as a mini-pool\n\n\r\n\r\n",
"sig": "d0a5f301231156e33120a70dcb7c4bfe39d91067fd4eabb7f921996a74d14fbe5bda649f0317fbf7470732aa29ff3ee8ad92bc9f14955a5627726eb7a6a5d813"
}