 Show Posts
|
|
Pages: [1] 2 »
|
I submitted my form 72 hours ago. No bitcoins. I'm really, really pissed. There is no way to contact them at all. Their website just has their statements and their claim form.
When I try to log in now, it says "your balance is zero." (your bitcoins have been claimed).
From what I can see they're basically doing the bare minimum required to stop the community coming after them and nothing more. You're quite likely never to see any of your bitcoins again. I know. Frankly, I don't know why "they" bothered. It's not like anyone can find "them," right? |
|
|
|
When I try to log in now, it says "your balance is zero." (your bitcoins have been claimed).
Anyone else get this message?
That's the message you get when your claim has been submitted, whether or not your balance ever reaches you. |
|
|
|
Bitcoins have entered the Void.
I doubt it. But the MyBitcoin database now has the wrong balance for my account, of course. Grr. |
|
|
|
|
Ok, this is partly UI trouble, but it's blocking my claim now, permanently. Yes, I'm aware that MyBitcoin originally truncated the password, this is not the root cause of my problem at the moment. Before the claim, when I re-installed 1Password after the Mac OS X Lion update, the default behavior is to auto submit the form after filling in the username and password.
Basically, I had 1Password fill in the claim form authentication. But it automatically submitted the form right away. Right before it submitted, it filled in my username as the claim address. Now it says my balance is zero.
|
|
|
|
|
MacBook Pro (6,2 NVIDIA GeForce GT 330M), Snow Leopard, -f 1 -w 64
7845 khash/s
|
|
|
|
All the information gathering you mentioned above did not come from the bitcoin network. You are referring to common browser and user security weaknesses. Let's assume that a user is not revealing personal information on a channel outside of the bitcoin network. Maybe they are using Tor (and turning off cookies). Or maybe they place an ad in the newspaper with their bitcoin address.
What might someone be able to learn about this bitcoin address I saw in a recent newspaper classified ad: 1N9vKDweKCF9Yibapky7UmqRJ8PKgnvM2s
I'm fairly technical and I feel confident you cannot learn anything about the bitcoin client that is receiving bitcoins at that address.
http://blockexplorer.com/address/1N9vKDweKCF9Yibapky7UmqRJ8PKgnvM2s |
|
|
|
Hi, is anyone of you able to build a statically linked version of the bitcoin-pool server? I found a static one of the client but not of the server. The reason is I GAVE UP!  I tried compiling the sources since the last weekend without success. As soon as I solved an issue the next one was rising up. The machine on which I like to use the server is 64 bits Ubuntu 8.04. But, just as a sidenote, I also tried to build it on Ubuntu 10.10 32 Bits which doesn't work better. 73! Hey, jiffy, did you install ibdb4.8++-dev before trying to compile on Ubuntu 10.10? |
|
|
|
I think the MyBitcoin address problem will be solved. As I mentioned, I gave MyBitcoin more details. His reply: Hello,
We are aware of the problem. It's actually a bug in Bitcoin's JSON RPC facility.
We are working on a solution. Once we have one we will release patches to the Bitcoin community.
I'll keep you posted.
Tom |
|
|
|
Thanks, BitLex & doublec!
Sounds like a MyBitcoin problem.
I have the same problem using a MyBitcoin address. I reported a problem to them, and got this reply: Hello,
The MyBitcoin addresses work exactly the same as regular Bitcoin addresses.
So, if you "generate on them" you should see a deposit on your MyBitcoin account.
I hope that helps.
Tom So I got more specific with them and sent the block explorer info, the amount I was expecting, as well as the address that should have the credit. I'll report back what they say. |
|
|
|
|
So if enough people switch to the new client, could that theoretically increase the capacity of the server due to fewer TCP connections?
|
|
|
|
Ok, I think I see the address I might have used for testing a while back. Wow, this pool really does remember everyone who contributes.  |
|
|
|
|
The pool mining service just happens to run on the same machine. But the payment address did not come from the client in question.
And besides, I wouldn't expect the pool mining service to cause any "Generated" message in anyone's client. Wouldn't it just come in as a regular payment?
Is there a keyword I should look for in Bitcoin.app debug.log file?
|
|
|
|
It's been a long time since I've generated any bitcoins on my Mac, and that's one thing. I understand it has to do with difficulty index and popularity. Stuff like that. But I don't know what to make of this: http://cl.ly/0p3e1G083o2k2d3Y0z3UI'm on Bitcoin 0.3.17 (Mac). |
|
|
|
@FairUser asked a very good question and I'm glad he did. It took me a few days to discern the rules by observation. Since this is totally experimental, not to mention donation driven, I wanted to just watch and learn. I really appreciate all the effort @doublec put into this, to just let us pound away at this. |
|
|
|
Ok! Everybody back in the pool!  |
|
|
|
|
For the CUDA miner arguments, I can see what -gpu=X values might be as well as -aggression=X, and perhaps -gputhreads=X is obvious. But what would go in -gpugrid=X?
|
|
|
|
|
That is the problem. He didn't have the developer drivers. Now it's working. I'm getting ~5600 khash/s. He's getting ~2700 khash/s.
|
|
|
|
|
