Show Posts
|
Pages: [1]
|
CoinLenders called "make a transaction" to Inputs, but Inputs was under DDoS at that time. CoinLenders didn't know if it went through or not, and it's better to be safe than sorry, so a manual processing was required.
Thanks for explanation, TradeFortress. Is there anything like two phase commit protocol implemented between coinlenders and inputs.io nodes? From your description of failure it doesn't seem. I suggest you to use It, although it may decrease performance of both sides, but will increase security for sure. In this case transaction would be rolled back on coinlenders side after some timeout, followed by appropriate message in application like "try again later". The other thing you may try is not to use the same route from coinlenders <-> inputs.io communication as you use for coinlenders <-> outside traffic and inputs.io <-> outside traffic. This way you would avoid congestion if any of 2 is under DDoS from outside, assuming that you have some inverse proxies (like nginx) in front of your servers that keep applications from excessive load. Just my 2 cents... Good luck.
|
|
|
Tnx for reply, problem solved, I got refund 
|
|
|
I tried to solve this problem with coinlenders (TradeFortress) in private, but 7 days passed from my mail sent to admin@glados.cc, already, and no reply, still. It is not possible to send private message to TradeFortress here, either, so that leaves me a few options and the first is to write about my problem here. Here is what happened... I issued withdrawal from coinlenders to my inputs.io wallet last Saturday (14.9.2013.) about 23:45 CET. I noticed site was running really slow at the time, but I thought it was due increased load or some update in progress. After several minutes transaction passed on coinlenders side and it is shown in the list. However, that amount never arrived to my inputs.io wallet. As both sides of transaction (coinlenders -> inputs.io) are run by TradeFortress I find him responsible for this failure, so I'm looking for explanation and my coins back.
|
|
|
Oh, sorry, didn't read this carefully enough. Then maybe he temporarily switched some of his miners to PPS mode ? PPS reward is not shown in this table.
Tycho, I'm certain I haven't done proportional -> pps switch during shown blocks, furthermore that problematic block was in the middle of the night while I was sleeping and I don't have any software for automatic management of my workers. Too bad I don't have access to some log so I can prove it, my miners haven't reported anything strange about rejected blocks or something, but maybe you may check it out in pool logs and pass me info via PM or even better make more info accessible on the site. 0.4 bt cents is not much of difference, but I'm more interested in the true reason why that happened and to help you investigate the case so it won't repeat. I'm developer myself and I don't like when things don't work as expected 
|
|
|
Hi, Tycho, I've sent you 3 same messages via PM, but as you know they got redirected to some other account, so I'll try here as I just passed forum noob restrictions...
I'll c/p sample of my statistics:
Time/Link Found in Your Total Reward
29.04 15:17:57 0h 52m 615 1894788 0.00787093 29.04 14:25:15 5h 56m 4088 12532185 0.00788713 29.04 08:28:19 1h 39m 1144 3552804 0.00780848 29.04 06:49:03 1h 13m 861 2628794 0.00794252 29.04 05:35:56 9h 28m 6041 19191553 0.00361762 <-------------------------------------- (Block 233685) 28.04 20:07:17 0h 30m 340 1080488 0.00763081 28.04 19:37:10 3h 35m 2355 7643323 0.00734798
Worker payout method was proportional for all these blocks, so it is expected to get paid pretty evenly for each block, with condition that ratio of pool hash rate / my hash rate stays the same. As you may see by the number of my shares and the total number of shares for each block in the sample it is true, how do you explain more than 50% cut for block 233685?
Tnx in advance for your answer and I hope that issue about PM redirection is going to be solved asap. I know this kind of message is not most suitable for forum discussion, but I don't have other choice.
Regards, vasvla
|
|
|
As difficulty increased, we may expect some higher prices?
|
|
|
Proportional payments vary due to the erratic nature of finding work. For steady payouts choose PPS.
The only variable is time to solve a block, with steady hash rate of my equipment and steady hash rate of the rest of the pool, my proportional part of the pool is the same, nevermind if block lasts 12 minutes or 12 hours. The longer the block is, smaller is the variance between my strength compared to strength of the pool, and that block was pretty long - 20m shares, so it has to be something else...
|
|
|
I had strange situation today and tried to PM Tycho, but somehow messages are redirected to some obsolete account...
For one block today my payment was nearly halved and all the time I was mining by proportional method with no significant hashrate changes, no downtime, number of shares follow the proportions for other blocks, just payment is halved... Any help would be appreciated.
|
|
|
Do you have adequate PSU, anything less than real 650W is too weak for 2 X 7970, even more, depends partially on the rest of hardware. For example, I had almost no problem to put 6770 and 7770 on the same mb with full hash rate of both cards, 550W psu, old 939 mb and processor, dedicated for mining only. So I guess combo with same cards should be even easier to manage. Good luck!
|
|
|
|