[ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 122.

Ellieo

member

Activity: 60

Merit: 10

Quote from: fairglu on December 17, 2014, 03:27:50 AM

Quote from: Ellieo on December 17, 2014, 02:41:59 AM

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.

The peaks don't drfit. Suffice to said the current superblock made a poor navigator (more stationary than dynamic motion) towards the peaks as its reference. As casues of the blocks drift versus their standard timing were the factors stated then there should be some algorithm placed (perhaps a self correcting drift) to pinpoint the correct timing for superblock at the peak of hashing power.

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.

fairglu

legendary

Activity: 1100

Merit: 1032

Quote from: Ellieo on December 17, 2014, 02:41:59 AM

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.

Ellieo

member

Activity: 60

Merit: 10

Quote from: fairglu on December 17, 2014, 02:20:45 AM

Quote from: Ellieo on December 17, 2014, 01:18:49 AM

Hopefully they reconnected with a new demographic profile that optimises the superblock difficulty for Riecoin. Grin

Would be nice, but I do not think Riecoin can affect worldwide daylight times... yet

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.

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.

fairglu

legendary

Activity: 1100

Merit: 1032

Quote from: Ellieo on December 17, 2014, 01:18:49 AM

Hopefully they reconnected with a new demographic profile that optimises the superblock difficulty for Riecoin. Grin

Would be nice, but I do not think Riecoin can affect worldwide daylight times... yet

Ellieo

member

Activity: 60

Merit: 10

My old mining protocol does not work anymore thru

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. Grin

Ellieo

member

Activity: 60

Merit: 10

Quote from: gatra on December 16, 2014, 07:58:34 AM

Quote from: Ellieo on December 15, 2014, 07:14:37 PM

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... Roll Eyes

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.

The Riecoin miners demographic at ypool is very much predictable (with 24/7 pattern of single & twin peaks). There's a 24hrs cycle instance that miners seem to rises from 00AM-2AM to 12PM-14PM and then started to decline there onwards; and the cycle repeats (exception for twin-peak over the weekend). As the peak of miners increases (or decreases) for each different cycle so do too the rising and declining rates (for each side of a peak) over the same fixed time period.

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)?

Quote from: gatra on December 16, 2014, 07:58:34 AM

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.

Quote from: gatra on December 16, 2014, 07:58:34 AM

Quote from: eule on December 16, 2014, 06:58:56 AM

Instead of focusing on superblocks and world records, how about focusing on merchant adoption and distribution to newbies? Tongue

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.

The not yet a currency (or utility) for everyday use has to start soon or later.

eule

hero member

Activity: 756

Merit: 501

Glad you like it! I planned to do something like this for dogecoin, but since I also own a few RIC, why not both?

gatra

hero member

Activity: 583

Merit: 505

CTO @ Flixxo, Riecoin dev

Quote from: eule on December 16, 2014, 08:28:55 AM

Fair points. Cheesy

My idea: a site that lets reddit users redeem their karma for riecoins. Same could be done for bitcointalk/riecointalk too, more activity = more coins. Grin

nice! much better and more effective than a faucet! but they have to mention Riecoin on their posts, otherwise it's not advertising... I'll think about it

gatra

hero member

Activity: 583

Merit: 505

CTO @ Flixxo, Riecoin dev

Quote from: fairglu on December 16, 2014, 08:55:56 AM

No longer flat-lined!

What is this?

The rewards mini-chart in the explorer inflation chart for Riecoin!
It used to be flat and utterly boring, and is now starting to show some "beat", thanks to the super-blocks.

beautiful!

fairglu

legendary

Activity: 1100

Merit: 1032

No longer flat-lined!

What is this?

The rewards mini-chart in the explorer inflation chart for Riecoin!
It used to be flat and utterly boring, and is now starting to show some "beat", thanks to the super-blocks.

eule

hero member

Activity: 756

Merit: 501

Fair points. Cheesy

My idea: a site that lets reddit users redeem their karma for riecoins. Same could be done for bitcointalk/riecointalk too, more activity = more coins. Grin

