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

[curefrankosflue]

hey, just a question, in case you have time to answer.

how did you manage to compile the Riecoin miner on your Odroid? I have a U3 and have been trying to compile it without luck. I followed the instructions in the github directory:
https://github.com/gatra/fastrie/tree/stratum/xptMiner


Prerequisites:
Ubuntu: sudo apt-get -y install build-essential m4 openssl libssl-dev git libjson0 libjson0-dev libcurl4-openssl-dev wget

Building:
wget http://mirrors.kernel.org/gnu/gmp/gmp-5.1.3.tar.bz2 tar xjvf gmp-5.1.3.tar.bz2 cd gmp-5.1.3 ./configure --enable-cxx make -j4 && sudo make install cd git clone https://github.com/clintar/xptMiner.git cd xptMiner LD_LIBRARY_PATH=/usr/local/lib make -j4 ./xptminer -u username.riecoinworkername -p workerpassword

I'm running Ubuntu 14.04 Lts on the Odroid.

Any help would be greatly appreciated. I'm still new to linux, so the problem might very well be sitting in front of the screen

Thanks for your time.

What was the error? If I had to guess apt-get install libjansson-dev and try again.

Hey nonce-pool, thanks for answering. in case you have time to answer again I would appreciate your help.

I tried what you suggested and managed the miner compile on Ubuntu 14.04. I got an executable xptminer file, although the miner didn't mine.
It got just 0s for all chains and no shares even after some 30 minutes. Of course I triplechecked whether I was mining to the right address and the other syntax was right.

2ch/s: 0.000 3ch/s: 0.000 4ch/s: 0.0000

I switched back to Ubuntu 13.10 as some other things did not work properly and Ubuntu 13.10 has done more or less well so far.
I tried to download and compile the miner there.

All steps went well until the command:
LD_LIBRARY_PATH=/usr/local/lib make -j4

As far as I understand the line LD_LIBRARY_PATH.... compiles the xptMiner to make an executable file.


It compiled many of the source code files but in the end I got the error message:
/usr/bin/ld: cannot find -lcrypto
/usr/bin/ld: cannot find -lssl
collect2: error: ld returned 1 exit status
make: *** [xptminer] Error 1

maybe I am missing some other libraries? or are these missing source code files of the xptminer? as I said I'm a newbie to Linux

Thank you very much for your help.

Michael
ana: curefrankosflue

[1714046675]

1714046675

[1714046675]

1714046675

[1714046675]

1714046675

[1714046675]

1714046675

[1714046675]

1714046675

[cinnamon_carter]

Huge thanks to dga for his work on the miner which I am running and having a bit of fun experimenting with.
Also thanks Gatra for making it all possible by creating Riecoin.

Most people have no idea how much work and costs are involved in coding, testing and creating these things.

[bsunau7]

It compiled many of the source code files but in the end I got the error message:
/usr/bin/ld: cannot find -lcrypto
/usr/bin/ld: cannot find -lssl
collect2: error: ld returned 1 exit status
make: *** [xptminer] Error 1

maybe I am missing some other libraries? or are these missing source code files of the xptminer? as I said I'm a newbie to Linux

Thank you very much for your help.

Michael
ana: curefrankosflue

Try installing libssl-dev if ubuntu 13 does not have it.  As root:

Code:

# apt-get install libssl-dev

Next try setting LD_LIBRARY_PATH before you run xptminer.  It sets the path which the executable will look for it's libraries.  Doing it on the make line sets it for that execution of "make" and not the executable created.

Something like

Code:

# export LD_LIBRARY_PATH=/usr/local/lib
# xptminer

Should work.  The export makes it active for the life of the shell.  There are a few ways to make this "sticky" my preference is to add it into dynamic linker, there are are lots of hits on google for this, search for something like "adding /usr/local/lib to library path" should give you a pretty good start!

Regards,

--
bsunau7

[nonce-pool]

Hey nonce-pool, thanks for answering. in case you have time to answer again I would appreciate your help.

