chrysophylax I personally really appreciate the effort into doing this,....but have some question's / sugesstions
How does this differ at the moment as if you use MinerControl and set it with sp btc adress,...that's the way I've currently chosen to contribute/donate my one gpu, that i'm not using it full time?
will you expand it to all the other devs? and how will it be implemented? If the donator has to change the server address from donate-sp.granitecoin.com to donate-tpruvot .granitecoin.com, then,...we'll nobody is going to use it,...
maybe a solution would be a customized API to pull the correct "price" and let MinerControl do the rest. In order to do that you would need also a web site with a "dev pool" of where donators could vote which dev gets more "votes" and the one with more votes gets the higher price in the API, and offcourse the API has to be time limited according to the votes,...so the adresses of devs are switched fair and square according to the dev pool site,... It's a little bit of complicated but I think it can be done,...by someone who has that kind of experience...and what's even more interesting is if it takes really off then even devs get a direct feedback from the community about their work and therefore also more beer for them
really appreciate your kind words and suggestions and questions ...
just to clarify ... there is no difference to setting the address up in the miner itself ( or through miner control - or any other mining software for that matter ) than setting the btc donation address itself ... except for two main points ( which i suppose DO make it a difference ) ...
1 - when using the donation links - it is completely anonymous to the general public as to who is mining ...
2 - the hashrate is aggregated and as such will produce a larger hashrate on a single miner than many many small miners ...
with this - it allows reduced load on the stratum servers at the pool that you mining at - and creates a single anonymous miner for donation using this aggregated hashrate ...
also - i have found that the idea that even the smallest miner can 'add' to the hashrate and help alongside the medium to larger miners - is something that a lot of people prefer to do ...
its the same analogy as the drop of water in the ocean ... it really means little - unless you realize that billions of drops make that body of water ...
so no matter how small your miner - it is beneficial ( and in some cases - more enticing ... as some miners dont think that their contribution would be much - until it is added to all the others ) to mine with others ...
as for the other devs - YES! ... definitely ...
we would not have the size of farm that we have currently ( apart from my personal investment ) had it not been for the likes of devs - sp - djm34 - wolf0 - tsiv and a few others ...
the issue is more time and money - than facilities ... all this does cost in terms of finances as well as time ... we have the facilities - now to get the hardware / cloud services purchased and active ... which leads us on to the reason the donation link was broken up to names ...
if you mine on the link donate.granitecoin.com with the same ports as above - you will find that it mines at exactly the same place ...
the reason is that the original donation link ( donate.granitecoinx.com - which changed to donate.granitecoin.com when we finally got the domain ) was simply donate.granitecoin.com combined with port of the donation algo ...
the issues that arose with this is two fold ...
1 - the ports were numbered to algo and dev accordingly - but became quite confusing ...
eg - donate.granitecoin.com:7898 and donate.granitecoin.com:7989 for donation to djm34 and sp respectively using x13 and x11 ... it is much easier to remember donate-sp or donate-djm34 or donate-wolf0 than to remember which port each one belongs to on which algo ...
2 - the servers themselves were running out of working space as each stratum proxy takes its chunk of RAM ...
so unless there was a HUGE server running HUGE cores ( 12 would suffice for a large server - with multiple cpu's ) and MASSIVE amounts of RAM - there would be no way of redirecting the link to the right server ...
as a separate server and separate donation link - its easier to manage - as nicehash is also finding out with their new dns reshuffle ...
it also makes it easier for separate servers to use the same ports so that x11 is one port - x13 is another - and so forth - on each of the servers ...
if there is a way to have the ONE donation link - and redirect it to the various ip's of the various servers - then i would be more than happy to implement ...
your idea of an API that supplies the info to the miner is a good one ...
same with the website - though i think the website would be a damn site easier to produce than the api
...
though the idea sounds like it would be complicated to implement - i think the simpler that we make this ( for the time being anyway ) - the better ... at least until it can be used as a standard - if it ever does ...
so if i understand this correctly ... a voting system via the website that determines which dev - that determines which algo - that mines according to an API that points the miner to the donation address based on the original vote ... wow
...
a nice algorithm that would be
... but one which alas - i cannot implement without the help of a dev that can do that ...
as a start though - would anyone know how ( or know anyone that knows how ) to redirect an address based on port? ... ie - single address ( donation.granitecoin.com ) where pot 9797 goes to server xxx.xxx.xxx.1 and port 9897 goes to server xxx.xxx.xxx.2 ...
at the moment they are a-record redirections to server ip's ( the one vps at the moment - until the others come on line ) ...
tanx for you feedback - its much appreciated
...
#crysx
