As the thread title says, I've been away from Altcoins for 6 months... I see XMR is still around, which is great, but anyone wanna give me a TL:DR on what the new trends are, or where to look? - Still POW/POS?
- Bittrex still King?
- Ninja launches, pre/postmines
- What is/are the most promising Alts now? Darkcoin & Blackcoin?
PS. I would do the research myself, but I get 1 hour Internet privs per month (long story )
|
|
|
They certainly can This coin has some great features coming up. Getting in now would make some nice profit What is the coin then ? Great viral marketing campaign, OP!
|
|
|
--satoshi-datadir="d:\data\bitcoincore\testnet3"
This is what you need if you want testnet to work. You should ignore the testnet part in the trouble shooting page. I guess it's confusing, we should change that.
Yes, you're right, it is extremely confusing. There's also issues where sometimes quoted directories ( --flag="DIR" vs --flag=DIR) cause issues when specifying log file locations etc. Thanks for the help, however, it is not --satoshi-datadir="d:\data\bitcoincore\testnet3"... The working CMDs/flags are: - ARMORY: armory-qt.exe --testnet --datadir=d:\data\armory\testnet3 --satoshi-datadir=d:\data\bitcoincore --rpcport=8332
- BITCOIN-QT: bitcoin-qt.exe -datadir="d:\data\bitcoincore" -testnet -txindex=1 -rpcport=8332
|
|
|
why are you pointing Armory to d:\data\bitcoincore when you are using tesnet?
I am following the instructions outlined in Armory Troubleshooting Q19 of Armory FAQ. *NOTE: Due to some quirks in the path resolution, if you want to use a custom directory for Armory and Bitcoin, the --datadir and --satoshi-datadir arguments are inconsistent. For instance, if you moved both your bitcoin home dir and your armory home dir to F:\Bitcoin and F:\Armory, respectively, do the following:
bitcoind.exe -testnet -datadir=F:\Bitcoin
Armory.exe --testnet --datadir=F:\Armory\testnet3 --satoshi-datadir=F:\Bitcoin
The problem is that Bitcoin-Qt expects the base bitcoin home directory, even for testnet, and will add the "testnet3" for you. If you specify F:\Bitcoin\testnet3, it will run in F:\Bitcoin\testnet3\testnet3. However, this wasn't realized when initially setting up the code for processing arguments, and therefore, Armory requires explicitly specifying the full path. EDIT/UPDATE: HERE'S WHY I THINK YOU (goatpig) MAY BE RIGHT... My Mainnet Armory runs perfectly fine.. If you want to reset and re-download the blockchain from scratch, you should also delete every file in the %APPDATA%\Bitcoin\blocks directory Can I delete just the testnet3 block dir? As I mentioned, the only issue is with Armory testnet not working
|
|
|
-WARN - 1427685617: (..\Blockchain.cpp:47) Somehow tried to add header that's already in map -WARN - 1427685617: (..\Blockchain.cpp:48) Header Hash: 00000000ad4e4c886567776c89e752614f251cca28b7dfcaf16867677ba0245a Screenshot: https://imgur.com/tuF8uBPWin7 x64, Armory 0.93, BitcoinCore 0.10: Flags: -testnet -rest -txindex=1 -server --testnet --datadir=d:\data\armorynew\testnet3 --satoshi-datadir="d:\data\bitcoincore" --rpcport=8332 --debug --netlog --mtdebug --logfile=d:\data\armorynew Have deleted the d:\data\armory and tried to start again but same shit! HOW DO I FIX THIS GODDAMNED STUCK BLOCKCHAIN ISSUE? PLEASE! Thank you kindly, HOT
|
|
|
Currently Armory has its default installation location (in my case) set to C:\Program Files (x86) and on top of that bitcoin-qt installation is set to C:\Program Files AND on top of that it stores all it's data in TWO folders in C:\Users\User\AppData\Roaming Bitcoin and Armory
Wait, is Armory using the %appdata%\Armory directory and also putting stuff into the %appdata%\bitcoin directory too? If so, even in advanced mode with the "let armory manage..." setting turned off? I have the same problem described here, namely that Armory is getting stuck on a block, won't confirm incoming Txs, and deleting the datadirs and starting fresh just isn't working.
|
|
|
I think one would want clarity on whether this marketplace is running on the clearnet or via TOR too, if you catch my drift
|
|
|
First of all, how do you denominate something in USD when talking about a part of the Bitcoin protocol ?
1. USD is not an universal currency like Bitcoin.
2. FIAT value is varying from exchange to exchange.
I look forward to one day ignoring the value of even thinking about USD , but the reality we currently face is USD is still the largest reserve currency worldwide by a healthy margin We live in some prosperous times - no wars, nothing to want for, choices/freedom so diverse it can be overwhelming... I think the only reason people speak shit about fiat/USD is because they've never lived through real adversity. And by that I mean fighting a wars in far away lands, or starving through the great depression, or the 6 or 7 years in the 70s when dunking was not allowed in the NBA. I like Bitcoin, but the DOWN WITH FIAT!!![ and chant-worthy diatribes (not you per se, but like a college demonstration screaming... 2 bits, 4 bits, 6 bits, a dollar, all who hate the Feds in here, give me a hollar!)
|
|
|
backup your wallet.dat then re-sync from the beginning that should be fix That did it, however I was unclear (in that I failed to fully understand) that I was looking to get what the *txindex* and *reindex* flags have just now given me: namely the full Tx index so that *getrawtransaction* works for everything. I must say, v0.10.rc4 (and the final release) are amazingly fast. Congrats to devs! (took ~12hrs Vs the usual 3-4 days)
|
|
|
people who appeared to be hacked Receipts of btc have miraculously and then have to empty their wallet.
Everything leads to believe that the haker send modified bitcoin to walet interested and the person can not refuse them.User is forced to be scam.
All of those words are English words, but you didn't put them together in a way that creates a coherent thought. Bitcoin Ipsum Lorem: you'll find rants of this over on Reddit
|
|
|
Satoshi Nakamoto set in motion the unraveling of the nation state
You sound like the kind of person who denounces the state as a legitimate authority. So why then, do you then continually equate 'identity' with only government-approved identity? I'm glad OP is considering the really important questions. Not what does the future hold, but **who is the person(s) who coded some software**? The ironic part is 90% of the community could hear a name of Satoshi's identity and not know who it is due to never venturing out of the Karpeles, Ver, Shrem circle of names: perhaps reading stuff related to the tech based functions would be more educational than wondering what size shoe God wears
|
|
|
I'm getting a corrupted database warning with Win7 x64 0.9.3. Power outage reset the machine and upon reboot there were problems. The database started re-indexing but is taking forever. LUCKILY, I have 2 backups of the %appdata%\bitcoin directory (which is usually a junction to d:\data\bitcoincore). Anyhow, I ran it with datadir flag as e:\bitcoincore (one of 2 dirs which I backed up the entire dir to on Feb 8th) and it's not solving the problem. db.log:Program version 4.8 doesn't match environment version 4.7 debug.loghttps://gist.github.com/anonymous/d1c9a35ae4971d226c072015-02-11 04:24:58 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.18/: version 70001, blocks=342952, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=31.134.143.131:50979 2015-02-11 04:24:58 Added time data, samples 48, offset +24 (+0 minutes) 2015-02-11 04:25:43 ERROR: AcceptToMemoryPool : inputs already spent 2015-02-11 04:50:57 2015-02-11 04:50:57 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:50:57 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:50:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:50:57 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:50:57 Using data directory d:\data\bitcoincore 2015-02-11 04:50:57 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:50:57 Using 8 threads for script verification 2015-02-11 04:50:57 Using wallet wallet.dat 2015-02-11 04:50:57 init message: Verifying wallet... 2015-02-11 04:50:57 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:50:57 Bound to [::]:8333 2015-02-11 04:50:57 Bound to 0.0.0.0:8333 2015-02-11 04:50:57 init message: Loading block index... 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:03 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:03 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999940 2015-02-11 04:51:03 init message: Verifying blocks... 2015-02-11 04:51:03 Verifying last 288 blocks at level 3 2015-02-11 04:51:04 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 : Error opening block database. Do you want to rebuild the block database now? 2015-02-11 04:51:04 Aborted block database rebuild. Exiting. 2015-02-11 04:51:04 Shutdown : In progress... 2015-02-11 04:51:04 StopNode() 2015-02-11 04:51:04 Shutdown : done Requesting initialize Running AppInit2 in thread 2015-02-11 04:51:20 2015-02-11 04:51:20 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:51:20 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:51:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:51:20 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:51:20 Using data directory d:\data\bitcoincore 2015-02-11 04:51:20 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:51:20 Using 8 threads for script verification 2015-02-11 04:51:20 Using wallet wallet.dat 2015-02-11 04:51:20 init message: Verifying wallet... 2015-02-11 04:51:20 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:51:21 Bound to [::]:8333 2015-02-11 04:51:21 Bound to 0.0.0.0:8333 2015-02-11 04:51:21 init message: Loading block index... 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:23 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:23 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999939 2015-02-11 04:51:23 init message: Verifying blocks... 2015-02-11 04:51:23 Verifying last 288 blocks at level 3 2015-02-11 04:51:23 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:23 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:29 init message: Loading block index... 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Initializing databases... 2015-02-11 04:51:29 init message: Verifying blocks... 2015-02-11 04:51:29 block index 285ms 2015-02-11 04:51:29 init message: Loading wallet... 2015-02-11 04:51:29 nFileVersion = 90300 2015-02-11 04:51:29 Keys: 0 plaintext, 365 encrypted, 365 w/ metadata, 365 total 2015-02-11 04:51:29 wallet 269ms 2015-02-11 04:51:29 init message: Loading addresses... 2015-02-11 04:51:30 Reindexing block file blk00000.dat... 2015-02-11 04:51:30 Loaded 0 addresses from peers.dat 36ms 2015-02-11 04:51:30 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 log2_work=32.000022 tx=1 date=2009-01-03 18:15:05 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 Pre-allocating up to position 0x100000 in rev00000.dat 2015-02-11 04:51:30 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 log2_work=33.000022 tx=2 date=2009-01-09 02:54:25 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:24:58 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.18/: version 70001, blocks=342952, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=31.134.143.131:50979 2015-02-11 04:24:58 Added time data, samples 48, offset +24 (+0 minutes) 2015-02-11 04:25:43 ERROR: AcceptToMemoryPool : inputs already spent 2015-02-11 04:50:57 2015-02-11 04:50:57 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:50:57 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:50:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:50:57 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:50:57 Using data directory d:\data\bitcoincore 2015-02-11 04:50:57 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:50:57 Using 8 threads for script verification 2015-02-11 04:50:57 Using wallet wallet.dat 2015-02-11 04:50:57 init message: Verifying wallet... 2015-02-11 04:50:57 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:50:57 Bound to [::]:8333 2015-02-11 04:50:57 Bound to 0.0.0.0:8333 2015-02-11 04:50:57 init message: Loading block index... 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:03 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:03 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999940 2015-02-11 04:51:03 init message: Verifying blocks... 2015-02-11 04:51:03 Verifying last 288 blocks at level 3 2015-02-11 04:51:04 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 : Error opening block database. Do you want to rebuild the block database now? 2015-02-11 04:51:04 Aborted block database rebuild. Exiting. 2015-02-11 04:51:04 Shutdown : In progress... 2015-02-11 04:51:04 StopNode() 2015-02-11 04:51:04 Shutdown : done Requesting initialize Running AppInit2 in thread 2015-02-11 04:51:20 2015-02-11 04:51:20 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:51:20 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:51:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:51:20 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:51:20 Using data directory d:\data\bitcoincore 2015-02-11 04:51:20 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:51:20 Using 8 threads for script verification 2015-02-11 04:51:20 Using wallet wallet.dat 2015-02-11 04:51:20 init message: Verifying wallet... 2015-02-11 04:51:20 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:51:21 Bound to [::]:8333 2015-02-11 04:51:21 Bound to 0.0.0.0:8333 2015-02-11 04:51:21 init message: Loading block index... 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:23 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:23 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999939 2015-02-11 04:51:23 init message: Verifying blocks... 2015-02-11 04:51:23 Verifying last 288 blocks at level 3 2015-02-11 04:51:23 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:23 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:29 init message: Loading block index... 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Initializing databases... 2015-02-11 04:51:29 init message: Verifying blocks... 2015-02-11 04:51:29 block index 285ms 2015-02-11 04:51:29 init message: Loading wallet... 2015-02-11 04:51:29 nFileVersion = 90300 2015-02-11 04:51:29 Keys: 0 plaintext, 365 encrypted, 365 w/ metadata, 365 total 2015-02-11 04:51:29 wallet 269ms 2015-02-11 04:51:29 init message: Loading addresses... 2015-02-11 04:51:30 Reindexing block file blk00000.dat... 2015-02-11 04:51:30 Loaded 0 addresses from peers.dat 36ms 2015-02-11 04:51:30 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 log2_work=32.000022 tx=1 date=2009-01-03 18:15:05 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 Pre-allocating up to position 0x100000 in rev00000.dat 2015-02-11 04:51:30 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 log2_work=33.000022 tx=2 date=2009-01-09 02:54:25 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 03:22:15 UpdateTip: new best=0000000000000000094a953f2412f7ff058b83356e9500187cbc684f6051f8b3 height=342944 log2_work=82.207776 tx=59274330 date=2015-02-11 02:00:45 progress=0.999887 2015-02-11 03:22:15 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:15 ProcessBlock: ACCEPTED 2015-02-11 03:22:18 UpdateTip: new best=00000000000000000a1ad22a8c0b5471f0511a22041629b0f2b1adf1bd45cd4a height=342945 log2_work=82.207825 tx=59275092 date=2015-02-11 02:21:38 progress=0.999916 2015-02-11 03:22:18 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:18 ProcessBlock: ACCEPTED 2015-02-11 03:22:21 UpdateTip: new best=00000000000000000889dc00d6aac3bda42a7e79662f5f0ce2dba020484d8d52 height=342946 log2_work=82.207875 tx=59275997 date=2015-02-11 02:37:27 progress=0.999938 2015-02-11 03:22:21 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:21 ProcessBlock: ACCEPTED 2015-02-11 03:22:24 UpdateTip: new best=0000000000000000004983ddbc0ea812045fe542003b1cf9cb00810bee87518f height=342947 log2_work=82.207924 tx=59276650 date=2015-02-11 02:49:45 progress=0.999955 2015-02-11 03:22:24 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:24 ProcessBlock: ACCEPTED 2015-02-11 03:22:25 UpdateTip: new best=00000000000000000eba9e65987d2b01cd1851933df42556a2d5d808624ba45f height=342948 log2_work=82.207973 tx=59277041 date=2015-02-11 02:56:06 progress=0.999964 2015-02-11 03:22:25 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:25 ProcessBlock: ACCEPTED 2015-02-11 03:22:26 UpdateTip: new best=0000000000000000118cb7f49c62d573ed033266bd843c464b5a9b51b35b844e height=342949 log2_work=82.208023 tx=59277722 date=2015-02-11 03:19:16 progress=0.999996 2015-02-11 03:22:26 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:26 ProcessBlock: ACCEPTED Requesting initialize Running AppInit2 in thread 2015-02-11 03:24:33 Initialization result: 0 2015-02-11 03:24:33 Requesting shutdown 2015-02-11 03:24:33 Running Shutdown in thread 2015-02-11 03:24:33 Shutdown : In progress... 2015-02-11 03:24:33 StopNode() 2015-02-11 03:24:33 Shutdown : done 2015-02-11 03:24:33 Shutdown finished 2015-02-11 03:24:33 Shutdown result: 1 2015-02-11 03:24:33 Stopping thread 2015-02-11 03:24:33 Stopped thread 2015-02-11 03:24:42 keypool reserve 5 2015-02-11 03:24:42 keypool return 5 2015-02-11 03:25:20 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:47160 2015-02-11 03:26:18 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:54709 2015-02-11 03:26:29 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.19/: version 70001, blocks=342804, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=73.170.6.150:47790 2015-02-11 03:26:29 Added time data, samples 38, offset +24 (+0 minutes) 2015-02-11 03:26:56 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.153.147.74:3085 2015-02-11 03:28:31 ResendWalletTransactions() 2015-02-11 03:28:56 receive version message: /Satoshi:0.9.3/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=148.251.249.69:0, peer=148.251.249.69:15873 2015-02-11 03:29:00 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:38602 2015-02-11 03:30:42 receive version message: /Satoshi:0.9.3/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=127.0.0.1:47640, peer=46.105.210.248:47640 2015-02-11 03:30:42 Added time data, samples 39, offset +25 (+0 minutes) 2015-02-11 03:30:42 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:31:27 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:41220 2015-02-11 03:31:37 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2015-02-11 03:31:37 receive version message: /Satoshi:0.9.3/: version 70002, blocks=342949, us=XXX.XXX.129.69:50236, them=71.166.38.146:8333, peer=71.166.38.146:8333 2015-02-11 03:31:37 Added time data, samples 40, offset +26 (+0 minutes) 2015-02-11 03:31:37 receive version message: : version 32100, blocks=308636, us=XXX.XXX.129.69:8333, them=46.4.121.99:8333, peer=46.4.121.99:35062 2015-02-11 03:31:37 Added time data, samples 41, offset +24 (+0 minutes) 2015-02-11 03:31:37 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:34:39 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.194.231.211:7997 2015-02-11 03:35:13 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.67.102.19:64097 2015-02-11 03:35:15 receive version message: /Satoshi:0.8.1/: version 70001, blocks=342949, us=127.0.0.1:6378, them=XXX.XXX.129.69:8333, peer=54.82.89.182:37026 2015-02-11 03:35:15 Added time data, samples 42, offset +24 (+0 minutes) 2015-02-11 03:36:39 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:43888 2015-02-11 03:37:19 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:30280 2015-02-11 03:38:23 connected to self at 127.0.0.1:51088, disconnecting 2015-02-11 03:39:17 receive version message: /Satoshi:0.9.1/: version 70002, blocks=342582, us=XXX.XXX.129.69:51112, them=24.35.17.153:8333, peer=24.35.17.153:8333 2015-02-11 03:39:17 Added time data, samples 43, offset +8 (+0 minutes) 2015-02-11 03:39:17 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:39:44 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.153.147.74:18062 2015-02-11 03:40:04 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:9663 2015-02-11 03:40:14 UPnP Port Mapping successful. 2015-02-11 03:41:54 receive version message: /Satoshi:0.8.6/: version 70002, blocks=275686, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=46.63.26.63:32570 2015-02-11 03:41:54 Added time data, samples 44, offset +25 (+0 minutes) 2015-02-11 03:45:30 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:23815 2015-02-11 03:47:37 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=0, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:12834 2015-02-11 03:47:55 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.152.68.195:9035 2015-02-11 03:51:13 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.153.147.74:32502 2015-02-11 03:51:50 receive version message: /BitCoinJ:0.11.2/MultiBit:0.5.18/: version 70001, blocks=342949, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=71.246.193.126:60033 2015-02-11 03:51:50 Added time data, samples 45, offset +17 (+0 minutes) 2015-02-11 03:51:50 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:52:13 receive version message: /Shibetoshi:0.1/: version 70002, blocks=0, us=[::]:0, them=[::]:0, peer=192.155.84.55:54857 2015-02-11 03:52:25 receive version message: /Satoshi:0.8.6/: version 70001, blocks=329127, us=XXX.XXX.129.69:8333, them=24.86.204.139:8333, peer=24.86.204.139:53768 2015-02-11 03:52:25 Added time data, samples 46, offset +24 (+0 minutes) 2015-02-11 03:53:46 Pre-allocating up to position 0x200000 in rev00229.dat 2015-02-11 03:53:47 UpdateTip: new best=00000000000000001182cc7fc6569bd8612107af6abe696ccb56de8d16d7e85d height=342950 log2_work=82.208072 tx=59279136 date=2015-02-11 03:49:44 progress=0.999994 2015-02-11 03:53:47 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:53:47 ProcessBlock: ACCEPTED 2015-02-11 03:54:21 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:30528 2015-02-11 03:54:48 UpdateTip: new best=000000000000000012e7874c34155d89897c58014c86f02925f32748a35c0867 height=342951 log2_work=82.208121 tx=59279585 date=2015-02-11 03:54:40 progress=1.000000 2015-02-11 03:54:48 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:54:48 ProcessBlock: ACCEPTED 2015-02-11 03:56:23 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:45423 2015-02-11 03:56:29 ResendWalletTransactions() 2015-02-11 03:56:52 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.94.223.66:64086 2015-02-11 03:56:58 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.194.231.211:31393 2015-02-11 03:58:13 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.67.102.19:29820 2015-02-11 03:59:56 receive version message: /Shibetoshi:0.1/: version 70002, blocks=0, us=[::]:0, them=[::]:0, peer=192.155.84.55:59985 2015-02-11 04:00:14 UPnP Port Mapping successful. 2015-02-11 04:01:09 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342951, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.94.223.66:3357 2015-02-11 04:02:28 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:37536 2015-02-11 04:03:48 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342951, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:35467 2015-02-11 04:03:59 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.152.68.195:27052 2015-02-11 04:06:44 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342951, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:11396 2015-02-11 04:07:48 UpdateTip: new best=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 log2_work=82.208171 tx=59280195 date=2015-02-11 04:07:33 progress=1.000000 2015-02-11 04:07:48 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 04:07:48 ProcessBlock: ACCEPTED 2015-02-11 04:08:10 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:51813 2015-02-11 04:08:21 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:08:22 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:08:22 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:08:23 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:12:45 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.94.223.66:17730 2015-02-11 04:13:03 ResendWalletTransactions() 2015-02-11 04:13:20 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342952, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:42671 2015-02-11 04:13:59 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:48226 2015-02-11 04:16:39 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.152.68.195:40948 2015-02-11 04:16:51 receive version message: /Satoshi:0.9.2/: version 70002, blocks=447232, us=XXX.XXX.129.69:8333, them=128.8.124.7:8333, peer=128.8.124.7:50920 2015-02-11 04:16:51 Added time data, samples 47, offset +25 (+0 minutes) 2015-02-11 04:16:51 nTimeOffset = +24 (+0 minutes) 2015-02-11 04:17:47 keypool reserve 5 2015-02-11 04:17:47 keypool return 5 2015-02-11 04:20:14 UPnP Port Mapping successful. 2015-02-11 04:24:44 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:54400 2015-02-11 04:24:58 UpdateTip: new best=000000000000000012a62978fcbe7bd3bf9ee105573b15efcddc26bf75330c38 height=342953 log2_work=82.20822 tx=59280949 date=2015-02-11 04:25:11 progress=1.000000 2015-02-11 04:24:58 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 04:24:58 ProcessBlock: ACCEPTED 2015-02-11 04:24:58 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.18/: version 70001, blocks=342952, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=31.134.143.131:50979 2015-02-11 04:24:58 Added time data, samples 48, offset +24 (+0 minutes) 2015-02-11 04:25:43 ERROR: AcceptToMemoryPool : inputs already spent 2015-02-11 04:50:57 2015-02-11 04:50:57 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:50:57 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:50:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:50:57 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:50:57 Using data directory d:\data\bitcoincore 2015-02-11 04:50:57 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:50:57 Using 8 threads for script verification 2015-02-11 04:50:57 Using wallet wallet.dat 2015-02-11 04:50:57 init message: Verifying wallet... 2015-02-11 04:50:57 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:50:57 Bound to [::]:8333 2015-02-11 04:50:57 Bound to 0.0.0.0:8333 2015-02-11 04:50:57 init message: Loading block index... 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:03 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:03 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999940 2015-02-11 04:51:03 init message: Verifying blocks... 2015-02-11 04:51:03 Verifying last 288 blocks at level 3 2015-02-11 04:51:04 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 : Error opening block database. Do you want to rebuild the block database now? 2015-02-11 04:51:04 Aborted block database rebuild. Exiting. 2015-02-11 04:51:04 Shutdown : In progress... 2015-02-11 04:51:04 StopNode() 2015-02-11 04:51:04 Shutdown : done Requesting initialize Running AppInit2 in thread 2015-02-11 04:51:20 2015-02-11 04:51:20 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:51:20 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:51:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:51:20 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:51:20 Using data directory d:\data\bitcoincore 2015-02-11 04:51:20 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:51:20 Using 8 threads for script verification 2015-02-11 04:51:20 Using wallet wallet.dat 2015-02-11 04:51:20 init message: Verifying wallet... 2015-02-11 04:51:20 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:51:21 Bound to [::]:8333 2015-02-11 04:51:21 Bound to 0.0.0.0:8333 2015-02-11 04:51:21 init message: Loading block index... 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:23 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:23 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999939 2015-02-11 04:51:23 init message: Verifying blocks... 2015-02-11 04:51:23 Verifying last 288 blocks at level 3 2015-02-11 04:51:23 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:23 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:29 init message: Loading block index... 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Initializing databases... 2015-02-11 04:51:29 init message: Verifying blocks... 2015-02-11 04:51:29 block index 285ms 2015-02-11 04:51:29 init message: Loading wallet... 2015-02-11 04:51:29 nFileVersion = 90300 2015-02-11 04:51:29 Keys: 0 plaintext, 365 encrypted, 365 w/ metadata, 365 total 2015-02-11 04:51:29 wallet 269ms 2015-02-11 04:51:29 init message: Loading addresses... 2015-02-11 04:51:30 Reindexing block file blk00000.dat... 2015-02-11 04:51:30 Loaded 0 addresses from peers.dat 36ms 2015-02-11 04:51:30 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 log2_work=32.000022 tx=1 date=2009-01-03 18:15:05 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 Pre-allocating up to position 0x100000 in rev00000.dat 2015-02-11 04:51:30 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 log2_work=33.000022 tx=2 date=2009-01-09 02:54:25 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd height=2 log2_work=33.584985 tx=3 date=2009-01-09 02:55:44 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 height=3 log2_work=34.000022 tx=4 date=2009-01-09 03:02:53 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 height=4 log2_work=34.32195 tx=5 date=2009-01-09 03:16:28 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc height=5 log2_work=34.584985 tx=6 date=2009-01-09 03:23:48 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d height=6 log2_work=34.807377 tx=7 date=2009-01-09 03:29:49 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 height=7 log2_work=35.000022 tx=8 date=2009-01-09 03:39:29 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 height=8 log2_work=35.169947 tx=9 date=2009-01-09 03:45:43 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000008d9dc510f23c2657fc4f67bea30078cc05a90eb89e84cc475c080805 height=9 log2_work=35.32195 tx=10 date=2009-01-09 03:54:39 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000002c05cc2e78923c34df87fd108b22221ac6076c18f3ade378a4d915e9 height=10 log2_work=35.459454 tx=11 date=2009-01-09 04:05:52 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000097be56d606cdd9c54b04d4747e957d3608abe69198c661f2add73073 height=11 log2_work=35.584985 tx=12 date=2009-01-09 04:12:40 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000027c2488e2510d1acf4369787784fa20ee084c258b58d9fbd43802b5e height=12 log2_work=35.700462 tx=13 date=2009-01-09 04:21:28 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000005c51de2031a895adc145ee2242e919a01c6d61fb222a54a54b4d3089 height=13 log2_work=35.807377 tx=14 date=2009-01-09 04:23:40 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000080f17a0c5a67f663a9bc9969eb37e81666d9321125f0e293656f8a37 height=14 log2_work=35.906913 tx=15 date=2009-01-09 04:33:09 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=00000000b3322c8c3ef7d2cf6da009a776e6a99ee65ec5a32f3f345712238473 height=15 log2_work=36.000022 tx=16 date=2009-01-10 04:45:46 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=00000000174a25bb399b009cc8deff1c4b3ea84df7e93affaaf60dc3416cc4f5 height=16 log2_work=36.087485 tx=17 date=2009-01-10 04:45:58 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000003ff1d0d70147acfbef5d6a87460ff5bcfce807c2d5b6f0a66bfdf809 height=17 log2_work=36.169947 tx=18 date=2009-01-10 05:03:11 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000008693e98cf893e4c85a446b410bb4dfa129bd1be582c09ed3f0261116 height=18 log2_work=36.24795 t
|
|
|
I've been using various Python libraries, including Blockcypher, Chain.com, Blocktrail, etc so code a blockchain parser as a personal project. The API documentation for them all is quite reasonable. I was looking into Bitcoin ABE and understand Bitpay's Insight API advanced blockchain functionality, however the documentation seems incredibly lacking (I'm not well versed in Javascript yet). Can someone outline the advantages Insight's API and front end provide? Any related links (especially for Python!) would be greatly appreciated. TL:DR; what is so great about the Bitpay Insight API services?
|
|
|
There is something I don't understand about usage of OP_RETURN. I've read that UTXOs with OP_RETURN cannot be spent. That's a misnomer. Read below. However it is also said that those outputs can be used to indicate an ownership or control of a property. What if someone wants to transfer this kind of property to another peer while these outputs can not be spent. Thanks
You're paying the miner to accept the OP_RETURN data into a block. The fact that it's OP_RETURN means it's no longer a UTXO. The indication of ownership of property is simply this: information is preserved in the blockchain and is proved to be true by POW. What that info is, how it's read, what it means: none of that is determined by the blockchain.
|
|
|
I hope the wallet isn't costly like Trezor
Yeah, everything should be free. Especially when you consider SLs made profit from Trezor! The shame! Seriously though.... awesomeTRADER, why do you not have $100 for a Trezor?
|
|
|
Back online again answering questions via pm or on the forums!
How, just how, does someone with 6 posts get -6 reputation?
|
|
|
Maybe (cicada) have understood one of their responsibility in the thing of just the first and last wallets that remained and that is why they intervene ??
a winner will emerge I'm sure! I've figured several parts out and can assume it's a supplemented part of the rushwallet contest. Not sure, though I'll give a sha256 hash of where I stand presently: 68232890dcf8d70a6fa8b70b9adf974d364070338b618d86b4a18b9cf7bc5add
|
|
|
I don't think this actually has anything to do with Cicada. I think they're just trying to get across that it's a similar kind of puzzle and we have to figure tons of stuff out.
What has 30 sometimes and 31 other times? Contest started 22/Sept/14 ... 30 days in Sept Then new clues in Oct/Dec/Jan: 31 days in those months I'm almost there, but will share the 44% image part shortly
|
|
|
I don't think this actually has anything to do with Cicada. I think they're just trying to get across that it's a similar kind of puzzle and we have to figure tons of stuff out.
I'm soooooooooooooooooo close! To allay any doubts/challenges, I'm posting a digest of the puzzle's solution ........ 0x2ce99553c47a519d64f110c2aa4f03c1f614da3ccfa78c3f7cd1209e6dcf37d
|
|
|
|