I tried what you suggested and managed the miner compile on Ubuntu 14.04. I got an executable xptminer file, although the miner didn't mine.
It got just 0s for all chains and no shares even after some 30 minutes. Of course I triplechecked whether I was mining to the right address and the other syntax was right.

2ch/s: 0.000 3ch/s: 0.000 4ch/s: 0.0000

I switched back to Ubuntu 13.10 as some other things did not work properly and Ubuntu 13.10 has done more or less well so far.
I tried to download and compile the miner there.

All steps went well until the command:
LD_LIBRARY_PATH=/usr/local/lib make -j4

As far as I understand the line LD_LIBRARY_PATH.... compiles the xptMiner to make an executable file.

It compiled many of the source code files but in the end I got the error message:
/usr/bin/ld: cannot find -lcrypto
/usr/bin/ld: cannot find -lssl
collect2: error: ld returned 1 exit status
make: *** [xptminer] Error 1

maybe I am missing some other libraries? or are these missing source code files of the xptminer? as I said I'm a newbie to Linux

Thank you very much for your help.

Michael
ana: curefrankosflue

Looking back through the bash history, didn't really need to do anything special to get it to work on 14.04, just follow bsunau7 advice for 13.10 and that should get you going.

also adding to your command line when running increases performance considerably (not sure what the best number here is, still trying)

Code:

-s 50000000

[F22Raptor]

i haven't seen this coin for a while,god bless me that this coin isn't dead.i will read posts to decide invest or not

[gatra]

hi!

I tryed the uninitialized variable fix and yes, it now seems to work well under windows. I also made the stratum protocol properly reconnect after losing the connection to the pool.
Source is (under the stratum branch) here: https://github.com/gatra/fastrie

dga: would you please merge this?

thanks and regards,
gatra

[gatra]

