I cannot send 1000 coin to MN address. I get "the transactioon is too big. Cannot create transaction".
How to fix?
Topic: [ANN] [CPU mining] WAVI [YescryptR32] [NO Pre-mine] [Masternode] - page 27. (Read 57548 times)
April 26, 2018, 09:41:46 AM
April 26, 2018, 09:03:43 AM
digger 2 Ryzen - 1600 - 558 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards GTX1050/2G - 230 h/s, GTX1060/3G - 420 h/s GTX 1070 - 890 h/s GTX 1080 Ti - 1.2 k/h
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards GTX1050/2G - 230 h/s, GTX1060/3G - 420 h/s GTX 1070 - 890 h/s GTX 1080 Ti - 1.2 k/h
You are mining Wavi with GPUs?
How does this work? April 26, 2018, 04:23:35 AM
for Rizen 1600 better fit 2 * ddr2400 with overclock of 3200, dual channel
overclocking on the core 3.8 megahertz gives an increase, consumption is increased by 30 watts, so you need to change the drain cooling. Watch out for the temperatures
overclocking on the core 3.8 megahertz gives an increase, consumption is increased by 30 watts, so you need to change the drain cooling. Watch out for the temperatures
April 26, 2018, 04:09:07 AM
digger 2 Ryzen - 1600 - 558 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards 1060 - 420 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards 1060 - 420 h/s
That sound about right!
So weird my issue it drives me nuts!
I did memtest to be sure, seems ok.
I understand you. I remember how I started to mining on video cards, constantly changing MHz trying to find the optimal ratio of temperature and speed of mining, spent a lot of time on it. What was my surprise when on another algorithm these settings were not optimal and I had to start all over again. I want to help you, but I do not know how. I still think you need to dig in the direction of the settings of the RAM, it is possible to swap the bars or something else.
Yeah I'll play around with this tomorrow, right now I'm just pissed.
Need sleep! April 26, 2018, 03:59:55 AM
digger 2 Ryzen - 1600 - 558 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards 1060 - 420 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards 1060 - 420 h/s
That sound about right!
So weird my issue it drives me nuts!
I did memtest to be sure, seems ok.
I understand you. I remember how I started to mining on video cards, constantly changing MHz trying to find the optimal ratio of temperature and speed of mining, spent a lot of time on it. What was my surprise when on another algorithm these settings were not optimal and I had to start all over again. I want to help you, but I do not know how. I still think you need to dig in the direction of the settings of the RAM, it is possible to swap the bars or something else.
April 26, 2018, 03:54:36 AM
digger 2 Ryzen - 1600 - 558 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards 1060 - 420 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards 1060 - 420 h/s
That sound about right!
So weird my issue it drives me nuts!
I did memtest to be sure, seems ok.
April 26, 2018, 03:50:01 AM
digger 2 Ryzen - 1600 - 558 h/s
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards GTX1050/2G - 230 h/s, GTX1060/3G - 420 h/s GTX 1070 - 890 h/s GTX 1080 Ti - 1.2 k/h
the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s
I dig on video cards GTX1050/2G - 230 h/s, GTX1060/3G - 420 h/s GTX 1070 - 890 h/s GTX 1080 Ti - 1.2 k/h
April 26, 2018, 03:46:09 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled
I was mining Yenten also before and will get back to it soon... I am running dual channel, I just spent 20 minutes in the bios to check all the options available, though besides the sticks being faster @ 3200Mhz 14-14-14-31 vs 2666Mhz 16-16-18-36, nothing else is different... that I can see. If anything it should be faster no?
Now what is the speed on the YescryptR16?
Now is 900H/s (up to 450H/s now with YescryptR32) but before with the other ram I was doing ~1.1K/s
So it's exactly in the hardware settings. Try to play around with the RAM settings, can the energy-saving mode be enabled?
No nonsense settings are applied, I am the type of geek that disables whatever is not needed like com ports, even the S3 mode is disabled...
I can't imagine that an actual faster ram slows down this algo?
If I swap right now to my old one, I get the better results of 585H/s, but if not it's at 450H/s
April 26, 2018, 03:39:15 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled
I was mining Yenten also before and will get back to it soon... I am running dual channel, I just spent 20 minutes in the bios to check all the options available, though besides the sticks being faster @ 3200Mhz 14-14-14-31 vs 2666Mhz 16-16-18-36, nothing else is different... that I can see. If anything it should be faster no?
Now what is the speed on the YescryptR16?
Now is 900H/s (up to 450H/s now with YescryptR32) but before with the other ram I was doing ~1.1K/s
So it's exactly in the hardware settings. Try to play around with the RAM settings, can the energy-saving mode be enabled?
April 26, 2018, 03:38:57 AM
For information : I confirm dual chanel is very important with tis algorithm.
Currently, with 2x4 GB @2400 MHz, I have 518 H/s with my i5 8600k (@minimal core voltage and minimal mem voltage).
Currently, with 2x4 GB @2400 MHz, I have 518 H/s with my i5 8600k (@minimal core voltage and minimal mem voltage).
April 26, 2018, 03:36:25 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled
I was mining Yenten also before and will get back to it soon... I am running dual channel, I just spent 20 minutes in the bios to check all the options available, though besides the sticks being faster @ 3200Mhz 14-14-14-31 vs 2666Mhz 16-16-18-36, nothing else is different... that I can see. If anything it should be faster no?
Now what is the speed on the YescryptR16?
Now is 900H/s (up to 450H/s now with YescryptR32) but before with the other ram I was doing ~1.1K/s
April 26, 2018, 03:23:54 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled
I was mining Yenten also before and will get back to it soon... I am running dual channel, I just spent 20 minutes in the bios to check all the options available, though besides the sticks being faster @ 3200Mhz 14-14-14-31 vs 2666Mhz 16-16-18-36, nothing else is different... that I can see. If anything it should be faster no?
Now what is the speed on the YescryptR16?
April 26, 2018, 03:21:35 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled
I was mining Yenten also before and will get back to it soon... I am running dual channel, I just spent 20 minutes in the bios to check all the options available, though besides the sticks being faster @ 3200Mhz 14-14-14-31 vs 2666Mhz 16-16-18-36, nothing else is different... that I can see. If anything it should be faster no?
April 26, 2018, 02:57:15 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled
April 26, 2018, 02:37:25 AM
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel?
I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard
@WNC12k Where have you read this?
I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die.
It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it?
Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys!
April 26, 2018, 02:08:50 AM
Examining the Wavi code further .... this is obviously a fork of Dash.
The same code I note above .... right down to the comments ... is in the Dash code.
The only change the Wavi developer seems to have made is to the max block reward (reduced from 500 to 50).
It curious that a coin designed to be long term CPU-only so quickly exits what is referred to as the "CPU mining era".
It would be interesting to hear from the dev regarding this design decision.
Yes, for the reward, we are in the "GPU/ASIC mining era" but in facts, there is presently no possibility to mine WAVI with GPU or ASIC.The same code I note above .... right down to the comments ... is in the Dash code.
The only change the Wavi developer seems to have made is to the max block reward (reduced from 500 to 50).
It curious that a coin designed to be long term CPU-only so quickly exits what is referred to as the "CPU mining era".
It would be interesting to hear from the dev regarding this design decision.
What could be the explaination ?
April 25, 2018, 08:34:33 PM
Examining the Wavi code further .... this is obviously a fork of Dash.
The same code I note above .... right down to the comments ... is in the Dash code.
The only change the Wavi developer seems to have made is to the max block reward (reduced from 500 to 50).
It curious that a coin designed to be long term CPU-only so quickly exits what is referred to as the "CPU mining era".
It would be interesting to hear from the dev regarding this design decision.
The same code I note above .... right down to the comments ... is in the Dash code.
The only change the Wavi developer seems to have made is to the max block reward (reduced from 500 to 50).
It curious that a coin designed to be long term CPU-only so quickly exits what is referred to as the "CPU mining era".
It would be interesting to hear from the dev regarding this design decision.
April 25, 2018, 02:26:57 PM
Here's the part of the code that governs the amount of the block reward:
CAmount GetBlockSubsidy(int nPrevBits, int nPrevHeight, const Consensus::Params& consensusParams, bool fSuperblockPartOnly)
{
double dDiff;
CAmount nSubsidyBase;
// if (nPrevHeight <= 4500 && Params().NetworkIDString() == CBaseChainParams::MAIN) {
/* a bug which caused diff to not be correctly calculated */
// dDiff = (double)0x0000ffff / (double)(nPrevBits & 0x00ffffff);
// } else {
dDiff = ConvertBitsToDouble(nPrevBits);
// }
if (nPrevHeight < 5465) {
// Early ages...
// 1111/((x+1)^2)
nSubsidyBase = (1111.0 / (pow((dDiff+1.0),2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 1) nSubsidyBase = 1;
} else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) {
// CPU mining era
// 11111/(((x+51)/6)^2)
nSubsidyBase = (11111.0 / (pow((dDiff+51.0)/6.0,2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 25) nSubsidyBase = 25;
} else {
// GPU/ASIC mining era
// 2222222/(((x+2600)/9)^2)
nSubsidyBase = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if(nSubsidyBase > 25) nSubsidyBase = 25;
else if(nSubsidyBase < 5) nSubsidyBase = 5;
}
// LogPrintf("height %u diff %4.2f reward %d\n", nPrevHeight, dDiff, nSubsidyBase);
CAmount nSubsidy = nSubsidyBase * COIN;
// yearly decline of production by ~7.1% per year, projected ~18M coins max by year 2050+.
for (int i = consensusParams.nSubsidyHalvingInterval; i <= nPrevHeight; i += consensusParams.nSubsidyHalvingInterval) {
nSubsidy -= nSubsidy/14;
}
// Hard fork to reduce the block reward by 10 extra percent (allowing budget/superblocks)
CAmount nSuperblockPart = (nPrevHeight > consensusParams.nBudgetPaymentsStartBlock) ? nSubsidy/10 : 0;
return fSuperblockPartOnly ? nSuperblockPart : nSubsidy - nSuperblockPart;
}
We appear to be in what the developer labeled in comments as the "GPU/ASIC mining era".
The exact amount is governed by current difficulty level, but at the current block height it cannot be more than 25, and can go as low as 5.
Thank you a lot for this research.Code:
CAmount GetBlockSubsidy(int nPrevBits, int nPrevHeight, const Consensus::Params& consensusParams, bool fSuperblockPartOnly)
{
double dDiff;
CAmount nSubsidyBase;
// if (nPrevHeight <= 4500 && Params().NetworkIDString() == CBaseChainParams::MAIN) {
/* a bug which caused diff to not be correctly calculated */
// dDiff = (double)0x0000ffff / (double)(nPrevBits & 0x00ffffff);
// } else {
dDiff = ConvertBitsToDouble(nPrevBits);
// }
if (nPrevHeight < 5465) {
// Early ages...
// 1111/((x+1)^2)
nSubsidyBase = (1111.0 / (pow((dDiff+1.0),2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 1) nSubsidyBase = 1;
} else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) {
// CPU mining era
// 11111/(((x+51)/6)^2)
nSubsidyBase = (11111.0 / (pow((dDiff+51.0)/6.0,2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 25) nSubsidyBase = 25;
} else {
// GPU/ASIC mining era
// 2222222/(((x+2600)/9)^2)
nSubsidyBase = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if(nSubsidyBase > 25) nSubsidyBase = 25;
else if(nSubsidyBase < 5) nSubsidyBase = 5;
}
// LogPrintf("height %u diff %4.2f reward %d\n", nPrevHeight, dDiff, nSubsidyBase);
CAmount nSubsidy = nSubsidyBase * COIN;
// yearly decline of production by ~7.1% per year, projected ~18M coins max by year 2050+.
for (int i = consensusParams.nSubsidyHalvingInterval; i <= nPrevHeight; i += consensusParams.nSubsidyHalvingInterval) {
nSubsidy -= nSubsidy/14;
}
// Hard fork to reduce the block reward by 10 extra percent (allowing budget/superblocks)
CAmount nSuperblockPart = (nPrevHeight > consensusParams.nBudgetPaymentsStartBlock) ? nSubsidy/10 : 0;
return fSuperblockPartOnly ? nSuperblockPart : nSubsidy - nSuperblockPart;
}
We appear to be in what the developer labeled in comments as the "GPU/ASIC mining era".
The exact amount is governed by current difficulty level, but at the current block height it cannot be more than 25, and can go as low as 5.
Effectively, there is a condition on the reward before the bloc 24001 ("else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) ").
Some others surprises like that ?
April 25, 2018, 01:22:39 AM
Here's the part of the code that governs the amount of the block reward:
CAmount GetBlockSubsidy(int nPrevBits, int nPrevHeight, const Consensus::Params& consensusParams, bool fSuperblockPartOnly)
{
double dDiff;
CAmount nSubsidyBase;
// if (nPrevHeight <= 4500 && Params().NetworkIDString() == CBaseChainParams::MAIN) {
/* a bug which caused diff to not be correctly calculated */
// dDiff = (double)0x0000ffff / (double)(nPrevBits & 0x00ffffff);
// } else {
dDiff = ConvertBitsToDouble(nPrevBits);
// }
if (nPrevHeight < 5465) {
// Early ages...
// 1111/((x+1)^2)
nSubsidyBase = (1111.0 / (pow((dDiff+1.0),2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 1) nSubsidyBase = 1;
} else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) {
// CPU mining era
// 11111/(((x+51)/6)^2)
nSubsidyBase = (11111.0 / (pow((dDiff+51.0)/6.0,2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 25) nSubsidyBase = 25;
} else {
// GPU/ASIC mining era
// 2222222/(((x+2600)/9)^2)
nSubsidyBase = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if(nSubsidyBase > 25) nSubsidyBase = 25;
else if(nSubsidyBase < 5) nSubsidyBase = 5;
}
// LogPrintf("height %u diff %4.2f reward %d\n", nPrevHeight, dDiff, nSubsidyBase);
CAmount nSubsidy = nSubsidyBase * COIN;
// yearly decline of production by ~7.1% per year, projected ~18M coins max by year 2050+.
for (int i = consensusParams.nSubsidyHalvingInterval; i <= nPrevHeight; i += consensusParams.nSubsidyHalvingInterval) {
nSubsidy -= nSubsidy/14;
}
// Hard fork to reduce the block reward by 10 extra percent (allowing budget/superblocks)
CAmount nSuperblockPart = (nPrevHeight > consensusParams.nBudgetPaymentsStartBlock) ? nSubsidy/10 : 0;
return fSuperblockPartOnly ? nSuperblockPart : nSubsidy - nSuperblockPart;
}
We appear to be in what the developer labeled in comments as the "GPU/ASIC mining era".
The exact amount is governed by current difficulty level, but at the current block height it cannot be more than 25, and can go as low as 5.
Thank you a lot for this research.Code:
CAmount GetBlockSubsidy(int nPrevBits, int nPrevHeight, const Consensus::Params& consensusParams, bool fSuperblockPartOnly)
{
double dDiff;
CAmount nSubsidyBase;
// if (nPrevHeight <= 4500 && Params().NetworkIDString() == CBaseChainParams::MAIN) {
/* a bug which caused diff to not be correctly calculated */
// dDiff = (double)0x0000ffff / (double)(nPrevBits & 0x00ffffff);
// } else {
dDiff = ConvertBitsToDouble(nPrevBits);
// }
if (nPrevHeight < 5465) {
// Early ages...
// 1111/((x+1)^2)
nSubsidyBase = (1111.0 / (pow((dDiff+1.0),2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 1) nSubsidyBase = 1;
} else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) {
// CPU mining era
// 11111/(((x+51)/6)^2)
nSubsidyBase = (11111.0 / (pow((dDiff+51.0)/6.0,2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 25) nSubsidyBase = 25;
} else {
// GPU/ASIC mining era
// 2222222/(((x+2600)/9)^2)
nSubsidyBase = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if(nSubsidyBase > 25) nSubsidyBase = 25;
else if(nSubsidyBase < 5) nSubsidyBase = 5;
}
// LogPrintf("height %u diff %4.2f reward %d\n", nPrevHeight, dDiff, nSubsidyBase);
CAmount nSubsidy = nSubsidyBase * COIN;
// yearly decline of production by ~7.1% per year, projected ~18M coins max by year 2050+.
for (int i = consensusParams.nSubsidyHalvingInterval; i <= nPrevHeight; i += consensusParams.nSubsidyHalvingInterval) {
nSubsidy -= nSubsidy/14;
}
// Hard fork to reduce the block reward by 10 extra percent (allowing budget/superblocks)
CAmount nSuperblockPart = (nPrevHeight > consensusParams.nBudgetPaymentsStartBlock) ? nSubsidy/10 : 0;
return fSuperblockPartOnly ? nSuperblockPart : nSubsidy - nSuperblockPart;
}
We appear to be in what the developer labeled in comments as the "GPU/ASIC mining era".
The exact amount is governed by current difficulty level, but at the current block height it cannot be more than 25, and can go as low as 5.
Effectively, there is a condition on the reward before the bloc 24001 ("else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) ").
Some others surprises like that ?
April 24, 2018, 09:41:07 PM
Here's the part of the code that governs the amount of the block reward:
CAmount GetBlockSubsidy(int nPrevBits, int nPrevHeight, const Consensus::Params& consensusParams, bool fSuperblockPartOnly)
{
double dDiff;
CAmount nSubsidyBase;
// if (nPrevHeight <= 4500 && Params().NetworkIDString() == CBaseChainParams::MAIN) {
/* a bug which caused diff to not be correctly calculated */
// dDiff = (double)0x0000ffff / (double)(nPrevBits & 0x00ffffff);
// } else {
dDiff = ConvertBitsToDouble(nPrevBits);
// }
if (nPrevHeight < 5465) {
// Early ages...
// 1111/((x+1)^2)
nSubsidyBase = (1111.0 / (pow((dDiff+1.0),2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 1) nSubsidyBase = 1;
} else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) {
// CPU mining era
// 11111/(((x+51)/6)^2)
nSubsidyBase = (11111.0 / (pow((dDiff+51.0)/6.0,2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 25) nSubsidyBase = 25;
} else {
// GPU/ASIC mining era
// 2222222/(((x+2600)/9)^2)
nSubsidyBase = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if(nSubsidyBase > 25) nSubsidyBase = 25;
else if(nSubsidyBase < 5) nSubsidyBase = 5;
}
// LogPrintf("height %u diff %4.2f reward %d\n", nPrevHeight, dDiff, nSubsidyBase);
CAmount nSubsidy = nSubsidyBase * COIN;
// yearly decline of production by ~7.1% per year, projected ~18M coins max by year 2050+.
for (int i = consensusParams.nSubsidyHalvingInterval; i <= nPrevHeight; i += consensusParams.nSubsidyHalvingInterval) {
nSubsidy -= nSubsidy/14;
}
// Hard fork to reduce the block reward by 10 extra percent (allowing budget/superblocks)
CAmount nSuperblockPart = (nPrevHeight > consensusParams.nBudgetPaymentsStartBlock) ? nSubsidy/10 : 0;
return fSuperblockPartOnly ? nSuperblockPart : nSubsidy - nSuperblockPart;
}
We appear to be in what the developer labeled in comments as the "GPU/ASIC mining era".
The exact amount is governed by current difficulty level, but at the current block height it cannot be more than 25, and can go as low as 5.
Code:
CAmount GetBlockSubsidy(int nPrevBits, int nPrevHeight, const Consensus::Params& consensusParams, bool fSuperblockPartOnly)
{
double dDiff;
CAmount nSubsidyBase;
// if (nPrevHeight <= 4500 && Params().NetworkIDString() == CBaseChainParams::MAIN) {
/* a bug which caused diff to not be correctly calculated */
// dDiff = (double)0x0000ffff / (double)(nPrevBits & 0x00ffffff);
// } else {
dDiff = ConvertBitsToDouble(nPrevBits);
// }
if (nPrevHeight < 5465) {
// Early ages...
// 1111/((x+1)^2)
nSubsidyBase = (1111.0 / (pow((dDiff+1.0),2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 1) nSubsidyBase = 1;
} else if (nPrevHeight < 17000 || (dDiff <= 75 && nPrevHeight < 24000)) {
// CPU mining era
// 11111/(((x+51)/6)^2)
nSubsidyBase = (11111.0 / (pow((dDiff+51.0)/6.0,2.0)));
if(nSubsidyBase > 50) nSubsidyBase = 50;
else if(nSubsidyBase < 25) nSubsidyBase = 25;
} else {
// GPU/ASIC mining era
// 2222222/(((x+2600)/9)^2)
nSubsidyBase = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if(nSubsidyBase > 25) nSubsidyBase = 25;
else if(nSubsidyBase < 5) nSubsidyBase = 5;
}
// LogPrintf("height %u diff %4.2f reward %d\n", nPrevHeight, dDiff, nSubsidyBase);
CAmount nSubsidy = nSubsidyBase * COIN;
// yearly decline of production by ~7.1% per year, projected ~18M coins max by year 2050+.
for (int i = consensusParams.nSubsidyHalvingInterval; i <= nPrevHeight; i += consensusParams.nSubsidyHalvingInterval) {
nSubsidy -= nSubsidy/14;
}
// Hard fork to reduce the block reward by 10 extra percent (allowing budget/superblocks)
CAmount nSuperblockPart = (nPrevHeight > consensusParams.nBudgetPaymentsStartBlock) ? nSubsidy/10 : 0;
return fSuperblockPartOnly ? nSuperblockPart : nSubsidy - nSuperblockPart;
}
We appear to be in what the developer labeled in comments as the "GPU/ASIC mining era".
The exact amount is governed by current difficulty level, but at the current block height it cannot be more than 25, and can go as low as 5.
Jump to: