Replies: 2 comments 16 replies
-
|
It's the luck of the math. How many minutes/hours are you renting 20TH for from NH? Currently in order to solve a block the GPU needs to find a solution equivalent to D=2,882,421.42 or greater, 12.38 P at the time I'm posting this Have a look at this wallet - https://solo-eth.2miners.com/account/0x0e3918efec28549af51a80f7776d0a75783083ec#rewards. From what I can see, this person often sends 15TH - 20TH though out the day and if you look at the "personal luck" there are times when it is well over 200% ever 400%. Even though it takes longer than expected to find a block, the one thing to keep in mind is that over the long-term, say 365 days, you will average a 100% luck/probability factor. In my personal experience, my network will constantly solve 3 block (last on November 1st, 10th & 11th) but then will not solve another block for 60-80 days, then it does it again.. 2 or 3 blocks. I track the actual difficulty of each share that my pool receives so I can see the math. I can tell you that the last time I rented 6TH from NH from 1h 20m the largest share received was 5.04P. 6TH should, statically, solve 1.5 blocks per hour but, I just didn't have the luck that day. |
Beta Was this translation helpful? Give feedback.
-
|
The red you are seeing is not rejected at the pool but the delta at the pool. The delta at the pool is when you receive more (green) or less (red) hash rate then you are paying for. You buy 1 TH, the pool reports to receive 1.01 TH - Green, positive delta of 0.01 TH I don't see the need to pause after solving a block. Remember only 1 correct solution is required to solve a block. If there are 200 GPUs attempting to solve a block, their attempts don't change because one of them found a solution. In fact, they are so busy attempting to solve that they have no idea that someone in their family just solved one.. They just get new work and keep going. I have solved multiple blocks within minutes by not only the same rig but the same GPU.. That 3080 was having a good day, Ha! |
Beta Was this translation helpful? Give feedback.
-
|
All this information was really helpful and removed a lot of cloud from our vision. we willl surrely get more experience by time. We are trying to achieve the same goal as : https://miningdao.io/blocks but even running the same hash we are too faraway from their resullt. Do you think that's because of configuration ? or do we need a time to warmup our pool for exemple ? |
Beta Was this translation helpful? Give feedback.
-
|
It's all about time. Some days you will solve 0 block, others 5 or 6.. Sometimes even 10 The one thing I really love about crypto is the math.. It never lies. Men lie, Women lie but math never lies. Ha! Again, my OCD.. I like to know the minute my chance of solving a block goes from 0% to 0.01%. It's how I ignore the rest of the world around me.. Some people use TikTok, I use math and mining. Haha.. Now, on to the next block! :) |
Beta Was this translation helpful? Give feedback.
-
|
That's mean the time of getting a block can be predicted with some math ? that can help us to put off the hash 80% and run it 20% if we get the good calculation ? |
Beta Was this translation helpful? Give feedback.
-
|
It is possible but not as much when you're renting hashrate, I've tried to predict it many times. |
Beta Was this translation helpful? Give feedback.
-
|
Not a block was found at a hashrate of 40GH/s in the last 20 days. |
Beta Was this translation helpful? Give feedback.
-
|
Statistically you should have won between 4-5 blocks but until day 22 there is a 1% chance you will have 0 blocks. As an example lets say you have 40GH of hashrate and we know that right now the network hashrate is 1,004,974.89 GH and the block time is 14s (rounded for ease). Since we know the number of events and the frequency of the events, I would use Poisson Distribution (https://en.wikipedia.org/wiki/Poisson_distribution) to calculate probability. Convert everything to MH/s - I'm giving these variables a,b,c,d which I will use in the math formulas below For Poisson Distribution first we need to find Lambda. Then we use Lambda as the mean value in the Poisson Distribution formula and find the percentage chance of a solve blocks.. Here was can see that if we mine with 40GH for 20 days the probability is that we will solve between 4-5 blocks. If we are extremely lucky the we could solve up to 11 and if we are extremely unlucky then we can solve as little as 0. On day 22 solving 0 blocks becomes 0% I would say that if you don't solve a block over the next few days, then there could be is something wrong with our network/node. Ping time, speed, etc... but chances are that you will solve many blocks very quickly in a cluster. You can also use Binomial Distribution, calculate the probability per block against time and yield the same results |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Could we assume that if we let 100 Gh run all the time and run multiple time rent power for example 15th for 15 min each 2 hours could we define the best time to launch and optimize our luck to catch somes blocks ? |
Beta Was this translation helpful? Give feedback.
-
|
Not necessary. There is no way to calculate the best time to add hash power. |
Beta Was this translation helpful? Give feedback.
-
|
I put together a quick Excel sheet with Poisson and Binomial Distribution calculations. Just remember, mining POW is all about time. Consistency of block wins requires time, nothing more. You can use this for (almost) any POW mining where you know;
|
Beta Was this translation helpful? Give feedback.
-
|
You rock it @XIII39 Thanks |
Beta Was this translation helpful? Give feedback.
-
We use nicehash for our miner, and we send 20TH hashpower to mine the block of Ethereum which should get a block every 5 min, but in reality, no block mined from our mining pool, what's going on? Here is the configuration file:
_{
"logging": {
"level": "info",
"enableConsoleLog": true,
"enableConsoleColors": true,
"logFile": "",
"logBaseDirectory": "",
"perPoolLogFile": false
},
"banning": {
"manager": "Integrated",
"banOnJunkReceive": true,
"banOnInvalidShares": false
},
"notifications": {
"enabled": false,
"email": {
"host": "smtp.example.com",
"port": 587,
"user": "user",
"password": "password",
"fromAddress": "[email protected]",
"fromName": "support"
},
"admin": {
"enabled": false,
"emailAddress": "[email protected]",
"notifyBlockFound": true
}
},
"persistence": {
"postgres": {
"host": "127.0.0.1",
"port": 5432,
"user": "miningcore",
"password": "some-secure-password",
"database": "miningcore"
}
},
"paymentProcessing": {
"enabled": true,
"interval": 100,
"shareRecoveryFile": "recovered-shares.txt"
},
"api": {
"enabled": true,
"listenAddress": "0.0.0.0",
"port": 4000,
"metricsIpWhitelist": [
"18.162.57.76"
],
"rateLimiting": {
"disabled": true
}
},
"pools": [
{
"id": "eth1",
"enabled": true,
"coin": "ethereum",
"address": "0x6486A3f7849734d0EA333eaf9244A4A34dCA17f6",
"rewardRecipients": [
{
"type": "op",
"address": "0x6486A3f7849734d0EA333eaf9244A4A34dCA17f6",
"percentage": 0
}
],
"enableDaemonWebsocketStreaming": false,
"blockRefreshInterval": 50,
"clientConnectionTimeout": 600,
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 50,
"checkThreshold": 50
},
"ports": {
"6161": {
"listenAddress": "*",
"difficulty": 3,
"varDiff": null
}
},
"daemons": [
{
"host": "127.0.0.1",
"port": 8545,
"portWs": 8546,
"notifyWorkUrl": "http://127.0.0.1:8107"
}
],
"paymentProcessing": {
"enabled": true,
"minimumPayment": 0.01,
"payoutScheme": "SOLO",
"payoutSchemeConfig": {
"factor": 0.5
},
"gas": 21000,
"maxFeePerGas": 50000000000,
"keepUncles": false,
"keepTransactionFees": false
}
}
]
}
_
Beta Was this translation helpful? Give feedback.
All reactions