So a couple of things I am not seeing here, maybe I am missing it.
1. How should the miners connect? Do they use their payout address for the target coin when mining all coins? (I am assuming yes)
yes, that is exactly what they do.
2. I have not seen any code that gets the exchange to send the coins back to your target wallet. This is still part of the still to come or is that a manual operation for the pool operator?
i haven't included any of the exchange-side code yet. it supports withdrawals from cryptsy, at least. bter and mintpal and poloniex require manual withdrawals by the pool operator. having a healthy reserve of the target coin sorta mitigates this a a big issue, though. it does support automated withdrawals as long as the pool's wallet address is added as a trusted withdrawal address within cryptsy.
3. If a shift is sent to an exchange I am assuming that the payout just fail until there is enough funds in the wallet of the target coin to payout what is owed?
the payout script actually is triggered by another script i have (which first of all estimates the amunt of the payout, then checks the local daemon and verifies that enough is present to cover the payout. If there is not enough it will try and withdraw from cryptsy, if there is still not enough it will log an error in a log file. I still mean to set it up so that it can notify the op via SMTP at that point.
Really liking what you are doing so far.
J
thanks very much man!
i plan on eventually trying to document all of this stuff
the best way to understand lots of this stuff is just fire up a basic nomp pool
run redis-server and run the command '
monitor' and just watch how NOMP interacts with the various redis values. there really needs to be tons of documentation created around that sort of stuff, then how my modifications alter all that. i will try and get it done eventually ,but I'm also in the process of setting up a big (well, relatively, ~100th) sha community-owned mine that will pay out solely in NXT.
