[9 TH] Bitparking Pool, DGM 0%,vardiff,stratum,Merge Mining

[superfastkyle]

Please do what you can to help us. I know this is 100% not your fault but I setup all deposit addresses with vircurex (even btc). And I had several of my friends do the same for ease of use. I hate to have to tell them their coins are gone too.

[1713977051]

1713977051

[1713977051]

1713977051

[1713977051]

1713977051

[1713977051]

1713977051

[doublec]

Please do what you can to help us. I know this is 100% not your fault but I setup all deposit addresses with vircurex (even btc). And I had several of my friends do the same for ease of use. I hate to have to tell them their coins are gone too.

Ok, I'm going to do a one off fix for this issue. If users email admin@bitparking.com or bitmessage BM-BbgTgGa6LX3yYqwJSwdwrzysvfWjM2u6 with the following:

• Your account name
• Your bitcoin address registered with that name

I will reply with a message you need to sign using your bitcoin address.

For those of you who do not have the private keys for any of the addresses I'll deal on a case by case basis via email/bitmessage. What you should do now though is register a new account with new coin addresses that you own.

[ssateneth]

Emailed

[matt4054]

I guess I'll not be the only one having difficulties installing Devcoin and Ixcoin tonight. Both clients refuse to download the chain: they try to bootstrap from IRC, fail to connect to IRC and stay idle. Anyone had success here installing the Windows binaries? Both IXC and DVC... one user suggested 64bit to be a problem (I don't have any 32bit left to test)

I'm too frustrated to take hours putting up a dev env to compile them on my current machine. I was supposed to start a nice week-end and chill off. There are times I would just like things not to go awry, so unexpectedly... I'll think I'll renounce my merged alt coins for now and maybe go back to a pure PPS pool like 50BTC, I'm fed up with fear, uncertainty and doubt I had these days due to various troubles, and this includes unlucky PPLNS / DGM pools

I know I look like a whining bastard here, but bad luck in series is getting on my nerves. EDIT: yes whining auto-detected so I'll not switch pool but wait for a solution to the IXC/DVC not being installable.

doublec: your own coin-wallet service would definitely be a big plus in such a situation.

Edit2: just saw your proposal to edit addresses exceptionally, it's very much appreciated too, now I know I have a chance to recover the alt coins at least. I can sign messages with my BTC address so it should be fine. Thank you for allowing me to go to sleep with hope ;-)

[doublec]

I guess I'll not be the only one having difficulties installing Devcoin and Ixcoin tonight. Both clients refuse to download the chain: they try to bootstrap from IRC, fail to connect to IRC and stay idle. Anyone had success here installing the Windows binaries? Both IXC and DVC... one user suggested 64bit to be a problem (I don't have any 32bit left to test)

Try adding 50.116.37.18 as a node for both DVC and IXC:

Code:

ixcoind -addnode=50.116.37.18

doublec: your own coin-wallet service would definitely be a big plus in such a situation.

I'll try and get something together for this in the coming week.

[matt4054]

Try adding 50.116.37.18 as a node for both DVC and IXC:

Code:

ixcoind -addnode=50.116.37.18

Unfortunately, for Devcoind.exe I get a TCP error "connection refused" trying to connect to 50.116.37.18 on port 52333

Code:

ThreadRPCServer started
ThreadIRCSeed started
ThreadSocketHandler started
ThreadMessageHandler started
ThreadOpenConnections started
trying connection 50.116.37.18:52333 lastseen=-352286.5hrs lasttry=-380064.3hrs
connection timeout
IRC connect failed
IRC waiting 71 seconds to reconnect
connection timeout

But it worked for Ixcoin! Getting closer, maybe the ports from devcoin.conf needs tweaking, I used the sample .conf file from this thread

[doublec]

Unfortunately, I get a TCP error "connection refused" trying to connect to 50.116.37.18 on port 52333

I don't know where it's getting port 52333 from. It should be port 8337. Where did you get the source from? Try:

