Bitcoin has a file in it's data directory called addr.dat, which contains a list of all IP addresses you've previously connected to. Providing that your clock is now correct, it looks like the cache of previously used addresses is bad. I would delete the addr.dat file to bootstrap your client again. You can also remove the command line options and any bitcoin.conf config file you created. When you run Bitcoin, make sure the "Connect through socks4 proxy" is not selected, some users mess with this not understanding what it does.
I think I narrowed it down to a client corruption somewhere, but if reinstalling bitcoin (which AFAIK does not change addr.dat) worked, I think addr.dat is not involved. I don't have the technology to run md5sums or something on my executables, so I can't prove any of this. But what happened is what happen ed and I shouldn't worry too much about it. |
|
|
|
|
Ah, whatever, I'll participate. 12umu11g2SnwtSioa3GiUya7bvehRJQUAB
|
|
|
|
Now, that was the first post I ever made you replied to  . This type of problem seems to be caused by a corrupt bitcoin installation, according to a certain Bitcoin developer: The "lastseen" value of the nodes your client knows about is 65000 hours in the future. My guess is that your system clock is set to somewhere in 2005.
Still, the client should warn you about this instead of having this erratic behavior.
(note: my clock is not set to 2005; therefore the client is broken). I don't know what could be causing client problems, and it certainly is a problem only I have had. Both times, reinstalling Bitcoin worked perfectly (the first time by accident, so I thought little of it). |
|
|
|
The current market cap for I0Coin is merely 150 BTC in that case. A question; has the I0Coin block reward halved yet? Apparently 50 blocks ago it was 210000.
It halves at 218,750. What is the reason for selecting such a number, rather than Bitcoin's round 210000? Is it because I0Coin generates blocks faster? |
|
|
|
hmm, as the coin though that I designed been put into the client? I guess no one is pushing i0coins anymore, now they aren't doing that great. http://allchains.info/106 gigahash But its from merge mining, I think merge mining made everyone have a lot of it, and now its not worth anything. Namecoin used to be 0.03, after merged mining it became 0.004, so it seems merge mining drops the value a lot. The only value i read for i0coin atm is 0.00002 at https://www.vircurex.com/main/index. which is like 500K for 10btc, its not worth much. The current market cap for I0Coin is merely 150 BTC in that case. A question; has the I0Coin block reward halved yet? Apparently 50 blocks ago it was 210000. |
|
|
|
|
Interesting charts you have there, chodpada. The Price/$ Volume somewhat scares me: it indicates the dollars pumped into the market since the June 2011 peak is close to 8 times the amount that brought Bitcoin to that peak. Is this interpretation correct, or am I missing something?
|
|
|
|
Thanks to Bitclockers, Bitlc.net, Bitcoin.cz, BitMinter, pool.itzod.ru, BTC Guild and ozco.in for supporting BIP 16
What about slush? Emphasis mine. |
|
|
|
I want OHLC (Open, High, Low, Close) format like you can download from Yahoo! Finance or any other financial data site.
Isn't this already in the bitcoincharts? |
|
|
|
Thanks for all the help guys. Bitcoin is running smooth again!  That's 8 connections!I don't what exactly fixed it, but it was either the reinstall or the addr.dat corruption. |
|
|
|
Can someone verify the following steps are safe? - Uninstall Bitcoin
- Delete addr.dat
- Reinstall Bitcoin
- Run bitcoin with addnode=bitcoin.es
|
|
|
|
There is no risk, your client will verify the whole block chaianyway, no matter where it gets it from.
Looks to me like there's some serious networking issue on your end. Are you able to browse the web with that machine at all?
Yes, I am able to browse the web with that machine. And I'm not talking about a block chain attack, but an isolation attack. |
|
|
|
I tried addnode=46.182.18.245, the first on on fallback which was supposedly up. The issue is resolved now! The -dns -addnode=bitcoin.es resolved it:  Thanks for your help! (edit): Though, I sort of feel uneasy about having only one connection. Isn't this an attack vector for the one person I'm connecting to? |
|
|
|
As I mentioned in the OP, the debug file is full of IRC this and IRC that. Here is a freshly generated one: Bitcoin version 0.5.2-beta
Default data directory C:\Users\<redacted>\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open strLogDir=C:\Users\<redacted>\AppData\Roaming\Bitcoin/database strErrorFile=C:\Users\<redacted>\AppData\Roaming\Bitcoin/db.log
Loaded 111056 addresses
addresses 1728ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000000000007f407fd height=165105
block index 7192ms
Loading wallet...
nFileVersion = 50200
fGenerateBitcoins = 0
nTransactionFee = 0
fMinimizeToTray = 1
fMinimizeOnClose = 1
fUseProxy = 0
addrProxy = 127.0.0.1:9050
fUseUPnP = 0
wallet 141ms
Done loading
mapBlockIndex.size() = 165127
nBestHeight = 165105
setKeyPool.size() = 100
mapWallet.size() = 85
mapAddressBook.size() = 43
Bound to port 8333
02/03/12 02:45 RandAddSeed() 236236 bytes
02/03/12 02:45:21 sending: version (85 bytes)
addrLocalHost = 192.168.1.108:8333
ThreadIRCSeed started
ThreadDNSAddressSeed started
ThreadSocketHandler started
Loading addresses from DNS seeds (could take a while)
ThreadMessageHandler started
ThreadOpenConnections started
AddAddress(78.46.244.171:8333)
AddAddress(108.40.82.240:8333)
IRC :irc.lechat.ir NOTICE AUTH :*** Looking up your hostname...
trying connection 174.97.136.86:8333 lastseen=65541.0hrs lasttry=-368954.8hrs
IRC :irc.lechat.ir NOTICE AUTH :*** Found your hostname
IRC SENDING: NICK x75187980
IRC SENDING: USER x75187980 8 * : x75187980
IRC :irc.lechat.ir 001 x75187980 :Welcome to the LFNet Internet Relay Chat Network x75187980
IRC :irc.lechat.ir 002 x75187980 :Your host is irc.lechat.ir[193.107.204.22/6667], running version hybrid-7.2.3
IRC :irc.lechat.ir 003 x75187980 :This server was created Jun 29 2011 at 17:30:40
IRC :irc.lechat.ir 004 x75187980 irc.lechat.ir hybrid-7.2.3 CDGabcdfgiklnorsuwxyz biklmnopstveI bkloveI
AddAddress(76.178.146.91:8333)
AddAddress(146.229.116.229:8333)
AddAddress(81.43.251.160:8333)
AddAddress(62.78.44.253:8333)
AddAddress(94.125.248.245:8333)
AddAddress(69.246.253.155:8333)
AddAddress(74.207.231.186:8333)
IRC SENDING: USERHOST x75187980
66 addresses found from DNS seeds
ThreadDNSAddressSeed exiting
IRC :irc.lechat.ir 302 x75187980 :x75187980=+x75187980@99.236.60.25
GetIPFromIRC() got userhost 99.236.60.25
GetIPFromIRC() returned 99.236.60.25
IRC SENDING: NICK u6cbyJzEGSa4qJC
IRC SENDING: JOIN #bitcoin64
IRC SENDING: WHO #bitcoin64
IRC got join
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(108.211.237.163:8333)
IRC got new address: 108.211.237.163:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(84.49.105.149:8333)
IRC got new address: 84.49.105.149:8333
IRC got who
AddAddress(80.1.160.194:8333)
IRC got new address: 80.1.160.194:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(83.160.111.199:8333)
IRC got new address: 83.160.111.199:8333
IRC got who
AddAddress(2.120.228.144:8333)
IRC got new address: 2.120.228.144:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(68.230.212.139:8333)
IRC got new address: 68.230.212.139:8333
IRC got who
IRC got who
AddAddress(108.208.208.23:8333)
IRC got new address: 108.208.208.23:8333
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(180.183.188.191:8333)
IRC got new address: 180.183.188.191:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(70.176.200.53:8333)
IRC got new address: 70.176.200.53:8333
IRC got who
AddAddress(78.108.106.180:8333)
IRC got new address: 78.108.106.180:8333
IRC got who
IRC got who
AddAddress(113.170.37.47:8333)
IRC got new address: 113.170.37.47:8333
IRC got who
IRC got who
IRC got who
AddAddress(66.68.10.240:8333)
IRC got new address: 66.68.10.240:8333
IRC got who
IRC got who
IRC got who
AddAddress(128.113.152.79:8333)
IRC got new address: 128.113.152.79:8333
connection timeout
trying connection 89.253.186.190:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 70.245.188.82:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 98.247.166.0:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 60.242.242.214:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
IRC got join
connection timeout
trying connection 188.27.201.67:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 184.145.154.137:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 69.251.191.143:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 218.212.75.155:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.134.93.44:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 98.235.160.96:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.23.198.59:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 24.229.80.54:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 196.209.225.4:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 108.12.78.239:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 79.232.109.153:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 188.2.62.21:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 69.166.26.247:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 88.206.160.2:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 24.14.215.107:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 81.101.6.185:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 99.252.0.73:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 68.115.73.64:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 98.19.59.47:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.180.27.189:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 109.197.69.58:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 92.247.106.5:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.82.107.221:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 94.217.231.140:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 87.104.14.134:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 208.125.16.50:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 208.88.251.119:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 110.168.89.194:8333 lastseen=65540.9hrs lasttry=-368954.8hrs
connection timeout
trying connection 46.237.78.6:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 94.19.74.20:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 195.218.190.37:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 92.255.237.79:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
The one I had previously is very big, and also full of these connection timeout things. |
|
|
|
I'm thinking about building a mining rig or to just buy bitcoins, seems that buying bitcoin at these low prices is the way to go? say I have 3200 to build a system and get 2600Mhash I can only generate 700 bitcoins a year. if I spend 3200 to buy bitcoins say at these price I can buy 500 bitcoins. which is more risky?
At this point, you won't have a year to generate those bitcoins. This phenomenon has occured before: the price now is 20% of that in 2011-06 but the difficulty is 200%. In ten months, the mining revenue will effectively halve, and the difficulty may still increase. I would suggest purchasing the bitcoins now, unless you have a way of creating a very efficient rig. |
|
|
|
Take the first photo.
Run md5sum on it.
Print out the hash.
Include the printout in the second photo.
Photochain.
Nope, because you could still edit the photo and change printed hash before running md5 on that file. It all boils down to having a way to prove that photo has not been edited since taking a shot, but how to achieve that, I do not know. OP's original idea is not bad and definitely works, but is quite cumbersome. By the way, how cool would be to have image showing md5 hash, exact hash of that given image file? You can edit the first file all you want but the only way to get that hash into the second photo is if those edits are done first. That was the given criteria. You could also publish the hash so that you have the first photo locked in without having to reveal the photo. Publishing the hash first is exactly what the OP proposed. No system like this is completely malice-proof, as one could use superior photoshopping skills to "glue" the photo of a newspaper/md5 hash with the after photo, even if the after photo was taken before. Error-level analysis effectly debunks this for JPEG files, however PNG files can be faked this way. |
|
|
|
Yeah, the exception for bitcoin-qt is still there (I had to correct that from bitcoin.exe a while ago). All outgoing ports are open on my router (for security reasons, I think most incoming ports are blocked). As for ISP, I hope they're not blocking it; that would ruin the decentralized nature of Bitcoin. Just to make sure, I tested it on that link anyways: Firebind Ports:8333
Status: 100.0%
Passed: 8333
Result: Test Successful. None of the tested ports are blocked.
|
|
|
|
|
So, my bitcoin client has ran out of connections recently. The debug file is full of IRC this and IRC that, but there hasn't been any nodes connecting even once to my client. I tried running it with the "addnode=", but all that does is start bitcoin with 0 connections, without even an error message. I'm running 0.5.2 on Windows 7. Can someone help me with this?
|
|
|
|
|
I'll just add that in Look and Layout preferences one can choose to not see other's signatures, if you find them obnoxious.
|
|
|
|
|
I don't see how controlling many bitcoinica accounts would help. You can have many positions on one account.
|
|
|
|
By the way, how cool would be to have image showing md5 hash, exact hash of that given image file?
This is simply impossible unless a preimage attack against md5 is developed. Theoretically you could pick up random hash, slap it onto image and then adjust various pixels, exiff data, compression, until you get matching hash. It takes immense computational power, so it's infeasible with today's technology, and frankly quite pointless. But to present such image, it would make few nerdgasms worldwide =) That is a preimage attack. |
|
|
|
|
Show Posts
