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

subSTRATA

legendary

Activity: 1288

Merit: 1043

:^)

Quote from: Tupsu on August 28, 2014, 04:28:53 PM

Is that money now gone for me now or not ?

28.08.2014 12:18 PoS Mined (n/a) [327.108042]

Code:

Status: 0/unconfirmed
Date: 28.08.2014 12:18
Debit: 0.00 TEK
Net amount: -590.00 TEK
Transaction ID: f9375444d73be0c29c3235945e471f0c9bf015d936635b50abc14b84c50782fc

Generated coins must mature 30 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

You mean block ended up orphaned? If so, stake used to generate it is back where it was before (stakepool) ready to be staked.

Quote from: vancefox on August 28, 2014, 04:32:50 PM

For everyone's knowledge:

.conf is for MAC
.config is for PC

It is .conf in all cases, as far as I know.

zeeman

hero member

Activity: 598

Merit: 501

@johan

I'm now at 410225. 80% of the blockchain.
I'm connected to 3 peers, all on with version: 60007
and "subver" : "/tekcoin:2.0.0/"

How it will sync in the right way now. Then I can check my different wallet.dat files.
I stake for some friends as well. Some coins were at stake when the whole network got splitted.
Hope things will work out fine this time Grin

vancefox

legendary

Activity: 1033

Merit: 1005

For everyone's knowledge:

.conf is for MAC
.config is for PC

I will assume you have the same equipment as I, and a majority, do... if you don't have the more common equipment, let us know that information when you ask a question...

Quote from: zeeman on August 28, 2014, 04:20:32 PM

Quote from: vancefox on August 28, 2014, 04:10:29 PM

Use connect instead of addnode and change listen to 0.

Quote from: zeeman on August 28, 2014, 04:04:44 PM

How can I block ip's who are on the wrong subversion???

"addr" : "86.xxxxxxxxxxxxxxxxx",
"services" : "00000001",
"lastsend" : 1409256090,
"lastrecv" : 1409256075,
"conntime" : 1409256065,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 273006,
"banscore" : 0

I have a number of good ip's now.

I did that. But named my file tekcoin.config Shocked

tekcoin.conf that's the right one:

listen=0
connect=74.196.63.95
connect=75.90.67.140
connect=68.229.91.209
connect=108.59.185.202
connect=98.236.102.116
connect=75.91.15.240
connect=94.156.230.246
connect=212.21.68.60

Now all the nodes are the right ones.
I'm at 75% of all the blocks.

Tupsu

legendary

Activity: 1218

Merit: 1003

Is that money now gone for me now or not ?

28.08.2014 12:18 PoS Mined (n/a) [327.108042]

Code:

Status: 0/unconfirmed
Date: 28.08.2014 12:18
Debit: 0.00 TEK
Net amount: -590.00 TEK
Transaction ID: f9375444d73be0c29c3235945e471f0c9bf015d936635b50abc14b84c50782fc

Generated coins must mature 30 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

johan11

sr. member

Activity: 480

Merit: 250

Quote from: zeeman on August 28, 2014, 04:20:32 PM

Quote from: vancefox on August 28, 2014, 04:10:29 PM

Use connect instead of addnode and change listen to 0.

Quote from: zeeman on August 28, 2014, 04:04:44 PM

How can I block ip's who are on the wrong subversion???

"addr" : "86.xxxxxxxxxxxxxxxxx",
"services" : "00000001",
"lastsend" : 1409256090,
"lastrecv" : 1409256075,
"conntime" : 1409256065,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 273006,
"banscore" : 0

I have a number of good ip's now.

I did that. But named my file tekcoin.config Shocked

tekcoin.conf that's the right one:

listen=0
connect=74.196.63.95
connect=75.90.67.140
connect=68.229.91.209
connect=108.59.185.202
connect=98.236.102.116
connect=75.91.15.240
connect=94.156.230.246
connect=212.21.68.60

Now all the nodes are the right ones.
I'm at 75% of all the blocks.

If you not download block 506500 restart wallet with new .conf

zeeman

hero member

Activity: 598

Merit: 501

Quote from: vancefox on August 28, 2014, 04:10:29 PM

Use connect instead of addnode and change listen to 0.

Quote from: zeeman on August 28, 2014, 04:04:44 PM

How can I block ip's who are on the wrong subversion???

"addr" : "86.xxxxxxxxxxxxxxxxx",
"services" : "00000001",
"lastsend" : 1409256090,
"lastrecv" : 1409256075,
"conntime" : 1409256065,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 273006,
"banscore" : 0

I have a number of good ip's now.

I did that. But named my file tekcoin.config Shocked

tekcoin.conf that's the right one:

listen=0
connect=74.196.63.95
connect=75.90.67.140
connect=68.229.91.209
connect=108.59.185.202
connect=98.236.102.116
connect=75.91.15.240
connect=94.156.230.246
connect=212.21.68.60

Now all the nodes are the right ones.
I'm at 75% of all the blocks.

subSTRATA

legendary

Activity: 1288

Merit: 1043

:^)

