yes except: why the fuck would they do #1 in the first place?
Because they're only allowed to withdraw $1000 worth of BTC per day. The lower the price of BTC, the more you can withdraw. |
|
|
|
|
Surely the correct order is:
1. sell a lot of bitcoins, driving the price to $0.01
2. withdraw $1000 worth of bitcoins. that's 100,000 BTC
3. buy a lot of bitcoins, driving the price back to $13
now the $1000 worth of bitcoins you withdrew are now worth $1.3 million.
I wonder if that's what happened.
|
|
|
|
You can check your own password by giving this line to perl: print('password', '$1$salt');where password is your password and salt is the characters between $1$ and the next $ in your encrypted passord. I think you typo'ed that. My line in the accounts file is: 1449,dooglus,dooglus@gmail.com,$1$WFHWAF9p$T/WxZez30/WCigLRwB2eQ/
and to check my password, I do this in Perl: print(crypt('myguess', '$1$WFHWAF9p'));
That comes back with '$1$WFHWAF9p$mQTG1Teo6ojeuyXRYN7Na.' and so my password isn't 'myguess'. |
|
|
|
The front page of mtgox is redirecting to something showing this now: UPDATE REGARDING LEAKED ACCOUNT INFORMATIONS
We will address this issue too and prevent logins from each users. Leaked information includes username, email and hashed password, which does not allow anyone to get to the actual password, should it be complex enough. If you used a simple password you will not be able to login on Mt.Gox until you change your password to something more secure. If you used the same password on different places, it is recommended to change it as soon as possible.
It also says "One account with a lot of coins was compromised" and "Apart from this no account was compromised, and nothing was lost". If that's true, how did everyone's password hashes end up on the Internet for public download? Something fishy is going on. |
|
|
|
I use http://mtgoxlive.com/ for a more short term market depth + recent trades overview if I feel the urge to put up a few orders gefore going to bed... I don't understand that graph. It's kind of cool, and I hadn't seen it before, but the left axis goes from 0 to 7000BTC while the right axis goes from 0 to $900k. What does it mean? For 7k BTC to be $900k we'd need bitcoins to be worth over $100 each. Also, why does the brown line stop before hitting the edge? I'd expect there to be enough buy orders for tiny amounts to push the line off the edge of the graph. |
|
|
|
|
I think the addr.dat file in your .bitcoin/ folder is a database of known peers, with details of how recently they communicated with you, etc. It's used to reconnect to peers that you were using last time you ran the client, and appeared to work pretty well last time I looked into it.
One thing I have found that really significantly increases the number of peers I connect to is to forward the bitcoin port (TCP port 8333) on my router to my computer. That way hosts which don't have the port forwarded on their router can connect to you. If neither you nor the remote host have the port forwarded, you'll never be able to connect to each other.
|
|
|
|
|
I've done a very small amount of work on the code, and I have a very small number of bitcoins. 42.43 to be precise.
One of those I received as an anonymous donation, presumably for the work I did (my address is 1Ed62ZfuPzT9jeD4ZtbaiFtKVUsoD34JoD ), 40 I bought for about $15, and most of the rest I mined on an old CPU over a month or so.
Oh, and I have about 11 bitcents on betco.in where I play micro stakes poker.
|
|
|
|
|
I'm retiring from my career in bitcoin mining.
I've been working flat out for a few weeks now and have finally managed to mine a whole coin.
Thanks slush for making this possible - I think I'd have been waiting a long long time to get my first coin without your help.
Please feel free to do whatever you like with the 0.00763751 BTC remaining in my mining pool account.
Na zdravi.
Chris.
|
|
|
|
Currently, its master branch mirrors the GitHub one, but with a few bugfixes I added. This ( http://gitorious.org/bitcoin/bitcoin/commit/c16b9402673cf7376c81cad4fe00fc2099e790a8) doesn't look like a bug fix: - int64 nAmount = roundint64(dAmount * 100.00) * CENT;
+ int64 nAmount = (int64)(dAmount * (double)COIN); It looks like removing a feature that was deliberately added. You should open a thread on the forum to discuss whether being able to make sub-cent payments using the RPC interface is something most people want. Chris. |
|
|
|
|
why not?
1DVEak5a6WbzXqZM2ruVwmTyvjYWAHj7gs
|
|
|
|
And it would be fantastic to get somebody who knows, or is willing to learn, git to step up and volunteer to submit translation file patches.
I know git, and have time on my hands (as evidenced by the number of typo corrections I've made recently in the wiki...). I'd be willing to submit translation file patches if it doesn't require me being able to speak languages other than English... Let me know what you need. I'll soon be asking for building and testing help, too (after fixing another couple of bugs, I think it'll be time to pull non-controversial patches into the integration tree and start some serious testing to prepare for another release).
I only have Ubuntu on the computers here, but have various versions (10.04, 10.10, 11.04 pre-release) so can build and test on those. In the mean time I'll take a look at the bug list and see if there's anything I can work on. I have a fair bit of C++ experience, but am quite new to Bitcoin. |
|
|
|
|
Approx. cluster performance: 20349.286848 Mhash/s
|
|
|
|
I regularly get a crash when running 2 threads, and never when running one. I'm using the current git version, which claims to be "minerd version 0.5". The crash looks like this: $ ~/Programs/cpuminer/minerd --algo cryptopp_asm32 --threads 2 --url http://mining.bitcoin.cz:8332 --userpass user.worker:password
2 miner threads started, using SHA256 'cryptopp_asm32' algorithm.
[...]
HashMeter(1): 16777216 hashes, 569.79 khash/sec
HashMeter(0): 16777216 hashes, 447.54 khash/sec
*** longjmp causes uninitialized stack frame ***: /home/chris/Programs/cpuminer/minerd terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x50)[0xb7625cc0]
/lib/libc.so.6(+0xe5c2a)[0xb7625c2a]
/usr/lib/libcurl-gnutls.so.4(+0x8b18)[0xb76c4b18]
[0xb7726400]
/home/chris/Programs/cpuminer/minerd[0x8049956]
/lib/libc.so.6(__libc_start_main+0xe6)[0xb7556ce6]
/home/chris/Programs/cpuminer/minerd[0x8048e61]
======= Memory map: ========
08048000-08054000 r-xp 00000000 08:01 158243 /home/chris/Programs/cpuminer/minerd
08054000-08055000 r--p 0000b000 08:01 158243 /home/chris/Programs/cpuminer/minerd
08055000-08056000 rw-p 0000c000 08:01 158243 /home/chris/Programs/cpuminer/minerd
083e9000-0842b000 rw-p 00000000 00:00 0 [heap]
b61eb000-b6205000 r-xp 00000000 08:01 51253 /lib/libgcc_s.so.1
b6205000-b6206000 r--p 00019000 08:01 51253 /lib/libgcc_s.so.1
b6206000-b6207000 rw-p 0001a000 08:01 51253 /lib/libgcc_s.so.1
b6220000-b6221000 ---p 00000000 00:00 0
b6221000-b6a21000 rw-p 00000000 00:00 0
b6a21000-b6a25000 r-xp 00000000 08:01 17645 /lib/libnss_dns-2.12.2.so
b6a25000-b6a26000 r--p 00003000 08:01 17645 /lib/libnss_dns-2.12.2.so
b6a26000-b6a27000 rw-p 00004000 08:01 17645 /lib/libnss_dns-2.12.2.so
b6a27000-b6a29000 r-xp 00000000 08:01 2648 /lib/libnss_mdns4_minimal.so.2
b6a29000-b6a2a000 r--p 00001000 08:01 2648 /lib/libnss_mdns4_minimal.so.2
b6a2a000-b6a2b000 rw-p 00002000 08:01 2648 /lib/libnss_mdns4_minimal.so.2
b6a2b000-b6a35000 r-xp 00000000 08:01 21674 /lib/libnss_files-2.12.2.so
b6a35000-b6a36000 r--p 00009000 08:01 21674 /lib/libnss_files-2.12.2.so
b6a36000-b6a37000 rw-p 0000a000 08:01 21674 /lib/libnss_files-2.12.2.so
b6a37000-b6a38000 ---p 00000000 00:00 0
b6a38000-b723a000 rw-p 00000000 00:00 0
b723a000-b723c000 r-xp 00000000 08:01 1046 /lib/libkeyutils.so.1.3
b723c000-b723d000 r--p 00001000 08:01 1046 /lib/libkeyutils.so.1.3
b723d000-b723e000 rw-p 00002000 08:01 1046 /lib/libkeyutils.so.1.3
b723e000-b7240000 r-xp 00000000 08:01 14733 /lib/libdl-2.12.2.so
b7240000-b7241000 r--p 00001000 08:01 14733 /lib/libdl-2.12.2.so
b7241000-b7242000 rw-p 00002000 08:01 14733 /lib/libdl-2.12.2.so
b7242000-b7245000 r-xp 00000000 08:01 581 /lib/libgpg-error.so.0.8.0
b7245000-b7246000 r--p 00002000 08:01 581 /lib/libgpg-error.so.0.8.0
b7246000-b7247000 rw-p 00003000 08:01 581 /lib/libgpg-error.so.0.8.0
b7247000-b7248000 rw-p 00000000 00:00 0
b7248000-b7257000 r-xp 00000000 08:01 270737 /usr/lib/libtasn1.so.3.1.9
b7257000-b7258000 r--p 0000e000 08:01 270737 /usr/lib/libtasn1.so.3.1.9
b7258000-b7259000 rw-p 0000f000 08:01 270737 /usr/lib/libtasn1.so.3.1.9
b7259000-b725f000 r-xp 00000000 08:01 265677 /usr/lib/libkrb5support.so.0.1
b725f000-b7260000 r--p 00005000 08:01 265677 /usr/lib/libkrb5support.so.0.1
b7260000-b7261000 rw-p 00006000 08:01 265677 /usr/lib/libkrb5support.so.0.1
b7261000-b7263000 r-xp 00000000 08:01 2180 /lib/libcom_err.so.2.1
b7263000-b7264000 r--p 00001000 08:01 2180 /lib/libcom_err.so.2.1
b7264000-b7265000 rw-p 00002000 08:01 2180 /lib/libcom_err.so.2.1
b7265000-b7286000 r-xp 00000000 08:01 264676 /usr/lib/libk5crypto.so.3.1
b7286000-b7287000 r--p 00021000 08:01 264676 /usr/lib/libk5crypto.so.3.1
b7287000-b7288000 rw-p 00022000 08:01 264676 /usr/lib/libk5crypto.so.3.1
b7288000-b7330000 r-xp 00000000 08:01 265623 /usr/lib/libkrb5.so.3.3
b7330000-b7335000 r--p 000a8000 08:01 265623 /usr/lib/libkrb5.so.3.3
b7335000-b7336000 rw-p 000ad000 08:01 265623 /usr/lib/libkrb5.so.3.3
b7336000-b7337000 rw-p 00000000 00:00 0
b7337000-b734c000 r-xp 00000000 08:01 262572 /usr/lib/libsasl2.so.2.0.23
b734c000-b734d000 r--p 00015000 08:01 262572 /usr/lib/libsasl2.so.2.0.23
b734d000-b734e000 rw-p 00016000 08:01 262572 /usr/lib/libsasl2.so.2.0.23
b734e000-b735f000 r-xp 00000000 08:01 23646 /lib/libresolv-2.12.2.so
b735f000-b7360000 r--p 00010000 08:01 23646 /lib/libresolv-2.12.2.so
b7360000-b7361000 rw-p 00011000 08:01 23646 /lib/libresolv-2.12.2.so
b7361000-b7363000 rw-p 00000000 00:00 0
b7363000-b73d4000 r-xp 00000000 08:01 1042 /lib/libgcrypt.so.11.5.3
b73d4000-b73d5000 r--p 00070000 08:01 1042 /lib/libgcrypt.so.11.5.3
b73d5000-b73d7000 rw-p 00071000 08:01 1042 /lib/libgcrypt.so.11.5.3
b73d7000-b7468000 r-xp 00000000 08:01 264937 /usr/lib/libgnutls.so.26.14.12
b7468000-b746c000 r--p 00090000 08:01 264937 /usr/lib/libgnutls.so.26.14.12
b746c000-b746d000 rw-p 00094000 08:01 264937 /usr/lib/libgnutls.so.26.14.12
b746d000-b7480000 r-xp 00000000 08:01 1852 /lib/libz.so.1.2.3.4
b7480000-b7481000 r--p 00012000 08:01 1852 /lib/libz.so.1.2.3.4
b7481000-b7482000 rw-p 00013000 08:01 1852 /lib/libz.so.1.2.3.4
b7482000-b74b0000 r-xp 00000000 08:01 265607 /usr/lib/libgssapi_krb5.so.2.2
b74b0000-b74b1000 r--p 0002d000 08:01 265607 /usr/lib/libgssapi_krb5.so.2.2
b74b1000-b74b2000 rw-p 0002e000 08:01 265607 /usr/lib/libgssapi_krb5.so.2.2
b74b2000-b74b3000 rw-p 00000000 00:00 0
b74b3000-b74ba000 r-xp 00000000 08:01 23648 /lib/librt-2.12.2.so
b74ba000-b74bb000 r--p 00006000 08:01 23648 /lib/librt-2.12.2.so
b74bb000-b74bc000 rw-p 00007000 08:01 23648 /lib/librt-2.12.2.so
b74bc000-b74fe000 r-xp 00000000 08:01 265686 /usr/lib/libldap_r-2.4.so.2.5.6
b74fe000-b74ff000 r--p 00041000 08:01 265686 /usr/lib/libldap_r-2.4.so.2.5.6
b74ff000-b7500000 rw-p 00042000 08:01 265686 /usr/lib/libldap_r-2.4.so.2.5.6
b7500000-b7501000 rw-p 00000000 00:00 0
b7501000-b750c000 r-xp 00000000 08:01 265727 /usr/lib/liblber-2.4.so.2.5.6
b750c000-b750d000 r--p 0000a000 08:01 265727 /usr/lib/liblber-2.4.so.2.5.6
b750d000-b750e000 rw-p 0000b000 08:01 265727 /usr/lib/liblber-2.4.so.2.5.6
b750e000-b753e000 r-xp 00000000 08:01 262982 /usr/lib/libidn.so.11.6.1
b753e000-b753f000 r--p 0002f000 08:01 262982 /usr/lib/libidn.so.11.6.1
b753f000-b7540000 rw-p 00030000 08:01 262982 /usr/lib/libidn.so.11.6.1
b7540000-b769a000 r-xp 00000000 08:01 14730 /lib/libc-2.12.2.so
b769a000-b769b000 ---p 0015a000 08:01 14730 /lib/libc-2.12.2.so
b769b000-b769d000 r--p 0015a000 08:01 14730 /lib/libc-2.12.2.so
b769d000-b769e000 rw-p 0015c000 08:01 14730 /lib/libc-2.12.2.so
b769e000-b76a2000 rw-p 00000000 00:00 0
b76a2000-b76b8000 r-xp 00000000 08:01 23645 /lib/libpthread-2.12.2.so
b76b8000-b76b9000 r--p 00015000 08:01 23645 /lib/libpthread-2.12.2.so
b76b9000-b76ba000 rw-p 00016000 08:01 23645 /lib/libpthread-2.12.2.so
b76ba000-b76bc000 rw-p 00000000 00:00 0
b76bc000-b7708000 r-xp 00000000 08:01 262488 /usr/lib/libcurl-gnutls.so.4.2.0Aborted |
|
|
|
Thanks for answering my questions. it is performance optimization, because it's not possible to ask databaase 100x per second to check worker's login/password. So I plan to add periodic reload of those credentials, but even then it will take some time until credentials loaded in memory expire...
Perhaps it would be better to update the in-memory credentials for just that worker at the same time as you update the password in the database. Then you don't need the periodic reload. By the way, I looked at your location on the bitcoin map as you suggested. I used to stand right there regularly waiting for the tramvaj home to Strasnicka. But now I'm living in Canada, so coming to "pay you a visit" for being "a scammer" isn't really an option. I don't think the 0.002 BTC you "owe me" would pay for the plane ticket. Yet. Chris. |
|
|
|
On http://mining.bitcoin.cz/home/ is says: "Shares do not carry over from one block to the next. When the pool mints a block, only users who worked on that block are rewarded, and only for work they did on that block." but that doesn't seem to be the case. I am getting rewarded for all blocks I contribute shares to, not only the ones the pool mints. It seems that the server counts up all the shares in the current round, not just the current block. The distinction being that a round lasts until we mint a block. Sometimes over 20 blocks are minted by others before we get to mint one, but all the shares I contribute in the mean time also get rewarded. |
|
|
|
|
--quiet works
-q doesn't
That's the bug I was reporting.
Similarly with -r.
|
|
|
|
|
I tried changing the password for one of my workers. The new password is displayed on the website, but the original password is still required when running the miner. I even tried deleting the worker and recreating it with the new password, but the original password is still required. Eventually I had to make a worker with a different name to get the password changed.
Also, is it possible to change my account password, as opposed to the worker passwords?
Thanks.
Chris.
|
|
|
|
The available options don't match the help text. For instance: $ ./minerd -q
./minerd: invalid option -- 'q'
minerd version 0.5
Usage: minerd [options]
Supported options:
[...]
(-q) Disable per-thread hashmeter output (default: off)
-r doesn't work either. Chris. |
|
|
|
|
Show Posts