Regarding the superblock thing, I think that the easiest would be to force one block (let's say block 122000) to have the desired difficulty and then return to normal. At current rates, I expect it would take about 30 mins (expected time) to solve the world-record block. Less if we are lucky, more if we aren't. This would require everyone to update to the new client but nothing else would need to be changed.
There will be a delay on transactions, but only for less than half an hour. Think of it as "expected downtime". We could make that block have a reward of 600 to accomodate for the extra difficulty.

What do you say?

[The Dark Knight]

Regarding the superblock thing, I think that the easiest would be to force one block (let's say block 122000) to have the desired difficulty and then return to normal. At current rates, I expect it would take about 30 mins (expected time) to solve the world-record block. Less if we are lucky, more if we aren't. This would require everyone to update to the new client but nothing else would need to be changed.
There will be a delay on transactions, but only for less than half an hour. Think of it as "expected downtime". We could make that block have a reward of 600 to accomodate for the extra difficulty.

What do you say?

Great idea in my opinion!

[Ellieo]

At current rates, I expect it would take about 30 mins (expected time) to solve the world-record block.

What do you say?

I don't mind even if it takes a day to find the world-record prime block. The bigger prime the better.

LEAP FORWARD RIECOIN!!!

[dga]

hi!

I tryed the uninitialized variable fix and yes, it now seems to work well under windows. I also made the stratum protocol properly reconnect after losing the connection to the pool.
Source is (under the stratum branch) here: https://github.com/gatra/fastrie

dga: would you please merge this?

thanks and regards,
gatra

Yup.  I'm traveling right now but will try to get this done on Sunday.

[fairglu]

Regarding the superblock thing, I think that the easiest would be to force one block (let's say block 122000) to have the desired difficulty and then return to normal. At current rates, I expect it would take about 30 mins (expected time) to solve the world-record block. Less if we are lucky, more if we aren't. This would require everyone to update to the new client but nothing else would need to be changed.
There will be a delay on transactions, but only for less than half an hour. Think of it as "expected downtime". We could make that block have a reward of 600 to accomodate for the extra difficulty.

What do you say?

Great idea!

Actually, why not go one step forward and have regular world-record superblocks?

Say once a week, first super-block would have minimum world record difficulty (or maybe below, to make sure the stall is reasonnable as expected), then next week, super-block with world record difficulty + a tiny bit, then + 2x tiny bit, etc.

A weekly reasonable "stall" in exchange of weekly world records, exploring the prime frontier, going boldly where no blockchain has gone before.

[esuncloud]

Regarding the superblock thing, I think that the easiest would be to force one block (let's say block 122000) to have the desired difficulty and then return to normal. At current rates, I expect it would take about 30 mins (expected time) to solve the world-record block. Less if we are lucky, more if we aren't. This would require everyone to update to the new client but nothing else would need to be changed.
There will be a delay on transactions, but only for less than half an hour. Think of it as "expected downtime". We could make that block have a reward of 600 to accomodate for the extra difficulty.

What do you say?

I am surprised that it will only take 30 mins to solve the world-record block. It is absolutely worthy to do a hard fork for this idea.

[bsunau7]

Hi,

Another 5% from making sieve2 code ~30% smaller and starting to optimize memory access (pre-fetching).  Once again to see this improvement you'll need to increase the sieve size (-m).  I am running it at 15million which means I am sieving against the first 970k primes.

Link is, as always; https://mega.co.nz/#F!6Y8ywRoZ!5ogMJEc2Teq5ckt9WClNpg

Note:  This runs the chip hot, very hot.  The CPU is sitting on 94-104c (thermal throttles at 104c) even with a heat sink and a 12v noctua fan.  Stock systems will probably clock right down to save themselves (and thus give bad performance).

I do like the idea of a monthly super block, so much so I am considering putting a bounty of the first super block not mined by a pool.

Regards,

--
bsunau7

[northranger79510]

Keep up good work Gatra!

[aamarket]

Everybody's so excited about 'superblock' - so I try to be a bit negativist.

I really doubt 30 minutes for record breaking 6tuple, the Riecoin network diff was more than 1700 ( I guess ), now it is less than 1450.
Please bear in mind it is exponentially difficult to find 6tuplets with higher diff ( I posted some rough estimation before ).

Is the network 'slowdown' for (possibly much more than) 30 minutes - and the need for everybody to update his clients -
 really worth the risk of 'hard fork' problems ?

Do you have any math support for "30 minutes time to find superblock" other than "At current rates, I expect it would take about 30 mins" ?

I like Riecoin, and I wish all the best to it.

[gatra]

Everybody's so excited about 'superblock' - so I try to be a bit negativist.

I really doubt 30 minutes for record breaking 6tuple, the Riecoin network diff was more than 1700 ( I guess ), now it is less than 1450.
Please bear in mind it is exponentially difficult to find 6tuplets with higher diff ( I posted some rough estimation before ).

Is the network 'slowdown' for (possibly much more than) 30 minutes - and the need for everybody to update his clients -
 really worth the risk of 'hard fork' problems ?

Do you have any math support for "30 minutes time to find superblock" other than "At current rates, I expect it would take about 30 mins" ?

I like Riecoin, and I wish all the best to it.

Sure! there's always math to be had when it comes to ric.
The assumption is that the difficulty raised to the ninth power is linear (6 because according to Hardy-Littlewood's k tuple conjecture the average space between 6 tuples is O(log^6 p), and 3 because testing for primality takes about O(log^3 p), so 6+3=9). This has been working nicely: the average time between blocks is about the expected 150 seconds, which means the assumption is working so far.

Current diff is 1441, but we want a block with 1857. So (1857/1441)^9 = 9.8 times harder. If we now have 2.5 minutes then 9.8 times harder would take 24.5 minutes (24.5 in average! it should be between 18.5 and 32 mins with 90% confidence, we have about 5% chance of it being more than 32 minutes and 0.2% of it taking more than an hour - this is calculated assuming we are following a Poisson process).
When difficulty was 1700, it would have been 1.7 times harder, meaning that choosing a block interval target of 5 minutes instead of 2.5 would have made us break the record a couple of months ago.

[fairglu]

When difficulty was 1700, it would have been 1.7 times harder, meaning that choosing a block interval target of 5 minutes instead of 2.5 would have made us break the record a couple of months ago.

Interesting side-effect of the block interval.

Diff 1857 is close enough to the ATH to probably not enter truly uncharted territory.

What about the proposal of weekly/monthly superblocks of ever-increasing difficulty?

Higher risk of stall in the long term, but some opportunity to test less-complex superblocks first with the current network hashrate.

Is the network 'slowdown' for (possibly much more than) 30 minutes - and the need for everybody to update his clients -
 really worth the risk of 'hard fork' problems ?

TBH the network isn't terribly busy, especially once you filter-out the yPool payouts (check the explorer), and during the superblock, yPool wouldn't have to issue payouts, so the stall shouldn't be too problematic in itself.

The hard fork risks should also be limited given there are few pools to be notified (and yPool is dominating).

Question is, which exchange has the dominating exchange wallet? they would have to be notified, and seem to be neither poloniEx nor Mintpal.

Almost 50% of the network is on 0.8.x versions though, according to the sample seen by the explorer, they would have to update, that can be seen as both a bad or a good thing.

[gatra]

Diff 1857 is close enough to the ATH to probably not enter truly uncharted territory.

What about the proposal of weekly/monthly superblocks of ever-increasing difficulty?

I'm leaning towards a 30min block once a week. With current difficulty this would get us slightly above world record. If difficulty increases, the goal of the weekly superblock would increase too, going farther where no man has gone before.

Question is, which exchange has the dominating exchange wallet? they would have to be notified, and seem to be neither poloniEx nor Mintpal.

If it's not poloniex nor mintpal my guess is that it's btc38, but how could we really know?

Almost 50% of the network is on 0.8.x versions though, according to the sample seen by the explorer, they would have to update, that can be seen as both a bad or a good thing.

I'd give a couple of weeks for everyone to update and use the built-in alert system to let everyone know.

I hate it that we still have one pool dominating, however it does make hard-forking easier and I'm thankful that it's ypool because it's behaving really well.

[esuncloud]

Diff 1857 is close enough to the ATH to probably not enter truly uncharted territory.

What about the proposal of weekly/monthly superblocks of ever-increasing difficulty?

I'm leaning towards a 30min block once a week. With current difficulty this would get us slightly above world record. If difficulty increases, the goal of the weekly superblock would increase too, going farther where no man has gone before.

Question is, which exchange has the dominating exchange wallet? they would have to be notified, and seem to be neither poloniEx nor Mintpal.

If it's not poloniex nor mintpal my guess is that it's btc38, but how could we really know?

Almost 50% of the network is on 0.8.x versions though, according to the sample seen by the explorer, they would have to update, that can be seen as both a bad or a good thing.

I'd give a couple of weeks for everyone to update and use the built-in alert system to let everyone know.

I hate it that we still have one pool dominating, however it does make hard-forking easier and I'm thankful that it's ypool because it's behaving really well.

According to http://api.riecoin.org/minted.php, the total Riecoin is 6022200.
Meanwhile, the cold wallet of btc38 riecoin is public as RUrTHyyKiPr1SkAraTHvSY9d3vsdQHBjca, which has 3487644.
Therefore, we know that more than 50% of Riecoins are sitting in btc38.

[vidarn]

I believe you guys are making your estimates based on an old world record.
The 1857 difficulty corresponds to a 559 digits 6-tuplet found in 2009. The present record, according to Tony Forbes, is 593 digits or a difficulty of about 1970. The record 6-tuplet is

219946485329 * 1399# / 2 + d, d = −8, −4, −2, 2, 4, 8, found by Serge Batalov in December 2013.

Tony Forbes' k-tuplet page may be found here:

http://anthony.d.forbes.googlepages.com/ktuplets.htm

But as (1973/1441)^9 = 16.9 using gatra's estimates, we should be able to beat the record with an extra digit within an hour or so. The Primecoin lot have broken quite a few world records, it would be nice if we could get some too.