Quote from: ryanb on August 28, 2014, 02:48:43 PM

I have coins stuck in unconfirmed and i did repairwallet they are still there

How do i fix it?

Start wallet with -rescan option.

vancefox

legendary

Activity: 1033

Merit: 1005

Use connect instead of addnode and change listen to 0.

Quote from: zeeman on August 28, 2014, 04:04:44 PM

How can I block ip's who are on the wrong subversion???

"addr" : "86.xxxxxxxxxxxxxxxxx",
"services" : "00000001",
"lastsend" : 1409256090,
"lastrecv" : 1409256075,
"conntime" : 1409256065,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 273006,
"banscore" : 0

I have a number of good ip's now.

zeeman

hero member

Activity: 598

Merit: 501

How can I block ip's who are on the wrong subversion???

"addr" : "86.xxxxxxxxxxxxxxxxx",
"services" : "00000001",
"lastsend" : 1409256090,
"lastrecv" : 1409256075,
"conntime" : 1409256065,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 273006,
"banscore" : 0

I have a number of good ip's now.

vancefox

legendary

Activity: 1033

Merit: 1005

Client # will be in your wallet info.

Quote from: jdhatch on August 28, 2014, 03:43:14 PM

Quote from: vancefox on August 28, 2014, 03:39:38 PM

No. Client should be 2.0.1

Blockchain sub version should be 2.0.0

{
"addr" : "68.229.91.209",
"services" : "00000001",
"lastsend" : 1409254830,
"lastrecv" : 1409254830,
"conntime" : 1409254056,
"version" : 60007,
"subver" : "/tekcoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 508924,
"banscore" : 0
}

I don't see a client number. Should I?

Thanks, Jason

jdhatch

newbie

Activity: 58

Merit: 0

in the debug console

getinfo

Quote from: zeeman on August 28, 2014, 03:46:58 PM

Where can I find this version etc. Is it in the debug console??

zeeman

hero member

Activity: 598

Merit: 501

Quote from: jdhatch on August 28, 2014, 03:37:57 PM

The recommended IPs are showing:

"version" : 60007,
"subver" : "/tekcoin:2.0.0/",

Should the subver be 2.0.1 ??

Thanks, Jason

Where can I find this version etc. Is it in the debug console??

vancefox

legendary

Activity: 1033

Merit: 1005

You're missing a very important node:

connect=71.187.236.173

That one is fully synced and working 24/7.

Also, salvagewallet is not needed if you can use a wallet backup from pre-fork or if your wallet isn't missing anything.

Quote from: David Latapie on August 28, 2014, 03:35:22 PM

OK, this one will updated, no more reposting.

We finally have a working TEK again. Of course, caution should be exercised.

0. Everywhere on this tutorial case matters, especially on Unix (Mac and Linux). "T" is not the same letter a "t".
1. Backup your wallet (%appdata%/Teckcoin/wallet.dat on Windows, ~/.tekcoin/wallet.dat on Unix). Ideally two instances on two USB disks.
2. Empty your wallet folder (%appdata%/Teckcoin on Windows, ~/.tekcoin on Unix - Mac and Linux)
3. Copy your backup wallet on the now-empty folder (copy, not move - keep these backups!)
4. In the same wallet folder, create a tekcoin.conf file with the following code:
listen=0 connect=74.196.63.95 connect=75.90.67.140 connect=68.229.91.209 connect=108.59.185.202 connect=98.236.102.116 connect=75.91.15.240 connect=94.156.230.246 connect=212.21.68.60
Until further notice, use connect, not addnode.
If you are using notepad.exe, you will have to change the .txt extension to .conf. How to do this is beyond the scope of this tutorial[/tt].
5. Download the latest wallet (see addresses on the OP)
For Linux users, until there is a binary available, you must manually change Makefile to remove this character string several times: mgw48- - this is an oversight, it will hopefully get fixed later on.
Presently, the wallet includes neither the newer layout nor checkpoints.
6. Run this command

Code:

Tekcoin-qt.exe --salvagewallet

We assume you know how to open up a terminal ("DOS window").
For Unix users, replace Tekcoin-qt.exe with Tekcoin-qt.
it will redownload the whole blockchain, which is long but necessary, you'd better not just keep the old blockchain.
For information, the repair wallet button on the GUI will only look to fill in missing pieces, whilst --salvagewallet will actually attempt to recreate your wallet.

Note that, if you want to have something closer to the advertised 40%, you should WAIT before stacking, because of high competition (and thus, do not leave you wallet open more than for checking it works). Please note this is not an evidence that NVCS is really working as it should, only that under exceptional circumstances, it does sort work - but this is still not sure it works as intended. Presstab elaborated on this.

jdhatch

newbie

Activity: 58

Merit: 0

Quote from: vancefox on August 28, 2014, 03:39:38 PM

No. Client should be 2.0.1

Blockchain sub version should be 2.0.0

{
"addr" : "68.229.91.209",
"services" : "00000001",
"lastsend" : 1409254830,
"lastrecv" : 1409254830,
"conntime" : 1409254056,
"version" : 60007,
"subver" : "/tekcoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 508924,
"banscore" : 0
}

I don't see a client number. Should I?

Thanks, Jason

vancefox

legendary

Activity: 1033

Merit: 1005

No. Client should be 2.0.1

Blockchain sub version should be 2.0.0

Quote from: jdhatch on August 28, 2014, 03:37:57 PM

The recommended IPs are showing:

"version" : 60007,
"subver" : "/tekcoin:2.0.0/",

Should the subver be 2.0.1 ??

Thanks, Jason

jdhatch

newbie

Activity: 58

Merit: 0

The recommended IPs are showing:

"version" : 60007,
"subver" : "/tekcoin:2.0.0/",

Should the subver be 2.0.1 ??

Thanks, Jason

David Latapie

hero member

Activity: 658

Merit: 503

Monero Core Team

OK, this one will updated, no more reposting.

We finally have a working TEK again. Of course, caution should be exercised.

0. Everywhere on this tutorial case matters, especially on Unix (Mac and Linux). "T" is not the same letter a "t".
1. Backup your wallet (%appdata%/Teckcoin/wallet.dat on Windows, ~/.tekcoin/wallet.dat on Unix). Ideally two instances on two USB disks.
2. Empty your wallet folder (%appdata%/Teckcoin on Windows, ~/.tekcoin on Unix - Mac and Linux)
3. Copy your backup wallet on the now-empty folder (copy, not move - keep these backups!)
4. In the same wallet folder, create a tekcoin.conf (if you're on Mac of Linux) or tekcoin.config (if you're on Windows) file with the following code:
listen=0 addnode=74.196.63.95 addnode=75.90.67.140 addnode=188.168.134.55 addnode=159.205.243.208 addnode=94.220.6.66 addnode=69.181.230.66 addnode=108.61.10.90 addnode=62.116.254.204 addnode=193.53.89.147 addnode=98.162.248.8 addnode=75.152.82.196
If you are using notepad.exe, you will have to change the .txt extension to .conf. How to do this is beyond the scope of this tutorial[/tt].
5. Download the latest wallet (see addresses on the OP
   - source https://github.com/maxxine/TEK
   - Windows http://www.mediafire.com/download/82390o41vsnwv5v/Tekcoin-qt-fix.zip
   - Mac https://www.dropbox.com/s/y17rjlji1ruxgsv/tekcoin-Qt-2.0.1.0-Mac.zip?dl=0
For Linux users, until there is a binary available, you must manually change Makefile to remove this character string several times: mgw48- - this is an oversight, it will hopefully get fixed later on.
Presently, the wallet includes neither the newer layout nor checkpoints.
6. Run this command (you can ignore this step if you have a pre-forks backup at hand)

Code:

Tekcoin-qt.exe --salvagewallet

We assume you know how to open up a terminal ("DOS window").
For Unix users, replace Tekcoin-qt.exe with Tekcoin-qt.
it will redownload the whole blockchain, which is long but necessary, you'd better not just keep the old blockchain.
You can know if you are on the correct blockchain by typing getinfo in the console or use the stats tab on new GUI. The correct chain is on block 510264
For information, the repair wallet button on the GUI will only look to fill in missing pieces, whilst --salvagewallet will actually attempt to recreate your wallet. If you have coins stuck in unconfirmed even after using Repair wallet, use -rescan.

Note that, if you want to have something closer to the advertised 40%, you should WAIT before stacking, because of high competition (and thus, do not leave you wallet open more than for checking it works). Please note this is not an evidence that NVCS is really working as it should, only that under exceptional circumstances, it does sort work - but this is still not sure it works as intended. Presstab elaborated on this.

ryanb

legendary

Activity: 1148

Merit: 1000

I got cannot initialize keypool when i ran salvagewallet and now i am getting the same when i run the wallet without the salavage command

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: David Latapie on August 28, 2014, 02:09:34 PM

Quote from: presstab on August 28, 2014, 02:00:58 PM

Hope this helps everyone understand the reward system. I got rid of this altogether in HYP because it wasn't my cup of tea.

Thanks presstab. I updated my previous post accordingly.

The ELI5 version (presstab, don't hesitate to correct me) is that the NVCS code is not smooth enough; it kicks in late and when it kicks in, it kicks hard and this hurts. HYP code is smoother, less painful to users.
For people familiar with Monero and PoW, consider NVCS as block halving and HYP staking (we have to find a better name, press) is continous decrease.

Well its not really a NVCS problem, although I think NVCS is a flawed approach.

Ha ha I am not sure there is an ELI5 version of this, but the hard fork switched the bit-wise operations on bnProofofStakeLimit from rightshift 24 to rightshift 18. This is why the difficulty before the fork was something like 0.03 and did not trigger NVCS, and now the diff is 0.0025 - less diff, but NVCS still kicked in? Well the math changed so the diff from before is not very comparable to the current diff. It will be interesting to see this one play out.

m33

legendary

Activity: 1064

Merit: 1000

Never invest with borrowed coins

guys which is the correct update file ,pls give link,rhanks

Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 207. (Read 446058 times)