rieMiner - Solo + pooled Riecoin mining

[czakris]

I added these rpc settings into riecoin.conf and noticed that GetBlockTemplate part is causing connection error on solo mining.

Protocol = GetBlockTemplate

After removing this line everything works fine again on benchmark mode with following settings. (rieMiner0.9b1Win64)

rpcuser=myRICaddress
rpcpassword=pass
rpcport=28332
port=28333
rpcallowip=127.0.0.1
connect=nodes.riecoin-community.com
connect=5.9.39.9
connect=37.59.143.10
connect=144.217.15.39
connect=149.14.200.26
connect=178.251.25.240
connect=193.70.33.8
connect=195.138.71.80
connect=198.251.84.221
connect=199.126.33.5
connect=217.182.76.201
server=1
daemon=1
Address = myRICaddress
Tuples = 6
TestTime = 101600
Threads = 7
Sieve = 4073741824

[Pttn]

Do not confuse riecoin.conf with rieMiner.conf!

rieMiner.conf must be

Code: Select all

Host     = 127.0.0.1
Port     = 28332
User     = username
Pass     = -#AnImpossibleToGuessPasswordLulz123#-
Protocol = GetBlockTemplate
Address  = ...
Threads  = 8

and riecoin.conf

Code: Select all

rpcuser=username
rpcpassword=-#AnImpossibleToGuessPasswordLulz123#-
rpcport=28332
port=28333
rpcallowip=127.0.0.1
connect=nodes.riecoin-community.com
connect=5.9.39.9
connect=37.59.143.10
connect=144.217.15.39
connect=149.14.200.26
connect=178.251.25.240
connect=193.70.33.8
connect=195.138.71.80
connect=198.251.84.221
connect=199.126.33.5
connect=217.182.76.201
server=1
daemon=1

[czakris]

Thanks for help Pttn. It is working even better now.
I checked manual one time again and found that this what is causing connection error. This issue was fixed after placing miner file into riecoin main folder ( I had it inside another folder) with these two config files. Now it's working even better than before.

[Pttn]

Great, I am glad that you got it working :D ! Was it you, who mined the blocks 953484 and 953486 :D? I am 100% sure that they were mined with rieMiner as they have its signature. And impressive, almost 2 blocks in a row!

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 (or by continuing using β1 if you downloaded it before).

[tgspring]

it's Me.:)
it's very lucky. Now the difficulty is 1359. I will continue to mine.
Thanks a lot for your rieMiner.:)

[Pttn]

Very nice :D ! I encourage you to continue mining to help making the network more robust and improve its value! And yes, the difficulty is really low... One of the blocks that I mined was at difficulty 1804, which was as far as I know the highest ever (not counting Superblocks). The RLGzid... miner is sometimes getting more than 50% of the hash power now!

I see that you found a third block :D ! I am glad that you like rieMiner, do not hesitate to report bugs or make suggestions!

[Pttn]

For Bounty Hunters: I am now willing to donate 1000 RIC for the person who fixes this rieMiner issue elegantly. This offer will expire on October 8 2018 at 00:00 Zurich Timezone. It is currently about the price of one beer, but remember how much a pizza cost years ago... And who knows if this is just 2 lines to change, but I am currently too busy to look. After this deadline, the bounty will be reduced to 250 RIC and remain valid until the new wallet is officially updated, or until January 1 2019 at 00:00 Zurich Timezone if gatra never comes back.

Note that this bug is present since fastrie/xptMiner. Obviously, there must be no performance loss, you should benchmark before and after and compare before submitting the fix. And by elegantly, I mean, inter alia, a fix that is not just a workaround (you could for example compute 2 sieves and imitate the launching of 2 instances with less threads, but this is not worth any bounty).

The fix must also make Testnet mining work properly with any sieve size (in my 2700X, only about 25% of the CPU is used when mining at difficulty 304 using 16 threads!).

[IGJ]

Only one little note

do not use:
connect=(node_ip)

instead use
addnode=(node_ip)

If you use "connect" the wallet will try to connect periodically to that node, and if the node is down, this could trigger network flood. You should use connect only to nodes that you know they will always work and you trust them. With "addnode" the wallet will connect on start to this node and will get his connected nodes list, then will try to connect to them after time. This is better for p2p network.

[Pttn]

Really? I read somewhere ziiip saying exactly the inverse, that we should use Connect instead of AddNode... Now, I am confused...

[Pttn]

Bounty deadline extended to November 1 2018, 00:00 Zurich timezone and increased to 2000 RIC, and even 5000 RIC if more work is done! Read this post.

Remember that 5000 RIC was worth hundreds of $ before the crash, and could be much more in the future.

After the deadline, the reward will be reduced to 500 RIC (or 1250 for the complete rewriting) until January 1 2019 00:00 Zurich Timezone, or as soon as the new wallet is officially approved. So please someone try to fix the CPU underuse bug before November. I do not have the time to do this myself until a while.