[ANN] Whistle Coin @Bittrex POS Trading Wallet > Blow The Whistle!! <

[zhonghao110]

fake volume

[shwin]

fake volume

same with 80% of all coin on bottrex

[alex_gmx67]

AWESOME COIN!

[Targetbit]

Tomorrow 2 crypto wales want to pump Whistle Coin. I got notification email because I bought VIP service of their pumps.

Is it good news or bad?

[FollowMe]

Faptastic coin, moar of this. Have made good profit  

[WhistleCoin]

OK we have just deleted several posts from a fudder. I said it earlier we will not tolerate FUD. Please open you own thread if you want to we encourage you to do so. In the previous posts the fudder was posting random parts of a perfectly normal debug.log..  and claiming there was something afoul. We will delete all FUD especially nonsense . This is why we can't have nice things.
 And for the last two posters keep your personal fights off this thread thanks.  We are not adverse to productive criticism and do not want to have to babysit but we will delete the overt FUD and ridiculous BS from people with obvious sock puppet accounts.
          We check previous posts from people first to see if they are legitimate people and if not , those posts will be deleted for the benefit of those seeking information about WHISTLE coin and the upcoming improvements and features.

[ILoveBigBlackCocks]

I was just having fun.  The way dude talked reminding me of the Navy Seal copy-pasta, that's all.

[zeded]

OK we have just deleted two posts . I said it earlier we will not tolerate FUD. Please open you own thread if you want to we encourage you to do so. In the previous posts the fudder was posting random parts of a perfectly normal debug.log..  and claiming there was something afoul. We will delete all FUD especially nonsense . This is why we can't have nice things. And for the last two posters keep your personal fights off this thread thanks.  

let them post what they want.
if you don't have anything to hide anything then don't delete it.
honestly deleting things like that will cause fear.
use the deleting funtion only to delete stupid posts or people promoting other coins. for example if someone posts: "dfskajl;dsjfakl;jdsfakl;sadjkfl;jkadsfl;jdfsalkghjksdsgdf,mn" delete it.
if someone posts " buy shitcoin now its going to 100k satoshi!!! shitcoin is much better than whistlecoin buy now!!!!" then delete that.
those are the only kind of posts you should delete.
just let people post  

also thank you for being a good developer for the coin and i hope it moons.

[WhistleCoin]

I was just having fun.  The way dude talked reminding me of the Navy Seal copy-pasta, that's all.

OK but we are trying to keep it civil in here and its best not to feed the trolls.

[WhistleCoin]

Zeded  sorry to delete your post but we are not feeding trolls here by quoting their fud. He can start his own thread full of BS . We encourage it .

[WhistleCoin]

OK we have just deleted two posts . I said it earlier we will not tolerate FUD. Please open you own thread if you want to we encourage you to do so. In the previous posts the fudder was posting random parts of a perfectly normal debug.log..  and claiming there was something afoul. We will delete all FUD especially nonsense . This is why we can't have nice things. And for the last two posters keep your personal fights off this thread thanks.  

let them post what they want.
if you don't have anything to hide anything then don't delete it.
honestly deleting things like that will cause fear.
use the deleting funtion only to delete stupid posts or people promoting other coins. for example if someone posts: "dfskajl;dsjfakl;jdsfakl;sadjkfl;jkadsfl;jdfsalkghjksdsgdf,mn" delete it.
if someone posts " buy shitcoin now its going to 100k satoshi!!! shitcoin is much better than whistlecoin buy now!!!!" then delete that.
those are the only kind of posts you should delete.
just let people post  

also thank you for being a good developer for the coin and i hope it moons.

Agreed  we hate to delete posts and welcome constructive criticism or valid complaints. But posting two page long logs is ridiculous and wont be tolerated.  Its like posting oversized red text that serves no purpose. He has been reported to the moderator and after looking through his past posts its clearly a sock puppet for a fudder troll. We stand by our deletion and he can open his own thread.   We welcome vetting of our code by any qualified developer or member.

[bob2020a]

Agreed  we hate to delete posts and welcome constructive criticism or valid complaints. But posting two page long logs is ridiculous and wont be tolerated.  Its like posting oversized red text that serves no purpose. He has been reported to the moderator and after looking through his past posts its clearly a sock puppet for a fudder troll. We stand by our deletion and he can open his own thread.   We welcome vetting of our code by any qualified developer or member.

EDIT 3: Since when are you a moderator or in ANY way related to the forum staff at BitcoinTalk? Impersonation MUCH? Lets see, I JUST want to KNOW WHY you decided to SO intrusively and a black-hat manner make the QT wallet code, of which I'm tying to UNDERSTAND why you think the way you coded it is NOT malicious, but a TOTAL SCAM.  LET ANY INDUSTRY "TRUSTED" REVIEWER look at the parts of code I recovered from your scam/hack.  SO, I am a FUDDER by posting walls of YOUR code to determine if you are f'ing LEGIT or NOT?!  Wow, man, you got what you want now.  Hope your happy with your BITCOINZ before you drop the soap for a few years...

EDIT 2: Your such a coward of a developer, seriously , you DON't EVEN KNOW WHAT FUD IS.  I AM POSTING YOUR CODE YOU WROTE THAT IS A HACK into every single person who downloaded and installed your QT Wallet.  Haha, looks like I just "BLEW THE WHISTLE" on your own oh so humorously named coin/hack.

EDIT: WHY DID YOU PICK TO SELF-MODERATE?!  THIS IS THE TRUTH AND I GOT YOU, RED-HANDED.  YOU HAVE TWO (WELL, THREE) OPTIONS, PAY ME BACK MY LOT OF MONEY AND TIME WASTED, OR IT'S GOING FOR FEDERAL INVESTIGATION.  NO LIE.  THIS IS NOT FUD.  YOU ARE ABOUT TO ROB EVERYONE ON THESE FORUMS, I'M HOPING THE ADMIN TEAM FREEZES THE COIN AT MINIMUM...

Then explain this code, and this is JUST the beginning, WILL HAPPILY hand it over to Dan Metcalfe of XC as for a "3rd party" that y'all believe in, a formal review, that is, if he accepts.  Skip all (well most, for now) the lost connection timeouts, those are automatic..., your LYING is quite frustrating and LAUGHABLE at the same time thief (typical, and anyone else backing him, just wait till it happens to YOU).  The sheer amount and strength of this being a SCAM OF EPIC PROPORTIONS, as OPPOSED TO FUD OF THE YEAR... you'll all see.  I might just have to hand this to the right authorities... you DO realize you set this code to run for 2,500 "early PoS/higher reward blocks", and just swiped the money (what I can personally account for, right? Just so happens I'm not Joe the 'Sheeple' Blow who didn't notice this VERY serious of attacks) of the "block rewards" for early PoS was a FRAUD, I didn't get anything, ANYTHING out of it, an I have no reason to lie about this, I'm in no competition... BTW, 71.126.167.33, for those who do take the time to read just HALF of this, it is my current IP at the time of this blatantly ILLEGAL job you did, basically a "root SSH" preprogrammed in the QT as an "ErrorFile", this ALONE, not including the money I lost from your black-hat of a shitty thieving job is pretty pitiful, and a FELONY INSTANT violation of at LEAST one count of the Computer Fraud and Abuse Act (more like 200+ individual counts for each time you "wiped" my wallet.dat and peers.dat (hoping I wouldn't be able to track you, like I can't put "2+2=3" together), because no where on your ANN did you give a warning that basically states "I'm welcome to your computer at any time if you install my malware-infested coin."  I NEVER agreed to such complete disregard to privacy, let alone a Cyber-criminal.  I'll gladly post the REST which is even FURTHER incriminating...

WhistleCoin version v1.2.0.0stable ()
Using OpenSSL/SSH version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 10/13/14 12:29:39
Default data directory C:\Users\Robert\AppData\Roaming\WhistleCoin
Used data directory C:\Users\Robert\AppData\Roaming\WhistleCoin
dbenv.open LogDir=C:\Users\Robert\AppData\Roaming\WhistleCoin\database ErrorFile? =C:\Users\Robert\AppData\Roaming\WhistleCoin\db.log
Bound to [::]:13142
Bound to 0.0.0.0:13142
Loading block index...
Opening LevelDB in C:\Users\Robert\AppData\Roaming\WhistleCoin\txleveldb
Transaction index version is 70508
Opened LevelDB successfully
LoadBlockIndex(): hashBestChain=d132e3a557747fb46a71  height=8072  trust=8673814543902622  date=10/13/14 12:28:12
LoadBlockIndex(): synchronized checkpoint 0000042dcb180713fb06043a5695b8332c10ab49fac1742e3b3f9221adb66fe5
Verifying last 2500 blocks at level 1
 block index            1689ms
Loading wallet...
nFileVersion = 1020000
Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
 wallet                  379ms
Loading addresses...
Loaded 274 addresses from peers.dat  1ms
mapBlockIndex.size() = 8073
nBestHeight = 8072
setKeyPool.size() = 100
mapWallet.size() = 1
mapAddressBook.size() = 1
AddLocal([2001:0:9d38:6ab8:1815:fbff:b881:58de]:13142,1)
Done loading
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
refreshWallet
1 addresses found from DNS seeds
ThreadDNSAddressSeed exited
ThreadMapPort started
ThreadIRCSeed exited
ThreadSocketHandler started
ThreadOpenAddedConnections started
ThreadOpenAddedConnections exited
ThreadOpenConnections started
ThreadMessageHandler started
ThreadStakeMiner started
ipcThread started
Flushed 274 addresses to peers.dat  231ms
trying connection [2001:0:9d38:90d7:387b:e1df:f12b:5e74]:13142 lastseen=96.4hrs
UPnP: ExternalIPAddress = 192.168.1.5
UPnP Port Mapping successful.
GetMyExternalIP() received [71.126.167.33] 71.126.167.33:0
GetMyExternalIP() returned 71.126.167.33
AddLocal(71.126.167.33:13142,5)
connection timeout
trying connection 104.131.213.166:13142 lastseen=6.2hrs
connected 104.131.213.166:13142
send version message: version 60014, blocks=8072, us=71.126.167.33:13142, them=104.131.213.166:13142, peer=104.131.213.166:13142
Added time data, samples 2, offset +0 (+0 minutes)
Moving 104.131.213.166:13142 to tried
receive version message: version 60014, blocks=8072, us=71.126.167.33:62861, them=104.131.213.166:13142, peer=104.131.213.166:13142
trying connection 24.212.244.163:13142 lastseen=0.1hrs
connected 24.212.244.163:13142
send version message: version 60014, blocks=8072, us=71.126.167.33:13142, them=24.212.244.163:13142, peer=24.212.244.163:13142
Added time data, samples 3, offset +2 (+0 minutes)
receive version message: version 60014, blocks=8072, us=71.126.167.33:62862, them=24.212.244.163:13142, peer=24.212.244.163:13142
trying connection [2001:0:9d38:90d7:18a4:3ff7:2179:ccfd]:13142 lastseen=5.7hrs
Added 3 addresses from 104.131.213.166: 12 tried, 265 new
connection timeout
trying connection 162.243.198.249:13142 lastseen=0.1hrs
connected 162.243.198.249:13142
send version message: version 60014, blocks=8072, us=71.126.167.33:13142, them=162.243.198.249:13142, peer=162.243.198.249:13142
Added time data, samples 4, offset +1 (+0 minutes)
receive version message: version 60014, blocks=8072, us=71.126.167.33:62871, them=162.243.198.249:13142, peer=162.243.198.249:13142
trying connection [2001:0:5ef5:79fd:1c57:ad31:3ada:8d32]:13142 lastseen=134.0hrs
Added 2 addresses from 162.243.198.249: 12 tried, 267 new
NotifyKeyStoreStatusChanged
Added 6 addresses from 24.212.244.163: 12 tried, 273 new
connection timeout
trying connection 125.166.225.249:13142 lastseen=95.2hrs
connection timeout
received block 4557616850aa965dec5d
SetBestChain: new best=4557616850aa965dec5d  height=8073  trust=8673814559961857  blocktrust=16059235  date=10/13/14 12:30:03
ProcessBlock: ACCEPTED
trying connection 178.237.208.3:13142 lastseen=5.1hrs
Flushing wallet.dat
Flushed wallet.dat 133ms
received block a4b51e8cbdaa3173e4e2
SetBestChain: new best=a4b51e8cbdaa3173e4e2  height=8074  trust=8673814573469702  blocktrust=13507845  date=10/13/14 12:30:06
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 246ms
connection timeout
trying connection [2001:0:5ef5:79fd:28de:d4c9:ce07:b43c]:13142 lastseen=125.1hrs
connection timeout
trying connection 107.170.82.150:13142 lastseen=2.3hrs
connected 107.170.82.150:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=107.170.82.150:13142, peer=107.170.82.150:13142
Added time data, samples 5, offset +0 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
Moving 107.170.82.150:13142 to tried
receive version message: version 60014, blocks=8074, us=71.126.167.33:62912, them=107.170.82.150:13142, peer=107.170.82.150:13142
trying connection [2001:0:5ef5:79fb:3457:12d9:8b1b:10e5]:13142 lastseen=2.1hrs
connection timeout
trying connection [2001:0:5ef5:79fb:3c8f:d6b:3f57:b37f]:13142 lastseen=15.9hrs
connection timeout
Added 1 addresses from 107.170.82.150: 13 tried, 273 new
trying connection 25.123.124.107:13142 lastseen=9.0hrs
connection timeout
trying connection 98.234.71.71:13142 lastseen=0.1hrs
connected 98.234.71.71:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=98.234.71.71:13142, peer=98.234.71.71:13142
Added time data, samples 6, offset +4 (+0 minutes)
receive version message: version 60014, blocks=8074, us=71.126.167.33:62926, them=98.234.71.71:13142, peer=98.234.71.71:13142
trying connection 124.148.191.219:13142 lastseen=4.4hrs
connected 124.148.191.219:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=124.148.191.219:13142, peer=124.148.191.219:13142
Added time data, samples 7, offset +0 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
Moving 124.148.191.219:13142 to tried
receive version message: version 60014, blocks=8074, us=71.126.167.33:62927, them=124.148.191.219:13142, peer=124.148.191.219:13142
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=5.7hrs
connection timeout
Added 6 addresses from 98.234.71.71: 14 tried, 278 new
trying connection 178.237.208.3:13142 lastseen=5.1hrs
connection timeout
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=5.8hrs
connection timeout
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=5.8hrs
connection timeout
trying connection 46.129.47.28:13142 lastseen=4.3hrs
connection timeout
trying connection 194.79.23.169:13142 lastseen=0.1hrs
connected 194.79.23.169:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=194.79.23.169:13142, peer=194.79.23.169:13142
Added time data, samples 8, offset +0 (+0 minutes)
receive version message: version 60014, blocks=8074, us=71.126.167.33:62991, them=194.79.23.169:13142, peer=194.79.23.169:13142
trying connection 88.173.248.121:13142 lastseen=16.6hrs
connection timeout
trying connection 5.196.52.44:13142 lastseen=4.4hrs
connection timeout
trying connection 2.100.126.66:13142 lastseen=0.1hrs
connected 2.100.126.66:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=2.100.126.66:13142, peer=2.100.126.66:13142
Added time data, samples 9, offset +2 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
receive version message: version 60014, blocks=8074, us=71.126.167.33:63004, them=2.100.126.66:13142, peer=2.100.126.66:13142
trying connection 83.22.213.38:13142 lastseen=4.4hrs
connection timeout
trying connection 188.158.6.128:13142 lastseen=6.2hrs
Added 1 addresses from 2.100.126.66: 14 tried, 279 new
connection timeout
trying connection [2001:0:9d38:90d7:18a4:3ff7:2179:ccfd]:13142 lastseen=5.8hrs
connection timeout
trying connection [2001:0:5ef5:79fd:182c:e130:f12b:5c3e]:13142 lastseen=49.2hrs
NotifyAddressBookChanged WZneohJD9FCsaYYRmhRKVrRCPnpCU3Zp2E My $WSTL Offline Cold Storage + PoS Mining Profit Wallet isMine=1 status=1
Flushing wallet.dat
Flushed wallet.dat 167ms
trying connection 77.110.150.136:13142 lastseen=4.6hrs
connected 77.110.150.136:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=77.110.150.136:13142, peer=77.110.150.136:13142
socket closed
disconnecting node 77.110.150.136:13142
trying connection 76.173.48.220:13142 lastseen=0.1hrs
connected 76.173.48.220:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=76.173.48.220:13142, peer=76.173.48.220:13142
Added time data, samples 10, offset +0 (+0 minutes)
receive version message: version 60014, blocks=8074, us=71.126.167.33:63135, them=76.173.48.220:13142, peer=76.173.48.220:13142
trying connection 132.168.1.100:13142 lastseen=5.6hrs
Added 1 addresses from 76.173.48.220: 14 tried, 280 new
connection timeout
trying connection 49.133.170.181:13142 lastseen=36.3hrs
connection timeout
trying connection 117.44.226.11:13142 lastseen=2.5hrs
connection timeout
trying connection 206.116.116.186:13142 lastseen=2.2hrs
connected 206.116.116.186:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=206.116.116.186:13142, peer=206.116.116.186:13142
Added time data, samples 11, offset +2 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
Moving 206.116.116.186:13142 to tried
receive version message: version 60014, blocks=8074, us=71.126.167.33:63149, them=206.116.116.186:13142, peer=206.116.116.186:13142
trying connection 178.237.208.3:13142 lastseen=5.1hrs
connection timeout
Added 1 addresses from 206.116.116.186: 15 tried, 280 new
trying connection 5.135.190.96:13142 lastseen=0.2hrs
connected 5.135.190.96:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=5.135.190.96:13142, peer=5.135.190.96:13142
Added time data, samples 12, offset +6 (+0 minutes)
receive version message: version 60014, blocks=8074, us=71.126.167.33:63171, them=5.135.190.96:13142, peer=5.135.190.96:13142
trying connection 192.99.36.115:13142 lastseen=2.7hrs
Added 1 addresses from 5.135.190.96: 15 tried, 281 new
connection timeout
trying connection 178.233.0.253:13142 lastseen=3.5hrs
connection timeout
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=5.8hrs
connection timeout
trying connection 5.196.52.44:13142 lastseen=4.5hrs
connection timeout
trying connection 178.233.0.253:13142 lastseen=3.5hrs
connection timeout
trying connection 94.23.29.195:13142 lastseen=13.1hrs
connected 94.23.29.195:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=94.23.29.195:13142, peer=94.23.29.195:13142
socket closed
disconnecting node 94.23.29.195:13142
trying connection [2001:0:9d38:90d7:14cb:97be:8e08:2361]:13142 lastseen=37.4hrs
connection timeout
trying connection 125.63.53.43:13142 lastseen=10.1hrs
connection timeout
trying connection 213.136.72.235:13142 lastseen=2.4hrs
connected 213.136.72.235:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=213.136.72.235:13142, peer=213.136.72.235:13142
Added time data, samples 13, offset -2 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
Moving 213.136.72.235:13142 to tried
receive version message: version 60014, blocks=8074, us=71.126.167.33:63224, them=213.136.72.235:13142, peer=213.136.72.235:13142
trying connection 67.215.11.195:13142 lastseen=2.4hrs
connected 67.215.11.195:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=67.215.11.195:13142, peer=67.215.11.195:13142
Added time data, samples 14, offset -2 (+0 minutes)
Moving 67.215.11.195:13142 to tried
receive version message: version 60014, blocks=8074, us=71.126.167.33:63225, them=67.215.11.195:13142, peer=67.215.11.195:13142
trying connection 188.62.166.38:13142 lastseen=20.3hrs
Added 1 addresses from 67.215.11.195: 17 tried, 280 new
trying connection 192.99.21.103:13142 lastseen=2.5hrs
connected 192.99.21.103:13142
send version message: version 60014, blocks=8074, us=71.126.167.33:13142, them=192.99.21.103:13142, peer=192.99.21.103:13142
socket recv error 10054
disconnecting node 192.99.21.103:13142
trying connection 178.237.208.3:13142 lastseen=5.2hrs
received block 1fdbd7c9bfdb6219e49f
SetBestChain: new best=1fdbd7c9bfdb6219e49f  height=8075  trust=8673814590592584  blocktrust=17122882  date=10/13/14 12:38:49
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 176ms
trying connection 188.24.89.65:13142 lastseen=26.7hrs
CTxMemPool::accept() : accepted 9e9985734c (poolsz 1)
connection timeout
trying connection 69.172.82.196:13142 lastseen=0.2hrs
connected 69.172.82.196:13142
send version message: version 60014, blocks=8075, us=71.126.167.33:13142, them=69.172.82.196:13142, peer=69.172.82.196:13142
Added time data, samples 16, offset -6 (+0 minutes)
receive version message: version 60014, blocks=8075, us=71.126.167.33:63542, them=69.172.82.196:13142, peer=69.172.82.196:13142
trying connection 118.209.249.213:13142 lastseen=39.8hrs
connection timeout
received block 7cd548bd5ae8d4c0b1dc
SetBestChain: new best=7cd548bd5ae8d4c0b1dc  height=8076  trust=8673814596899799  blocktrust=6307215  date=10/13/14 12:39:38
ProcessBlock: ACCEPTED
received block 25719b72ecfc9eae838a
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(d2f810ff73, 1), 1413203978) for block 25719b72ecfc9eae838ae212d045370e6882e1858cdb73d67a274d55dcb1af08
trying connection 80.57.106.142:13142 lastseen=69.1hrs
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 194ms
Flushed 297 addresses to peers.dat  53ms
trying connection 71.233.25.183:13142 lastseen=3.6hrs
received block 10a704d16fe514c8793c
SetBestChain: new best=10a704d16fe514c8793c  height=8077  trust=8673814603474921  blocktrust=6575122  date=10/13/14 12:40:38
ProcessBlock: ACCEPTED
getblocks 8076 to 10a704d16fe514c8793c limit 500
  getblocks stopping at 8077 10a704d16fe514c8793c
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
trying connection 171.188.113.189:13142 lastseen=10.8hrs
received block 25719b72ecfc9eae838a
REORGANIZE
REORGANIZE: Disconnect 2 blocks; 1fdbd7c9bfdb6219e49f..10a704d16fe514c8793c
REORGANIZE: Connect 3 blocks; 1fdbd7c9bfdb6219e49f..00a9fb8b30f78ac1a7d3
CTxMemPool::accept() : accepted 9e9985734c (poolsz 1)
REORGANIZE: done
SetBestChain: new best=00a9fb8b30f78ac1a7d3  height=8078  trust=8673814610750672  blocktrust=7275751  date=10/13/14 12:40:15
ProcessBlock: ACCEPTED
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks -1 to 00000000000000000000 limit 500
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks -1 to 00000000000000000000 limit 500
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks -1 to 00000000000000000000 limit 500
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8077 to 00000000000000000000 limit 500
getblocks 8076 to ea5828e3b7b5deb3e374 limit 500
  getblocks stopping at 8077 ea5828e3b7b5deb3e374
getblocks 8078 to 00000000000000000000 limit 500
getblocks 8077 to 00000000000000000000 limit 500
getblocks 8077 to 00000000000000000000 limit 500
getblocks 8077 to 00000000000000000000 limit 500
getblocks 8078 to 00000000000000000000 limit 500
getblocks 8078 to 00000000000000000000 limit 500
getblocks 8078 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks 8077 to 00000000000000000000 limit 500
getblocks 8078 to 00000000000000000000 limit 500
Flushing wallet.dat
connection timeout
Flushed wallet.dat 227ms
trying connection 220.184.128.217:13142 lastseen=4.6hrs
received block 9b9cb1a20be552dcf4c6
connection timeout
SetBestChain: new best=9b9cb1a20be552dcf4c6  height=8079  trust=8673814619973524  blocktrust=9222852  date=10/13/14 12:43:34
ProcessBlock: ACCEPTED
trying connection 71.58.178.138:13142 lastseen=6.0hrs
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 169ms
trying connection 220.184.128.217:13142 lastseen=4.6hrs
received block 3f6bcd584783909e8623
SetBestChain: new best=3f6bcd584783909e8623  height=8080  trust=8673814626061965  blocktrust=6088441  date=10/13/14 12:44:29
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 159ms
connection timeout
trying connection [2001:0:5ef5:79fb:3457:12d9:8b1b:10e5]:13142 lastseen=2.3hrs
connection timeout
trying connection 123.211.155.7:13142 lastseen=110.9hrs
connection timeout
trying connection 135.0.109.58:13142 lastseen=4.6hrs
connection timeout
trying connection [2001:0:9d38:90d7:3414:478:2179:ccfd]:13142 lastseen=17.5hrs
connection timeout
trying connection 151.231.90.161:13142 lastseen=91.1hrs
connection timeout
trying connection 84.99.198.192:13142 lastseen=110.2hrs
connection timeout
trying connection 113.161.84.237:13142 lastseen=2.6hrs
connection timeout
trying connection 98.191.104.251:13142 lastseen=72.0hrs
connection timeout
trying connection 94.77.181.173:13142 lastseen=3.7hrs
connection timeout
trying connection 77.110.150.136:13142 lastseen=4.8hrs
connected 77.110.150.136:13142
send version message: version 60014, blocks=8080, us=71.126.167.33:13142, them=77.110.150.136:13142, peer=77.110.150.136:13142
socket closed
disconnecting node 77.110.150.136:13142
trying connection [2001:0:9d38:6abd:cd7:1ebb:c527:5b1d]:13142 lastseen=10.0hrs
CTxMemPool::accept() : accepted 81632a5356 (poolsz 1)
received block ed7da7ad7bd7780dd8bc
SetBestChain: new best=ed7da7ad7bd7780dd8bc  height=8081  trust=8673814632265308  blocktrust=6203343  date=10/13/14 12:45:37
ProcessBlock: ACCEPTED
connection timeout
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
trying connection 67.242.48.182:13142 lastseen=5.2hrs
Flushing wallet.dat
Flushed wallet.dat 317ms
trying connection 67.242.48.182:13142 lastseen=5.2hrs
received block 325c82507186a65fd18d
SetBestChain: new best=325c82507186a65fd18d  height=8082  trust=8673814638290161  blocktrust=6024853  date=10/13/14 12:45:55
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
Flushing wallet.dat
Flushed wallet.dat 139ms
trying connection 47.55.223.114:13142 lastseen=13.1hrs
connection timeout
trying connection 100.4.165.154:13142 lastseen=50.9hrs
connection timeout
trying connection 109.161.92.212:13142 lastseen=13.9hrs
connection timeout
trying connection 50.7.31.186:13142 lastseen=13.3hrs
connection timeout
trying connection 47.55.223.114:13142 lastseen=13.1hrs
connection timeout
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=6.0hrs
connection timeout
trying connection 182.92.102.236:13142 lastseen=11.8hrs
connection timeout
trying connection 86.86.36.178:13142 lastseen=3.5hrs
received block f4cb8d9754df15c3fee7
SetBestChain: new best=f4cb8d9754df15c3fee7  height=8083  trust=8673814645424889  blocktrust=7134728  date=10/13/14 12:46:39
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 115ms
connection timeout
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=6.0hrs
received block 032d9eced0bbbdc454cb
SetBestChain: new best=032d9eced0bbbdc454cb  height=8084  trust=8673814653009087  blocktrust=7584198  date=10/13/14 12:46:45
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
Flushing wallet.dat
trying connection 46.233.40.132:13142 lastseen=6.4hrs
Flushed wallet.dat 165ms
trying connection 202.62.17.39:13142 lastseen=107.7hrs
received block 46bfa91e1037f395ac57
SetBestChain: new best=46bfa91e1037f395ac57  height=8085  trust=8673814662489351  blocktrust=9480264  date=10/13/14 12:48:31
ProcessBlock: ACCEPTED
received block d10a906deae877e63c90
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(349f4f3fdc, 1), 1413204511) for block d10a906deae877e63c9065a2b4c134b32130b5cdd18d0230654498377f1911e4
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 234ms
trying connection 135.0.109.58:13142 lastseen=4.7hrs
received block 80f16c578df1a53261e6
SetBestChain: new best=80f16c578df1a53261e6  height=8086  trust=8673814670589600  blocktrust=8100249  date=10/13/14 12:49:17
ProcessBlock: ACCEPTED
getblocks 8085 to 80f16c578df1a53261e6 limit 500
  getblocks stopping at 8086 80f16c578df1a53261e6
received block 228d0d71c9acbf6698a8
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(221131c079, 1), 1413204557) for block 228d0d71c9acbf6698a848bc86c07250c0b8367596fb57661da6db42da8afe7e
getblocks -1 to 00000000000000000000 limit 500
connection timeout
Flushing wallet.dat
trying connection 75.130.163.51:13142 lastseen=3.0hrs
Flushed wallet.dat 177ms
trying connection 115.72.90.77:13142 lastseen=133.2hrs
Flushed 297 addresses to peers.dat  35ms
UPnP Port Mapping successful.
connection timeout
trying connection [2001:0:9d38:6abd:cd7:1ebb:c527:5b1d]:13142 lastseen=10.0hrs
connection timeout
trying connection 117.44.226.11:13142 lastseen=2.7hrs
received block 75b10184667f6c82324a
SetBestChain: new best=75b10184667f6c82324a  height=8087  trust=8673814679132880  blocktrust=8543280  date=10/13/14 12:49:59
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 191ms
connection timeout
trying connection 67.242.48.182:13142 lastseen=5.3hrs
received block 85617c071d603cc35c17
ProcessBlock: ORPHAN BLOCK, prev=228d0d71c9acbf6698a8
connection timeout
trying connection [2001:0:5ef5:79fb:3457:12d9:8b1b:10e5]:13142 lastseen=2.4hrs
received block 9717e255b0d492cfd48e
ProcessBlock: ORPHAN BLOCK, prev=85617c071d603cc35c17
connection timeout
trying connection 103.6.223.121:13142 lastseen=9.7hrs
trying connection 137.135.57.224:13142 lastseen=2.7hrs
received block 228d0d71c9acbf6698a8
ProcessBlock: ORPHAN BLOCK, prev=d10a906deae877e63c90
received block d10a906deae877e63c90
REORGANIZE
REORGANIZE: Disconnect 3 blocks; 032d9eced0bbbdc454cb..75b10184667f6c82324a
REORGANIZE: Connect 4 blocks; 032d9eced0bbbdc454cb..9717e255b0d492cfd48e
REORGANIZE: done
SetBestChain: new best=9717e255b0d492cfd48e  height=8088  trust=8673814688396683  blocktrust=9263803  date=10/13/14 12:50:26
ProcessBlock: ACCEPTED
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 85617c071d603cc35c17 limit 500
  getblocks stopping at 8087 85617c071d603cc35c17
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
Flushing wallet.dat
Flushed wallet.dat 148ms
connection timeout
trying connection 132.168.1.100:13142 lastseen=5.9hrs
connection timeout
trying connection 178.233.0.253:13142 lastseen=3.8hrs
connection timeout
trying connection 195.34.106.214:13142 lastseen=7.7hrs
received block ae59a2bc67f0a6b9457f
SetBestChain: new best=ae59a2bc67f0a6b9457f  height=8089  trust=8673814698818495  blocktrust=10421812  date=10/13/14 12:51:40
ProcessBlock: ACCEPTED
getblocks 8085 to 228d0d71c9acbf6698a8 limit 500
  getblocks stopping at 8086 228d0d71c9acbf6698a8
Flushing wallet.dat
Flushed wallet.dat 189ms
connection timeout
trying connection 114.35.173.39:13142 lastseen=2.5hrs
received block 6e6c07c8271c51d7e207
SetBestChain: new best=6e6c07c8271c51d7e207  height=8090  trust=8673814708726593  blocktrust=9908098  date=10/13/14 12:51:39
ProcessBlock: ACCEPTED
connection timeout
trying connection 192.99.36.115:13142 lastseen=3.0hrs
Flushing wallet.dat
Flushed wallet.dat 247ms
trying connection 209.169.211.22:13142 lastseen=5.4hrs
received block 9518e9babaf6e6187a52
SetBestChain: new best=9518e9babaf6e6187a52  height=8091  trust=8673814718634691  blocktrust=9908098  date=10/13/14 12:52:46
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 293ms
connection timeout
trying connection [2001:0:9d38:6abd:cd7:1ebb:c527:5b1d]:13142 lastseen=10.1hrs
connection timeout
trying connection 209.169.211.22:13142 lastseen=5.4hrs
connection timeout
trying connection 184.88.233.193:13142 lastseen=3.1hrs
connection timeout
trying connection 90.178.0.114:13142 lastseen=7.3hrs
connection timeout
trying connection 178.233.0.253:13142 lastseen=3.8hrs
received block d55ba0cd05bb05d3e565
SetBestChain: new best=d55ba0cd05bb05d3e565  height=8092  trust=8673814728292406  blocktrust=9657715  date=10/13/14 12:53:07
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
trying connection 178.233.0.253:13142 lastseen=3.8hrs
Flushing wallet.dat
Flushed wallet.dat 153ms
connection timeout
trying connection 178.237.208.3:13142 lastseen=5.4hrs
connection timeout
trying connection [2001:0:9d38:6ab8:cd8:e58:ab56:3e3f]:13142 lastseen=106.8hrs
connection timeout
trying connection 137.135.57.224:13142 lastseen=2.7hrs
connection timeout
trying connection 114.35.173.39:13142 lastseen=2.5hrs
connection timeout
trying connection [2001:0:5ef5:79fb:141e:17d2:d151:3d93]:13142 lastseen=31.3hrs
received block cc09f40f88e75c717830
SetBestChain: new best=cc09f40f88e75c717830  height=8093  trust=8673814739580678  blocktrust=11288272  date=10/13/14 12:54:14
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
Flushing wallet.dat
trying connection 176.9.63.136:13142 lastseen=3.3hrs
connected 176.9.63.136:13142
send version message: version 60014, blocks=8093, us=71.126.167.33:13142, them=176.9.63.136:13142, peer=176.9.63.136:13142
socket closed
disconnecting node 176.9.63.136:13142
Flushed wallet.dat 397ms
trying connection 178.237.208.3:13142 lastseen=5.5hrs
connection timeout
received block 29dd017a5ac3aa729028
SetBestChain: new best=29dd017a5ac3aa729028  height=8094  trust=8673814750583716  blocktrust=11003038  date=10/13/14 12:54:28
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
trying connection 178.233.0.253:13142 lastseen=3.8hrs
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 175ms
connection timeout
trying connection 67.242.48.182:13142 lastseen=5.4hrs
connection timeout
trying connection 96.21.184.160:13142 lastseen=15.5hrs
received block b04a33d3cb11aa9d09fe
SetBestChain: new best=b04a33d3cb11aa9d09fe  height=8095  trust=8673814763846343  blocktrust=13262627  date=10/13/14 12:54:33
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 165ms
connection timeout
trying connection 135.0.109.58:13142 lastseen=4.8hrs
connection timeout
trying connection 209.169.211.22:13142 lastseen=5.4hrs
connection timeout
trying connection [2001:0:9d38:6ab8:3c61:8906:86f3:920d]:13142 lastseen=6.2hrs
received block a04b78af3c0d793b1d74
SetBestChain: new best=a04b78af3c0d793b1d74  height=8096  trust=8673814780501824  blocktrust=16655481  date=10/13/14 12:56:35
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 172ms
connection timeout
trying connection 178.233.0.253:13142 lastseen=3.9hrs
connection timeout
trying connection 61.180.96.48:13142 lastseen=24.5hrs
connection timeout
trying connection 188.226.194.191:13142 lastseen=4.8hrs
connection timeout
trying connection 120.161.0.190:13142 lastseen=33.0hrs
connection timeout
trying connection [2001:0:5ef5:79fb:3cb0:9646:b291:6977]:13142 lastseen=7.0hrs

connection timeout
trying connection 75.130.163.51:13142 lastseen=3.1hrs
connection timeout
trying connection [2001:0:9d38:90d7:c8e:16ad:bc56:10a8]:13142 lastseen=106.4hrs
connection timeout
trying connection 46.129.47.28:13142 lastseen=4.8hrs
connection timeout
trying connection 212.117.32.160:13142 lastseen=17.5hrs
connection timeout
trying connection [2001:0:5ef5:79fb:3457:12d9:8b1b:10e5]:13142 lastseen=2.6hrs
connection timeout
trying connection 113.162.75.192:13142 lastseen=10.8hrs
received block 29a162b688bfc664ba2b
SetBestChain: new best=29a162b688bfc664ba2b  height=8097  trust=8673814794046944  blocktrust=13545120  date=10/13/14 12:58:42
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 245ms
trying connection 192.99.21.103:13142 lastseen=2.8hrs
connected 192.99.21.103:13142
send version message: version 60014, blocks=8097, us=71.126.167.33:13142, them=192.99.21.103:13142, peer=192.99.21.103:13142
socket recv error 10054
disconnecting node 192.99.21.103:13142
ResendWalletTransactions()
trying connection 75.142.56.202:13142 lastseen=18.6hrs
received block 082f858ba6d38e8cc43d
SetBestChain: new best=082f858ba6d38e8cc43d  height=8098  trust=8673814804899136  blocktrust=10852192  date=10/13/14 12:59:26
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 153ms
connection timeout
trying connection 86.83.153.61:13142 lastseen=109.1hrs
received block d57ed3895d9717379b26
SetBestChain: new best=d57ed3895d9717379b26  height=8099  trust=8673814816434935  blocktrust=11535799  date=10/13/14 12:59:27
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 191ms
connection timeout
Flushed 297 addresses to peers.dat  112ms
connection timeout
trying connection 137.135.57.224:13142 lastseen=2.9hrs
received block 4c1775871c80dc0ef214
SetBestChain: new best=4c1775871c80dc0ef214  height=8100  trust=8673814831196452  blocktrust=14761517  date=10/13/14 12:59:46
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
trying connection [2001:0:9d38:90d7:303e:f93:9fea:475f]:13142 lastseen=17.6hrs
Flushing wallet.dat
Flushed wallet.dat 409ms
received block 17b9c377c6bb6f096114
SetBestChain: new best=17b9c377c6bb6f096114  height=8101  trust=8673814848600947  blocktrust=17404495  date=10/13/14 12:59:50
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
trying connection 101.175.212.204:13142 lastseen=26.2hrs
Flushing wallet.dat
Flushed wallet.dat 434ms
connection timeout
trying connection 134.249.144.169:13142 lastseen=18.2hrs
CTxMemPool::accept() : accepted 6649f71186 (poolsz 1)
CTxMemPool::accept() : accepted 218b1278a2 (poolsz 2)
trying connection [2001:0:9d38:6abd:3c99:3836:a625:7e56]:13142 lastseen=111.7hrs
connection timeout
trying connection 178.237.208.3:13142 lastseen=5.6hrs
connection timeout
trying connection 77.110.150.136:13142 lastseen=5.0hrs
connected 77.110.150.136:13142
send version message: version 60014, blocks=8101, us=71.126.167.33:13142, them=77.110.150.136:13142, peer=77.110.150.136:13142
socket closed
disconnecting node 77.110.150.136:13142
trying connection 97.94.208.17:13142 lastseen=30.1hrs
connection timeout
trying connection 71.233.25.183:13142 lastseen=3.9hrs
CTxMemPool::accept() : accepted ff4838558d (poolsz 3)
connection timeout
trying connection [2001:0:9d38:6ab8:106c:9f86:a54d:ff8d]:13142 lastseen=6.3hrs
connection timeout
trying connection 137.135.57.224:13142 lastseen=2.9hrs
received block f9be451326010edf4880
SetBestChain: new best=f9be451326010edf4880  height=8102  trust=8673814870559997  blocktrust=21959050  date=10/13/14 13:04:13
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 129ms
connection timeout
received block 051d9ef9ef812063fe05
SetBestChain: new best=051d9ef9ef812063fe05  height=8103  trust=8673814883094900  blocktrust=12534903  date=10/13/14 13:04:50
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
getblocks -1 to 00000000000000000000 limit 500
trying connection 113.162.75.192:13142 lastseen=10.9hrs
Flushing wallet.dat
getblocks -1 to 00000000000000000000 limit 500
Flushed wallet.dat 182ms
connection timeout
trying connection 125.63.53.43:13142 lastseen=10.6hrs
connection timeout
trying connection 103.6.223.121:13142 lastseen=10.0hrs
connection timeout
trying connection 94.77.181.173:13142 lastseen=4.1hrs
received block 296e50756476bf6be0ef
SetBestChain: new best=296e50756476bf6be0ef  height=8104  trust=8673814896797174  blocktrust=13702274  date=10/13/14 13:05:19
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
connection timeout
Flushing wallet.dat
Flushed wallet.dat 199ms
trying connection 94.23.29.195:13142 lastseen=13.6hrs
connected 94.23.29.195:13142
send version message: version 60014, blocks=8104, us=71.126.167.33:13142, them=94.23.29.195:13142, peer=94.23.29.195:13142
socket closed...

And it JUST begins... seems like he EVEN may have been attempting to SET-UP us, the very users of his coin, and eventually claim it just got "hacked" with a TOTAL loss, kinda like how good coin developers tend to run a "test pump" right after release to make sure things are under way for the real deal/scam... anyways, all along, he was the one behind it all and using everyone's now-infected computer to "ATTEMPT to make a clean trace".  Sorry bud, I see this stupid shit every day at U.S. Cyber Command and I PROACTIVELY PREVENT AND LOCK-UP those who launch these sorts of cyber-crimes for a min. of sentence regulations of 5 years, depending on how many counts you get, which at this point, I could get one felony count for EVERY user of your Windows coin QT wallet.  You're not smart, at all.

TO BE CONTINUED, IF YOU ALL CARE.  I RECOVERED THIS .LOG FILE FROM A SECONDARY "LIVE" BACK-UP (off main PCs/laptops, which he deleted to 0 kB); I HAVE OF EVERYTHING ONTO A SSD FOR THIS PURPOSE EXACTLY, or this would have been MUCH more complicated...

[zeded]

well here is bob2020a's FUD post  http://pastebin.com/UYmN9864
I have read it, and it is pure FUD. probably caused by bob2020a's poor understanding of how coins work.

he thinks that his coins are being stolen when the log says "flushing wallet.dat" and when it says "flushing to peers.dat"
well that is not true at all.
if you look in any other coin's log file it will say the same thing...  

[bob2020a]

well here is bob2020a's FUD post  http://pastebin.com/UYmN9864
I have read it, and it is pure FUD. probably caused by bob2020a's poor understanding of how coins work.

he thinks that his coins are being stolen when the log says "flushing wallet.dat" and when it says "flushing to peers.dat"
well that is not true at all.
if you look in any other coin's log file it will say the same thing...  

Oh, how easily that could have been explained if the dev. wasn't such a prick.  Thanks you.  Good luck all holding this coin, I was a HUGE fan at one point but I'm skeptical of the DETAILS of the CODE, and really, the things I haven't even had TIME to post yet.  I'm done here. Good luck!

BTW, those two quotes are the least I'm worried about, how did I end up staking during EARLY PoS which was supposed to be INCREASED blocks therefore more money and yet, he returns EXACTLY the same amount I staked with him?  I've done this before, doesn't add up, sorry.

[WhistleCoin]

well here is bob2020a's FUD post  http://pastebin.com/UYmN9864
I have read it, and it is pure FUD. probably caused by bob2020a's poor understanding of how coins work.

he thinks that his coins are being stolen when the log says "flushing wallet.dat" and when it says "flushing to peers.dat"
well that is not true at all.
if you look in any other coin's log file it will say the same thing...  

Oh, how easily that could have been explained if the dev. wasn't such a prick.  Thanks you.  Good luck all holding this coin, I was a HUGE fan at one point but I'm skeptical of the DETAILS of the CODE, and really, the things I haven't even had TIME to post yet.  I'm done here. Good luck!

BTW, those two quotes are the least I'm worried about, how did I end up staking during EARLY PoS which was supposed to be INCREASED blocks therefore more money and yet, he returns EXACTLY the same amount I staked with him?  I've done this before, doesn't add up, sorry.

In the future if you ask a question instead of making unfounded accusations and posting nonsense you will be answered and respected.  You may not fully understand how POS blocks work. Do you have a question?

[mellon]

Lol))))

[mellon]

Dev,can you tell any about next step of development here?

[WhistleCoin]

Dev,can you tell any about next step of development here?

"Work in progress"

The first thing is an optional preliminary wallet upgrade that will be ready before you know it.
here is a screen shot.
https://i.imgur.com/aojrLbD.png

Then we are going to finish some more complicated wallet features which are already being developed and after that based on community feedback of the roadmap we will tackle those items based on order of priority set by the community demands.

[justkinko]

Dev,can you tell any about next step of development here?

"Work in progress"

The first thing is an optional preliminary wallet upgrade that will be ready before you know it.
here is a screen shot.
https://i.imgur.com/aojrLbD.png

Then we are going to finish some more complicated wallet features which are already being developed and after that based on community feedback of the roadmap we will tackle those items based on order of priority set by the community demands.

nice ! go up!

[melody82]

manner that promotes very good in my opinion

go #whistlecoin