Pages:
Author

Topic: [POOL] HASHPOWER.CO - YAAMP CLONE - X11, X13, X15, Quark, Neoscrypt - page 20. (Read 36536 times)

legendary
Activity: 1470
Merit: 1114
Mining seems to be working well so far, and the pool's coin selection is at least good enough that my miners are spending time on it on-and-off, so that's a plus.

Payouts have been regular, but with a slight problem... It's not entirely the pool's fault, but it seems that payouts are being made with extremely low transaction fees, which due to the strange spamming of the blockchain that's going on right now, has resulted in payments that haven't confirmed in over 15 hours as of writing this. Obviously lower tx fees are good for profitability of the pool/its miners, but when it's at the point that transactions simply aren't confirming at all, perhaps some adjustment is due Undecided. Just for comparison's sake, another YAAMP clone my miners have been frequenting is spending more on tx fees (though it has higher pool fees in general) and its payments have been going through fine all day.

My payouts from ffpool have been confirming quickly. I would not be in favour of higher fees for faster confirmations in any case.
member
Activity: 97
Merit: 10
Hello,

Thank you for your interest in this pool.

We havent changed anything from the original yaamp code regarding payments. It uses the sendmany function with no special parameters to lower the fees.

But im having problems sending BTC around too. I sent BTC from my phone's blockchain app to cryptsy yesterday and it's still not confirmed yet.

Yeah, someone (or some group) has been bombarding the blockchain with spam transactions with higher-than normal fees, making it so that very few transactions with lower/no tx fees are getting confirms. This may go away at some point, but it's doing a good job of simulating how the network performs when block space becomes scarce and a, "fees market", decides what gets confirmed and what doesn't. Unfortunately, payouts from the pool are currently falling into the, "what doesn't", category. Might be able to just ride this one out (if it ever stops), but it might be good to look at a method of handling these sorts of situations in the future, as this probably isn't the last time we'll see these conditions.
newbie
Activity: 21
Merit: 0
Hello,

Thank you for your interest in this pool.

We havent changed anything from the original yaamp code regarding payments. It uses the sendmany function with no special parameters to lower the fees.

But im having problems sending BTC around too. I sent BTC from my phone's blockchain app to cryptsy yesterday and it's still not confirmed yet.


Here are some information on algo switching for sgminer.

https://www.nicehash.com/index.jsp?p=multialgo

member
Activity: 97
Merit: 10
Mining seems to be working well so far, and the pool's coin selection is at least good enough that my miners are spending time on it on-and-off, so that's a plus.

Payouts have been regular, but with a slight problem... It's not entirely the pool's fault, but it seems that payouts are being made with extremely low transaction fees, which due to the strange spamming of the blockchain that's going on right now, has resulted in payments that haven't confirmed in over 15 hours as of writing this. Obviously lower tx fees are good for profitability of the pool/its miners, but when it's at the point that transactions simply aren't confirming at all, perhaps some adjustment is due Undecided. Just for comparison's sake, another YAAMP clone my miners have been frequenting is spending more on tx fees (though it has higher pool fees in general) and its payments have been going through fine all day.
newbie
Activity: 6
Merit: 0
Hi,

can you post sample for algo switching for sgminer?

Thank you.
newbie
Activity: 21
Merit: 0
YAAMP Based Pool

http://hashpower.co

We have put together the yaamp software. There's a bit to learn but I feel it's all running fine now.

We have most of the good X11, X13, X15 quark and neoscript coins as of now. We should add scrypt and qubit coins next.

Thanks
Pages:
Jump to: