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

[PttnMe]

Now, rieMiner 0.9β1.5 (2018-09-15) drops GetWork support and proposes a better Standard Benchmark. I will publish some results soon.

Hi PttnMe,
Right now I am testing your miner using fx8350, 32GB of RAM and W7 64bits trying solo mining with these rieMiner.conf settings:

Host = 127.0.0.1;
Port = 28332;
User = (my wallet address);
Pass = (my password);
Protocol = GetBlockTemplate;
Address =  (my wallet address);
Tuples = 6;
Threads = 8;
Sieve = 4073741824; (because why not?   )
Refresh = 30;

Miner works fine, trashing my CPU   at full speed, but still, I am unable to switch into GetBlockTemplate Protocol. (Benchmark only). Any idea how to turn it on?

Remove the ; at the end of each line.
Normally, rieMiner told you "Invalid Protocol", and the Benchmark Mode is the default "Protocol".

[1713979731]

1713979731

[xandry]

One standalone binary for Windows 64 bits is provided for rieMiner 0.9β1, but was not much tested. It should work on Core 2 Duo computers and higher. I even got it working on Wine! You can download it in the rieMiner GitHub release page.

How can i setup it to riepool.ovh?

[PttnMe]

I just published some rieMiner Benchmark results here, so people can compare and have an idea of mining speeds. Do not hesitate to benchmark and submit your result too. Be sure to use the Standard or Easy Benchmark parameters.

One standalone binary for Windows 64 bits is provided for rieMiner 0.9β1, but was not much tested. It should work on Core 2 Duo computers and higher. I even got it working on Wine! You can download it in the rieMiner GitHub release page.

How can i setup it to riepool.ovh?

Create a rieMiner.conf file next to the executable containing:

Code:

Host     = riepool.ovh
Port     = 8000
User     = User.Worker
Pass     = Password
Protocol = Stratum
Threads  = 8

Change User, Pass, and Threads fields to what they should be. Read the README.md file in the source code/project's page for more options.

For XPoolX:

Code:

Host     = mining.xpoolx.com
Port     = 5000
User     = User.Worker
Pass     = Password
Protocol = Stratum
Threads  = 8

For uBlock.it:

Code:

Host     = mine.ublock.it
Port     = 5000
User     = User.Worker
Pass     = Password
Protocol = Stratum
Threads  = 8

For solo mining (change Host and Port if needed, and set the User, Pass, Address, and Threads to what they should be):

Code:

Host     = 127.0.0.1
Port     = 28332
User     = 
Pass     = 
Protocol = GetBlockTemplate
Address  = 
Threads  = 8

[xandry]

Create a rieMiner.conf file next to the executable containing:

Code:

Host     = riepool.ovh
Port     = 8000
User     = User.Worker
Pass     = Password
Protocol = Stratum
Threads  = 8

All options is ignoring as ill formed configuration line. Screenshot:

[millepag]

I've had rieMiner 0.9β1 running on uBlock for about 12 hours now, and it seems to be working just fine

[PttnMe]

All options is ignoring as ill formed configuration line.

The syntax for each line is and only is

Code:

Key = Value

Not

Code:

Key: Value

or whatever else. No :, no ;. just a = between the key and the value. Just do a simple copy paste and replace the values.

I've had rieMiner 0.9β1 running on uBlock for about 12 hours now, and it seems to be working just fine

Thank you for the feedback !

[PttnMe]

New bêta release, rieMiner 0.9β2 (2018-09-16) - Drops GetWork support, adds an assistant to configure rieMiner without rieMiner.conf.

One standalone binary for Windows 64 bits is included. It should work on Windows 7+ with Core 2 Duo or more recent, and you can download it in the rieMiner GitHub release page.

Official binaries will always include a developer fee of 2% for solo mining, which is very reasonable, as solo mining pools are usually taking about 5% of fees. You can remove it by compiling yourself the program.

I hope that you were able to configure rieMiner to mine, xandry. Else, try rieMiner 0.9β2 with its assistant doing the work for you.

Edit: clo1, I found my first block submitted via Riecoin 0.16. But it was not accepted in the network. I am not sure what happened. The block that I found was 953518.
Why did the wallet redownload the 953517 and discarded my 953518? Was I just very unlucky finding an orphan? But in this case, why does this happens if the real 953518 was found only 4 minutes later? I am pretty sure that my connection is fine...

By some chance I also found 953521 and 953528, which were accepted, but they were submitted to the old 0.10.2 wallet.

Code:

2018-09-16 22:22:47 UpdateTip: new best=153151906342817a46aec18c3211f5c4d14dd24f78685e5865c09d6908cf70ce height=953516 version=0x00000002 work=000000000000000000000000000000000009605b03a157e499602ddc3398e9a7 tx=2252145 date='2018-09-16 22:21:46' progress=0.999998 cache=0.3MiB(2223txo)
2018-09-16 22:22:47 CreateNewBlock(): block weight: 904 txs: 0 fees: 0 sigops 400
2018-09-16 22:24:23 UpdateTip: new best=621eba06c9047e2931b330c94a45a1b3041772c67f54255c714ab3940f5d1ac9 height=953517 version=0x00000002 work=000000000000000000000000000000000009605b47b0336dcee2055c9d991dc2 tx=2252146 date='2018-09-16 22:23:56' progress=0.999999 cache=0.3MiB(2224txo)
2018-09-16 22:24:23 CreateNewBlock(): block weight: 904 txs: 0 fees: 0 sigops 400
2018-09-16 22:25:08 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:25:08 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:25:20 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:25:20 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:25:55 UpdateTip: new best=4a9ad3dc47ca6e61485f6ad506ec33df54a6eeb7288ed983a1cf7cdeed50482f height=953518 version=0x20000000 work=000000000000000000000000000000000009605b8bbf0ef70463dcdd079951dd tx=2252147 date='2018-09-16 22:25:44' progress=1.000000 cache=0.3MiB(2225txo)
2018-09-16 22:25:55 CreateNewBlock(): block weight: 904 txs: 0 fees: 0 sigops 400
2018-09-16 22:27:55 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:27:55 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:27:57 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:27:57 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:28:04 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:28:04 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:29:35 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:29:35 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:29:44 UpdateTip: new best=621eba06c9047e2931b330c94a45a1b3041772c67f54255c714ab3940f5d1ac9 height=953517 version=0x00000002 work=000000000000000000000000000000000009605b47b0336dcee2055c9d991dc2 tx=2252146 date='2018-09-16 22:23:56' progress=0.999991 cache=0.3MiB(2225txo)
2018-09-16 22:29:45 UpdateTip: new best=be664dc86be5020b72e380940419fe0cfefa4b0c569182f515a2080d4675ca36 height=953518 version=0x00000002 work=000000000000000000000000000000000009605b8bbf0ef70463dcdd079951dd tx=2252147 date='2018-09-16 22:25:05' progress=0.999993 cache=0.3MiB(2227txo)
2018-09-16 22:29:45 UpdateTip: new best=3ee54168430c3e73efbf61fda5fae56567bc35cdb1db72cde83fb3e429aa516b height=953519 version=0x00000002 work=000000000000000000000000000000000009605bcfcdea8039e5b45d719985f8 tx=2252149 date='2018-09-16 22:30:38' progress=1.000001 cache=0.3MiB(2231txo)
2018-09-16 22:29:45 CreateNewBlock(): block weight: 904 txs: 0 fees: 0 sigops 400
2018-09-16 22:30:36 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:30:36 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:30:38 UpdateTip: new best=53b48f01c56c28e84872992c571b300b267a8a62c256c7ae19f34e13369c049d height=953520 version=0x00000002 work=000000000000000000000000000000000009605c13dcc6096f678bdddb99ba13 tx=2252150 date='2018-09-16 22:29:45' progress=0.999999 cache=0.3MiB(2233txo)
2018-09-16 22:30:39 CreateNewBlock(): block weight: 904 txs: 0 fees: 0 sigops 400
2018-09-16 22:31:18 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:31:18 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:31:58 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:31:58 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:32:31 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:32:31 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:32:46 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:32:47 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:33:43 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:33:43 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:34:46 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:34:46 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:34:58 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:34:58 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:35:01 UpdateTip: new best=144348ecbcd975c5cbd43c7b42d24cc3c62283ec65bfb21ad101b25902399fd5 height=953521 version=0x00000002 work=000000000000000000000000000000000009605c57eba192a4e9635e4599ee2e tx=2252151 date='2018-09-16 22:34:42' progress=1.000000 cache=0.3MiB(2234txo)
2018-09-16 22:35:02 CreateNewBlock(): block weight: 904 txs: 0 fees: 0 sigops 400
2018-09-16 22:35:36 ERROR: CheckProofOfWork() : n+12 not prime
2018-09-16 22:35:36 ERROR: ProcessNewBlock: AcceptBlock FAILED (proof of work failed)
2018-09-16 22:35:58 UpdateTip: new best=12af672fdcaae93d10a295b827885ab7697648d7ff484a34efb649b240501c67 height=953522 version=0x00000002 work=000000000000000000000000000000000009605c9bfa7d1bda6b3adeaf9a2249 tx=2252152 date='2018-09-16 22:35:29' progress=0.999999 cache=0.3MiB(2235txo)

[xandry]

I hope that you were able to configure rieMiner to mine, xandry. Else, try rieMiner 0.9β2 with its assistant doing the work for you.

Yep, thank you. Did you compare performance between your miner and xptminer?

[PttnMe]

Great!

There is no performance change as they use the same algorithm. I tested both in pooled mining and got the same results (note that the find rates in xptMiner needs to be divided by 4.096). I hope that the new features, interface, and modernization that rieMiner proposes would still justify the xptMiner replacement for most miners.

The code is also much easier to work for people willing to improve the algorithm.

And about the block that was not accepted, I will assume that it was an orphan anyway... Block 953811 was this time submitted without any issue via the Riecoin Core 0.16.

