I noticed a problem. It could be betarigs, could be sgminer 4.1 or could be me ;-)
Help/Ideas appreciated:
I posted earlier, that after some time of not beeing rented sgminer will quit polling/testing/checking (whatever it does) on the betarigs pool.
This has two consequences: 1. if it gets rented in that period, the miner will not auto switch to betarigs-pool... that is bad
2. after some time my rig will be shown as offline by the website. If I restart sgminer manually it will show as online again within minutes.
Is this a bug? is this a misconfiguration? (should I add something to my miner config to keep polling?)
Anybody else noticed this behaviour?
Topic: [ANN] BETARIGS.COM - Cryptocurrency cloud mining - thousands of rigs available! - page 98. (Read 200998 times)
February 11, 2014, 03:36:10 PM
February 11, 2014, 12:55:03 PM
Asked this once before, how can we delete rigs?
February 11, 2014, 12:23:35 PM
Bitcoin’s Transaction Malleability issue
Ok since every big bitcoin exchange is making a blog post/announce about the Bitcoin transaction malleability issue, I figured I should make one too
So 2/3 days ago, for the first time in all Betarigs long history, I got a weird thing: A unconfirmed transaction dissapeared! Looking into blockchain.info, it told me that it was a double spend attack. Really? Well, ok, my first double spend attack. But then the other transaction had exactly the same amounts and destination BTC addresses. So I was, wtf?
Then 1/2 days ago, it was 7 more of them! I corrected them manually, since I actually got the fund, but well, wtf? Then mtgox made the big announce telling about the malleability thing.
And since then, I'm getting dozens and dozens of these transactions with hash numbers that changes! (And then this Murphy guy decided to break blockchain.info API as I was busy manually correcting these transactions.. grr).
But I can now tell that Betarigs is automatically handling these malleabe transactions, and that all previous malleable transactions have been dealt with manually. The only side effect for you is for some of you to have had the "Payment confirmed - waiting 1 conf" hung for several hours. But that is now fixed.
Ok since every big bitcoin exchange is making a blog post/announce about the Bitcoin transaction malleability issue, I figured I should make one too
So 2/3 days ago, for the first time in all Betarigs long history, I got a weird thing: A unconfirmed transaction dissapeared! Looking into blockchain.info, it told me that it was a double spend attack. Really? Well, ok, my first double spend attack. But then the other transaction had exactly the same amounts and destination BTC addresses. So I was, wtf?
Then 1/2 days ago, it was 7 more of them! I corrected them manually, since I actually got the fund, but well, wtf? Then mtgox made the big announce telling about the malleability thing.
And since then, I'm getting dozens and dozens of these transactions with hash numbers that changes! (And then this Murphy guy decided to break blockchain.info API as I was busy manually correcting these transactions.. grr).
But I can now tell that Betarigs is automatically handling these malleabe transactions, and that all previous malleable transactions have been dealt with manually. The only side effect for you is for some of you to have had the "Payment confirmed - waiting 1 conf" hung for several hours. But that is now fixed.
February 11, 2014, 11:33:24 AM
Can we get Keccak rigs in BTC/GH/Day rather than BTC/MH/Day?
February 11, 2014, 09:45:24 AM
Mux, is your "pool" down?
My "pool" will be seen as down when a customer choose a unstable pool -- Betarigs is only acting as a proxy.
As for Betarigs itself being down, I have only a 15mn downtime since the launch
February 11, 2014, 09:30:29 AM
Mux, is your "pool" down?
pool isn't down. I have my rig rented and it works just fine.
Did you rent a rig or are you a rig owner?
February 11, 2014, 09:13:05 AM
Mux, is your "pool" down?
February 11, 2014, 08:37:14 AM
I like the filters, but as a slight imrovement to the complex search style I would prefer some "single link" solution.
just a line of major filters: scyrpt | min xxx kH | lowest price
that would be activated by clicking on them
just a line of major filters: scyrpt | min xxx kH | lowest price
that would be activated by clicking on them
February 11, 2014, 07:45:18 AM
I paid for a rig but it wasnt delivered.Now I have been refunded.Thanks.
February 11, 2014, 07:39:50 AM
Really annoying that no renter seems to bother to vote.
Got like 10 jobs and no feedback. :/
Got like 10 jobs and no feedback. :/
February 11, 2014, 05:44:46 AM
Shame it didn't take long for everyone to lowball the Kaccak pricing
Mux any chance of seperating the Kaccak rigs from the Scrypt..And possibly adding more decimal places on the BTC cost for Kaccak?
Mux any chance of seperating the Kaccak rigs from the Scrypt..And possibly adding more decimal places on the BTC cost for Kaccak?
February 11, 2014, 04:30:07 AM
Hey mux
Thought I would let you know the end result of a bug I logged a call on your support system for.
You sent me 2 payments to the same wallet under 1 transaction.
My wallet in this case was hosted at www.coinjar.com
Here is their response
"It appears that there were two outputs of the same address 1ME4sB8R8LziuQa3q258D7hMbSnBpCh2Xk. The first one is for 0.0199871 BTC and the second one is for 0.010682 BTC. At this moment our system can only accept unique output addresses (which is a standard practice used by the reference client), and the second one was ignored.
However, we have indeed received both transactions, so we will reimburse 0.010682 BTC to you shortly. Thanks!"
So I ended up getting my BTC which is good.
Not sure what he means by standard practise though. Whether its a problem on their side or the way your database base groups together payments for single wallets.
It seems in this case, sending 2 payments to the same wallet on 1 transaction caused the issue.
Just FYI
Thought I would let you know the end result of a bug I logged a call on your support system for.
You sent me 2 payments to the same wallet under 1 transaction.
My wallet in this case was hosted at www.coinjar.com
Here is their response
"It appears that there were two outputs of the same address 1ME4sB8R8LziuQa3q258D7hMbSnBpCh2Xk. The first one is for 0.0199871 BTC and the second one is for 0.010682 BTC. At this moment our system can only accept unique output addresses (which is a standard practice used by the reference client), and the second one was ignored.
However, we have indeed received both transactions, so we will reimburse 0.010682 BTC to you shortly. Thanks!"
So I ended up getting my BTC which is good.
Not sure what he means by standard practise though. Whether its a problem on their side or the way your database base groups together payments for single wallets.
It seems in this case, sending 2 payments to the same wallet on 1 transaction caused the issue.
Just FYI
Thanks, good to know. I'll consider this when I'll review the payment system.
Ok now I'm working on using another blockchain API to handle incoming payments...
February 11, 2014, 04:19:39 AM
Hey mux
Thought I would let you know the end result of a bug I logged a call on your support system for.
You sent me 2 payments to the same wallet under 1 transaction.
My wallet in this case was hosted at www.coinjar.com
Here is their response
"It appears that there were two outputs of the same address 1ME4sB8R8LziuQa3q258D7hMbSnBpCh2Xk. The first one is for 0.0199871 BTC and the second one is for 0.010682 BTC. At this moment our system can only accept unique output addresses (which is a standard practice used by the reference client), and the second one was ignored.
However, we have indeed received both transactions, so we will reimburse 0.010682 BTC to you shortly. Thanks!"
So I ended up getting my BTC which is good.
Not sure what he means by standard practise though. Whether its a problem on their side or the way your database base groups together payments for single wallets.
It seems in this case, sending 2 payments to the same wallet on 1 transaction caused the issue.
Just FYI
Thought I would let you know the end result of a bug I logged a call on your support system for.
You sent me 2 payments to the same wallet under 1 transaction.
My wallet in this case was hosted at www.coinjar.com
Here is their response
"It appears that there were two outputs of the same address 1ME4sB8R8LziuQa3q258D7hMbSnBpCh2Xk. The first one is for 0.0199871 BTC and the second one is for 0.010682 BTC. At this moment our system can only accept unique output addresses (which is a standard practice used by the reference client), and the second one was ignored.
However, we have indeed received both transactions, so we will reimburse 0.010682 BTC to you shortly. Thanks!"
So I ended up getting my BTC which is good.
Not sure what he means by standard practise though. Whether its a problem on their side or the way your database base groups together payments for single wallets.
It seems in this case, sending 2 payments to the same wallet on 1 transaction caused the issue.
Just FYI
February 11, 2014, 03:49:40 AM
+1 for right to reply.
My rig has only 10 out of 10 and repeat customers, but if someone pointed it at a rubbish pool and then gave me 1/10 and bad feedback there is nothing I could do about that... It would also let us thank renters who give good feedback...
My rig has only 10 out of 10 and repeat customers, but if someone pointed it at a rubbish pool and then gave me 1/10 and bad feedback there is nothing I could do about that... It would also let us thank renters who give good feedback...
February 11, 2014, 12:12:56 AM
Here's an idea to combat that. How about an out of office style auto responder?
If renter emails owner between hours of x and y they will either get an email back saying they are away and will get to you ASAP or a warning on the website that says you are about to email out of office hours?
You can set your rig to be offline, so why not set owner to be offline too?
Could do it in a similar way as well, using drop downs rather than time.
If renter emails owner between hours of x and y they will either get an email back saying they are away and will get to you ASAP or a warning on the website that says you are about to email out of office hours?
You can set your rig to be offline, so why not set owner to be offline too?
Could do it in a similar way as well, using drop downs rather than time.
I don't go offline. I hibernate...
Joke aside, contacting the renters after time is up and responding to ratings seem more practical. But making some statuses for rig owners isn't a bad idea. These could be combined.
We need a way to defend our reputation.
February 10, 2014, 11:44:52 PM
Here's an idea to combat that. How about an out of office style auto responder?
If renter emails owner between hours of x and y they will either get an email back saying they are away and will get to you ASAP or a warning on the website that says you are about to email out of office hours?
You can set your rig to be offline, so why not set owner to be offline too?
Could do it in a similar way as well, using drop downs rather than time.
If renter emails owner between hours of x and y they will either get an email back saying they are away and will get to you ASAP or a warning on the website that says you are about to email out of office hours?
You can set your rig to be offline, so why not set owner to be offline too?
Could do it in a similar way as well, using drop downs rather than time.
February 10, 2014, 11:29:15 PM
How to add downtime compensation & communicate with the rented person after rental period is over.
I would also like that, and a way to respond to ratings.
I received a 6/10 rating because the renter wrote when I was asleep. And I know my rig is stable. I am active 18/19 hours a day, it doesn't seem right to get bad rating because i was just sleeping. And probably the issue was from the pool my rig was directed at.
February 10, 2014, 08:05:53 PM
i just rented 2 rigs for a few hours, however something is wrong with the transactions which i sent,
for some reason, in my client, the transactions are twice in the client.
2 have 3 confirms now, the others none.
Also, no confirms the webpage.
for some reason, in my client, the transactions are twice in the client.
2 have 3 confirms now, the others none.
Also, no confirms the webpage.
February 10, 2014, 06:28:58 PM
Update:
Tonight we experienced both Cloudflare being attacked (Cloudflare: "Mitigating a large attack hitting much of the EU") which made the website sometimes unresponsive even though the server was OK; and the blockchain.info API which was particularly lagging. I managed payment validation by hand during an 1 hour period, but some payments may not have been recognized. In this case, the usual process: please post a ticket and we'll refund you.
Meanwhile, tomorrow, I'm going to use an extra one/two others blockchain API for security, if one went to get laggy.
On the good news part, new record: 700 Mh/s!
Tonight we experienced both Cloudflare being attacked (Cloudflare: "Mitigating a large attack hitting much of the EU") which made the website sometimes unresponsive even though the server was OK; and the blockchain.info API which was particularly lagging. I managed payment validation by hand during an 1 hour period, but some payments may not have been recognized. In this case, the usual process: please post a ticket and we'll refund you.
Meanwhile, tomorrow, I'm going to use an extra one/two others blockchain API for security, if one went to get laggy.
On the good news part, new record: 700 Mh/s!
February 10, 2014, 05:34:09 PM
Keccak rig owners:
You can now set your real keccak hashrate!
You can now set your real keccak hashrate!
Nice! I've added it to the BunnyFarm.
Jump to: