[ANN] BETARIGS.COM - Cryptocurrency cloud mining - thousands of rigs available!

[sdhayes12345]

Yes, I'm certain that was what the issue was then -- my account name is "eidal12345".  My 2nd job (Job #3652) was a complete failure due to a typo in a config file that I didn't catch until the morning.  I put a ticket (#498490) in to make sure the renter would get a full refund.  Every job after that has been completely stable.  

Thank you for the quick response, I was not expecting that.  

[freeloader1969]

Nailed it Mux.  Thanks.

So used to just entering the //xxxx.com:3333 portion.  Never thought to use http.

[mooninite]

Feature request: Include renter/owner message history as well as history about any extra time that was added.

[freeloader1969]

Mux...are you experiencing some kind of problems on your end right now?

I'm currently renting two rigs that aren't showing up in the pools I'm mining.  The response from one of the rig owners is here...

http://prntscr.com/2r1xkj
http://prntscr.com/2r2098


Suggestions?

NVM...running again and rig owner has taken care of me!  Stand up person.

[coins101]

Just wanted to let folks know I have 30 Mh of my farm available for scrypt mining.  http://www.betarigs.com/rig/915

U D Man. 

[mux]

Mux...are you experiencing some kind of problems on your end right now?

I'm currently renting two rigs that aren't showing up in the pools I'm mining.  The response from one of the rig owners is here...

http://prntscr.com/2r1xkj
http://prntscr.com/2r2098


Suggestions?

NVM...running again and rig owner has taken care of me!  Stand up person.

Yes, it was the pool you were mining that was a bit unstable.

[SheepOnDrugs]

Awesome, got my first jobs already paid.

Something I'd like to see:
Could you please add a graph where we could see the uptime to your proxy? This would help us spot downtimes easier.

[mux]

ANNOUNCE to Rig owners

Ok you can now select the mining algorithm your rig is using -- I've added keccak && Scrypt-Adaptive-Nfactor.

Filters are coming next

[Zae]

ANNOUNCE to Rig owners

Ok you can now select the mining algorithm your rig is using -- I've added keccak && Scrypt-Adaptive-Nfactor.

Filters are coming next

Great work!

[sdhayes12345]

My rig is tested and keccak capable, however it appears I'll have to manually change it over to keccak at the renters request.   Is this how the rest of you are doing things?  My pool in an unrented status mines scrypt, in a rented status it will mine scrypt unless I restart it as keccak.  Is there anyway around this manual intervention?

[carly200]

My rig is tested and keccak capable, however it appears I'll have to manually change it over to keccak at the renters request.   Is this how the rest of you are doing things? 

well, your rig can only be either or...

[sdhayes12345]

My rig is tested and keccak capable, however it appears I'll have to manually change it over to keccak at the renters request.   Is this how the rest of you are doing things? 

well, your rig can only be either or...

How do you advertise for KECCAK appropriately then if a 1.4MH/s scrypt rig runs at 700MH/s keccak.  Betarigs does not accept a 700MH hash rate.

[mux]

My rig is tested and keccak capable, however it appears I'll have to manually change it over to keccak at the renters request.   Is this how the rest of you are doing things?  My pool in an unrented status mines scrypt, in a rented status it will mine scrypt unless I restart it as keccak.  Is there anyway around this manual intervention?

The algorithm you should select in your rig edit page is the one which is currently, by default, active.

Whether you want to allow customers to select another algo is up to you, but then you'll have to manage that -- cgminer switches, restarts -- which can become cumbersome.

[mux]

My rig is tested and keccak capable, however it appears I'll have to manually change it over to keccak at the renters request.   Is this how the rest of you are doing things?  

well, your rig can only be either or...

How do you advertise for KECCAK appropriately then if a 1.4MH/s scrypt rig runs at 700MH/s keccak.  Betarigs does not accept a 700MH hash rate.

Oh. Didn't know there was such a hash difference with this algo. Will handle that in the next hours. For now, keep your scrypt hash and advertise on title.

[MrBobC]

So my 30Mh farm has been "Payment received - waiting 1 confirmation" for over 8 hours.  Anybody else have this kind of problem?  It was a 6-hour rental, it should have been finished by now but instead it hasn't even started.

[sdhayes12345]

My rig is tested and keccak capable, however it appears I'll have to manually change it over to keccak at the renters request.   Is this how the rest of you are doing things?  

well, your rig can only be either or...

How do you advertise for KECCAK appropriately then if a 1.4MH/s scrypt rig runs at 700MH/s keccak.  Betarigs does not accept a 700MH hash rate.

Oh. Didn't know there was such a hash difference with this algo. Will handle that in the next hours. For now, keep your scrypt hash and advertise on title.

Yea, I'm saw a different guy do that and I adopted the same.  FYI Mux, I still have not been paid for any job completed since my first. 

[mux]

Yea, I'm saw a different guy do that and I adopted the same.  FYI Mux, I still have not been paid for any job completed since my first. 

We discussed this yesterday -- the pending ticket was resolved, you'll get paid with this evening payout.

[mux]

So my 30Mh farm has been "Payment received - waiting 1 confirmation" for over 8 hours.  Anybody else have this kind of problem?  It was a 6-hour rental, it should have been finished by now but instead it hasn't even started.

ANNOUNCE

Some of you read probably the announcment by mtgox that triggered a brief BTC selllof:
https://www.mtgox.com/press_release_20140210.html

If you read the technical details, then you'll see that there is a kind of attack that allows an attacker to alter a hash of an existing transaction that is just being propagated on the network.
So the attack goes: 1/ Attacker request withdrawal from Exchange; 2/ Exchange send, and store Transaction TX on database; 3/ Attacker alter the TX number of the transaction 4/ Attacker claims to Exchange it never received funds 5/ Exchange check Transaction TX Id on database and indeed sees it does not exists, send again.

That being said, yesterday I was puzzled because I saw 1 incoming payment for a rig, which was seen on the network (so it went to the status "Payment received -- Waiting 1 confirm", but then the transaction has now disappeared! Or rather, in fact, it appeared with another transaction number! So yesterday I was puzzled and suspected maybe a double spend.

Then today, I got 6 more of those. Each from differents users.
Now I know where this come from. The sender are of course not attackers (wouldn't work in above describded attack) but probably side effect in an ongoing large scale attack -- but this is only some guessing from my side from the little I know now.

That being said, if your rented rig is in status "Payment received - waiting 1 confirmation" , then you are probably part of the 7 transactions that dissapeared, and I'll deal with you individually in the next 3 hours -- read, checking real payment and unblocking.

Mux

[mux]

So my 30Mh farm has been "Payment received - waiting 1 confirmation" for over 8 hours.  Anybody else have this kind of problem?  It was a 6-hour rental, it should have been finished by now but instead it hasn't even started.

Ok resolved your case right now, as it was a big rental.

Mux

[carly200]

waiting to see rental prices adjust to the new value of BTC...