PurpleHash on Nostr: Theoretically yes, but practically no. If there is an average of one draw every 10 ...
Theoretically yes, but practically no.
If there is an average of one draw every 10 minutes, I would need to be able to submit at least 1 ticket (= 1 share with difficulty 1) every 10 minutes. If I fill out a lottery ticket but don't submit it in time, my ticket will not be considered in the draw.
With the NerdMiner, it takes an average of 60 hours to generate 1 share that meets the required minimum difficulty of 1 and is actually submitted to the solo pool. All hashes smaller than difficulty 1 are not transmitted and are essentially nonexistent because no one takes notice of them.
The technical explanation is as follows:
By default, ckpool has a pool difficulty of 10,000. For example, with cgminer, it is possible to lower the minimum difficulty to 1 using the parameter --suggest-diff 1. This means a share must meet the minimum difficulty of 1 for it to be accepted by the solo pool. Anything smaller than difficulty 1 is ignored. That's why there is no statistics for the NerdMiner because hardly anything gets through.
In terms of numbers, this means that for every GH per minute, 14 shares with difficulty 1 are generated. Therefore, for every GH in 10 minutes, 140 shares with difficulty 1 are generated:
1,000,000,000 H/s ÷ 2^32 x 60s x 10min = 140 shares with difficulty 1
In other words, I would need at least 71 MH/s or 3,550 NerdMiners in order to transmit 1 share with difficulty 1 to the solo pool every 10 minutes and for the pool to take note of the submitted hashrate:
1,000,000,000 H/s ÷ 140 = 7,142,857 H/s = 71 MH/s
71 MH/s ÷ 20 KH/s ≈ 3,550 NerdMiners
Nerdminer: 21.500
Newpac: 45.000.000.000
Compac F: 350.000.000.000
S9: 14.500.000.000.000
S19: 110.000.000.000.000
Hashes per second.
Published at
2023-07-20 12:08:17Event JSON
{
"id": "6ebddfdeb7791cfc618b3293d5b6df9175f9381926855d39d7ce0093aa2ad91a",
"pubkey": "b2fd8208199f8cea100b23a583bb888bcda38d042fd1514427964fe51ce7150e",
"created_at": 1689854897,
"kind": 1,
"tags": [
[
"e",
"35edaee815a74169673e28b06a2d6442c7c3604b64745fb384f20a60e38e7192"
],
[
"e",
"78183cf2c57ba70ba6e3fc1aba7779f0975d5a3348ab5a3727a45624a72c1ae9"
],
[
"p",
"b9a537523bba2fcdae857d90d8a760de4f2139c9f90d986f747ce7d0ec0d173d"
],
[
"p",
"95181f816dc80a141e9158a2a398bec37f580f4309633321a1ca53757bf08794"
]
],
"content": "Theoretically yes, but practically no.\n\nIf there is an average of one draw every 10 minutes, I would need to be able to submit at least 1 ticket (= 1 share with difficulty 1) every 10 minutes. If I fill out a lottery ticket but don't submit it in time, my ticket will not be considered in the draw.\n\nWith the NerdMiner, it takes an average of 60 hours to generate 1 share that meets the required minimum difficulty of 1 and is actually submitted to the solo pool. All hashes smaller than difficulty 1 are not transmitted and are essentially nonexistent because no one takes notice of them.\n\nThe technical explanation is as follows:\nBy default, ckpool has a pool difficulty of 10,000. For example, with cgminer, it is possible to lower the minimum difficulty to 1 using the parameter --suggest-diff 1. This means a share must meet the minimum difficulty of 1 for it to be accepted by the solo pool. Anything smaller than difficulty 1 is ignored. That's why there is no statistics for the NerdMiner because hardly anything gets through.\n\nIn terms of numbers, this means that for every GH per minute, 14 shares with difficulty 1 are generated. Therefore, for every GH in 10 minutes, 140 shares with difficulty 1 are generated:\n1,000,000,000 H/s ÷ 2^32 x 60s x 10min = 140 shares with difficulty 1\n\nIn other words, I would need at least 71 MH/s or 3,550 NerdMiners in order to transmit 1 share with difficulty 1 to the solo pool every 10 minutes and for the pool to take note of the submitted hashrate:\n1,000,000,000 H/s ÷ 140 = 7,142,857 H/s = 71 MH/s\n71 MH/s ÷ 20 KH/s ≈ 3,550 NerdMiners\n\n\n\n\nNerdminer: 21.500\nNewpac: 45.000.000.000\nCompac F: 350.000.000.000\nS9: 14.500.000.000.000\nS19: 110.000.000.000.000\n\nHashes per second.",
"sig": "54b1ca08a6f805f953b4384490c8ac21f26e95d6f03121b007930c1fc72e0cda99948897fb3c27dc2e115797788ae7a1a9d1af91c573f39cae13459fd5e8128e"
}