Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Author

Topic: bitcoind starts from the very first block instead of continuing (Read 927 times)

DrakonX
jr. member
Activity: 99
Merit: 4
bitcoind starts from the very first block instead of continuing
September 05, 2017, 03:23:44 AM
#17
After the mentioned reinstallation of the whole system, bitcoind is working now as aspected. I now have a newer version, though I can't say which one. Didn't find another way to get it work. Thank you for your appreciated help, jackg.
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
September 03, 2017, 12:47:46 PM
#16
Quote from: DrakonX on September 03, 2017, 12:28:33 PM
I installed Raspbian from scratch and now I am at the point to start the client. I also coppied the so far grown blockchain into the corresponding folder. Suddenly I'm wondering if I used the right command:
Code:
bitcoind -daemon

Shortly I saw an example where the user startet bitcoind with the following command:
Code:
MALLOC_ARENA_MAX=1 bitcoind -daemon -blocksonly -dbcache=200 -maxconnections=50 -maxorphantx=5 -maxmempool=5

This doesn't seem to me to be a valid linux command though, but I'd like to know what it does if any. What is the correct way to start bitcoind?

I think dbcache is to do with RAM usage and orphaned txs are relating to the txs that haven't yet been confirmed and being broadcast by the node (presumably but a bit more information on that command by someone else would be helpful).
Max connections is the total of the incoming connections+ outgoing connections and is used so it is more difficult to overload the node.

If bitcoind -daemon works, and I've seen that being used then it's probably correct. What you want to look out for is using the correct way to end it so you don't get a corrupted blockchain.

All the comands you can use will be listed in bitcoind -help.
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
September 03, 2017, 12:28:33 PM
#15
I installed Raspbian from scratch and now I am at the point to start the client. I also coppied the so far grown blockchain into the corresponding folder. Suddenly I'm wondering if I used the right command:
Code:
bitcoind -daemon

Shortly I saw an example where the user startet bitcoind with the following command:
Code:
MALLOC_ARENA_MAX=1 bitcoind -daemon -blocksonly -dbcache=200 -maxconnections=50 -maxorphantx=5 -maxmempool=5

This doesn't seem to me to be a valid linux command though, but I'd like to know what it does if any. What is the correct way to start bitcoind?
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
August 29, 2017, 10:14:06 AM
#14
Quote from: DrakonX on August 29, 2017, 05:31:38 AM
In order to check the node do I need the many entries with the ip-adresses? Can't see any hostname within the log.

I don't have any anti-virus app running. But I had one once I started the download process under my windows system. Nevertheless this can't be an issue since I deleted the whole .bitcoin directory from my linux system and startet the rebuild from scratch.

Do I have to upgrade the bitcoin app because I have an outdatet one? Does the following (extracted from the log) help?

Code:
Bitcoin version 0.3.24-beta
Default data directory /home/pi/.bitcoin
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=/home/pi/.bitcoin/database strErrorFile=/home/pi/.bitcoin/$
Loaded 11071 addresses
dbenv.open strLogDir=/home/pi/.bitcoin/database strErrorFile=/home/pi/.bitcoin/$
Loaded 11071 addresses
 addresses              3710ms
Loading block index...
LoadBlockIndex(): hashBestChain=000000000000590e3054  height=124275
 block index          135840ms
Loading wallet...
nFileVersion = 32400
fGenerateBitcoins = 0
nTransactionFee = 0
addrIncoming = 255.255.255.255:8333
fMinimizeToTray = 0
fMinimizeOnClose = 0
fUseProxy = 0
addrProxy = 127.0.0.1:9050
 wallet                  108ms
Done loading
mapBlockIndex.size() = 124776
nBestHeight = 124275
mapBlockIndex.size() = 124776
nBestHeight = 124275
mapKeys.size() = 101
setKeyPool.size() = 100
mapPubKeys.size() = 101
mapWallet.size() = 0
mapAddressBook.size() = 1
Loading addresses from DNS seeds (could take a while)
AddAddress(162.243.194.210:8333)
AddAddress(96.2.103.25:8333)
AddAddress(68.48.214.241:8333)
AddAddress(173.69.49.106:8333)
AddAddress(94.226.111.26:8333)
AddAddress(99.242.230.163:8333)
AddAddress(76.111.96.126:8333)
AddAddress(97.117.255.48:8333)
AddAddress(198.38.93.227:8333)
AddAddress(50.177.196.160:8333)
AddAddress(209.208.110.92:8333)
AddAddress(50.177.196.160:8333)
AddAddress(209.208.110.92:8333)
AddAddress(94.136.40.82:8333)
AddAddress(120.55.171.74:8333)
AddAddress(163.172.228.191:8333)
AddAddress(67.207.80.143:8333)
AddAddress(83.135.91.173:8333)
AddAddress(217.23.6.148:8333)
AddAddress(70.162.92.2:8333)
AddAddress(202.133.115.115:8333)
AddAddress(142.4.214.187:8333)
AddAddress(5.196.65.205:8333)
AddAddress(46.4.120.75:8333)
AddAddress(84.84.3.32:8333)
AddAddress(213.174.156.73:8333)
AddAddress(212.24.105.41:8333)
35 addresses found from DNS seeds
sending: version (85 bytes)
ipv4 eth0: 192.168.178.71
sending: version (85 bytes)
ipv4 eth0: 192.168.178.71
addrLocalHost = 192.168.178.71:8333
ThreadRPCServer started
ThreadIRCSeed started
ThreadOpenConnections started
ThreadSocketHandler started
ThreadMessageHandler started
IRC :irc.smutfairy.com NOTICE * :*** Looking up your hostname
IRC :irc.smutfairy.com NOTICE * :*** Found your hostname
IRC SENDING: NICK x592110682
IRC SENDING: USER x592110682 8 * : x592110682
IRC :irc.smutfairy.com 001 x592110682 :Welcome to the LFNet Internet Relay Chat$
IRC :irc.smutfairy.com 002 x592110682 :Your host is irc.smutfairy.com[::/6667],$
IRC :irc.smutfairy.com 003 x592110682 :This server was created Sep 11 2015 at 1$
IRC :irc.smutfairy.com 004 x592110682 irc.smutfairy.com hybrid-8.2.8 DFGHRSWabc$
trying connection 184.144.78.195:8333 lastseen=-64.5hrs lasttry=-417778.4hrs
IRC SENDING: USERHOST x592110682
IRC :irc.smutfairy.com 302 x592110682 :[email protected]
IRC SENDING: USERHOST x592110682
IRC :irc.smutfairy.com 302 x592110682 :[email protected]
GetIPFromIRC() got userhost 87.158.40.102
GetIPFromIRC() returned 87.158.40.102
IRC SENDING: NICK u5vWP9k2ps34bL7
IRC SENDING: JOIN #bitcoin27
IRC SENDING: WHO #bitcoin27
connected 184.144.78.195:8333
sending: version (85 bytes)
IRC got join
IRC got who
received: version (101 bytes)
Added time data, samples 2, offset +0 (+0 minutes)
sending: verack (0 bytes)
sending: getaddr (0 bytes)
sending: getblocks (933 bytes)
version message: version 70002, blocks=482462
sending: addr (31 bytes)
received: verack (0 bytes)
sending: addr (31 bytes)
received: verack (0 bytes)
received: alert (168 bytes)
trying connection 137.74.30.99:8333 lastseen=-64.6hrs lasttry=-417778.4hrs
accepted alert 2147483647, AppliesToMe()=1
connected 137.74.30.99:8333
sending: version (85 bytes)
received: version (113 bytes)
Added time data, samples 3, offset +9 (+0 minutes)
sending: verack (0 bytes)
sending: getaddr (0 bytes)
sending: alert (168 bytes)
version message: version 70015, blocks=484083
received: verack (0 bytes)
received: alert (168 bytes)
cancelling alert 2147483647
accepted alert 2147483647, AppliesToMe()=1
received: ping (0 bytes)
received: addr (31 bytes)

