Node at 70.181.40.178 was reporting the highest block height and wallet v1.1 but I can not connect to it anymore. That node seems to be connected to both
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 225. (Read 446058 times)
It is impossible to tell who is trusted "seeder".
Until we have trusted seeders we can not use the wallet unless you want to risk loosing coins.Hope I have not lost any coins while re-arranging my stacks.
So where we at with this, we need to rebuild the wallet or will just using the correct nodes.
It is impossible to tell who is trusted "seeder".
Damn !
Sorry for sounding harsh here, but how on earth could you release a client without proper fail-save build in !!
No checkpoints ??
No rejection of old clients ??
Again sorry for my harsh words on this, but this is BIG time stupid if you consider how many coins have screwed up in the past exactly by not implementing these fail-save tricks !
Do NOT use in your config addnode= use connect= and make sure you have listen=0
This will force the wallet only to connect to given/known trusted "seeders".
============
listen=1
connect=
connect=
============
Sorry for sounding harsh here, but how on earth could you release a client without proper fail-save build in !!
No checkpoints ??
No rejection of old clients ??
Again sorry for my harsh words on this, but this is BIG time stupid if you consider how many coins have screwed up in the past exactly by not implementing these fail-save tricks !
Do NOT use in your config addnode=
This will force the wallet only to connect to given/known trusted "seeders".
============
listen=1
connect=
connect=
============
This mess actualy took "The biggest hard-fork mess reward" from Terracoin (3 or 4 hard-forks in a single week but it was not as ugly as this one). 
HAHA! I still count this one as one hardfork
with a few blocks being orphaned >_< build this and give it a try, it will take a resynch
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
1. Majority of hashrate is solo mining (possibly at 70.181.40.178) using wallet v1.1 and can be seen at http://tek_blockcrawler.miners-point.com/block_crawler.php and also
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool (compare block heights, they are the same).
2. http://tek.dsync.net/index.php?page=statistics&action=pool is on different block height.
3. http://xguild.net/tek/index.php?page=statistics&action=pool and http://tek.blockx.info/get/chain/TekCoin are also on very different block heigh.
yea it seems once a few stake blocks minted after 506500 everyone was calculating the difficulty differently, this actually happened with CAPS and mullick reminded me of it. This fix should keep everything smooth.
This mess actualy took "The biggest hard-fork mess reward" from Terracoin (3 or 4 hard-forks in a single week but it was not as ugly as this one).
build this and give it a try, it will take a resynch
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
1. Majority of hashrate is at 70.181.40.178 and he is solo mining using wallet v1.1 and can be seen at http://tek_blockcrawler.miners-point.com/block_crawler.php and also
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool (compare block heights, they are the same).
2. http://tek.dsync.net/index.php?page=statistics&action=pool is on different block height.
3. http://xguild.net/tek/index.php?page=statistics&action=pool and http://tek.blockx.info/get/chain/TekCoin are also on very different block heigh.
Yea we will get them to change over, testing out this fix. So far it seems to work but we wont know until more people use it and sync.
connect=74.196.63.95
build this and give it a try, it will take a resynch
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
1. Majority of hashrate is solo mining (possibly at 70.181.40.178) using wallet v1.1 and can be seen at http://tek_blockcrawler.miners-point.com/block_crawler.php and also
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool (compare block heights, they are the same).
2. http://tek.dsync.net/index.php?page=statistics&action=pool is on different block height.
3. http://xguild.net/tek/index.php?page=statistics&action=pool and http://tek.blockx.info/get/chain/TekCoin are also on very different block heigh.
so is there any pools confirmed to be on the correct fork yet?
build this and give it a try, it will take a resynch
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
https://github.com/chrisfranko/TEK/commit/f982faeb6a580d5f6030fc460b9e3dce1b8461b0
im on 506604
updated source with a fix from defaced https://github.com/maxxine/TEK testing it seems ok.. edit maybe not hold on.... 
Ofeefee I figured it out, sorry for the waste of time, don't know why the add node is missing from the RPC call list.. but regardless, there was a hidden character in the conf file for some reason.. all works now (except for the other issues). Thanks for your help!!
Next question, if a TEK pool has updated their wallet, is it safe to mine there? or shoo;d we hold off regardless?
Next question, if a TEK pool has updated their wallet, is it safe to mine there? or shoo;d we hold off regardless?
OK, before I go to sleep - a final analysis:
1. http://xguild.net and http://tek.blockx.info/get/chain/TekCoin are on the same wrong fork, not a single PoS block was generated on it for over few thousand blocks.
2. Majority of hashrate is most likely a solo miner at 70.181.40.178
Good luck!
1. http://xguild.net and http://tek.blockx.info/get/chain/TekCoin are on the same wrong fork, not a single PoS block was generated on it for over few thousand blocks.
2. Majority of hashrate is most likely a solo miner at 70.181.40.178
Good luck!
Addnode huh, interesting. Code doesn't have DNS seeds I tried to see if they were there and maybe use them to sync, other option is to see if anyone has good checkpoints, Dev changed out key so assume he has this running on the network to give us an idea of what to shoot for. Run getcheckpoint if you are in sync and see if anyone has new ones being sent to network.
At dinner but will look later see what else. In the interim, just hang tight, when its fixed, you will have your coins and other things like exchanges will flow properly as well.
If mullick is monitoring can you let us know what block Cryptsy is on?
At dinner but will look later see what else. In the interim, just hang tight, when its fixed, you will have your coins and other things like exchanges will flow properly as well.
If mullick is monitoring can you let us know what block Cryptsy is on?
Is cryptsy having deposit issues? I made a deposit and i have 70 confirmation and it is still not posted on my cryptsy account
I sent a few there 4.5hrs ago... still not there
here are RPC calls available from the help menu
16:57:48

