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

[gatra]

Hi people! the update is ready! This is a mandatory update because of a hard fork required for the new superblock feature.

Please update to v0.10.2 before Nov 8th.
Sources are in github (github.com/riecoin/riecoin) and binaries in sourceforge (https://sourceforge.net/projects/riecoin/files/riecoin%200.10.2/).
Block 156672 will be the first one that breaks the old protocol, and 156816 will be the first superblock.
From then on, superblocks every 4032 blocks (one week).

[1550365248]

1550365248

[1550365248]

1550365248

[1550365248]

1550365248

[1550365248]

1550365248

[gatra]

yay! the alert system works! I just broadcasted and alert.

[Ellieo]

Yayyyyyyy....SUPERBLOCKS IS COMING!!!

[fairglu]

Explorer daemon updated!

Apparently already a third of the network seems to have already updated

https://chainz.cryptoid.info/ric/#!network

[bsunau7]

I just need to wrap to the next page and put those animations behind me!

[bsunau7]

I just need to wrap to the next page and put those animations behind me!

And this should do it!

Regards,

--
bsunau7

[fairglu]

yay! the alert system works! I just broadcasted and alert.

Hmmm, I'm on 10.2 and still seeing the alert is it normal?

Code:

{
    "version" : 100200,
    "protocolversion" : 10070001,
    "walletversion" : 60000,
    ...
    "errors" : "URGENT: upcoming hardfork. Update to v0.10.2 before Nov 8, 2014"
}

[gatra]

yay! the alert system works! I just broadcasted and alert.

Hmmm, I'm on 10.2 and still seeing the alert is it normal?

Code:

{
    "version" : 100200,
    "protocolversion" : 10070001,
    "walletversion" : 60000,
    ...
    "errors" : "URGENT: upcoming hardfork. Update to v0.10.2 before Nov 8, 2014"
}

oops, yes, I made the alert general and not specific to versions prior to v0.10.2
I guess I should cancel it and generate another one

[gatra]

hard fork featured here: http://www.satoshis.guru/riecoin-planed-hard-fork-superblocks/

[fairglu]

oops, yes, I made the alert general and not specific to versions prior to v0.10.2
I guess I should cancel it and generate another one

Good testing for the alert system then

I've reflected the alert on the explorer home page, but this makes me wonder if there could not be two "errors" message instead of one.

* errors: would be same as current, specific alert updates, problems with the daemon, etc.
* alerts: would hold general alert messages/messages, not specific to your daemon.

The alerts could be reflected in the explorers and websites, and be a way for the dev ( you ) to push news in a widespread fashion.

[gatra]

oops, yes, I made the alert general and not specific to versions prior to v0.10.2
I guess I should cancel it and generate another one

Good testing for the alert system then

I've reflected the alert on the explorer home page, but this makes me wonder if there could not be two "errors" message instead of one.

* errors: would be same as current, specific alert updates, problems with the daemon, etc.
* alerts: would hold general alert messages/messages, not specific to your daemon.

The alerts could be reflected in the explorers and websites, and be a way for the dev ( you ) to push news in a widespread fashion.

I think the priority field of the alerts is made for this purpose. It's odd that the getinfo rpc shows them as "errors" instead of "alerts", but alerts can have a start and an end time, a priority, and can be made to target specific client versions or general.
So, a low priority, general alert, could be used to push news... but for not important messages twitter is just more user friendly

[gatra]

I forgot to mention that there can be more than one active alert at any given time, but only the one with highest priority is displayed in the status bar of the QT client and shown in the getinfo rpc.

And of course, thanks for updating the chain explorer. There's one more feature we'll all want: the records! showing the largest primes so far!
I'll see if I can make a quick implementation inside the client, so you could just query it.

Thank you,
Gatra

[fairglu]

So, a low priority, general alert, could be used to push news... but for not important messages twitter is just more user friendly

Twitter messages fossilize way too fast however, unless you go to profile pages (which takes a lot of time), twitter messages are usually buried in a matter of minutes, regardless of their importance (tweets about the latest TV shows top the re-tweets charts, real news never does).
Having something more focused could be useful.

There's one more feature we'll all want: the records! showing the largest primes so far!
I'll see if I can make a quick implementation inside the client, so you could just query it.

Will super-block report a higher than normal difficulty?
If so, I could find the record-breaking blocks directly this way

[gatra]

There's one more feature we'll all want: the records! showing the largest primes so far!
I'll see if I can make a quick implementation inside the client, so you could just query it.

Will super-block report a higher than normal difficulty?
If so, I could find the record-breaking blocks directly this way

Yes, the superblocks will have higher difficulty and the record holder would have the highest, however if more than one of them share the same top difficulty you'll have to decide by comparing the value of the hash of the block's header (in the bit order that is used to generate the base prime), or just compare the base prime for those.

[fairglu]

Yes, the superblocks will have higher difficulty and the record holder would have the highest, however if more than one of them share the same top difficulty you'll have to decide by comparing the value of the hash of the block's header (in the bit order that is used to generate the base prime), or just compare the base prime for those.

Ok, that should work directly then, I cache the primes in the explorer db, so it should just be a matter of sorting.

Beta version: https://chainz.cryptoid.info/ric/halloffame.dws

Will probably need to tweak stuff once the first super-block happens

Speaking of which, maybe just having the blockheight of the next super-block in the RPC getinfo API could be nice for a count-down.
I could hard-code it in the explorer, but this would be more fragile, and it could be nice to show the countdown in the Qt client as well.

[fairglu]

Hmmm, something seems wrong, blockchain is stuck on 153640

And yPool stats reports 153640 being found by many times 

[jh00]

Hmmm, something seems wrong, blockchain is stuck on 153640

And yPool stats reports 153640 being found by many times  

I have fixed the problem but I am not exactly sure what has caused it. Still looking into it.

Edit: Most likely an error in the pool and not a bug in Riecoin's code.

[hashes4.me]

But weird thing is, that my wallet didn't sync any further and the blockexplorers too.
Let's hope it doesn't happen again

[atro]

But weird thing is, that my wallet didn't sync any further and the blockexplorers too.
Let's hope it doesn't happen again

I noticed the same thing. My wallet was not synced for nearly 14 hours but my miner kept running and submitting shares. I watched both the miner and my wallet move on to the next block at nearly the same time.

[Ellieo]

Both my wallet and miner are working fine.