What are the odds I'll get a valid copy of the blockchain from these hosts?
Pls wait, I'll put up a bootstrap file for download soon.
Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 152. (Read 446058 times)
Pls wait, I'll put up a bootstrap file for download soon.
Invalid checkpoint problem.
I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
It seems like your wallet caught a bad block from an obsolete peer. Please re-sync with v2.2I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output:
Code:
{
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
try to synch without using those addnodes some of them seem to be bad, i am able to synch without using any addnodes at all
I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output:
Code:
{
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
It seems like you are still on a fork - current blockheight is only 683362 - http://tek.blockchain.lt/ , yours is 684620.
Unfortunately, you have to re-sync again.
Delete blockchain files and peers.dat and add these nodes to tekcoin.conf -
Code:
addnode=69.197.161.122
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36
I previously had no addnode lines in there (well, I had some, but they were all commented out). I tried putting the lines above in as "connect=" instead, but wasn't able to get through to download blocks in a reasonable time.
They're in now as addnodes and not connects. As I write this, getblockcount returns 15106 and getpeerinfo returns these addresses:
46.166.164.221
182.170.206.51
66.215.60.93
93.183.214.228
None are running Tekcoin 2.2. Here's the full getpeerinfo output:
Code:
[
{
"addr" : "46.166.164.221:8514",
"services" : "00000001",
"lastsend" : 1417794375,
"lastrecv" : 1417794375,
"conntime" : 1417794051,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684741,
"banscore" : 0
},
{
"addr" : "182.170.206.51:8514",
"services" : "00000001",
"lastsend" : 1417794422,
"lastrecv" : 1417794422,
"conntime" : 1417794171,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 93980,
"banscore" : 0
},
{
"addr" : "66.215.60.93:8514",
"services" : "00000001",
"lastsend" : 1417794412,
"lastrecv" : 1417794412,
"conntime" : 1417794227,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684745,
"banscore" : 0
},
{
"addr" : "93.183.214.228:8514",
"services" : "00000001",
"lastsend" : 1417794405,
"lastrecv" : 1417794405,
"conntime" : 1417794337,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 368479,
"banscore" : 0
}
]
{
"addr" : "46.166.164.221:8514",
"services" : "00000001",
"lastsend" : 1417794375,
"lastrecv" : 1417794375,
"conntime" : 1417794051,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684741,
"banscore" : 0
},
{
"addr" : "182.170.206.51:8514",
"services" : "00000001",
"lastsend" : 1417794422,
"lastrecv" : 1417794422,
"conntime" : 1417794171,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 93980,
"banscore" : 0
},
{
"addr" : "66.215.60.93:8514",
"services" : "00000001",
"lastsend" : 1417794412,
"lastrecv" : 1417794412,
"conntime" : 1417794227,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684745,
"banscore" : 0
},
{
"addr" : "93.183.214.228:8514",
"services" : "00000001",
"lastsend" : 1417794405,
"lastrecv" : 1417794405,
"conntime" : 1417794337,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 368479,
"banscore" : 0
}
]
What are the odds I'll get a valid copy of the blockchain from these hosts?
very good odds as long as they are not running older than 2.1.1 this 2.2 version just bans version prior to 2.1.1
I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output:
Code:
{
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
It seems like you are still on a fork - current blockheight is only 683362 - http://tek.blockchain.lt/ , yours is 684620.
Unfortunately, you have to re-sync again.
Delete blockchain files and peers.dat and add these nodes to tekcoin.conf -
Code:
addnode=69.197.161.122
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36
I previously had no addnode lines in there (well, I had some, but they were all commented out). I tried putting the lines above in as "connect=" instead, but wasn't able to get through to download blocks in a reasonable time.
They're in now as addnodes and not connects. As I write this, getblockcount returns 15106 and getpeerinfo returns these addresses:
46.166.164.221
182.170.206.51
66.215.60.93
93.183.214.228
None are running Tekcoin 2.2. Here's the full getpeerinfo output:
Code:
[
{
"addr" : "46.166.164.221:8514",
"services" : "00000001",
"lastsend" : 1417794375,
"lastrecv" : 1417794375,
"conntime" : 1417794051,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684741,
"banscore" : 0
},
{
"addr" : "182.170.206.51:8514",
"services" : "00000001",
"lastsend" : 1417794422,
"lastrecv" : 1417794422,
"conntime" : 1417794171,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 93980,
"banscore" : 0
},
{
"addr" : "66.215.60.93:8514",
"services" : "00000001",
"lastsend" : 1417794412,
"lastrecv" : 1417794412,
"conntime" : 1417794227,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684745,
"banscore" : 0
},
{
"addr" : "93.183.214.228:8514",
"services" : "00000001",
"lastsend" : 1417794405,
"lastrecv" : 1417794405,
"conntime" : 1417794337,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 368479,
"banscore" : 0
}
]
{
"addr" : "46.166.164.221:8514",
"services" : "00000001",
"lastsend" : 1417794375,
"lastrecv" : 1417794375,
"conntime" : 1417794051,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684741,
"banscore" : 0
},
{
"addr" : "182.170.206.51:8514",
"services" : "00000001",
"lastsend" : 1417794422,
"lastrecv" : 1417794422,
"conntime" : 1417794171,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 93980,
"banscore" : 0
},
{
"addr" : "66.215.60.93:8514",
"services" : "00000001",
"lastsend" : 1417794412,
"lastrecv" : 1417794412,
"conntime" : 1417794227,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684745,
"banscore" : 0
},
{
"addr" : "93.183.214.228:8514",
"services" : "00000001",
"lastsend" : 1417794405,
"lastrecv" : 1417794405,
"conntime" : 1417794337,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 368479,
"banscore" : 0
}
]
What are the odds I'll get a valid copy of the blockchain from these hosts?
I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output:
Code:
{
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
It seems like you are still on a fork - current blockheight is only 683362 - http://tek.blockchain.lt/ , yours is 684620.
Unfortunately, you have to re-sync again.
Delete blockchain files and peers.dat and add these nodes to tekcoin.conf -
Code:
addnode=69.197.161.122
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36
Invalid checkpoint problem.
I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
It seems like your wallet caught a bad block from an obsolete peer. Please re-sync with v2.2I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output:
Code:
{
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
Hi!
Does anyone have an opportunity to put block chain for download?
Thanks!
Does anyone have an opportunity to put block chain for download?
Thanks!
Quote
They should be in your wallet.
Check transactions IDs in built-in block browser, does it recognize them?
Check transactions IDs in built-in block browser, does it recognize them?
Okay I took the advice on updating the wallet to v 2.2.0.0 and then resynced the wallet from scratch and that recovered 1500 coins from cryptsy! So hopefully the wallet and network are now stable. Thanks for the help!
I have a similar problem
decided to update wallet
and here the problem:
In file included from src/qt/blockbrowser.cpp:2:
build/ui_blockbrowser.h: In member function ‘void Ui_BlockBrowser::retranslateUi(QDialog*)’:
build/ui_blockbrowser.h:362: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
It builds fine with Qt 4.8.6decided to update wallet
and here the problem:
In file included from src/qt/blockbrowser.cpp:2:
build/ui_blockbrowser.h: In member function ‘void Ui_BlockBrowser::retranslateUi(QDialog*)’:
build/ui_blockbrowser.h:362: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
blockbrowser is a standard code used in many coins, nothing specific to TEK
Debian 6 LTC amd64
no build fine
tekcoin version v2.0.1.0-gf96a5a-TEKv2.0.1.0-gf96a5a-TEK -build fine
obvious progress
Your security support expires in 2016. Bite the bullet and upgrade to Debian 7 "Wheezy" now. You'll have a much easier time building wallets going forward.
It's all self-deception.
The problem is a complete misunderstanding of stability
and backward compatibility.
For a month all broke and ruined his reputation.
There is no point chasing it all.
people have no idea that there is a stable, tested and unstable versions
programs ))
do not know anything about the lifetime of programs and distro
Only from git and only the last slice ))
I have a similar problem
decided to update wallet
and here the problem:
In file included from src/qt/blockbrowser.cpp:2:
build/ui_blockbrowser.h: In member function ‘void Ui_BlockBrowser::retranslateUi(QDialog*)’:
build/ui_blockbrowser.h:362: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
It builds fine with Qt 4.8.6decided to update wallet
and here the problem:
In file included from src/qt/blockbrowser.cpp:2:
build/ui_blockbrowser.h: In member function ‘void Ui_BlockBrowser::retranslateUi(QDialog*)’:
build/ui_blockbrowser.h:362: error: ‘class QLineEdit’ has no member named ‘setPlaceholderText’
blockbrowser is a standard code used in many coins, nothing specific to TEK
Debian 6 LTC amd64
no build fine
tekcoin version v2.0.1.0-gf96a5a-TEKv2.0.1.0-gf96a5a-TEK -build fine
obvious progress
Your security support expires in 2016. Bite the bullet and upgrade to Debian 7 "Wheezy" now. You'll have a much easier time building wallets going forward.
Yeah, everything seems like it should be in my wallet, the wallet says I am at block 681834 right now.
Why the hell cant I see the transaction in my wallet...
Why the hell cant I see the transaction in my wallet...
not present transaction ID:
1f68c822163d13bcd30b20a5074e3a4e105d980ddcf22c69cf3b0de81ce70443
18f591bd2678c17e7387b9d2f20622fe9a05b766db0a72bdad819af21ac04058
983d47a04aca6c8cecca33ff9e695b5a2918f7284e7be12e9a96e13e03c4c501
af001384590341bd78d90305baa79eedaa8f1a8fb7a89d8bf1c16a04b139617a
1f68c822163d13bcd30b20a5074e3a4e105d980ddcf22c69cf3b0de81ce70443
18f591bd2678c17e7387b9d2f20622fe9a05b766db0a72bdad819af21ac04058
983d47a04aca6c8cecca33ff9e695b5a2918f7284e7be12e9a96e13e03c4c501
af001384590341bd78d90305baa79eedaa8f1a8fb7a89d8bf1c16a04b139617a
You are on a wrong fork, probably because of outdated wallet.
Make sure your wallet version is at least 2.1.0.0 - versions below 2.1 are obsolete.
Please download or build the latest wallet version and re-sync.
Here is the latest build:
windows - http://downloads.truckcoin.net/misc/tekcoin-2.2.0.0.zip
ubuntu x64 - http://downloads.truckcoin.net/misc/tekcoin-2.2.0.0-ubuntu-x64.tar.gz
github - https://github.com/noise23/TEK/
Version 2.2.0.0 is a minor update which should prevent catching bad blocks from obsolete clients.
My 2.1 version wallets were not syncing or staking properly *** since this morning ***...
So everyone should probably just update to 2.2.0.0 and carry on.
And a good way to thank noise23 is to buy/trade some TRK...
Relative to the rest of the High Stake sector...
TRK should be trading in the 1000-1500 range...
At 400 it's a good value in relative terms.
I saw a 16 coin payout from my pool that I use. I watched the incoming notification from the wallet what it had got 16 coins but they are no wheres to be found. Their not in any list.. not in the pending .. no where!. Where the hell did almost 75 coins go? Though it matters not now as I'm done with tek coins. I'm also done with all bitcoin stuff. It's all way too kludgy and cost too much to mine. Good bye.
It seems that Cryptsy is still using old wallet version.
What is new wallet actualy about? Why hard-fork? Why different checkpoint? Was checkpoint changed before or after hard-fork point? All this looks to me like another shady deal, where someone messed with blockchain data for his profit. It will be fun to watch the show if Cryptsy ends up with negative TEK or BTC balance.
What is new wallet actualy about? Why hard-fork? Why different checkpoint? Was checkpoint changed before or after hard-fork point? All this looks to me like another shady deal, where someone messed with blockchain data for his profit. It will be fun to watch the show if Cryptsy ends up with negative TEK or BTC balance.
No shady deal your just behind on the process that happened over the update and hardfork. The hardfork was awhile ago, but the checkpoint server was just recently activated. This last wallet update only changes the accepting of peers using old versions, cryptsy not using a version that old so they are fine.
It seems that Cryptsy is still using old wallet version.
What is new wallet actualy about? Why hard-fork? Why different checkpoint? Was checkpoint changed before or after hard-fork point? All this looks to me like another shady deal, where someone messed with blockchain data for his profit. It will be fun to watch the show if Cryptsy ends up with negative TEK or BTC balance.
What is new wallet actualy about? Why hard-fork? Why different checkpoint? Was checkpoint changed before or after hard-fork point? All this looks to me like another shady deal, where someone messed with blockchain data for his profit. It will be fun to watch the show if Cryptsy ends up with negative TEK or BTC balance.
The OP needs to be updated with the correct source-code location. I built tekcoind from the source at https://github.com/maxxine/TEK yesterday and let it download the blockchain. It ended up on what I'm guessing is an invalid fork, as a few hours' mining at iSpace yesterday never showed up in my wallet, but according to http://tek.blockchain.lt/address/BrRijfWVpWkR8WeJ4DeWmUwxQFc1qp2oMu, nearly 24 coins had been paid out.
I've rebuilt tekcoind, this time with source from https://github.com/noise23/TEK, the link to which I found buried in this thread in some posts from mid-November. It looked like it was going to take an abnormally long time to fix the already-downloaded forked blockchain, so I just saved tekcoin.conf and wallet.dat and am downloading it again.
(According to this post, the block explorer is on the correct chain, which means iSpace is also on the correct chain. As I write this, my copy of the blockchain is up to #109248; it still has a while to go.)
I've rebuilt tekcoind, this time with source from https://github.com/noise23/TEK, the link to which I found buried in this thread in some posts from mid-November. It looked like it was going to take an abnormally long time to fix the already-downloaded forked blockchain, so I just saved tekcoin.conf and wallet.dat and am downloading it again.
(According to this post, the block explorer is on the correct chain, which means iSpace is also on the correct chain. As I write this, my copy of the blockchain is up to #109248; it still has a while to go.)
I updated to 2.2.0 .. changed to a backup copy of my wallet which now checks out as good. Tried to repair my old wallet and it kept giving an error -2 and would not repair. I still have it as a backup.bak but I'm still not able to retrieve my coins that are floating out there somewhere.
is there a wonderful Mac OS X version?? 
Actually v2.2 has no new features, just supposed to help those who have syncing problems. Invalid checkpoint problem.
I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
It seems like your wallet caught a bad block from an obsolete peer. Please re-sync with v2.2 I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
Invalid checkpoint problem.
I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
is there a wonderful Mac OS X version??
Jump to: