Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

7
RagerX - push for transparency in Cryptonote pools
Post Body

Here is a short frequently asked questions section that may help you:

Q: Why is my "friend" saying that I shouldn't be using free Xmr-Stak-RX or faster RagerX, but instead - go through extra steps to get free xmrig?
A: This is cryptocurreny world. Everyone is looking out for themselves. What your "friend" is trying to do is advance his social position by giving you bad financial advice. Think with your wallet, don't put yourself at a financial disadvantage to please a guy you have never seen.

Q: Does the fact that a pool is open sourced mean that it is honest by default?
A: Besides frontend (fancy design and pages) a pool has a backend side (the one is not visible for users) that can be modified by the pool admin to do whatever they want to do. So obvious answer is - no.

Q: Source code of RagerX is closed? What, how can it be!!
A: Just like SRBMiner, Teamredminer, Claymor, TTminer, Cryptodredge, Nanominer and a lot of other miners. There is still for you a possibility to use free and opensource Xmr-Stak-RX

Q: Why are you the only Monero pool to publish view keys and shares data?
A: Good question.

Introduction

Some may be concerned with RagerX miner and pool being close sourced. Is the displayed hashrate of the miner, pool is real? How can you verify it yourself besides running long run test on 2 same workers on 2 different pools?

We will explain you how RagerX team cared to be transparent enough and give each user a possibility to check everything.

RagerX pool has unprecedented transparency level and you can verify it yourself

So lets imagine pool block rewards as a whole pie and each miner as getting a piece of it:

https://preview.redd.it/77xxtblo3n341.jpg?width=700&format=pjpg&auto=webp&s=d5092f8b0f003af8f3719b739df5ec601ea6b304

There are 2 main parts in rewards verification process:

  1. Make sure your slice of the cake is as large as it should be.
  2. Make sure the cake itself is as large as it should be.

So, let's go through each of them individually.

Part 1. Make sure your slice of the cake is as large as it should be.

This part speaks for itself and is pretty easy to understand: If miner #1 hashrate is N% higher than miner #2 - and assuming you are a miner #2 - you will submit N% more shares (if they have same, static difficulty), or N% higher difficulty shares each same period of time. Both (static and variable diff settings) results in miner #2 sending N% cumulative diff. shares over same period of time.

Problem: Tricky point here is - that many (if not all CN pools) are not allowing you to check your share count its difficulty that you had submitted on them.

Solution: RagerX - allows you to check each share you submitted on pool frontend as well as gives you ability to download share report with PPLNS time frame on request.Cumulative difficulty of shares will be hashrate (h/s) displayed in miner * 86400 (24 hours * 60 min * 60 sec).Simply divide the share export sum by window size, multiply by block reward, and this is your slice of the cake.

user submitted shares statistics on the pool frontend

report generation tab

Note: RagerX uses PPLNS reward system, so reward will be credited to a miner in batches for shares within certain time frame. If you are mining consistently (24h and more) you have nothing to worry about. If you are a pool hopper (that joins and quits mining hoping to catch lucky blocks) - your share reward will be cut or completely absent.

Part 1 conclusion:

As you can see you can verify that displayed hashrate is equal to the part of the block that you were paid for.

Part 2. Making sure the cake is as large as it should be

Now, look again on pie chart image in the beginning of this article, and you may spot another problem that can come on the stage:

Problem: on most (if not all) CN pools, you can't be sure that the cake is the size it should be, or in the other words - that pool is not inflating the size of the cake to decrease your share.

Solution: RagerX team publishes pool wallet view key, that gives you ability to check incoming blocks, compare them to pool's mined blocks on blocks page: this means that no blocks were missing.

Pool wallet: 4AAocFHiPAxNqBgVg4q3PiHAFBvugGk7ULhuHzVC5GRXX2mWxYoCy4n4VE5Ya9AnDYAK5yaF5SvJ5PnyvpD9NrBEEUFJ7M5View key: 3f8398e86a5e43a8e6ea4c8e1ee760cec194e7dd213edcc99f6b2bcc43528405

Then make sure there are no ghost miners. To do that - take the pool hashrate as declared, monitor it for a week, make sure the observed luck (number of mined blocks / shares) matches the declared luck on pool frontend.

Part 2 conclusion:

As you can see you can verify that pool is not faking (inflating) it's hashrate that could possibly reduce your share %. Publishing pool viewkey is an ultimate transparency effort, that you won't more than likely find on any other Monero pool.

Author
Account Strength
90%
Account Age
6 years
Verified Email
Yes
Verified Flair
No
Total Karma
2,798
Link Karma
2,560
Comment Karma
n/a
Profile updated: 1 week ago
Posts updated: 10 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
5 years ago