 Show Posts
|
|
Pages: « 1 2 3 4 5 [6]
|
|
I just noticed one more thing in the logs.
-INFO - 1420984504: (BlockUtils.cpp:1119) Starting at block file 216 offset 124278660
-INFO - 1420984504: (BlockUtils.cpp:1121) Block height 338437
-DEBUG - 1420984504: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO - 1420984816: (BlockUtils.cpp:1236) Loading block data... file 21 offset 45157597
-INFO - 1421068874: (BlockUtils.cpp:1119) Starting at block file 217 offset 39342749
-INFO - 1421068874: (BlockUtils.cpp:1121) Block height 338585
-DEBUG - 1421068875: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO - 1421069155: (BlockUtils.cpp:1236) Loading block data... file 48 offset 62952398
|
|
|
|
...
Mine goes slightly slower than yours, and it fluctuates the exact same way. My Bitcoin QT also disconnects, then reconnects roughly every 1:45 hours. I noticed that read/write ops are running at the same speed that random ones do. Perhaps Armory or its new DB format isn't writing correctly? I'd still like to know why building databases is taking forever.
I'm running on OSX 10.10 with 16 GB of RAM and an SSHD with approx 85 MB/s read/write
I am planning on buying an SSD in the near future
I'm having the same problems/questions (I'm using --supernode, haven't tried without it): slow database building, about 1 MB/sec disk access during database building and 3 MB/sec during transaction scanning instead of max (about 30 MB/sec on my HDD), and now that the database is built, even slower transaction scanning (estimate ranging from 3 days to 2 weeks, usually about 6 days). What is the bottleneck here, since it's obviously not CPU (24 mins of CPU time used in 17 hours of running - usually 0-1% use) or hard drive access? Wait, so scanning transactions takes 6 days on average, you're saying? If it really takes that long, I'm waiting for 0.93 stable release, I'll take my chances with 0.92.3(0.92.3 worked fine with 0.10). |
|
|
|
database build is taking forever too. Been running for over 24 hours on my PC now, and last night when I went to bed it was 75%, now ~7 hours later it's at 80%, with the time varying wildly from 1.5 days to 16 hours.
I read into this, and my clock is properly synced with the internet, and the correct time zone.
It does flash up occasionally disconnected/reconnected from bitcoin qt, but if i've already downloaded the blockchain, and it's building databases (ie after this), surely this shouldn't matter, right?
Last few lines in the log are
-INFO - 1421029109: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 164 offset 134135074
-INFO - 1421031238: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 165 offset 133981448
-INFO - 1421033239: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 166 offset 133941531
-INFO - 1421035623: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 167 offset 134108933
-INFO - 1421037781: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 168 offset 134057186
-INFO - 1421040036: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 169 offset 133981151
-INFO - 1421042170: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 170 offset 134031450
-INFO - 1421044261: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 171 offset 134021369
-INFO - 1421046167: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 172 offset 133970023
-INFO - 1421048166: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 173 offset 133928453
-INFO - 1421050733: (..\BlockUtils.cpp:384) Reading raw blocks finished at file 174 offset 134127177
Just checked now ~40 minutes later, and it's jumped to 87% and says 2 hours remaining
Mine goes slightly slower than yours, and it fluctuates the exact same way, and building databases is the only thing that is so slow. Loading headers, organizing blockchain all take less than 5 mins and 20 mins respectively. My Bitcoin QT also disconnects, then reconnects roughly every 1:45 hours. I noticed that read/write ops are running at the same speed that random ones do. Perhaps Armory or its new DB format isn't writing correctly? I also have a Windows computer building databases right now, but it's going at about the same speed as jammer's(Windows 8, better hardware, etc). |
|
|
|
|
I'd still like to know why building databases is taking forever.
I'm running on OSX 10.10 with 16 GB of RAM and an SSHD with approx 85 MB/s read/write
I am planning on buying an SSD in the near future
|
|
|
|
snip
And just further to this, it lets me into the address book as above, but when I click addresses | view address book, it pops this
snip
Surely if I can't get in one way, I shouldn't be able to get into the other?
Note that the address book in the picture(from Wallet Properties) does not show sending addresses/lockboxes, and the one from the Addresses tab is supposed to show sending addresses/lockboxes. The Address Book that you were allowed to see only contained addresses from that wallet, which Armory already has, Armory doesn't have your sending addresses, so it cannot show those. |
|
|
|
Also, after I click 'Receive Bitcoins' below the Armory logo, a tiny window pops up with nothing but an empty progress bar and will not go away.
I get this on Windows too, it pops up a message and that little progress meter shows up. I move them side by side in screen below. snip I noticed something, you don't have any wallets loaded, but I have 7. Another note, the progress bar shows up after I close the Receive Bitcoins window. I have also been becoming more familiar with the Armory source code, perhaps I could help in bug fixing later. |
|
|
|
Found another bug in OS X. I am running Bitcoin Core v0.10 I'm not sure if this is a visual bug, if there's something wrong with the string, or if it just doesn't recognise 0.10, but here's a screenshot. http://prntscr.com/5r79etAlso, after I click 'Receive Bitcoins' below the Armory logo, a tiny window pops up with nothing but an empty progress bar and will not go away. |
|
|
|
I also believe the time prediction for building databases, etc. is bugged. It always starts at an outrageous time(ie. 2 months), then moves down to something more reasonable(ie. 6 hours)
+1 Would be better to have no time, than a time that just isn't true. Maybe have some sort of animation that builds up over time as the blockchain is assembled? The % is fine, but the time value never made sense in any version. I've actually proven myself wrong there, it's actually going to take 5 days. I did the calculations. It would be nice if it showed percent, or data/blocks remaining. |
|
|
|
Found 1 minor bug, 1 major bug http://prntscr.com/5qqia5Notice the HTML code not working I also believe the time prediction for building databases, etc. is bugged. It always starts at an outrageous time(ie. 2 months), then moves down to something more reasonable(ie. 6 hours)Then it hangs. It uses no memory, no CPU, and barely any I/O. And the time prediction starts going up slowly, and when it does use I/O, it only reads at ~1% the speed it did before and there is no progress indicator in the logs, it's frozen. Also noticed this: 2015-01-10 09:56 (INFO) -- ArmoryQt.py:2377 - loadBlockchainIfNecessary
2015-01-10 09:56 (ERROR) -- ArmoryQt.py:1220 - 8 attempts to load blockchain failed. Remove mempool.bin. '8 attempts' used to be '7 attempts' and '6 attempts' and so on. It does that every time, and number of attempts goes up by 1 or 2. After it finishes going into its "hanging" state, it starts up again, then it hangs again, then starts up. This I can tell because of the time indicator, it went from 5 days to 3 days, then started going back up again! Meanwhile I noticed a 'blocks' file in the databases directory, based on the name I'll assume block data is inside it. Well, there's one more thing - http://prntscr.com/5qr55dhttp://prntscr.com/5qr70xIf blocks is 600+ MB, and growing I might add, why does the progress bar not show it? Is the progress bar bugged, or is something wrong with Armory blockchain manager? At the time of this edit, I am performing a factory data reset, and will see if this fixes the issue. Edit: Factory data reset has not fixed the issue but Armory isn't hanging as bad as it was before, it's now using 4% of one CPU core, and 1 KB/s network bandwidth(both ways), also writing to disk which is a tiny bit of an improvement but not really noticeable, and I don't think it's Bitcoin Core causing this, so for the time being Armory is stuck with no databases, it seems. I will leave Armory on for a few hours and see if anything happens, I hope it actually starts to build DB, currently 'blocks' file is at 576 MB and doesn't seem to be growing or shrinking at all. Edit: Armory is reading block files, but it's not reading the full blockchain? -INFO - 1420907257: (BlockUtils.cpp:1115) Left off at file 0, offset 0
-INFO - 1420907257: (BlockUtils.cpp:1118) Reading headers and building chain...
-INFO - 1420907257: (BlockUtils.cpp:1119) Starting at block file 0 offset 0
-INFO - 1420907257: (BlockUtils.cpp:1121) Block height 0
-DEBUG - 1420907263: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO - 1420907270: (BlockUtils.cpp:1236) Loading block data... file 0 offset 0
-INFO - 1420907300: (BlockUtils.cpp:384) Reading raw blocks finished at file 0 offset 134214363
-INFO - 1420907804: (BlockUtils.cpp:384) Reading raw blocks finished at file 1 offset 134196904
-INFO - 1420908772: (BDM_mainthread.cpp:273) Stop requested detected
-INFO - 1420908772: (BDM_mainthread.cpp:316) UI asked build/scan thread to finish
Blank space -WARN - 1420908851: (BlockUtils.cpp:1102) --- Fetching SSH summaries for 853 registered addresses
-INFO - 1420908851: (BlockUtils.cpp:1115) Left off at file 216, offset 96791440
-INFO - 1420908851: (BlockUtils.cpp:1118) Reading headers and building chain...
-INFO - 1420908851: (BlockUtils.cpp:1119) Starting at block file 216 offset 96791440
-INFO - 1420908851: (BlockUtils.cpp:1121) Block height 338363
-DEBUG - 1420908852: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO - 1420908855: (BlockUtils.cpp:1236) Loading block data... file 2 offset 101076734
Later: -INFO - 1420910479: (BlockUtils.cpp:1119) Starting at block file 216 offset 97937840
-INFO - 1420910479: (BlockUtils.cpp:1121) Block height 338365
-DEBUG - 1420910479: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO - 1420910866: (BlockUtils.cpp:1236) Loading block data... file 3 offset 18312341
Edit: Resetting settings and such seemed to work, but Armory is loading outrageously slowly. -INFO - 1420910866: (BlockUtils.cpp:1236) Loading block data... file 3 offset 18312341
-INFO - 1420912097: (BlockUtils.cpp:384) Reading raw blocks finished at file 3 offset 134192403
-INFO - 1420914089: (BlockUtils.cpp:384) Reading raw blocks finished at file 4 offset 134210742
-INFO - 1420916448: (BlockUtils.cpp:384) Reading raw blocks finished at file 5 offset 134193056
-INFO - 1420918446: (BlockUtils.cpp:384) Reading raw blocks finished at file 6 offset 134187986
-INFO - 1420920724: (BlockUtils.cpp:384) Reading raw blocks finished at file 7 offset 134176596
-INFO - 1420923062: (BlockUtils.cpp:384) Reading raw blocks finished at file 8 offset 134212542
-INFO - 1420925461: (BlockUtils.cpp:384) Reading raw blocks finished at file 9 offset 134199478
-INFO - 1420927585: (BlockUtils.cpp:384) Reading raw blocks finished at file 10 offset 134015756
I've done some math, here are the times with some predictions: Loading file 3 - 20:31, full file would have taken 23:19 based on prediction Loading file 4 - 33:12 Loading file 5 - 39:19 Loading file 6 - 33:18 Loading file 7 - 37:58 Loading file 8 - 38:58 Loading file 9 - 39:59 Loading file 10 - 35:24 Average(excluding file 3) is 36:53 minutes per file, with a total of 217 files to process! At this rate, it would take 5 days, 13 hours, and 23 minutes! I have 16 GB of RAM, running on OS X 10.10, and have an SSHD installed(plan on dedicating an SSD of ~256 GB to Armory/Core), SSHD can write/read at about 85 MB/s. I don't know why Armory doesn't use at least half of what it used before(65.5 MB/s) |
|
|
|
Unless you're using a seriously old version, if you're seeing errors like this you have a hardware problem causing corruption of your system state. You really shouldn't be using a system experiencing errors as a wallet, since if it glitches out while sending a transaction you could suffer unrecoverable losses.
It doesn't just cover up for conditions which can only be caused by faulty hardware for several reasons, one if that if a fault happens again later in a undetectable way it can cause you unrecoverable loss (as mentioned). Two is because checking that the computer did what it was supposed to do adds overhead and so there is only enough of that to tell if something is seriously wrong, not enough to tell exactly what. Three is that having enough data to recover would require more storage... the error you sound like you're seeing is a leveldb error in the chainstate database, not an error with a Bitcoin block. With the database corrupt it cant fix it by just downloading something again, it must rebuild it. And, forth and finally, recovering a single system from an impossible state--even where possible-- requires extra code which must be written and tested and could later cause bugs, these are real costs which are hard to justify for something should only happen on broken hardware (which is doomed no matter what the software does) so it isn't added lightly.
Sorry you're having problems, but as you note your other system doesn't have these issues. A reindex should take only a few hours maximum (though if your disk is failing that can drastically increase the time.), here they take me under 2 hours though YMMV a bit due to system speed.
I just got a new SSHD, and like I said, if necessary I will give QT its own SSD to run on. |
|
|
|
snip
Could you use your other computer to get your coins out? I could, but Bitcoin QT isn't synchronized on the other computer either. EDIT: Bitcoin QT on the mac is reindexing, at 26% at the time of writing, it goes very slow. It doesn't use much RAM or CPU. I haven't seen much disk activity coming from QT either, is there any way I can get it to use more resources to speed up sync? |
|
|
|
|
Bitcoin QT failed 3 times while I was rebuilding the blockchain database.
Once at 94% it got one bad block 'block checksum mismatch', why can't it just delete that 1 block and redownload it? Yes it did this in the past! Why do I have to reindex the whole thing, that takes 18-30 hours? This happens nearly every time I restart the client.
If there's any way to fix this please tell me, I am losing my patience with QT. I have no problems with it on my other computer running Windows 8. I am running Mac OS X 10.10 right now.
I tried building from source and got this error:
configure: error: Could not find a version of the boost_system library!
Even though the boost::system library is available.
I am trying to switch wallet. But I can't, my BTC is in multisig address, and I don't know how to get it out.
I am going to try giving it its own storage, I have a spare SSHD with nothing on it. If this fails I'm going to get a SSD.
Yes I absolutely need to get this fixed to get my bitcoins out of this multi sig address in Armory.
|
|
|
|
I found out my bitcoin blockchain was corrupted and that's why it crashed.
how did you solve it? I had to reindex my blockchain, which took about 2 days How can I do that? I need to fix my armory wallet too, I really don't want to use my paper wallet on another PC =( I ran "bitcoind -reindex" in the command line, but I don't know what the issue is with your client |
|
|
|
I found out my bitcoin blockchain was corrupted and that's why it crashed.
how did you solve it? I had to reindex my blockchain, which took about 2 days |
|
|
|
|
Is this normal? If it is, I think it's about time to get some blockchain servers up for Bitcoin QT.
I'm frustrated because it corrupted database when I was 2 weeks behind. Right now I'm reindexing my blockchain.
|
|
|
|
|
I found out my bitcoin blockchain was corrupted and that's why it crashed.
|
|
|
|
Everything was good until the client decided to do this: 2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 93.7
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 93.8
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 93.8
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 93.9
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 94.0
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 94.1
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 94.2
2014-11-02 19:57 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 94.4
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1020 - C++ block utilities loaded successfully
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:565 - Executing popen: sysctl hw.memsize
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:565 - Executing popen: sysctl -n machdep.cpu.brand_string
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1127 -
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1128 -
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1129 -
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1130 - ************************************************************
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1131 - Invoked: /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1132 - ************************************************************
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1133 - Loading Armory Engine:
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1134 - Armory Version : 0.92.3
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1135 - PyBtcWallet Version : 1.35
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1136 - Detected Operating system: MacOSX
2014-11-02 19:58 (INFO) -- ArmoryUtils.py:1137 - OS Variant : 10.10 Loading wallets and such.. 2014-11-02 19:58 (INFO) -- ArmoryQt.py:2106 - Setting up networking...
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2159 - Internet connection is Available: True
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2160 - Bitcoin-Qt/bitcoind is Available: 0
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2161 - The first blk*.dat was Available: True
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2162 - Online mode currently possible: 0
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2349 - loadBlockchainIfNecessary
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2386 - Setting netmode: 0
2014-11-02 19:58 (INFO) -- BDM.py:470 - Setting online mode: False (wait=False)
2014-11-02 19:58 (INFO) -- ArmoryQt.py:1367 - setupUriRegistration
2014-11-02 19:58 (INFO) -- ArmoryQt.py:617 - Usermode: Expert
2014-11-02 19:58 (INFO) -- ArmoryQt.py:1662 - Changing usermode:
2014-11-02 19:58 (INFO) -- ArmoryQt.py:1663 - From: Expert
2014-11-02 19:58 (INFO) -- ArmoryQt.py:1671 - To: Expert
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5442 - Switching Armory state text to Mgmt:User, State:OfflineNoSatoshi
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5384 - Switching Armory functional mode to "Offline"
2014-11-02 19:58 (ERROR) -- announcefetch.py:171 - Loop was busy for more than one second
2014-11-02 19:58 (INFO) -- ArmoryQt.py:6066 - Dashboard switched to user-OfflineOnlinePoss
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5442 - Switching Armory state text to Mgmt:User, State:OfflineButOnlinePossible
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5384 - Switching Armory functional mode to "Offline"
2014-11-02 19:58 (INFO) -- BDM.py:470 - Setting online mode: True (wait=None)
2014-11-02 19:58 (INFO) -- BDM.py:1509 - Go online requested
2014-11-02 19:58 (INFO) -- BDM.py:982 - Setting Armory Home Dir: /Users/admin/Library/Application Support/Armory/
2014-11-02 19:58 (INFO) -- BDM.py:983 - Setting BlkFile Dir: /Users/admin/Library/Application Support/Bitcoin/blocks
2014-11-02 19:58 (INFO) -- BDM.py:984 - Setting LevelDB Dir: /Users/admin/Library/Application Support/Armory/databases
2014-11-02 19:58 (INFO) -- ArmoryQt.py:2386 - Setting netmode: 1
2014-11-02 19:58 (INFO) -- ArmoryQt.py:6138 - Dashboard switched to "Scanning" mode
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5442 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5442 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5384 - Switching Armory functional mode to "Scanning"
2014-11-02 19:58 (INFO) -- Networking.py:63 - Connection initiated. Start handshake
2014-11-02 19:58 (INFO) -- ArmoryQt.py:6138 - Dashboard switched to "Scanning" mode
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5442 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5442 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-11-02 19:58 (INFO) -- ArmoryQt.py:5384 - Switching Armory functional mode to "Scanning"
2014-11-02 19:59 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 0.0
2014-11-02 19:59 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 0.1
2014-11-02 20:00 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 0.1
2014-11-02 20:00 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 0.2
2014-11-02 20:00 (INFO) -- BDM.py:419 - Reading blockchain, pct complete: 0.2
I am using version 0.92.3, on Mac OS X 10.10 This happens, then the client needs to rescan the databases again. I've done this three times and no luck. Please help! Will be using different version until then |
|
|
|
|
Never mind I fixed it, turns out i was using the wrong charger xD
|
|
|
|
|
So I was mining with my gridseed GC3355 5 chip yesterday, I went to check on it and it stopped submitting shares.
Tried restarting computer, reconnecting USB cable, and power, nothing.
I am mining on a Mac with bfgminer 3.99.0 with a USB cable directly connected to the computer.
It appears to be hashing, this is my display.
bfgminer version 3.99.0 - Started: [2014-06-13 19:21:33] - [ 0 days 00:00:22]
[M]anage devices [P]ool management (S)ettings [D]isplay options [H]elp [Q]uit
Pool 0: doge.ghash.io Diff:61u +Strtm LU:[19:21:37] User:zombieslayer9099.ghash
Block: ...c2db73dc #259621 Diff:674 ( 4.83G) Started: [19:21:37]
ST:3 F:0 NB:2 AS:0 BW:[ 62/ 15 B/s] E:0.00 I: 0.00 BTC/hr BS:0
1 | 256.3/234.5/ 0.0kh/s | A:0 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------------------------------------------------------------------
GSD 0: | 252.5/234.5/ 0.0kh/s | A:0 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------------------------------------------------------------------
[2014-06-13 19:21:29] Loaded configuration file ghash-doge.conf
[2014-06-13 19:21:32] Probing for an alive pool
[2014-06-13 19:21:32] Pool 0 stratum+tcp://doge.ghash.io:3333 alive
[2014-06-13 19:21:32] Network difficulty changed to 606 ( 4.34G)
[2014-06-13 19:21:32] Stratum from pool 0 detected new block
[2014-06-13 19:21:37] Network difficulty changed to 674 ( 4.83G)
[2014-06-13 19:21:37] Stratum from pool 0 detected new block
Stratum difficulty 61u is 4.
Normally it submits around 3-5 shares right after i start the miner.
Does not show accepted shares on the pool either.
Can anyone help me please?
I do not want to stoop back down to GPU mining!
|
|
|
|
Guys, I've found a site that may or may not be the new makebtc.org It is very similar and has the same features as the old site! http://qoingrow.com/index.php |
|
|
|
|
