 Show Posts
|
|
Pages: [1]
|
Regarding pricing, I was thinking about a few different pricing options. Maybe a breakdown like this: Low cost plan - something like 1BTC per month plus small fee (1.5% maybe?), unlimited Mhash/s Medium - say 5 BTC per month and no fee, some mid level limit on Mhash/s High - maybe 10BTC per month and a very high limit on Mhash/s or maybe a dedicated server instance with no limit on Mhash/s Again that's nowhere near set in stone, just an idea of how the price structure could look. I'd imagine most would prefer to pay in BTC? No contract, no cancellation fees or anything like that. I want happy customers, not to lock them into something if they decide they don't want to use it! For those who don't want to or can't create their own front end, I could provide a pretty basic standard interface you could enable. Depending on extra server load, that might end up being an extra BTC per month or so (don't know yet). How will your customer be able to be in control? What type of back-end will you be providing? What about FTP/cPanel etc? I'm not quite sure what sort of control you are referring to here? The pool server back-end is custom built. I'm thinking there would be at least a basic admin page, what would you want to see there? Seems like maybe most people would be interested in using a default website interface to the pool rather than build and host their own front-end? |
|
|
|
|
I'm considering a pool-as-a-service offering, is there a market here?
Basic description of the service:
100% hosted - we handle database security, scalability, infrastructure management and bug fixes/enhancements
good data security practices - properly salted and hashed credentials, SSL-only, offsite backups, etc...
JSON and/or XML API - you put together a user interface (PHP, RoR, Python, whatever…) connected to the service API, requires no data storage/management/mining code on the web tier
possibly multiple scoring algorithms - could choose from several scoring algorithms (proportional, PPS, cheat-proof, etc…)
I'd imagine most interest would be from those who are looking to start a pool but are short on time or technical expertise. Ant other thoughts or ideas?
|
|
|
|
|
BitcoinPays.com is also up and running with no problems right now.
|
|
|
|
|
In light of the recent security trouble at some other sites, I thought I should share a bit about our information security practices so everyone can make an informed choice.
The BitcoinPays web interface uses HTTPS throughout and all account passwords are individually salted and SHA-512 hashed. In the case of a compromise, this provides a reasonable level of safety from brute force or rainbow table attacks.
|
|
|
|
New pool in early testing. LP, proportional, 3% fee (for now, may change when I can cover server cost). So what's different about this pool? That's up to you! Join up, give it a try and let me know what to do to make it better. More data, charts and graphs, API, other new features - I'll consider all reasonable requests. Please chime in with ideas or feedback. Signup, add a miner and point to bitcoinpays.com on port 5000. Note that there are almost certainly bugs here and there, please let me know if you find one! https://bitcoinpays.comCheers, Craig |
|
|
|
Miner usernames should be in the format of "Username.Minername" like other pools to prevent problems with generic miner names such as "GPU"
Fixed this so when adding a miner the name is defaulted to this scheme, but can still be overridden if the user desires. Hope that helps! |
|
|
|
|
FYI, sometime just tried to sign up but the confirmation email delivery bounced. If you see this, PM me and I can confirm the account manually.
|
|
|
|
Miner usernames should be in the format of "Username.Minername" like other pools to prevent problems with generic miner names such as "GPU"
Ok, I had figured folks would appreciate having the ability to use shorter names, but if not (and assuming no objections from anyone else) I can either make it default to adding the username before or make new miner additions prepend the name automatically. Good feedback.  |
|
|
|
|
I don't want to spill the beans too much since it's not quite ready, but I'll also be supporting turn-key private/public pool hosting soon, provided there is any demand.
|
|
|
|
Ill give it a shot later this afternoon.
Cool, I appreciate it! |
|
|
|
New pool in early testing. LP, proportional, 3% fee (for now, may change when I can cover server cost). So what's different about this pool? That's up to you! Join up, give it a try and let me know what to do to make it better. More data, charts and graphs, API, other new features - I'll consider all reasonable requests. Please chime in with ideas or feedback. Signup, add a miner and point to bitcoinpays.com on port 5000. Note that there are almost certainly bugs here and there, please let me know if you find one! https://bitcoinpays.comCheers, Craig |
|
|
|
|
Howdy everyone, I've been on the forum for a little while now but been too busy coding a mining pool to chat on here!
|
|
|
|
To understand the algorithm better, I tried to translate the SQL code from this thread into a more general pseudocode format. I decided to post it here in case it helps anyone else to understand how the scoring algorithm works. Note that it does not include the difficulty adjustment calculation as recently discussed. let f := <initial fixed fee, as portion of total payout>
let c := <initial variable fee, as portion of total payout>
let b := 50 // total block payout
add_share:
let d := most recent difficulty
let p := 1.0 / d
if first round:
let lr := log(1.0 - p + p / c)
let ls := 0
create round:
round.los := log(1 / (exp(lr) - 1))
round.f := f
round.c := c
round.b := b
else with latest round:
let lr := log(1.0 - p + p / round.c)
if first share:
let ls := 0
else with latest share:
let ls := share.lscore + lr
create share:
share.lscore := ls
calculate_payout:
let round := most recent round
with latest share:
let max := share.lscore
with all shares:
let totscore := sum(exp(share.lscore - max)) + exp(round.los - max)
for share in all shares grouped by worker:
let credit := (1 - round.f) * round.b * sum(exp(share.lscore - max)) / totscore |
|
|
|
|
