Search content
Sort by
Showing 20 of 60 results by Ellieo
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Hmm...not sure if the reduction/simplification from sum of five primes of other people works to sum of three primes is what it meant as less memory in the computational sense of that article. I'll continue to investigate and research for some inspiration, etc.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Gatra, I haven't been following the development for sometime but are you still the solo developer in this riecoin project? Your gmail still the same? I'll try look for some inspirational works not related but they shared the same complexity for solving in lesser memory space. I understood the resources to tackle the problem are rare, unique and difficult, etc.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Hi Gatra and all great contributors,
Major arcs for Goldbach's problem - H. A. Helfgott
https://arxiv.org/abs/1305.2897
HardyLittlewood circle method
https://en.wikipedia.org/wiki/Hardy%E2%80%93Littlewood_circle_method
https://www.youtube.com/watch?v=qhS9L-jTVkM
The Ternary Goldbach Problem - Harald Helfgott
It's been awhile since my absent from mining Riecoin with limited resources than before. Found the above and hope them can shed some light to improve the algorithms used in Riecoin's superblock for larger world records, etc. The youtube explain the C algorithm on circle method to find prime, etc.
Major arcs for Goldbach's problem - H. A. Helfgott
https://arxiv.org/abs/1305.2897
HardyLittlewood circle method
https://en.wikipedia.org/wiki/Hardy%E2%80%93Littlewood_circle_method
https://www.youtube.com/watch?v=qhS9L-jTVkM
The Ternary Goldbach Problem - Harald Helfgott
It's been awhile since my absent from mining Riecoin with limited resources than before. Found the above and hope them can shed some light to improve the algorithms used in Riecoin's superblock for larger world records, etc. The youtube explain the C algorithm on circle method to find prime, etc.
I did not get how "the sum of three primes" can help with the search for prime sextuplets ?
Also HardyLittlewood circle method is a technique used to prove asymptotic behavior of a series. AFAIK there is no generating function for prime numbers etc.
Video is from 2014 with bad sound (and no sound until 2:50), lost patience soon.
There may be ideas to use, only I may not see them.
I was referring to another work from the same author. The same man who worked on the "the sum of three primes" problem has recently been working on a method for making sieves that uses less RAM: that's the work that may (or may not) be helpful, but I still couldn't find any links to an actual paper.
If I get inspiration how that was done I'll share it with you all.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Hi Gatra and all great contributors,
Major arcs for Goldbach's problem - H. A. Helfgott
https://arxiv.org/abs/1305.2897
HardyLittlewood circle method
https://en.wikipedia.org/wiki/Hardy%E2%80%93Littlewood_circle_method
https://www.youtube.com/watch?v=qhS9L-jTVkM
The Ternary Goldbach Problem - Harald Helfgott
It's been awhile since my absent from mining Riecoin with limited resources than before. Found the above and hope them can shed some light to improve the algorithms used in Riecoin's superblock for larger world records, etc. The youtube explain the C algorithm on circle method to find prime, etc.
Major arcs for Goldbach's problem - H. A. Helfgott
https://arxiv.org/abs/1305.2897
HardyLittlewood circle method
https://en.wikipedia.org/wiki/Hardy%E2%80%93Littlewood_circle_method
https://www.youtube.com/watch?v=qhS9L-jTVkM
The Ternary Goldbach Problem - Harald Helfgott
It's been awhile since my absent from mining Riecoin with limited resources than before. Found the above and hope them can shed some light to improve the algorithms used in Riecoin's superblock for larger world records, etc. The youtube explain the C algorithm on circle method to find prime, etc.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
I'm all for the records breaking since it indicates to me there is increasing hashpower (miners) between each successive record breaker (3 2 birds with 1 stone). Obviously the data (with frequent updates) for hashpower peak optimization needed for superblock timing would be gathered from the pool that contributed the record breaker as the first tier filter then followed by the second, third, etc.
No prediction pattern can guarantee 100% accuracy but at least it's way better than having unacceptable hashpower (less than 80%) during the superblock event. Taking the drift assumption as reliable means of reaching the peak hashpower of any pool is far moreless unpredictable. Inspecting the past few superblock records said it has no decisive & consistent direction.
Superblock Date Time Drift Drift from Average Time
160848 2014-11-17 19:50 0 -01:25
164880 2014-11-24 20:28 +00:38 -00:47
168912 2014-12-01 22:33 +02:05 +01:18
172944 2014-12-08 21:20 -01:13 +00:05
176976 2014-12-15 22:07 +00:47 +00:52
Average Time = 21:15
No prediction pattern can guarantee 100% accuracy but at least it's way better than having unacceptable hashpower (less than 80%) during the superblock event. Taking the drift assumption as reliable means of reaching the peak hashpower of any pool is far more
Superblock Date Time Drift Drift from Average Time
160848 2014-11-17 19:50 0 -01:25
164880 2014-11-24 20:28 +00:38 -00:47
168912 2014-12-01 22:33 +02:05 +01:18
172944 2014-12-08 21:20 -01:13 +00:05
176976 2014-12-15 22:07 +00:47 +00:52
Average Time = 21:15
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
The database pattern for peak hashpower optimization (with frequent updates) is the first suggestion I regarded as technically related. And I've seem similar problem in the different accredit field of applications adapted very successfully. A few case examples for the light headed: Heuristics patterns found in antivirus, Weather forecasting, Automated trading system, Traffic control, Abstract game engines such as Chess, etc.
And guess what - they are all have some probabilistic elements.
But I admit not all my suggestions were technically as challenging but instead either opinionated by words alone (like here) or silenced until when attention deemed necessary (I can play that game too).
I hate asking questions with no relevant answers, or otherwise presented with counterexamples that could have their own solution unrelated or twisted into different form of misconceptions, etc. And that brings back if the problem presented was understood in the first place. It's mind-boggling how the same problem presented earlier categorized as nothing is wrong could later acknowledged to had some valid substance or points. Perhaps that mindset should change with different motivation and environment as in Employer-Employee (carrot & stick metaphor) relationship, higher level of recognition for great achievers as self starter, etc.
Don't call yourself a problem solver (very wide definition here) if you can't tie up the loose ends you created in the first place. Nobody likes hear another vapor passing thru or be interpreted as such.
Again for the second time what good is getting new miners when the superblock can't even make the full use hashpower at its peak (nevermind the records breaking)? Would you agree improving the odd of finding record breakers by having hashpower used at least by 95% is better than 35% all the time? Or do you prefer the current 35% level to climb up at steady rate to reach the current 95% level sometime later and then ask yourself why is it records breaking is so technically tough?
There you are - questions.
And guess what - they are all have some probabilistic elements.
But I admit not all my suggestions were technically as challenging but instead either opinionated by words alone (like here) or silenced until when attention deemed necessary (I can play that game too).
I hate asking questions with no relevant answers, or otherwise presented with counterexamples that could have their own solution unrelated or twisted into different form of misconceptions, etc. And that brings back if the problem presented was understood in the first place. It's mind-boggling how the same problem presented earlier categorized as nothing is wrong could later acknowledged to had some valid substance or points. Perhaps that mindset should change with different motivation and environment as in Employer-Employee (carrot & stick metaphor) relationship, higher level of recognition for great achievers as self starter, etc.
Don't call yourself a problem solver (very wide definition here) if you can't tie up the loose ends you created in the first place. Nobody likes hear another vapor passing thru or be interpreted as such.
Again for the second time what good is getting new miners when the superblock can't even make the full use hashpower at its peak (nevermind the records breaking)? Would you agree improving the odd of finding record breakers by having hashpower used at least by 95% is better than 35% all the time? Or do you prefer the current 35% level to climb up at steady rate to reach the current 95% level sometime later and then ask yourself why is it records breaking is so technically tough?
There you are - questions.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
One just needs to wonder how & what sort of parameters were used to estimate the first superblock difficulty before it took off. Had I realized the shortfall of the superblocks timing I'd have warned Gatra but correction is still aplenty. It's just a matter of choice, etc.
The timing is based on block intervals, rather than a set time of day, so the exact time is not set, and will depend on mining power, difficulty adjustement and a bit of random, so day and time will drift over the course of months/years.
First super-block was at 19:50, latest was at 22:07, and we had one at 22:30, so it's not a huge drift, but it's a drift.
So chances are the dry spell will last a few weeks, until we drift to the next peak.
Since superblock helded as weekly event some database peaks pattern (weekly updated for 1 month of data) built into miners would help guides the drift correction, etc.
Just a thought.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Hopefully they reconnected with a new demographic profile that optimises the superblock difficulty for Riecoin. 
Would be nice, but I do not think Riecoin can affect worldwide daylight times... yet
I don't have the big picture what's going on behind the scene. For that it's better for me refrained from asking questions that have adverse implication and responsibility in the Riecoin Project. I won't be pursuing this matter of optimizing the superblock's difficulty over the demographic at ypool any further. I've made my points clear enough.
To be honest it's tiring to see very attempts to make Riecoin Project worthwhile but only stayed in silence. I hope to see at least one of my suggests (2 were publically announced) came to see the light of day.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
My old mining protocol does not work anymore thru
It seems ypool.net is in the process of remaking that come new mining protocol thru
A lot of miners went off due to the new protocol (4696 workers currently). Hopefully they reconnected with a new demographic profile that optimises the superblock difficulty for Riecoin.
Code:
xptMiner.exe -o http://ypool.net -u . -p -t 4
It seems ypool.net is in the process of remaking that come new mining protocol thru
Code:
xptMiner.exe -o http://mining.ypool.net -u . -p -t 4
A lot of miners went off due to the new protocol (4696 workers currently). Hopefully they reconnected with a new demographic profile that optimises the superblock difficulty for Riecoin.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
A difference by 4 digits from the last superblock. Bearing the irony that latest superblock could had mined at the peak of 7176 instead 5565 miners with new world records well into the easy 7XX - 8XX digits range (and beyond).
What's wrong with you Riecoin Project??? C'mon, Christmas just around the corner...
What's wrong with you Riecoin Project??? C'mon, Christmas just around the corner...
It doesn't work exactly like that: the amount of hashing power at the moment of the superblock influences how long does it take to find it, but not how many digits will it have. The quantity of digits (the difficulty) is decided based on the hashing power during the interval prior to the superblock. And since the superblock is in the middle of an interval, its number of digits depends on the number of active miners in the interval of 432 to 144 blocks (expected to be 18hs to 6hs) before the superblock. It's the mining during that 12hs period that defines the superblock's difficulty.
If I understood correctly - A superblock could only defines its difficulty based on past interval of hasing power (as connected miners at ypool's demographic) that ranges from 6hrs to 18hrs (2.5mins per block) before and not the future interval (although I'm confused by And since the superblock is in the middle of an interval). At present the superblock event took place around 21PM-22PM of ypool's demographic (at declining side of a peak) that gives at best 8hrs of positive rising rate and 10hrs of negative declining rate with net 2hrs of negative declining rate (for the prior 18hrs difficulty justification), and at worse 6hrs of negative declining rate (for the prior 6hrs difficulty justification).
Now let suppose then 18hrs prior to a superblock event at 14PM justifies the difficulty computation it required from 20PM of the day before (with only 4hrs of negative declining rate before rising again around 12AM that gave at least 12hrs of positive rising rate). And, 6hrs prior to a superblock event at 14PM to justifies the difficulty computation it required from 8AM of the same day (with zero hours of declining rate and at least 12hrs of positive rising rate).
From the surface it's seem illogical to favor a difficulty computed from the declining side of a peak. Since the hashing power at that instance (around 21PM-22PM) is already dwindle down to handle the superblock's difficulty (computed from 6hrs-18hrs hashing power prior). My point being what good is the superblock's difficulty to already declining hashing power at that instance.
How do the superblock difficulty adapts to the amount of hours during either positive and/or negative rate as it required for the 18hrs and/or 6hrs prior? What justify the reason for not fixing the superblock on the rising side if not at the peak itself (but instead around 21PM-22PM)?
Nothing is wrong! it was kinda expected that after the high of the first record, it would become cold... if the record is broken every week it stops being news after 2 or 3 times...
Anything that's new will definitely made it into news. The idea with Riecoin Project should be staying in the lead of world records and gauging potential competition from various form of technologies (fairness apply here) - makes them staying out of the news.Instead of focusing on superblocks and world records, how about focusing on merchant adoption and distribution to newbies? 
I'm afraid we're not ready for merchant adoption: volume is not that high, and merchants would sell and convert to fiat immediately making the price go down. I see Riecoin as a scientific research project that pays with actual coins (instead of just "fun" like those math projects in BOINC), but it's not yet a currency for everyday use.Distribution to newbies OTOH is something we need right now.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Superblock #176976 found 647 digits (2014-12-15 22:07:33 extracted by YPOOL.net).
2049675983117467479892102276291689838485263409405451636635295756261574588597274 1624199604001904856593538339492575655711764836876497988902096506494862712005577 1001073076212399247778915899148829002194894493157875843313206471389211843746647 1093361425890884866792603840452869848145959924149418863811796391739014567334625 4468807025500916342374215790824639674261397844949764474426098606908204446631466 9368552608964167904307634700658634040884401676643125983915296995876022291980043 9739178962314751486085592362565919713463526209486834857714279668227751438187062 1229430623521002526080479570090126998962100509074981734254552060403594687973627 450022888361297
A difference by 4 digits from the last superblock. Bearing the irony that latest superblock could had mined at the peak of 7176 instead 5565 miners with new world records well into the easy 7XX - 8XX digits range (and beyond).
What's wrong with you Riecoin Project??? C'mon, Christmas just around the corner...
2049675983117467479892102276291689838485263409405451636635295756261574588597274 1624199604001904856593538339492575655711764836876497988902096506494862712005577 1001073076212399247778915899148829002194894493157875843313206471389211843746647 1093361425890884866792603840452869848145959924149418863811796391739014567334625 4468807025500916342374215790824639674261397844949764474426098606908204446631466 9368552608964167904307634700658634040884401676643125983915296995876022291980043 9739178962314751486085592362565919713463526209486834857714279668227751438187062 1229430623521002526080479570090126998962100509074981734254552060403594687973627 450022888361297
A difference by 4 digits from the last superblock. Bearing the irony that latest superblock could had mined at the peak of 7176 instead 5565 miners with new world records well into the easy 7XX - 8XX digits range (and beyond).
What's wrong with you Riecoin Project??? C'mon, Christmas just around the corner...
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Superblock #172944 found 643 digits without glitch about 3 hours ago (2014-12-08 21:20:39 extracted by YPOOL.net).
2501194353229052557234065325048746914306737394727681347553120236609245482522844 6516648216471266956377389009096452758708388136405635904537267227733444054393293 7566502884928590068353069673390946006829565485855809852057441326900138070112914 4230060467843693301013575887009908378890901529110466636251745199927796005572836 9999680135443439152894648631504046975598637835985836954897093372510222387740808 7646182994869664539286659228846846884105555543834366721146937732828943430528358 4850045696280562856838073839094278844293294595053415183071939410792029178217868 6444789316735211988117727405695238346224114000250443793837228794927871957181613 23540861827
But still, much can be said about the timing of superblock to harness the computation power at its peak. At this rate all the subsequent superblocks might as well be overshadowed by the leading Superblock #164880 654 digits found on 2014-11-24 20:28:12
Progress, planning and far sight (with great view) can only be seem from the top...
2501194353229052557234065325048746914306737394727681347553120236609245482522844 6516648216471266956377389009096452758708388136405635904537267227733444054393293 7566502884928590068353069673390946006829565485855809852057441326900138070112914 4230060467843693301013575887009908378890901529110466636251745199927796005572836 9999680135443439152894648631504046975598637835985836954897093372510222387740808 7646182994869664539286659228846846884105555543834366721146937732828943430528358 4850045696280562856838073839094278844293294595053415183071939410792029178217868 6444789316735211988117727405695238346224114000250443793837228794927871957181613 23540861827
But still, much can be said about the timing of superblock to harness the computation power at its peak. At this rate all the subsequent superblocks might as well be overshadowed by the leading Superblock #164880 654 digits found on 2014-11-24 20:28:12
Progress, planning and far sight (with great view) can only be seem from the top...
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Eveything fine here.
Code:
<- getblockchaininfo
->
{
"chain" : "main",
"blocks" : 171827,
"bestblockhash" : "693eae39ed2973f52ba4e6c5d2a9998934edcff7e9cb5f7e4974d2f51640818e",
"difficulty" : 1458.00000000,
"verificationprogress" : 0.99997783,
"chainwork" : "18c86ca8cc88a438f3f6071e8a935"
}
<- getpeerinfo
->
{
"addr" : "217.160.16.83:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907079,
"bytessent" : 4247,
"bytesrecv" : 92286,
"conntime" : 1417905753,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171816,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "54.186.107.237:28333",
"services" : "00000001",
"lastsend" : 1417907081,
"lastrecv" : 1417907078,
"bytessent" : 1848,
"bytesrecv" : 83322,
"conntime" : 1417905859,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "66.235.34.181:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907080,
"bytessent" : 1282,
"bytesrecv" : 77735,
"conntime" : 1417906011,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "92.222.19.210:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417907078,
"bytessent" : 1995,
"bytesrecv" : 78331,
"conntime" : 1417906117,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "24.107.75.17:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907079,
"bytessent" : 473,
"bytesrecv" : 76392,
"conntime" : 1417906267,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "77.92.201.169:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906970,
"bytessent" : 1171,
"bytesrecv" : 75658,
"conntime" : 1417906350,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.79.67.246:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907078,
"bytessent" : 692,
"bytesrecv" : 83206,
"conntime" : 1417906395,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "192.241.218.56:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906971,
"bytessent" : 631,
"bytesrecv" : 3192,
"conntime" : 1417906545,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
}
->
{
"chain" : "main",
"blocks" : 171827,
"bestblockhash" : "693eae39ed2973f52ba4e6c5d2a9998934edcff7e9cb5f7e4974d2f51640818e",
"difficulty" : 1458.00000000,
"verificationprogress" : 0.99997783,
"chainwork" : "18c86ca8cc88a438f3f6071e8a935"
}
<- getpeerinfo
->
{
"addr" : "217.160.16.83:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907079,
"bytessent" : 4247,
"bytesrecv" : 92286,
"conntime" : 1417905753,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171816,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "54.186.107.237:28333",
"services" : "00000001",
"lastsend" : 1417907081,
"lastrecv" : 1417907078,
"bytessent" : 1848,
"bytesrecv" : 83322,
"conntime" : 1417905859,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "66.235.34.181:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907080,
"bytessent" : 1282,
"bytesrecv" : 77735,
"conntime" : 1417906011,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "92.222.19.210:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417907078,
"bytessent" : 1995,
"bytesrecv" : 78331,
"conntime" : 1417906117,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "24.107.75.17:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907079,
"bytessent" : 473,
"bytesrecv" : 76392,
"conntime" : 1417906267,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "77.92.201.169:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906970,
"bytessent" : 1171,
"bytesrecv" : 75658,
"conntime" : 1417906350,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.79.67.246:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907078,
"bytessent" : 692,
"bytesrecv" : 83206,
"conntime" : 1417906395,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "192.241.218.56:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906971,
"bytessent" : 631,
"bytesrecv" : 3192,
"conntime" : 1417906545,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
}
Still doesn't want to sync.
What nodes you use?
Code:
<- getpeerinfo
->
{
"addr" : "169.237.10.147:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958391,
"bytessent" : 6894,
"bytesrecv" : 85965,
"conntime" : 1417955870,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172121,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "92.222.19.210:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958389,
"bytessent" : 3231,
"bytesrecv" : 82767,
"conntime" : 1417956073,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "67.225.172.77:28333",
"services" : "00000001",
"lastsend" : 1417958591,
"lastrecv" : 1417958389,
"bytessent" : 4785,
"bytesrecv" : 99442,
"conntime" : 1417956074,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "71.62.186.166:28333",
"services" : "00000001",
"lastsend" : 1417958389,
"lastrecv" : 1417958590,
"bytessent" : 3425,
"bytesrecv" : 84171,
"conntime" : 1417956119,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "66.235.34.181:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958590,
"bytessent" : 2790,
"bytesrecv" : 81696,
"conntime" : 1417956142,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "213.156.113.59:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958389,
"bytessent" : 4074,
"bytesrecv" : 79847,
"conntime" : 1417956187,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172125,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.79.67.246:28333",
"services" : "00000001",
"lastsend" : 1417958593,
"lastrecv" : 1417958389,
"bytessent" : 3214,
"bytesrecv" : 84164,
"conntime" : 1417956474,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172128,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "2.237.176.215:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958392,
"bytessent" : 4507,
"bytesrecv" : 77521,
"conntime" : 1417956585,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172129,
"banscore" : 0,
"syncnode" : false
}
->
{
"addr" : "169.237.10.147:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958391,
"bytessent" : 6894,
"bytesrecv" : 85965,
"conntime" : 1417955870,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172121,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "92.222.19.210:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958389,
"bytessent" : 3231,
"bytesrecv" : 82767,
"conntime" : 1417956073,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "67.225.172.77:28333",
"services" : "00000001",
"lastsend" : 1417958591,
"lastrecv" : 1417958389,
"bytessent" : 4785,
"bytesrecv" : 99442,
"conntime" : 1417956074,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "71.62.186.166:28333",
"services" : "00000001",
"lastsend" : 1417958389,
"lastrecv" : 1417958590,
"bytessent" : 3425,
"bytesrecv" : 84171,
"conntime" : 1417956119,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "66.235.34.181:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958590,
"bytessent" : 2790,
"bytesrecv" : 81696,
"conntime" : 1417956142,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172124,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "213.156.113.59:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958389,
"bytessent" : 4074,
"bytesrecv" : 79847,
"conntime" : 1417956187,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172125,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.79.67.246:28333",
"services" : "00000001",
"lastsend" : 1417958593,
"lastrecv" : 1417958389,
"bytessent" : 3214,
"bytesrecv" : 84164,
"conntime" : 1417956474,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172128,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "2.237.176.215:28333",
"services" : "00000001",
"lastsend" : 1417958590,
"lastrecv" : 1417958392,
"bytessent" : 4507,
"bytesrecv" : 77521,
"conntime" : 1417956585,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172129,
"banscore" : 0,
"syncnode" : false
}
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Need help guys i can t download die new version of the wallet.
Error:
"Unable to find any mirror information for the "/riecoin 0.10.2/riecoin-0.10.2-win.zip" file. Please select another file."
Anybody has a other mirror for me? Thx
These are the main sources where Riecoin v0.10.2 (Win 32 & 64) can be found:Error:
"Unable to find any mirror information for the "/riecoin 0.10.2/riecoin-0.10.2-win.zip" file. Please select another file."
Anybody has a other mirror for me? Thx
http://sourceforge.net/projects/riecoin/files/riecoin%200.10.2/
https://github.com/riecoin/riecoin
Here's the alternative download link for the same Riecoin v0.10.2 (Win 32 & 64) if neither links above not working for you:
http://www.megafileupload.com/en/file/585759/riecoin-0-10-2-win-zip.html
MD5: B803CA2FCC148E2CFC5177EACF8FC575
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Eveything fine here.
Code:
<- getblockchaininfo
->
{
"chain" : "main",
"blocks" : 171827,
"bestblockhash" : "693eae39ed2973f52ba4e6c5d2a9998934edcff7e9cb5f7e4974d2f51640818e",
"difficulty" : 1458.00000000,
"verificationprogress" : 0.99997783,
"chainwork" : "18c86ca8cc88a438f3f6071e8a935"
}
<- getpeerinfo
->
{
"addr" : "217.160.16.83:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907079,
"bytessent" : 4247,
"bytesrecv" : 92286,
"conntime" : 1417905753,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171816,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "54.186.107.237:28333",
"services" : "00000001",
"lastsend" : 1417907081,
"lastrecv" : 1417907078,
"bytessent" : 1848,
"bytesrecv" : 83322,
"conntime" : 1417905859,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "66.235.34.181:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907080,
"bytessent" : 1282,
"bytesrecv" : 77735,
"conntime" : 1417906011,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "92.222.19.210:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417907078,
"bytessent" : 1995,
"bytesrecv" : 78331,
"conntime" : 1417906117,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "24.107.75.17:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907079,
"bytessent" : 473,
"bytesrecv" : 76392,
"conntime" : 1417906267,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "77.92.201.169:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906970,
"bytessent" : 1171,
"bytesrecv" : 75658,
"conntime" : 1417906350,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.79.67.246:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907078,
"bytessent" : 692,
"bytesrecv" : 83206,
"conntime" : 1417906395,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "192.241.218.56:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906971,
"bytessent" : 631,
"bytesrecv" : 3192,
"conntime" : 1417906545,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
}
->
{
"chain" : "main",
"blocks" : 171827,
"bestblockhash" : "693eae39ed2973f52ba4e6c5d2a9998934edcff7e9cb5f7e4974d2f51640818e",
"difficulty" : 1458.00000000,
"verificationprogress" : 0.99997783,
"chainwork" : "18c86ca8cc88a438f3f6071e8a935"
}
<- getpeerinfo
->
{
"addr" : "217.160.16.83:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907079,
"bytessent" : 4247,
"bytesrecv" : 92286,
"conntime" : 1417905753,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171816,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "54.186.107.237:28333",
"services" : "00000001",
"lastsend" : 1417907081,
"lastrecv" : 1417907078,
"bytessent" : 1848,
"bytesrecv" : 83322,
"conntime" : 1417905859,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "66.235.34.181:28333",
"services" : "00000001",
"lastsend" : 1417906617,
"lastrecv" : 1417907080,
"bytessent" : 1282,
"bytesrecv" : 77735,
"conntime" : 1417906011,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "92.222.19.210:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417907078,
"bytessent" : 1995,
"bytesrecv" : 78331,
"conntime" : 1417906117,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171819,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "24.107.75.17:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907079,
"bytessent" : 473,
"bytesrecv" : 76392,
"conntime" : 1417906267,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "77.92.201.169:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906970,
"bytessent" : 1171,
"bytesrecv" : 75658,
"conntime" : 1417906350,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.79.67.246:28333",
"services" : "00000001",
"lastsend" : 1417907078,
"lastrecv" : 1417907078,
"bytessent" : 692,
"bytesrecv" : 83206,
"conntime" : 1417906395,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "192.241.218.56:28333",
"services" : "00000001",
"lastsend" : 1417907079,
"lastrecv" : 1417906971,
"bytessent" : 631,
"bytesrecv" : 3192,
"conntime" : 1417906545,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 171820,
"banscore" : 0,
"syncnode" : false
}
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
The amount of connected workers at ypool.net seem to peak between 12PM till 14PM. Hopefully the subsequent superblock rounds could coincide at the same peak timing to maximize possibly the largest record found.
Edited on 8th Dec 2014: Or optimised for a twin peaks over the weekend for the amount of connected workers at ypool.net between 8AM till 10AM or 12PM till 14PM, etc.
Edited on 8th Dec 2014: Or optimised for a twin peaks over the weekend for the amount of connected workers at ypool.net between 8AM till 10AM or 12PM till 14PM, etc.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Today's superblock is a second place, larger than our first record, smaller than last week's.
At 634 digits, this is from block 168912:
4671972729725352818122941149688795830368998253362115554837276881802333628717174 2452043367864623979884028668499412434355215700282247944506132121797379678999634 3146807090861190738742454232569941618189864683903326675169723070698409551818937 5221050541980536942301602739009515272908437015818063268988005118929691831130381 6089263962841268113114994000626351312774928523795646387116692243361325227122575 2639027031639590677238235001463520528469525508948854951738662011026294236894785 8319697456420704695819068953811745476317893342760661016016020194198635957129742 0634146813414364677014828568287912158992772479977781891115051345113517828553665 37
Thanks and let's keep them coming!
ps: this one took only 52 minutes
...but we still leading the world records!!!At 634 digits, this is from block 168912:
4671972729725352818122941149688795830368998253362115554837276881802333628717174 2452043367864623979884028668499412434355215700282247944506132121797379678999634 3146807090861190738742454232569941618189864683903326675169723070698409551818937 5221050541980536942301602739009515272908437015818063268988005118929691831130381 6089263962841268113114994000626351312774928523795646387116692243361325227122575 2639027031639590677238235001463520528469525508948854951738662011026294236894785 8319697456420704695819068953811745476317893342760661016016020194198635957129742 0634146813414364677014828568287912158992772479977781891115051345113517828553665 37
Thanks and let's keep them coming!
ps: this one took only 52 minutes
Anyone into future forecasting??? To spice up the general interest in prime sextuplet world records breaking. Let say Riecoin Project would makes at least
Choice A: Riecoin makes at least
Choice B: Riecoin didn't make at least
Choice C: Neither A or B.
The forecasting should be splited into 2 catgories per betting amount less than 50,000 Riecoin and those above it. In total 6 public accumulating Riecoin addresses should be made available for those interested. The winners will be equally divided by ratio of their betting shares in each category final total. An initial total
This is only a proposal to draws in more interest (hopefully new miners) into the Riecoin Project.
Edited on 5th Dec 2014: I've gave some thought into the game rules that could also be coupled with a mechanism of virtual-interest rate to encourage long-term saving by the participants. If the gaming strategy worked it would creates a new dynamic into the project for finding largest world records; and in general affecting its exchange markets in a beneficial way as well.
Edited on 9th Dec 2014: So far only #160848 633 digits and #164880 654 digits were considered making into world records listing with each one larger than the next largest.
"A jade stone is useless before it is processed; He is rich who knows when he has had enough." - Chinese Proverb
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
As expected and a fabulous welcoming news...more!!!
Besides the press releases, I think the Riecoin Project also deserved a certificate from Guinness World Records if it able to maintains the 6-tuples Prime world records breaking momentum for few more rounds, etc. Certainly an eye opener for the masses and the prestigious recognition would puts Riecoin Project into history as largest and most successful distributed computing project of finding prime numbers for research and applied sciences, etc.
Value your coins and be proud of what you all did Riecoin Miners!
Media Enquiries: press@guinnessworldrecords.com
See also:
http://www.guinnessworldrecords.com/set-a-record/record-services-for-corporates/
http://store.guinnessworldrecords.com/product_info.php?products_id=32
https://www.facebook.com/GuinnessWorldRecords
http://vimeo.com/95452783
Besides the press releases, I think the Riecoin Project also deserved a certificate from Guinness World Records if it able to maintains the 6-tuples Prime world records breaking momentum for few more rounds, etc. Certainly an eye opener for the masses and the prestigious recognition would puts Riecoin Project into history as largest and most successful distributed computing project of finding prime numbers for research and applied sciences, etc.
Value your coins and be proud of what you all did Riecoin Miners!
Media Enquiries: press@guinnessworldrecords.com
See also:
http://www.guinnessworldrecords.com/set-a-record/record-services-for-corporates/
http://store.guinnessworldrecords.com/product_info.php?products_id=32
https://www.facebook.com/GuinnessWorldRecords
http://vimeo.com/95452783
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
Can someone post some fresh nodes? Can't connect, even with latest client.
I cant sync the wallet already two days, very very very slow!!!
Above might not be a permanent solution but I hope your problems would be sorted out.
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
please proofread: http://riecoin.org/Press%20release%202014-11-21.pdf
and then watch this: https://www.youtube.com/watch?v=OonDPGwAyfQ
or maybe better, watch the video and then read the press release...
once verified I'll reach the media
and then watch this: https://www.youtube.com/watch?v=OonDPGwAyfQ
or maybe better, watch the video and then read the press release...
once verified I'll reach the media
As layman I think it's appropriately prepared and can be easily understood. Below are just my own personal taste, etc.
Quote
"The calculation took only 70 minutes of its massive distributed computing power,"
"In this context, innovators in the field of cryptography and virtual currencies delved into the concept of systems that could secure their transactions and at the same time doing valuable scientific computations than just hash functions. Riecoin is one such endeavor and it calculates prime sextuplets every 2.5 minutes."
"thus these results are interesting to researchers of number theory and other applied fields."
"In this context, innovators in the field of cryptography and virtual currencies delved into the concept of systems that could secure their transactions and at the same time doing valuable scientific computations than just hash functions. Riecoin is one such endeavor and it calculates prime sextuplets every 2.5 minutes."
"thus these results are interesting to researchers of number theory and other applied fields."