gatra

hero member

Activity: 583

Merit: 505

CTO @ Flixxo, Riecoin dev

Quote from: Ellieo on December 15, 2014, 07:14:37 PM

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... Roll Eyes

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.

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...

Quote from: eule on December 16, 2014, 06:58:56 AM

Instead of focusing on superblocks and world records, how about focusing on merchant adoption and distribution to newbies? Tongue

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.

eule

hero member

Activity: 756

Merit: 501

Instead of focusing on superblocks and world records, how about focusing on merchant adoption and distribution to newbies? Tongue

Ellieo

member

Activity: 60

Merit: 10

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... Roll Eyes

Ellieo

member

Activity: 60

Merit: 10

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...

gavrilo77

hero member

Activity: 819

Merit: 502

Quote from: Ellieo on December 07, 2014, 08:45:21 AM

Quote from: gavrilo77 on December 07, 2014, 08:27:43 AM

Quote from: Ellieo on December 06, 2014, 06:12:24 PM

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
}

Still doesn't want to sync.
What nodes you use?

Didn't add any extra nodes since I updated my wallet and nor did it ever failed to sync. Those you see from getpeerinfo should be the nodes my wallet registered with currently (oddly some were not in your list). And the latest getpeerinfo I got are

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
}

Still doesn't work. have no idea.

My getpeerinfo:

16:32:24

getpeerinfo

16:32:24

[
{
"addr" : "169.237.10.147:28333",
"addrlocal" : "77.46.171.24:28333",
"services" : "00000001",
"lastsend" : 1417966249,
"lastrecv" : 1417966340,
"bytessent" : 229,
"bytesrecv" : 75558,
"conntime" : 1417966243,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172184,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.160.16.83:28333",
"addrlocal" : "77.46.171.24:28333",
"services" : "00000001",
"lastsend" : 1417966332,
"lastrecv" : 1417966333,
"bytessent" : 1340,
"bytesrecv" : 94234,
"conntime" : 1417966244,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172184,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "183.97.21.146:28333",
"services" : "00000001",
"lastsend" : 1417966254,
"lastrecv" : 1417966334,
"bytessent" : 229,
"bytesrecv" : 75608,
"conntime" : 1417966252,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172184,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "217.233.85.41:28333",
"services" : "00000001",
"lastsend" : 1417966332,
"lastrecv" : 1417966333,
"bytessent" : 351,
"bytesrecv" : 76083,
"conntime" : 1417966253,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172184,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "67.225.172.77:28333",
"services" : "00000001",
"lastsend" : 1417966332,
"lastrecv" : 1417966333,
"bytessent" : 412,
"bytesrecv" : 76296,
"conntime" : 1417966283,
"pingtime" : 0.00000000,
"version" : 10070001,
"subver" : "/Satoshi:0.10.2/",
"inbound" : false,
"startingheight" : 172184,
"banscore" : 0,
"syncnode" : false
}
]

Ellieo

member

Activity: 60

Merit: 10

Quote from: gavrilo77 on December 07, 2014, 08:27:43 AM

Quote from: Ellieo on December 06, 2014, 06:12:24 PM

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
}

Still doesn't want to sync.
What nodes you use?

Didn't add any extra nodes since I updated my wallet and nor did it ever failed to sync. Those you see from getpeerinfo should be the nodes my wallet registered with currently (oddly some were not in your list). And the latest getpeerinfo I got are

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
}

gavrilo77

hero member

Activity: 819

Merit: 502

Quote from: Ellieo on December 06, 2014, 06:12:24 PM

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
}

Still doesn't want to sync.
What nodes you use?

Ellieo

member

Activity: 60

Merit: 10

Quote from: TheMaster1337 on December 07, 2014, 06:53:38 AM

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:
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

TheMaster1337

newbie

Activity: 37

Merit: 0

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

Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 122. (Read 685207 times)

Topic: [ANN][RIC] Riecoin: constellations POW CPU HARD FORK successful, world record - page 122. (Read 685207 times)