Change in payout time promises
Posted: Sun Jan 14, 2018 8:49 am
After a discussion with Chris, I decided to modify the documentation to change our payout time promises.
Most payouts will remain with the same promised level of service as they are now. However, in the case that the developers of a coin execute a planned hard fork, then we will only guarantee an update to the latest fork before the end of the weekend after the fork. We will also be updating the policy to state that a hard fork may require two weeks for us to restore the block explorer for that coin to normal operation.
Requiring Chris to investigate forks only on Saturdays will allow us to provide better service levels to other tickets. This policy is also designed to discourage development teams from executing excessive numbers of hard forks, which hurt exchanges, pools, and the industry as a whole. Hard forks are necessary for improvement, but they should be a rare circumstance when many worthwhile features rolled out at the same time.
When a coin we are mining forks, the mining server automatically detects that and will disable the coin until the weekend. When a payout coin forks, we ask that customers do not submit support tickets unless the issue has not been resolved by Sunday evening. Otherwise, you'll just get a canned reply pointing you to the policy. I plan to spend the day adding notifications to Chris so that most forks can be dealt with automatically.
Thanks for your understanding!
Most payouts will remain with the same promised level of service as they are now. However, in the case that the developers of a coin execute a planned hard fork, then we will only guarantee an update to the latest fork before the end of the weekend after the fork. We will also be updating the policy to state that a hard fork may require two weeks for us to restore the block explorer for that coin to normal operation.
Requiring Chris to investigate forks only on Saturdays will allow us to provide better service levels to other tickets. This policy is also designed to discourage development teams from executing excessive numbers of hard forks, which hurt exchanges, pools, and the industry as a whole. Hard forks are necessary for improvement, but they should be a rare circumstance when many worthwhile features rolled out at the same time.
When a coin we are mining forks, the mining server automatically detects that and will disable the coin until the weekend. When a payout coin forks, we ask that customers do not submit support tickets unless the issue has not been resolved by Sunday evening. Otherwise, you'll just get a canned reply pointing you to the policy. I plan to spend the day adding notifications to Chris so that most forks can be dealt with automatically.
Thanks for your understanding!