Code:

ixcoind -addnode=50.116.37.18:8337

[redtwitz]

Someone asked me if they could sign a message using one of the keys (ie. the bitcoin key) to prove ownership of the other addresses and have them changed. The problem with this is it leaves the pool open to social engineering. If the bitcoin key was kept on Vircurex too I don't know if it's the hacker then trying to withdraw funds from the pool. It's a bad situation. I'm open to suggestions.

I'd lose about 0.015 BTC in altcoins if there's no way to change my addresses (so I'm not terribly worried), but I'll share my thoughts:

• If the attacker has the private keys to the BTC address, he'll probably also have those for the others. I doubt there are many users that use Vircurex for BTC but not for the altcoins, so the signing method you referred to shouldn't be able to make things worse.
  
• My IP, wallet addresses and even user name might be known to the attacker, but I should be able to provide a piece of information that he can't possibly have: the local port number my miner is currently using.
  
• Some users might be using the same user name here and at your pool. Unless the forum account was registered after the breach, that should be difficult to exploit.
  
• This is probably too impractical given the size of the user base, but if a user still has access to his bitcoin address (but isn't in possession of the private key), the altcoins could be converted to BTC. This way, there's no risk of somebody introducing his own addresses.
  

I'll register a new account when the current block finishes. If I understood DGM well enough, I could lose more BTC abandoning the current round than I have in altcoins...

[pyra-proxy]

Someone asked me if they could sign a message using one of the keys (ie. the bitcoin key) to prove ownership of the other addresses and have them changed. The problem with this is it leaves the pool open to social engineering. If the bitcoin key was kept on Vircurex too I don't know if it's the hacker then trying to withdraw funds from the pool. It's a bad situation. I'm open to suggestions.

I'd lose about 0.015 BTC in altcoins if there's no way to change my addresses (so I'm not terribly worried), but I'll share my thoughts:

• If the attacker has the private keys to the BTC address, he'll probably also have those for the others. I doubt there are many users that use Vircurex for BTC but not for the altcoins, so the signing method you referred to shouldn't be able to make things worse.
  
• My IP, wallet addresses and even user name might be known to the attacker, but I should be able to provide a piece of information that he can't possibly have: the local port number my miner is currently using.
  
• Some users might be using the same user name here and at your pool. Unless the forum account was registered after the breach, that should be difficult to exploit.
  
• This is probably too impractical given the size of the user base, but if a user still has access to his bitcoin address (but isn't in possession of the private key), the altcoins could be converted to BTC. This way, there's no risk of somebody introducing his own addresses.
  

I'll register a new account when the current block finishes. If I understood DGM well enough, I could lose more BTC abandoning the current round than I have in altcoins...

I like the idea of enabling an "auto-trade" of alts to btc if you can sign a message with your btc address.  If your btc address was on vircurex you should probably get a new address immediately so social engineering should not be a problem there.  I suspect I'm not alone in using vircurex directly for alts and personal wallets for btc?

[matt4054]

I don't know where it's getting port 52333 from. It should be port 8337. Where did you get the source from? Try:

Code:

ixcoind -addnode=50.116.37.18:8337

I got the Windows "package" from here, I thought it was the closest to the "official" binary.

Now forcing port 8337 didn't seem to do the magic. I think I need another devcoind.exe or compile it myself...

Code:

trying connection 50.116.37.18:8337 lastseen=-352287.1hrs lasttry=-380064.8hrs
ThreadMessageHandler started
ThreadRPCServer started
connected 50.116.37.18:8337
sending: version (85 bytes) 
...
socket no message in first 60 seconds, 0 1
disconnecting node 50.116.37.18:8337

[juhakall]

I'll register a new account when the current block finishes. If I understood DGM well enough, I could lose more BTC abandoning the current round than I have in altcoins...

I'm under the impression that you should have no reason to think like that. In a fair payout method, all shares should have the same expected payout, and not depend on history at all. With DGM (and most other methods as well), the actual payout per share will have lots of variance, but it should average out after a long enough time, even over multiple accounts that are mining only occasionally.

DGM is really hard to understand, and unlike with PPLNS, I still haven't grasped it well enough to be 100% sure of the above. However, it would be a very lousy payout method if miners were forced to stay on the pool to not lose their expected payouts.

[doublec]

I got the Windows "package" from here, I thought it was the closest to the "official" binary.

Now forcing port 8337 didn't seem to do the magic. I think I need another devcoind.exe or compile it myself...

8337 is the ixcoind port. For devcoin I'm using 9333, sorry.

[doublec]

I'll register a new account when the current block finishes. If I understood DGM well enough, I could lose more BTC abandoning the current round than I have in altcoins...

I'm under the impression that you should have no reason to think like that. In a fair payout method, all shares should have the same expected payout, and not depend on history at all. With DGM (and most other methods as well), the actual payout per share will have lots of variance, but it should average out after a long enough time, even over multiple accounts that are mining only occasionally.

DGM is really hard to understand, and unlike with PPLNS, I still haven't grasped it well enough to be 100% sure of the above. However, it would be a very lousy payout method if miners were forced to stay on the pool to not lose their expected payouts.

It will look like you are losing because your new account will be 'charging the capacitor'. But at the same time the old account will be discharging and the two will add up such that nothing is lost. You can keep your old account if you use the email me/signing thing I discussed earlier. Just don't withdraw before then.

[matt4054]

8337 is the ixcoind port. For devcoin I'm using 9333, sorry.

You are my hero! :-) I got both DVC and IXC up tonight thanks to your help!

Now I'll just e-mail you my new addresses, sign with my BTC address and everything is fine again. So sweet!

[Lucko]

I know I must be missing something simple but I can't find where do I encrypt and backup IXC and DEV clients

[davebodger]

I know I must be missing something simple but I can't find where do I encrypt and backup IXC and DEV clients

You don't get to encrypt in the client as those clients do not have the encrypt feature yet.
Workaround is to run the client only when you want to send coins.
All other times keep it hidden away in an encrypted directory, or on a AES256 secured memory stick (if you are paranoid like me). 
The downside is waiting for the blockchain to update each time you do this.

[Chemicalbro]

Yes there's more to come with regards to stats and work on the pool. If you search in the Android Play store you'll see a Bitparking app with widget

I know the app is not your business - already reported to the developer:
namecoins are missing i=coin still in
and biggest problem for me: the widget permanently crashes on HTCs Sence

but the website is so lightweight that there is nor problem in using it on a mobile device

Hmm I didn't notice this report, how'd you get it to me? I'll get to fixing that soon. Feedbacks always a good thing.

[Lucko]

I have problems with ICS. Widget is crashing and CPU also produces a lot of heat. Samsung galaxy Note upgraded to ICS

[Lucko]

Nope not me, I've only progressed from newbie status today so these are some of my first posts!

Hm... I saw this nick somewhere. Did we talked on IRC then?

[firefop]

I'll register a new account when the current block finishes. If I understood DGM well enough, I could lose more BTC abandoning the current round than I have in altcoins...

I'm under the impression that you should have no reason to think like that. In a fair payout method, all shares should have the same expected payout, and not depend on history at all. With DGM (and most other methods as well), the actual payout per share will have lots of variance, but it should average out after a long enough time, even over multiple accounts that are mining only occasionally.

DGM is really hard to understand, and unlike with PPLNS, I still haven't grasped it well enough to be 100% sure of the above. However, it would be a very lousy payout method if miners were forced to stay on the pool to not lose their expected payouts.

as I understand it abandoning a round at any other time then "very near the start" could infact drastically reduce your payout. Which is why I've argued so much about the switch. I'm off mmpool (for good I think) finally as a result of vircurex going down I don't really feel like recreating another dozen worker accounts to reset addresses.