I am more concerned that 5 of the 10 stake pools might be planning on hosting at the same place. A major digital ocean outage takes down half the pool!
Unless the problem is a control issue... And I would think pool operators would have to be better at having things in place for edge cases like that. I know that our pool will not be single vendor... I have been in the field long enough to know how those failures go...
Yea..but many including us are not using digital ocean. So I wont be too worried with this scenario. stakepools hostings will also be fairly decentralized.
The first 10 groups have now formed that will attempt the first milestone. A lot of qualified people have stepped forward and the project had to work on a first in, first out (FIFO) basis with all those that met the requirements, so if you are not listed here, there were simply too many applicants. It does not mean you were unsuccessful, as a wait list has formed as well. If any of the 10 groups listed here do not meet the requirements of the first milestone, or dissolve their group in full, new groups will enter into the process from the wait list, or until the network demands more stake pool infrastructure. Please note that the process is ongoing as contracts and logistics are still being developed for some of these groups. The stake pool names below follow the NATO phonetic alphabet and are just preliminary markers. Each stake pool will have its own domain, can decide its own name, and is responsible for its own operations and internal dynamics. More information is forthcoming, as we all work together now in getting everything set up. So, without further ado, let's all welcome the latest 25 members of the Decred project! Stake Pool Alpha: @ClokworkGremlin, @drunkenmugsy, @Lee Sharp Stake Pool Bravo: @chappjc, @Fsig, @Shadowlance Stake Pool Charlie: @Arto, @frankbraun, @JLogan Stake Pool Delta: @Joopa, @woot Stake Pool Echo: @karamble, @lolekbolek Stake Pool Foxtrot: @theMsquared, @418Sec, @walkeralencar Stake Pool Golf: @diegox104, @Dyrk Stake Pool Hotel: @Emilio Mann, @girino, @skydivebr Stake Pool India: @Myagui, @tpruvot Stake Pool Juliett: @cryptokrill, @jyap
Good luck to all of the stakepools that have been chosen! If anyone needs a programmer in the future feel free to DM me .
Looks nice, but I was under the impression that PoW pool operators should not operate a PoS pool. Anything changed ?
Hey @.m. I'm assuming your post is in reference to Epsylon3, who hosts Yiimp. I insisted with Epsylon3 to join me in launching a PoS pool, otherwise I know it was not in his plans. I didn't read of anything relating to this exclusion, though as I confessed the other day, I have not caught up with the history of threads about PoS pools yet. I saw nothing about this in the RFP. Edit: I think I found the post that you had in mind there. It was on the call for action thread, in reference to an "ideal distribution", roughly described as reaching something like 20 PoS pools and respective managers not being related with exchanges or PoW pools.
@mreichardt: Remember that there is no guarantee all these groups will get everything up and running successfully. The c0 stake pool has problems too, and the software still needs to improve. It's still quite crude, but it''s definitely improving. More spots will open in time, or sooner if a group dissolves, which would mean new entrants to the RFP until 10 stake pools are up and running well.
Thanks for the clarifications. Does this mean it is still acceptable to submit proposals for this RFP? Thanks.
For the record, the contract and the professionalism of the team behind it is quite refreshing! I am used to projects where the agreements are a bit more "ad-hock" and that is not always a good thing.
I've had a great deal of experience in development, and administration. I've worked in the industry for going on 15 years. I have managed Linux and Windows servers for at least 5 of those years, and developed in languages ranging from PHP, to Java, to C/C++ and more recently NodeJS (although have quite a few years in client side JavaScript). I also have experience in integrating with third party APIs, and managing private clusters with auto-scaling via AWS. With regards to dcr - I have configured and successfully run my wallet for some time on a little VPS, backed by a few helper scripts to automate common tasks. While crypto currency, and subsequently dcr is by no means my area of expertise, it is something I can learn more about. I'd love to help out on this project. If any team is looking for someone with my skill set, count me in.