[PttnMe]

Finally I can post again! I wonder what happened...

As a serious bug was discovered in Bitcoin Core, we should upgrade to Riecoin 0.16.3 as well and not just 0.16.0.

Any news about the upgrade, clo1? We have not seen you since a while.

While we are at it, where is gatra? He did not appear since August 6! So like some people mentioned in the community forum, I am a bit worried whether he even remembers about it...

[cryptapus]

Finally I can post again! I wonder what happened...

As a serious bug was discovered in Bitcoin Core, we should upgrade to Riecoin 0.16.3 as well and not just 0.16.0.

Any news about the upgrade, clo1? We have not seen you since a while.

While we are at it, where is gatra? He did not appear since August 6! So like some people mentioned in the community forum, I am a bit worried whether he even remembers about it...

I have staged a merge of 0.16.3 into this repo:

https://github.com/riecointeam/riecoin/pulls

I hadn't merged it yet as I don't know where clo1 is in the process of bringing changes in. But it's ready at least.

[clo1]

I have staged a merge of 0.16.3 into this repo:

https://github.com/riecointeam/riecoin/pulls

I hadn't merged it yet as I don't know where clo1 is in the process of bringing changes in. But it's ready at least.

I approved the pull request. I started working on bringing in the changes but have only gotten through the build system and name changes. I'm hoping to get through the rest of the changes in the next few days so hopefully next week we will have a 0.16.3 version.

[lzknr]

First I need to apologize. I thought I could start working on Riecoin this summer but I only become available recently. Good news is that I can commit the next month on this project full time.

It seems that multiple people are working on this and made great progress in the past month. I will be happy to help on any smaller issues (testing/translation/whatever) or future developments (android wallet?)

[PttnMe]

Great everyone, thank you. So now the repository is https://github.com/riecointeam/riecoin , and the https://github.com/clo-prime/riecoin-0.16 one is dropped?

lzknr, one possibility for you could be to look at some thin wallets (like Electrum) and fork one for Riecoin. Indeed, having a Riecoin Core update is nice, but for mainstream adoption, we need something very simple that can be used instantly out of the box (i. e. without having to download the blockchain,...). And sure, an Android wallet is a must have. If you are willing to do so, it will be a very nice contribution for Riecoin.

[lzknr]

Great everyone, thank you. So now the repository is https://github.com/riecointeam/riecoin , and the https://github.com/clo-prime/riecoin-0.16 one is dropped?

lzknr, one possibility for you could be to look at some thin wallets (like Electrum) and fork one for Riecoin. Indeed, having a Riecoin Core update is nice, but for mainstream adoption, we need something very simple that can be used instantly out of the box (i. e. without having to download the blockchain,...). And sure, an Android wallet is a must have. If you are willing to do so, it will be a very nice contribution for Riecoin.

I don't see any new code in https://github.com/riecointeam/riecoin, the branch master is bitcoin; the branch master-ric has last commit May 2014.

I assume https://github.com/clo-prime/riecoin-0.16 is the latest we have? But I got errors when "make". I use ubuntu 18.04

./bignum.h: In function ‘bool operator>(const CBigNum&, const CBigNum&)’:
./bignum.h:658:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator>(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) > 0); }
^
Makefile:5523: recipe for target 'libriecoin_server_a-blockencodings.o' failed

I found similar issue here: https://github.com/zcoinofficial/zcoin/ ... 00e585db3c

Seems to be compatibility with OpenSSL 1.1.0 and could be fixed by ~100 lines of change?

I think a android wallet is the most needed for ordinary users, maybe the next priority.

[cryptapus]

...

I don't see any new code in https://github.com/riecointeam/riecoin, the branch master is bitcoin; the branch master-ric has last commit May 2014.

...

That's the repo I made for clo1 to put the 0.16 changes on top of. I suggested it would be easier to audit the changes that way. I believe clo1 is still working on a merge and we just need to be patient. It's a lot of work and we are all volunteers. Also a good reason why you don't need to apologize for anything.

[luksbit]

Is Riecoin being POW protected against these ASCI miners? This video available on youtube about Riecoin, do  have in other languages?

[barrysty1e]

may as well throw my hat in the ring also; i'd submitted my progress on a Bitcoin/Riecoin 0.16 port to gatra on the 18th July, but hadn't had time to revisit and hadn't heard much back. however looking at the volunteer work, i'm happy to share my code if any bits could be picked out. from memory the bitshift maths (esp considering uint256/arith_uint256 constraints) in pow.cpp was quite tricky, but i ended up with correct results..

james

[barrysty1e]

migrated from home git to remote (https://github.com/barrystyle/riecoin-0.16).. hope it helps the cause,

james.

[ziiip]

Registrations reopened at uBlock.it

https://ublock.it/index.php?page=register

uBlock.it is a private pool.

Give us a try and see why uBlock is the most profitable Riecoin Pool!

If you find that registrations have been closed please send a PM for invite information.
-Happy mining