addmultisigaddress <'["key","key"]'> [account]
backupwallet
checkwallet
createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...}
decoderawtransaction
dumpprivkey
encryptwallet
getaccount
getaccountaddress
getaddressesbyaccount
getbalance [account] [minconf=1]
getblock [txinfo]
getblock [txinfo]
getblockcount
getblockhash
getblocktemplate [params]
getcheckpoint
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getmininginfo
getnetworkhashps [blocks]
getnewaddress [account]
getnewpubkey [account]
getpeerinfo
getrawmempool
getrawtransaction [verbose=0]
getreceivedbyaccount [minconf=1]
getreceivedbyaddress [minconf=1]
gettransaction
getwork [data]
getworkex [data, coinbase]
help [command]
importprivkey [label]
keypoolrefill
listaccounts [minconf=1]
listaddressgroupings
listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]
listsinceblock [blockhash] [target-confirmations]
listtransactions [account] [count=10] [from=0]
listunspent [minconf=1] [maxconf=9999999] ["address",...]
makekeypair [prefix]
move [minconf=1] [comment]
repairwallet
resendtx
reservebalance [ [amount]]
sendalert [cancelupto]
sendfrom [minconf=1] [comment] [comment-to]
sendmany {address:amount,...} [minconf=1] [comment]
sendrawtransaction
sendtoaddress [comment] [comment-to]
setaccount
setgenerate [genproclimit]
settxfee
signmessage
signrawtransaction [{"txid":txid,"vout":n,"scriptPubKey":hex},...] [,...] [sighashtype="ALL"]
stop
submitblock [optional-params-obj]
validateaddress
validatepubkey
verifymessage
addnode is missing
16:57:48

addmultisigaddress
backupwallet
checkwallet
createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...}
decoderawtransaction
dumpprivkey
encryptwallet
getaccount
getaccountaddress
getaddressesbyaccount
getbalance [account] [minconf=1]
getblock
getblock
getblockcount
getblockhash
getblocktemplate [params]
getcheckpoint
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getmininginfo
getnetworkhashps [blocks]
getnewaddress [account]
getnewpubkey [account]
getpeerinfo
getrawmempool
getrawtransaction
getreceivedbyaccount
getreceivedbyaddress
gettransaction
getwork [data]
getworkex [data, coinbase]
help [command]
importprivkey
keypoolrefill
listaccounts [minconf=1]
listaddressgroupings
listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]
listsinceblock [blockhash] [target-confirmations]
listtransactions [account] [count=10] [from=0]
listunspent [minconf=1] [maxconf=9999999] ["address",...]
makekeypair [prefix]
move
repairwallet
resendtx
reservebalance [
sendalert
sendfrom
sendmany
sendrawtransaction
sendtoaddress
setaccount
setgenerate
settxfee
signmessage
signrawtransaction
stop
submitblock
validateaddress
validatepubkey
verifymessage
addnode is missing
If I make a tekcoin.conf file it immediately crashes the wallet when I run the wallet. doesn't even report to the debug log.
how about trying to delete the peers.dat and modifying the tekcoin.conf file. Just add the nodes you want and remove the old nodes then restart the wallet.
Jump to: