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

[B3dr0ck]

How to tell I'm running the correct Wallet

I downloaded the windows wallet from the dropbox link, backup'd my wallet.dat, unzipped it, ran the QT - sync'd, all looks fine.

Is there a way I can tell if I'm on the correct wallet for the fork coming up?

[Biomech]

How to tell I'm running the correct Wallet

I downloaded the windows wallet from the dropbox link, backup'd my wallet.dat, unzipped it, ran the QT - sync'd, all looks fine.

Is there a way I can tell if I'm on the correct wallet for the fork coming up?

Well, if you have the github link, you can look at a line in main.cpp. But if you are certain you're running the one from the dropbox link, it is correct. The version number wasn't incremented in the source. Thundertoe is aware of it and it'll be fixed at some point, but I noticed it after things were already pushed. The collective decision was to just go ahead anyway. Just be sure you ran the new QT and you're fine.

[mafort1469]

How to tell I'm running the correct Wallet

I downloaded the windows wallet from the dropbox link, backup'd my wallet.dat, unzipped it, ran the QT - sync'd, all looks fine.

Is there a way I can tell if I'm on the correct wallet for the fork coming up?

Yes, I was going to ask same question. Thanks.

[mafort1469]

How to tell I'm running the correct Wallet

I downloaded the windows wallet from the dropbox link, backup'd my wallet.dat, unzipped it, ran the QT - sync'd, all looks fine.

Is there a way I can tell if I'm on the correct wallet for the fork coming up?

Well, if you have the github link, you can look at a line in main.cpp. But if you are certain you're running the one from the dropbox link, it is correct. The version number wasn't incremented in the source. Thundertoe is aware of it and it'll be fixed at some point, but I noticed it after things were already pushed. The collective decision was to just go ahead anyway. Just be sure you ran the new QT and you're fine.

That is the one presstab linked too, correct?

[Biomech]

How to tell I'm running the correct Wallet

I downloaded the windows wallet from the dropbox link, backup'd my wallet.dat, unzipped it, ran the QT - sync'd, all looks fine.

Is there a way I can tell if I'm on the correct wallet for the fork coming up?

Well, if you have the github link, you can look at a line in main.cpp. But if you are certain you're running the one from the dropbox link, it is correct. The version number wasn't incremented in the source. Thundertoe is aware of it and it'll be fixed at some point, but I noticed it after things were already pushed. The collective decision was to just go ahead anyway. Just be sure you ran the new QT and you're fine.

That is the one presstab linked too, correct?

yes. And also the current master link in github. This update is not much changed. No new features or anything like that, it's just a fix to the staking problem. It looks identical to the previous version, it just has a few lines of code changed to make sure that it starts staking again and that the particular circumstance that caused it to hang in the first place can't happen again.

[mmfiore]

Yes just for sanity sake please verify for everyone what is the version number of the latest wallet with the staking fix. What should we all be at come Monday?

[johan11]

Fork in block 506000 - in Monday? on this time is stake on? If I two monts no stake, now is POS on the way?
p.s look - 290 000 transfer http://tek.blockx.info/get/block/0000000000003bc89cf3e0dff2160a4b5da239836cea738030c91460b08784b9

[mmfiore]

oh Biomech by the way Tompool.org is a tek mining pool. Don't forget them? I will send them a message as well.

[Biomech]

Yes just for sanity sake please verify for everyone what is the version number of the latest wallet with the staking fix. What should we all be at come Monday?

v1.1.0.0-gf96a5a-TEK

Unfortunately, it's also what it shows in the older version It got by us in code review, but it won't affect anything. Just make sure you either compiled from the master github page, or one of the two windows versions that were posted. Presstab's is probably the best, as it has statically linked libraries and don't need .dll files.

@ Johan11, yes, it should start staking at or near that block. In testing it worked within minutes. Given the time frame, however, I would expect a lot of orphans as damn near every holder of TEK is gonna be competing for stake at that point. That didn't happen in testing, but we only had two or three wallets linked at a time.

@mmfiore again. Damn, you guys are quick! Yes, I'll contact them.
I had forgotten them.

[johan11]

oh Biomech by the way Tompool.org is a tek mining pool. Don't forget them? I will send them a message as well.

ispace.co.uk - TEK pool



i send mesage them

[Biomech]

oh Biomech by the way Tompool.org is a tek mining pool. Don't forget them? I will send them a message as well.

ispace.co.uk - TEK pool



i send mesage them

cool. I've contacted miner's point, dsync, and tompool. Central Cavern is down, and Raskul is out of the country for a bit, but I'll let him know in case he's bringing it back.

Any others?

[vancefox]

Xguild

oh Biomech by the way Tompool.org is a tek mining pool. Don't forget them? I will send them a message as well.

ispace.co.uk - TEK pool



i send mesage them

cool. I've contacted miner's point, dsync, and tompool. Central Cavern is down, and Raskul is out of the country for a bit, but I'll let him know in case he's bringing it back.

Any others?

[Biomech]

Xguild

oh Biomech by the way Tompool.org is a tek mining pool. Don't forget them? I will send them a message as well.

ispace.co.uk - TEK pool



i send mesage them

cool. I've contacted miner's point, dsync, and tompool. Central Cavern is down, and Raskul is out of the country for a bit, but I'll let him know in case he's bringing it back.

Any others?

Don't know that one. Can you contact them or post a link?


Also, on buying my stake, I'm not sure I'm selling, but PM me. I'd rather do it off exchange myself.

[thundertoe]

this was just posted by user MystPhysX Thank you i am sure users will be happy.

mac wallet compile

TEKCoin: https://www.dropbox.com/s/4hvzl47knv2a0lf/Tekcoin-Qt.zip?dl=0

https://bitcointalk.org/index.php?topic=216672.480

[David Latapie]

Since TEK has no max_subsidy unlike CAP or HYP, there is no economical reason to have a particular stack size. I suggest you to keep them al together, you'll stake faster.

But it does have to do with the health of the coin, and the market.

That's why I said economical reasons as in "will the selfish and short-minded guy get more TEK out of it?". The fact that getting more coins but with less value makes no sense is out of scope for the selfish-short-minded. Your post is still right. Making the market more liquid is of great importance. Lack of block halving is great for initial distribution and I still like it, even though it comes at the cost of important illiquidity at first (this and high reward, of course).

Code:

mkdir -p ~/cryptos && cd ~/cryptos && rm -rf TEK && git clone git://github.com/maxxine/TEK && cd TEK && qmake-qt5 tekcoin-qt.pro && make && ln -s ~/cryptos/TEK/tekcoin-qt ~/Desktop/TEK

&& ln -s ~/cryptos/TEK/tekcoin-qt ~/Desktop/TEK is only if you want to create a shortcut on your Desktop

Still for Linux, updating should be just one line of code too:

Code:

cd ~/cryptos/TEK && git pull && qmake-qt5 tekcoin-qt.pro && make

It's not a bad idea to add STATIC=1, as that makes it so you can move the client to another computer without recompiling.  so you're last line would be make STATIC=1 -f Makefile. I build all my wallets this way, and it makes for better control, especially since I'm constantly experimenting. It DOES make the final executable program a bit bigger, as it compiles the necessary libraries into the program. Depending on your circumstances and ability to resist playing with your installation. (my ability in that arena is nonexistant ) An option to think about.

Can you paste my code with you STATIC=1 value? I fail to see where to place it on the two lines of code.

[Biomech]

Since TEK has no max_subsidy unlike CAP or HYP, there is no economical reason to have a particular stack size. I suggest you to keep them al together, you'll stake faster.

But it does have to do with the health of the coin, and the market.

That's why I said economical reasons as in "will the selfish and short-minded guy get more TEK out of it?". The fact that getting more coins but with less value makes no sense is out of scope for the selfish-short-minded. Your post is still right. Making the market more liquid is of great importance. Lack of block halving is great for initial distribution and I still like it, even though it comes at the cost of important illiquidity at first (this and high reward, of course).

Yeah, I see your point. But this community does seem to have above average players. We'll see. To me, my method makes sense personally as well as to the community, because I always will have a small amount of coins that I can spend if need be, and always have more coming at a regular interval. But I tend to try to plan farther than tomorrow, and I guess that's not common

Code:

mkdir -p ~/cryptos && cd ~/cryptos && rm -rf TEK && git clone git://github.com/maxxine/TEK && cd TEK && qmake-qt5 tekcoin-qt.pro && make && ln -s ~/cryptos/TEK/tekcoin-qt ~/Desktop/TEK

&& ln -s ~/cryptos/TEK/tekcoin-qt ~/Desktop/TEK is only if you want to create a shortcut on your Desktop

Still for Linux, updating should be just one line of code too:

Code:

cd ~/cryptos/TEK && git pull && qmake-qt5 tekcoin-qt.pro && make

It's not a bad idea to add STATIC=1, as that makes it so you can move the client to another computer without recompiling.  so you're last line would be make STATIC=1 -f Makefile. I build all my wallets this way, and it makes for better control, especially since I'm constantly experimenting. It DOES make the final executable program a bit bigger, as it compiles the necessary libraries into the program. Depending on your circumstances and ability to resist playing with your installation. (my ability in that arena is nonexistant ) An option to think about.

Can you paste my code with you STATIC=1 value? I fail to see where to place it on the two lines of code.

sure. I usually do it as several lines of code (I always screw up combining code ) but here you go.

Code:

cd ~/cryptos/TEK && git pull && qmake-qt5 tekcoin-qt.pro && make STATIC=1 -f Makefile 

[jk9694]

I am still getting the following message from the new code.

Unable to sign block, wallet locked?

This is a daemon running on linux that is freshly built and synced, and no it is not encrypted.  Can anyone shed light on this?

[Biomech]

I am still getting the following message from the new code.

Unable to sign block, wallet locked?

This is a daemon running on linux that is freshly built and synced, and no it is not encrypted.  Can anyone shed light on this?

Honestly not a clue. I've run the daemon and two separate compiles (one static, one not) of the QT on linux without issue. Only thing I can think of is permissions. Try starting the daemon with sudo?

Any more experienced linux guys wanna chime in? It's what I run now, but that's pretty recent. I think at this point I've enough experience to call myself a novice rather than a complete noob

[jk9694]

Nope, tried that and still the same error.  I get the same thing if I manually submit the same block in my windows wallet in the debug window.

Here is the rpc message

08/23/2014 23:25:23 -04:00 [Verbose] [DaemonClient] [Tekcoin] tx: "{
    'method' : 'submitblock',
    'params' : [
        '0400000016b197ac6dbb7702c46a730b906c7cbdc229101f49d0bba79d1f000000000000255d979 3badd2ba526e68a8e684d393a032b2feb9b13f5fab317b5c32fbd514beb5af953a65f4b1a8a0466 480101000000010000000000000000000000000000000000000000000000000000000000000000f fffffff2603b8ab07062f503253482f03527f150868000007ae0300000d2f436f696e69756d5365 72762f000000000140420f00000000001976a9141301f3cff078b9868e6ea48c8f6212b69a30465 088ac00000000'
    ],
    'id' : 20
}"

any chance that one of the devs could run the wallet in a debugger and see what the issue is?

[jk9694]

OK, so after doing some digging and a !@#$load of code comparison and translation, I see part of the problem here.  With POS coins, I believe there needs to be a timestamp in the getwork and I am not seeing that in coinium which is the new version of

https://github.com/Crypto-Expert/stratum-mining

So, that puts us at the only pool software that can be used is MPOS with this coin or another program that uses the above stratum server.  Somehow I feel this cant be right at all.