[TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico

[vancefox]

Brand new blockchain and new wallet 2.2.1.

For anyone wondering, exact same functionality as 2.2.0 but it will fix your forkage if you have found yourself on a forked chain.

Happy staking!

[1714136174]

1714136174

[1714136174]

1714136174

[1714136174]

1714136174

[HYPster]

I've been wondering this for awhile now so maybe a dev can help me understand this. Why does it take so long to load the wallet? I understand that it has to load the blk file, but this file is not exceptionally large. So why does it take so freaking long before wallet opens??? I have numerous other wallets and all of them have different times before they open. I do realize that the number of blocks matter, but still it is not a crazy large of a file. Please help me understand this as I would GREATLY appreciate it!!!!!!!!!!!!

[m33]

Does any one have shares not paid , (pending) from tek multipool?

[dollux]

Yesterday they where pending most of the day because of delays with Cryptsy and today they are at pending till later in the day but there is no clear reason given.

Taken from thepool.pw/TEK site

Notice: Payouts delayed, they will be processed later today.

[m33]

Yesterday they where pending most of the day because of delays with Cryptsy and today they are at pending till later in the day but there is no clear reason given.

Taken from thepool.pw/TEK site

Notice: Payouts delayed, they will be processed later today.

So they stop buying tek , why are we still mining !Or are they buying but can't send out?

[muddafudda]

The 2.2.0 client I downloaded from OP 3 days ago registers as v2.2.0.0-gf96a5a-noise23. If I have a look at github, clients on the v2.2.0.0-gf96a5a-noise23 should have the checkpoints from block  683658 as ( 683658, uint256("0x0000000000008c51b5caee62b2f51179e722863981d6f99249a752c7502759f3")). When checking the client there is no checkpoint from this block and the client was able to download the chain on the wrong hash.
Getblockbynumber 683658  "hash" : "00000000002b4a9d88e5421ec2a5b7cf95dc447871daffb4b55cbdf192a7092f". Im not sure what happened but the 2.2.0.0.

Now when I run getcheckpoint on the client it returns

Code:

getcheckpoint
21:43:13

{
"synccheckpoint" : "00000eaa8dd7e902871c444aeb415673b8244c6b7b1742ca398cefa60d87c4c1",
"height" : 0,
"timestamp" : "2013-08-11 10:01:09 UTC",
"policy" : "strict"
}

which means the 2.2.0 client has no checkpoints as that hash is the genesis block. So basically I have wasted a ton of downloads and time investigating what looks like a dud windows client release.

Not happy mate.

[vancefox]

The 2.2.0 client I downloaded from OP 3 days ago registers as v2.2.0.0-gf96a5a-noise23. If I have a look at github, clients on the v2.2.0.0-gf96a5a-noise23 should have the checkpoints from block  683658 as ( 683658, uint256("0x0000000000008c51b5caee62b2f51179e722863981d6f99249a752c7502759f3")). When checking the client there is no checkpoint from this block and the client was able to download the chain on the wrong hash.
Getblockbynumber 683658  "hash" : "00000000002b4a9d88e5421ec2a5b7cf95dc447871daffb4b55cbdf192a7092f". Im not sure what happened but the 2.2.0.0.

Now when I run getcheckpoint on the client it returns

Code:

getcheckpoint
21:43:13

{
"synccheckpoint" : "00000eaa8dd7e902871c444aeb415673b8244c6b7b1742ca398cefa60d87c4c1",
"height" : 0,
"timestamp" : "2013-08-11 10:01:09 UTC",
"policy" : "strict"
}

which means the 2.2.0 client has no checkpoints as that hash is the genesis block. So basically I have wasted a ton of downloads and time investigating what looks like a dud windows client release.

Not happy mate.

Don't understand why you had a problem.  I used 2.2.0 just fine with my old blockchain and decided to trial run a brand new fresh install of 2.2.1 per instructions to provide third party feedback to everyone and everything came out perfectly after bootstrap load.

I have had no problems with noise's wallets.  Please download the bootstrap provided and load through that along with the nodes that have been provided to ensure that you are on the chain that all the rest of the coin community is on.

[noise23]

The 2.2.0 client I downloaded from OP 3 days ago registers as v2.2.0.0-gf96a5a-noise23. If I have a look at github, clients on the v2.2.0.0-gf96a5a-noise23 should have the checkpoints from block  683658 as ( 683658, uint256("0x0000000000008c51b5caee62b2f51179e722863981d6f99249a752c7502759f3")). When checking the client there is no checkpoint from this block and the client was able to download the chain on the wrong hash.
Getblockbynumber 683658  "hash" : "00000000002b4a9d88e5421ec2a5b7cf95dc447871daffb4b55cbdf192a7092f". Im not sure what happened but the 2.2.0.0.

Now when I run getcheckpoint on the client it returns

Code:

getcheckpoint
21:43:13

{
"synccheckpoint" : "00000eaa8dd7e902871c444aeb415673b8244c6b7b1742ca398cefa60d87c4c1",
"height" : 0,
"timestamp" : "2013-08-11 10:01:09 UTC",
"policy" : "strict"
}

which means the 2.2.0 client has no checkpoints as that hash is the genesis block. So basically I have wasted a ton of downloads and time investigating what looks like a dud windows client release.

Not happy mate.

Your 2.2.0 client didn't get checkpoints from the checkpointing server because your wallet was on the wrong chain.

On your screensot are using 'checkpoint' command instead of 'getcheckpoint'.
To get checkpoint info type 'getcheckpoint'.

You have to re-sync:

1. Download TEK bootstrap.dat -  http://richlist.truckcoin.net/tekbootstrap.zip
2. Delete old blockchain files and peers.dat
2. Unzip bootstrap.dat to the tekcoin data directory (where wallet.dat is).
3. In the same directory create tekcoin.conf file with the following lines:

Code:

connect=69.197.161.122
connect=104.193.43.106
connect=104.218.234.124
connect=104.218.234.125
connect=199.233.245.36

4. Start the wallet. It will import blockchain from bootstrap.dat (will take some time, at least 2-3 hours).
5. (IMPORTANT!) When fully synced, change tekcoin.conf lines from "connect=" to "addnode=" and restart the wallet.

[muddafudda]

My client wouldnt pass that block if the checkpoint is in the client. Try it, put in a bad checkpoint and it wont download the chain. Thats the whole point of checkpoints.


But yes, once again thanks for wasting a whole bunch of my time on fuck all, appreciate it.

[noise23]

My client wouldnt pass that block if the checkpoint is in the client. Try it, put in a bad checkpoint and it wont download the chain. Thats the whole point of checkpoints.

Yes, that's why hardened checkpoint at 683658 has been added in v2.2.1
v2.2.0 binaries were built before that commit.

[muddafudda]

My client wouldnt pass that block if the checkpoint is in the client. Try it, put in a bad checkpoint and it wont download the chain. Thats the whole point of checkpoints.

Yes, that's why hardened checkpoint at 683658 has been added in v2.2.1
v2.2.0 binaries were built before that commit.

That hardened checkpoint was added 26 days ago. 2 days after 2.2.0. So why was the checkpoint added 2 days after the 2.2.0 release and sat there for 26 days before you released the 2.2.1 client. Your 2.2.0 client really did a whole heap of nothing and to release a client without a checkpoint update is amateur at best. Shit you guys just realised how to put in stake modifiers, after 2 years ROFL.

So for anyone to claim that the 2.2.0 is the correct chain is wrong, to deny their is a massive big fork out there is wrong.

Blundertoe honestly, if you need this shit done right just ask. Ill do it cheaper than these cowboys thats for sure.

EDIT: You might want to explain checkpoints to @vancefox

[gribgo]

Yesterday they where pending most of the day because of delays with Cryptsy and today they are at pending till later in the day but there is no clear reason given.

Taken from thepool.pw/TEK site

Notice: Payouts delayed, they will be processed later today.

So they stop buying tek , why are we still mining !Or are they buying but can't send out?

If we know that Cryptsy is upgrading to the newest version of the wallet... so this what holds Multipool payout!
The hasrate is low at the Multipool because of the very simple situation - people who are related to TEKcoin have sha256 algo miners mostly and it was PayCoin (XPY) mining faze, which is also sha256
The difficulty on Bitcoin network stabilized and does not go up like a rocket now - this fact makes BTC attractive to mine at the moment!
So now its just more profitable to mine BTC or Peercoin (PPC), but our multipool does not have this coins among the list of supported coins.. so people have to switch manually and will stay there until the difficulty rise again...
I asked the Multipool Admin about adding this coins (BTC and PPC) to the list of sha256 mined coins, but he answered this -

"Quote from: gribgo on December 22, 2014, 09:35:44 PM
Please put bitcoin and peercoin to list of sha256 coins mined at the multipool!
Marry Xmass good luck and happy new year!!!
peace
Thanx for TEKcoin Multipool! Like it alot.. just have to switch from your pool when bitcoin is more profit to mine directly and peercoin too!
but if you add this it will be present for all.. you can promote it!  Like: - MARY XMAS MINERS!!! HERE IS THE PRESENT 4 U!! I add btc annd ppc to list of coins we mine at or pool now!! Yooohhoooo!

Hi gribgo,

Unfortunately i cannot add btc or ppc as they require a lot of hash to find a block, the pool is mining directly from rpc and not using other pools.

Thanks,
sakr"

HAPPY NEW YEAR - PEACE! Not F.... WAR!
P.S. I am from Russia, but I am global.. I am from planet Earth and I don't give a fu.. about all this geography.. I love to meet earthlings from all over the world!
When aliens attack all nations will unite

ANY COMMENTS ARE WELCOME.. !!!

--
=I/O CONFLIKT=
listen to some of my muzik people - https://soundcloud.com/hiiz-io-conflikt/sets/my-chosen-playlist-my-own

[thundertoe]

check your on the right block at http://tek.blockchain.lt/

version 2.2.0 is ok, if you have issues go ahead and upgrade to 2.2.1

If syncing is stuck because your wallet got some blocks from the forked node. You have to delete blockchain files and re-sync from the scratch with correct nodes.
The fastest way is:

1. Download TEK bootstrap.dat -  http://richlist.truckcoin.net/tekbootstrap.zip
2. Delete old blockchain files and peers.dat
2. Unzip bootstrap.dat to the tekcoin data directory (where wallet.dat is).
3. In the same directory create tekcoin.conf file with the following lines:


connect=69.197.161.122
connect=104.193.43.106
connect=104.218.234.124
connect=104.218.234.125
connect=199.233.245.36

4. Start the wallet. It will import blockchain from bootstrap.dat (will take some time, at least 2-3 hours).
5. (IMPORTANT!) When fully synced, change tekcoin.conf lines from "connect=" to "addnode=" and restart the wallet.

[vancefox]

My client wouldnt pass that block if the checkpoint is in the client. Try it, put in a bad checkpoint and it wont download the chain. Thats the whole point of checkpoints.

Yes, that's why hardened checkpoint at 683658 has been added in v2.2.1
v2.2.0 binaries were built before that commit.

That hardened checkpoint was added 26 days ago. 2 days after 2.2.0. So why was the checkpoint added 2 days after the 2.2.0 release and sat there for 26 days before you released the 2.2.1 client. Your 2.2.0 client really did a whole heap of nothing and to release a client without a checkpoint update is amateur at best. Shit you guys just realised how to put in stake modifiers, after 2 years ROFL.

So for anyone to claim that the 2.2.0 is the correct chain is wrong, to deny their is a massive big fork out there is wrong.

Blundertoe honestly, if you need this shit done right just ask. Ill do it cheaper than these cowboys thats for sure.

EDIT: You might want to explain checkpoints to @vancefox

I don't need an explanation... not all of us (you) have a hard time figuring out things...

I didn't have a single problem with 2.2.0 which ran up till today.  I upgraded to 2.2.1 today with a complete fresh install without a problem...

Remember, whenever you point the finger at someone three are pointing right at the real problem.

[muddafudda]

My client wouldnt pass that block if the checkpoint is in the client. Try it, put in a bad checkpoint and it wont download the chain. Thats the whole point of checkpoints.

Yes, that's why hardened checkpoint at 683658 has been added in v2.2.1
v2.2.0 binaries were built before that commit.

That hardened checkpoint was added 26 days ago. 2 days after 2.2.0. So why was the checkpoint added 2 days after the 2.2.0 release and sat there for 26 days before you released the 2.2.1 client. Your 2.2.0 client really did a whole heap of nothing and to release a client without a checkpoint update is amateur at best. Shit you guys just realised how to put in stake modifiers, after 2 years ROFL.

So for anyone to claim that the 2.2.0 is the correct chain is wrong, to deny their is a massive big fork out there is wrong.

Blundertoe honestly, if you need this shit done right just ask. Ill do it cheaper than these cowboys thats for sure.

EDIT: You might want to explain checkpoints to @vancefox

I don't need an explanation... not all of us (you) have a hard time figuring out things...

I didn't have a single problem with 2.2.0 which ran up till today.  I upgraded to 2.2.1 today with a complete fresh install without a problem...

Remember, whenever you point the finger at someone three are pointing right at the real problem.

Your lack of knowledge and understanding have made TEK look like a bit of a joke. I hope your not involved in the team because really you have no idea.

I was willing to back TEK 100%, stake and follow it. Now I know you have two chumps in here calling shit wrong and for that I dumped.


Blundertoe I thought you had shit in control here but an unpatched 9000 block fork is not great at all.

And Vancefox, I lol and lol some more. Did you find out what a checkpoint is yet?

[muddafudda]

check your on the right block at http://tek.blockchain.lt/

version 2.2.0 is ok, if you have issues go ahead and upgrade to 2.2.1

If syncing is stuck because your wallet got some blocks from the forked node. You have to delete blockchain files and re-sync from the scratch with correct nodes.
The fastest way is:

1. Download TEK bootstrap.dat -  http://richlist.truckcoin.net/tekbootstrap.zip
2. Delete old blockchain files and peers.dat
2. Unzip bootstrap.dat to the tekcoin data directory (where wallet.dat is).
3. In the same directory create tekcoin.conf file with the following lines:


connect=69.197.161.122
connect=104.193.43.106
connect=104.218.234.124
connect=104.218.234.125
connect=199.233.245.36

4. Start the wallet. It will import blockchain from bootstrap.dat (will take some time, at least 2-3 hours).
5. (IMPORTANT!) When fully synced, change tekcoin.conf lines from "connect=" to "addnode=" and restart the wallet.

Version 2.2.0 is not ok as you have a 50% chance of being on the 9000 block fork. There is only 3 checkpoints and no stake modifiers in 2.2.0. Checkpoints in 2.2.0 are block 0,1 and 474965. 2.2.1 added a checkpoint for 683658 which is 100% necessary as the 9000 block fork, forks from the main chain before block 683658.

I hate doing this shit but please dont lie, I hate it. Especially when the proof is in the blockchain.

Just to clarify the 9000 block fork is the block difference I refer to. The chain sits around block 720000 while the fork was at 729000, so in theory you probably should have followed the longer chain. Second since the fork occurred before block 683658, it actually makes it a 47,000 block fork.

[m33]

My client wouldnt pass that block if the checkpoint is in the client. Try it, put in a bad checkpoint and it wont download the chain. Thats the whole point of checkpoints.

Yes, that's why hardened checkpoint at 683658 has been added in v2.2.1
v2.2.0 binaries were built before that commit.

That hardened checkpoint was added 26 days ago. 2 days after 2.2.0. So why was the checkpoint added 2 days after the 2.2.0 release and sat there for 26 days before you released the 2.2.1 client. Your 2.2.0 client really did a whole heap of nothing and to release a client without a checkpoint update is amateur at best. Shit you guys just realised how to put in stake modifiers, after 2 years ROFL.

So for anyone to claim that the 2.2.0 is the correct chain is wrong, to deny their is a massive big fork out there is wrong.

Blundertoe honestly, if you need this shit done right just ask. Ill do it cheaper than these cowboys thats for sure.

EDIT: You might want to explain checkpoints to @vancefox

I don't need an explanation... not all of us (you) have a hard time figuring out things...

I didn't have a single problem with 2.2.0 which ran up till today.  I upgraded to 2.2.1 today with a complete fresh install without a problem...

Remember, whenever you point the finger at someone three are pointing right at the real problem.

Your lack of knowledge and understanding have made TEK look like a bit of a joke. I hope your not involved in the team because really you have no idea.

I was willing to back TEK 100%, stake and follow it. Now I know you have two chumps in here calling shit wrong and for that I dumped.


Blundertoe I thought you had shit in control here but an unpatched 9000 block fork is not great at all.

And Vancefox, I lol and lol some more. Did you find out what a checkpoint is yet?

First I like to thank you for dumping , so that I could buy cheap
Next if you dun like it here , please leave since you already sold out
Last noise23 has been doing a great job for free , has saved other coins before . So if you looking for a job go beg at other coin unless you can contribute for free , which is the going rate for noise23 work.

Ps . I'll support any coin if noise23 is one of devs, thanks for great job noise23

[aSmallChild666]

I'm on wallet v 2.1.  Works just fine.  Any reason for me to change?

[m33]

I'm on wallet v 2.1.  Works just fine.  Any reason for me to change?

If I'm not wrong any wallet below 220 will be rejected

[dennislevy]

Hey, TekHeads!

Happy and Prosperous New Year!

I downloaded 2.2 wallet and had no problem.
I downloaded 2.2.1 wallet and had no problem.
Ran walletcheck and repairwallet and everything is fine. Staked a couple of times now and added some more coin.
Everything worked okie dokie. I guess, I was one of the lucky ones?

In any case, I think we should show some love to Noise. Working tirelessly on wallet upgrades, block explorer and
the rich list. Without which, we would no be able to stake coins, check our wallet and make sure we are on the
right block chain. And the rich list that kept crashing before, Noise came over and helped out.

I think we should start a bounty for him! I will start it off with a donation/tip of:
TekCoin    BrS57oUjVRcEhqEG7jBzLSEFi9s3gVNkd6    540.00020000 TEK    Yes    2015-01-01 18:09:37
Processed    TrxID: 5e8ce2fdeab4bd0ed0f849ed114cae88d0bd21abc65e5ee4fdf159ec06d72032 @ 2015-01-01 18:22:07

I think if you are still staking donate/tip him as well! Come on TEK Heads dig into your wallet and show Noise some LOVE!
Do not think he had to do any of this, yet he jumped if without be asked or paid for his time or setting up block explorer
and rich list on his own site. I appreciate what you have done to help this community! Thanks Noise!

To A Happy and Prosperous TEK New Year!

Peace, Dennis