Definitely update it. 0.3.24 is really old. It'll take much longer to reindex the blockchain.

Actually, once updating it, try running it and see if it contiues or reindexes on it's own, there may have been a fork somewhere that stopped your wallet being compatible.

When installing the new wallet, use the -updatewallet command first and save your 0.3.24 wallet.dat file and qt.exe file because you might need these if you run into a complication with the new wallet.
btctousd81
sr. member
Activity: 434
Merit: 270
Re: bitcoind starts from the very first block instead of continuing
August 29, 2017, 08:19:28 AM
#13
while starting bitcoind pass reindex parameter.
it will reindex the available blockchain files.

ref: https://bitcoin.stackexchange.com/questions/22199/what-exactly-did-bitcoin-qt-rescan-reindex-do
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 29, 2017, 05:31:38 AM
#12
In order to check the node do I need the many entries with the ip-adresses? Can't see any hostname within the log.

I don't have any anti-virus app running. But I had one once I started the download process under my windows system. Nevertheless this can't be an issue since I deleted the whole .bitcoin directory from my linux system and startet the rebuild from scratch.

Do I have to upgrade the bitcoin app because I have an outdatet one? Does the following (extracted from the log) help?

Code:
Bitcoin version 0.3.24-beta
Default data directory /home/pi/.bitcoin
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=/home/pi/.bitcoin/database strErrorFile=/home/pi/.bitcoin/$
Loaded 11071 addresses
dbenv.open strLogDir=/home/pi/.bitcoin/database strErrorFile=/home/pi/.bitcoin/$
Loaded 11071 addresses
 addresses              3710ms
Loading block index...
LoadBlockIndex(): hashBestChain=000000000000590e3054  height=124275
 block index          135840ms
Loading wallet...
nFileVersion = 32400
fGenerateBitcoins = 0
nTransactionFee = 0
addrIncoming = 255.255.255.255:8333
fMinimizeToTray = 0
fMinimizeOnClose = 0
fUseProxy = 0
addrProxy = 127.0.0.1:9050
 wallet                  108ms
Done loading
mapBlockIndex.size() = 124776
nBestHeight = 124275
mapBlockIndex.size() = 124776
nBestHeight = 124275
mapKeys.size() = 101
setKeyPool.size() = 100
mapPubKeys.size() = 101
mapWallet.size() = 0
mapAddressBook.size() = 1
Loading addresses from DNS seeds (could take a while)
AddAddress(162.243.194.210:8333)
AddAddress(96.2.103.25:8333)
AddAddress(68.48.214.241:8333)
AddAddress(173.69.49.106:8333)
AddAddress(94.226.111.26:8333)
AddAddress(99.242.230.163:8333)
AddAddress(76.111.96.126:8333)
AddAddress(97.117.255.48:8333)
AddAddress(198.38.93.227:8333)
AddAddress(50.177.196.160:8333)
AddAddress(209.208.110.92:8333)
AddAddress(50.177.196.160:8333)
AddAddress(209.208.110.92:8333)
AddAddress(94.136.40.82:8333)
AddAddress(120.55.171.74:8333)
AddAddress(163.172.228.191:8333)
AddAddress(67.207.80.143:8333)
AddAddress(83.135.91.173:8333)
AddAddress(217.23.6.148:8333)
AddAddress(70.162.92.2:8333)
AddAddress(202.133.115.115:8333)
AddAddress(142.4.214.187:8333)
AddAddress(5.196.65.205:8333)
AddAddress(46.4.120.75:8333)
AddAddress(84.84.3.32:8333)
AddAddress(213.174.156.73:8333)
AddAddress(212.24.105.41:8333)
35 addresses found from DNS seeds
sending: version (85 bytes)
ipv4 eth0: 192.168.178.71
sending: version (85 bytes)
ipv4 eth0: 192.168.178.71
addrLocalHost = 192.168.178.71:8333
ThreadRPCServer started
ThreadIRCSeed started
ThreadOpenConnections started
ThreadSocketHandler started
ThreadMessageHandler started
IRC :irc.smutfairy.com NOTICE * :*** Looking up your hostname
IRC :irc.smutfairy.com NOTICE * :*** Found your hostname
IRC SENDING: NICK x592110682
IRC SENDING: USER x592110682 8 * : x592110682
IRC :irc.smutfairy.com 001 x592110682 :Welcome to the LFNet Internet Relay Chat$
IRC :irc.smutfairy.com 002 x592110682 :Your host is irc.smutfairy.com[::/6667],$
IRC :irc.smutfairy.com 003 x592110682 :This server was created Sep 11 2015 at 1$
IRC :irc.smutfairy.com 004 x592110682 irc.smutfairy.com hybrid-8.2.8 DFGHRSWabc$
trying connection 184.144.78.195:8333 lastseen=-64.5hrs lasttry=-417778.4hrs
IRC SENDING: USERHOST x592110682
IRC :irc.smutfairy.com 302 x592110682 :[email protected]
IRC SENDING: USERHOST x592110682
IRC :irc.smutfairy.com 302 x592110682 :[email protected]
GetIPFromIRC() got userhost 87.158.40.102
GetIPFromIRC() returned 87.158.40.102
IRC SENDING: NICK u5vWP9k2ps34bL7
IRC SENDING: JOIN #bitcoin27
IRC SENDING: WHO #bitcoin27
connected 184.144.78.195:8333
sending: version (85 bytes)
IRC got join
IRC got who
received: version (101 bytes)
Added time data, samples 2, offset +0 (+0 minutes)
sending: verack (0 bytes)
sending: getaddr (0 bytes)
sending: getblocks (933 bytes)
version message: version 70002, blocks=482462
sending: addr (31 bytes)
received: verack (0 bytes)
sending: addr (31 bytes)
received: verack (0 bytes)
received: alert (168 bytes)
trying connection 137.74.30.99:8333 lastseen=-64.6hrs lasttry=-417778.4hrs
accepted alert 2147483647, AppliesToMe()=1
connected 137.74.30.99:8333
sending: version (85 bytes)
received: version (113 bytes)
Added time data, samples 3, offset +9 (+0 minutes)
sending: verack (0 bytes)
sending: getaddr (0 bytes)
sending: alert (168 bytes)
version message: version 70015, blocks=484083
received: verack (0 bytes)
received: alert (168 bytes)
cancelling alert 2147483647
accepted alert 2147483647, AppliesToMe()=1
received: ping (0 bytes)
received: addr (31 bytes)
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
August 26, 2017, 05:45:52 PM
#11
Quote from: DrakonX on August 26, 2017, 05:15:07 PM
Unfortunatly reindexing again didn't work. Strange seemed to me deleting the whole .bitcoin directory and starting over the sync process resulted in the same error at the same block 124,225.

This has happened quite a few times to other users but it's normaly further down the blockchain that the problem happens.
Do you have any antivirus installed, apparently that can cause problems with it quite early on.

Can you check the peer you're connected to to download it (you can find this in the debug.log file) and check it on here to check if the node has the entire blockchain on it or not?
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 26, 2017, 05:15:07 PM
#10
Unfortunatly reindexing again didn't work. Strange seemed to me deleting the whole .bitcoin directory and starting over the sync process resulted in the same error at the same block 124,225.
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
August 25, 2017, 03:40:08 PM
#9
Quote from: DrakonX on August 25, 2017, 02:03:56 PM
Thank you for your enduring help. This seems to become a never ending story. Sad

First, I got an error starting bitcoind with the reindex-command. (Took me some time to realize it must be executed while bitcoind isn't running.)
Code:
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ProcessMessage()
Ah yes, should probably have warned you on that one. It has to produce a "LOCK" on the directory where the data is stored when it starts and the lock doesn't finish until the program is closed.

Quote from: DrakonX on August 25, 2017, 02:03:56 PM
Second, I tried to copy some part from the log file:
Code:
sending getdata: tx 45f73fecb138bd5c8686
sending: getdata (37 bytes)
received: tx (258 bytes)
ERROR: ConnectInputs() : f14f401929 mapTransactions prev not found f105ab4368
ERROR: AcceptToMemoryPool() : ConnectInputs failed f14f401929
storing orphan tx f14f401929
received: tx (369 bytes)
ERROR: nonstandard txin: 0 304402202c56a470db18b5c6c1bed9483cd030c21afd446e098d$
ERROR: AcceptToMemoryPool() : nonstandard transaction type
received: inv (109 bytes)  got inventory: tx f14f4019294bb37a1c47  have
  got inventory: tx 385b3bf110d617a45eb2  new
askfor tx 385b3bf110d617a45eb2   0
  got inventory: tx 5e3759f119c4c720f6c1  new
askfor tx 5e3759f119c4c720f6c1   0
sending getdata: tx 385b3bf110d617a45eb2
sending getdata: tx 5e3759f119c4c720f6c1
sending: getdata (73 bytes)
received: tx (223 bytes)
ERROR: nonstandard txout: OP_HASH160 7c2f0073b7fed10a2c193baa8835eaa39278816a O$ERROR: AcceptToMemoryPool() : nonstandard transaction type
sending getdata: tx 2dead6f4d4b441180fb4
sending getdata: tx d9c33afd2f0e9d875d3f
sending getdata: tx 142fd7aaec040140af83
sending: getdata (109 bytes)
received: tx (372 bytes)
ERROR: ConnectInputs() : 5e3759f119 mapTransactions prev not found 07714cfaba
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5e3759f119
storing orphan tx 5e3759f119
received: tx (255 bytes)
ERROR: nonstandard txout: OP_RETURN 6f6d6e6900000000000000030000000000000369
ERROR: AcceptToMemoryPool() : nonstandard transaction type
received: tx (255 bytes)
ERROR: nonstandard txout: OP_RETURN 6f6d6e69000000000000000300000000000007ff
ERROR: AcceptToMemoryPool() : nonstandard transaction type
received: tx (189 bytes)
ERROR: nonstandard txout: OP_HASH160 8a8816b33f84cb8a3f6df3b901518908038b524b O$
ERROR: AcceptToMemoryPool() : nonstandard transaction type

Does this help you finding the problem's origin?
I'm not sure what the error is there, probably try just reindexing and see if you get the same error.
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 25, 2017, 02:03:56 PM
#8
Thank you for your enduring help. This seems to become a never ending story. Sad

First, I got an error starting bitcoind with the reindex-command. (Took me some time to realize it must be executed while bitcoind isn't running.)
Code:
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ProcessMessage()

Second, I tried to copy some part from the log file:
Code:
sending getdata: tx 45f73fecb138bd5c8686
sending: getdata (37 bytes)
received: tx (258 bytes)
ERROR: ConnectInputs() : f14f401929 mapTransactions prev not found f105ab4368
ERROR: AcceptToMemoryPool() : ConnectInputs failed f14f401929
storing orphan tx f14f401929
received: tx (369 bytes)
ERROR: nonstandard txin: 0 304402202c56a470db18b5c6c1bed9483cd030c21afd446e098d$
ERROR: AcceptToMemoryPool() : nonstandard transaction type
received: inv (109 bytes)  got inventory: tx f14f4019294bb37a1c47  have
  got inventory: tx 385b3bf110d617a45eb2  new
askfor tx 385b3bf110d617a45eb2   0
  got inventory: tx 5e3759f119c4c720f6c1  new
askfor tx 5e3759f119c4c720f6c1   0
sending getdata: tx 385b3bf110d617a45eb2
sending getdata: tx 5e3759f119c4c720f6c1
sending: getdata (73 bytes)
received: tx (223 bytes)
ERROR: nonstandard txout: OP_HASH160 7c2f0073b7fed10a2c193baa8835eaa39278816a O$ERROR: AcceptToMemoryPool() : nonstandard transaction type
sending getdata: tx 2dead6f4d4b441180fb4
sending getdata: tx d9c33afd2f0e9d875d3f
sending getdata: tx 142fd7aaec040140af83
sending: getdata (109 bytes)
received: tx (372 bytes)
ERROR: ConnectInputs() : 5e3759f119 mapTransactions prev not found 07714cfaba
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5e3759f119
storing orphan tx 5e3759f119
received: tx (255 bytes)
ERROR: nonstandard txout: OP_RETURN 6f6d6e6900000000000000030000000000000369
ERROR: AcceptToMemoryPool() : nonstandard transaction type
received: tx (255 bytes)
ERROR: nonstandard txout: OP_RETURN 6f6d6e69000000000000000300000000000007ff
ERROR: AcceptToMemoryPool() : nonstandard transaction type
received: tx (189 bytes)
ERROR: nonstandard txout: OP_HASH160 8a8816b33f84cb8a3f6df3b901518908038b524b O$
ERROR: AcceptToMemoryPool() : nonstandard transaction type

Does this help you finding the problem's origin?
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
August 25, 2017, 05:25:44 AM
#7
Quote from: DrakonX on August 25, 2017, 05:22:06 AM
Thank you very much, jackg. I'll check the log file, but I guess its content will be very meaningless to me. That's why, I certainly will have to start the reindexing from the front.
Post the log here if you want and about the time the problem started and I'll take a look at it at some point. It is fairly plain English so it's easy to spot a line with an error (even if you don't know what it means).
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 25, 2017, 05:22:06 AM
#6
Thank you very much, jackg. I'll check the log file, but I guess its content will be very meaningless to me. That's why, I certainly will have to start the reindexing from the front.
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
August 24, 2017, 03:09:35 PM
#5
Quote from: DrakonX on August 24, 2017, 02:50:27 PM
Now, the indexing process seems to got stuck at block 124,275. What can I do to fix this?

Check the debug.log to see if there's anything there about that time that can be fixed.
Otherwise, run bitcoind with the -reindex command.
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 24, 2017, 02:50:27 PM
#4
Now, the indexing process seems to got stuck at block 124,275. What can I do to fix this?
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 24, 2017, 02:43:30 AM
#3
I didn't know that. Thank you, man, for the explanation. Smiley
jackg
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Re: bitcoind starts from the very first block instead of continuing
August 23, 2017, 12:57:25 PM
#2
Quote from: DrakonX on August 23, 2017, 11:33:41 AM
I want to download the hole blockchain bitcoind on my Linux system. I installed bitcoind on the system and copied the partially downloaded blockchain to the directory "$ HOME /.bitcoin". Then I started bitcoind, but it starts to load the blockchain from the front instead of continuing from the existing data. How can I change this?

You don't.

It has to "reindex files on disk" before it can connect to the bitcoin network again and download their blocks. It SHOULD take slightly less time to do this, however, it must go back through everything again. Just check it does start downloading once it's finished reindexing at the point it got to in the download.
DrakonX
jr. member
Activity: 99
Merit: 4
Re: bitcoind starts from the very first block instead of continuing
August 23, 2017, 11:33:41 AM
#1
I want to download the hole blockchain bitcoind on my Linux system. I installed bitcoind on the system and copied the partially downloaded blockchain to the directory "$ HOME /.bitcoin". Then I started bitcoind, but it starts to load the blockchain from the front instead of continuing from the existing data. How can I change this?
Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Jump to: