With the upcoming new wallet release i plan to implement max PoS reward limit.
So the question is what limit should we set?
First i thought about 1000 but it looks too much to me.
I feel like it's better to set tough limit, something like 300 (HBN going to set 250 for example).
What do you guys think?
Good question. I have no magic number in my head as such. Maybe we should by "simple try and error" find the optimum for TRK ? Changing cap step by step as such. Is the reason for capping max. related to the chain that at times moves slowly or has even stalled in recent weeks ? Right now I just let my stacks stake and not re-combine, by doing so have 3X -4X if not more stacks then before I stopped re-combining them. Which is good for the chain. (Would that be a so-called no brainer ?) "try and error" method will not work here - max reward cap requires a hard fork so the number will be set for a long time - we can't hardfork too often  I see two main reasons for capping max reward - 1. it will encourage people to split to smaller blocks - more blocks means healthier network and faster blockchain. 2. those who just keep their wallets offline for months and then open them once for stake will not get a huge reward anymore - helps with inflation control and encourage people to stake more often - healthier network again. |
|
|
|
So... since HYP is basically a fork off TRK, I can't run both wallets at the same time... Any way around this without the need for separate computers or a VM?
You can run both wallets simultaneously, just need to change the port for one of the coins to make it different. Create Truckcoin.conf file with the following line: (you can put any port number there, just should be different from 18775. Put this Truckcoin.conf file into your Truckcoin directory with wallet and blockchain files - that's all Or you can run truckcoin-qt.exe with -port option Create a shortcut of the truckcoin-qt, right click on shortcut then select properties. add -port=18777 at the end of target line. Should look like C:\path\to\truckcoin-qt.exe -port=18777 |
|
|
|
With the upcoming new wallet release i plan to implement max PoS reward limit.
So the question is what limit should we set?
First i thought about 1000 but it looks too much to me.
I feel like it's better to set tough limit, something like 300 (HBN going to set 250 for example).
What do you guys think?
I think 300 or even 100 is better than 1000. Since nStakeTargetSpacing = 90, we have about 960 blocks each day (like HYP) so 300 x 960 = 288000 additional TRK each day. I don't know how many coins are currently created each day, but 288000 means 8.6M in a month. According to the block explorer now we have 14.8M. Well, i think maybe 200 then |
|
|
|
Noise23, can you explain the purpose of the new SplitThreshold code and how it affects staking, please? I think I understand it after reviewing the code, but I'd rather hear it from you.  Staking engine will not split blocks with amount smaller than this threshold so there is no need to combine blocks manually with coin control anymore. Can be set to 1010 max. Will add it to gui soon. |
|
|
|
|
With the upcoming new wallet release i plan to implement max PoS reward limit.
So the question is what limit should we set?
First i thought about 1000 but it looks too much to me.
I feel like it's better to set tough limit, something like 300 (HBN going to set 250 for example).
What do you guys think?
|
|
|
|
Well windows update ran last night and now so far two of the 4 wallets I have are stuck on loading block index. Anybody know the best way to resolve this issue. I do have backups of the wallets and the wallet files.
Maybe your blockchain files get damaged somehow, try to replace them with the files from good loading wallet - blk0001.dat , blkindex.dat and database dir. Also pls make sure you are running the latest version 2.1.1 NOT 2.1.0 |
|
|
|
Need some confirmation that I am on the correct chain.
block 642691 :
8a9cabd7ae25ce7fd7fe336471ef9b281b9d3e1e3946e1e24c2717b01d56f464
Yes this is the correct chain. |
|
|
|
I am getting orphans too, but right now I do not mind at all. You have fixed the AV alert in the Windows compiled version! Thank you!
I am able to run my TEK wallet for the first time in over 10 weeks. Woo hoo.
Please post a bounty addy when you get a chance.
My TEK address is BrS57oUjVRcEhqEG7jBzLSEFi9s3gVNkd6 Thanks Just sent some. Thanks again. Thank you |
|
|
|
I am getting orphans too, but right now I do not mind at all. You have fixed the AV alert in the Windows compiled version! Thank you!
I am able to run my TEK wallet for the first time in over 10 weeks. Woo hoo.
Please post a bounty addy when you get a chance.
My TEK address is BrS57oUjVRcEhqEG7jBzLSEFi9s3gVNkd6 Thanks |
|
|
|
Important: If you already upgraded from https://github.com/noise23/TEK please re-download the latest source from there and rebuild. Client version should be 2.1.1 , version 2.1.0 is not valid. Windows wallet coming soon. How does this affect blocks that where already mined on 2.1.0? Okay, just looked at the source and looks like mined blocks will be okay. Updating now. My node/pool is a very big one. Yes already mined blocks should be OK. |
|
|
|
New version still orphaning.....  New version is just a first stage to enable checkpointing, it's not supposed to fix orphaning by itself. Currently we are waiting for majority of TEK peers to upgrade to new version, then master node will be started. |
|
|
|
Hi,
Where can I find the Statistics in the new wallet?
Thx in advance.
Currently there is no Statistics page in the new wallet, will add it later. You can use 'getinfo' in console to get difficulty, etc. |
|
|
|
I launched version 2.1.1, but it has no connection.
here are some nodes addnode=89.25.54.130
addnode=54.234.181.73
addnode=24.156.71.22
addnode=97.106.73.166
addnode=82.72.216.165
addnode=24.85.126.229
addnode=46.129.18.254
addnode=205.197.252.28 |
|
|
|
Important: If you already upgraded from https://github.com/noise23/TEK please re-download the latest source from there and rebuild. Client version should be 2.1.1 , version 2.1.0 is not valid. Windows wallet coming soon.
|
|
|
|
Upgraded. Now waiting for client to stop saying checkpoint too old before I send my newly added coins from Cryptsy.
My pool is updated but I still get this message
"Checkpoint is too old..." message is normal, we are preparing TEK for autocheckpointing and the message just means that checkpointing server is not online yet. I just changed the code to not show this message, if you redownload the latest source it will disappear. |
|
|
|
Can you add "unlock wallet" in menu again ?
Right now I have to use console to unlock for tx.
Found it today after hours of frustrating entering passphrase for every single tx while creating a spread.
Thanks !
Already done, will be in the next wallet release |
|
|
|
dumper has been lost .. come up again to 2000 satoshi we are waiting for a great work of noise23 again ..  Working on a new wallet release and new website |
|
|
|
Help- My mac wallet version 9.6.0 has not synced since Oct 27. It has been doing great up til then. Staking has been automatic. The only change is that the stake amount has been quickly growing and now stuck at over 200,000 trk. I read post here about stake control to shorten the blocks but does the mac wallet have stake amount control? Is there anything I can do to help the syncing problem?
Did you encrypt the wallet? Unencrypted wallet may produce stake block while syncing and get on a fork. Please check if your latest block is from the correct chain - getblockhash <blocknumber> and compare it with the same block number at http://explorer.truckcoin.netYes wallet is encrypted. I am about to clear my truck coin folder on my mac,i.e. move the bootstrap into the folder , delete all files but wallet.dat and bootstrap and restart wallet to solve syncing problem. First I want to move as many coins out of the wallet to cryptex temporarily. I have over 200000 staking presently. Quesiton is how can I remove the 200000 staking back into the balance and then out of the wallet before I attempt the repair/snyncing of the wallet v 9.6.0. Am I in danger of losing my staked amount if I do a bootstrap solution to my mac wallet? There is no need to temporarily move coins out of the wallet - just backup your wallet.dat (it's good to have a few copies of wallet.dat saved on different drives to make sure you will always have a backup copy in case of any failure). If the wallet is encrypted you don't have to do anything with it while bootstraping/syncing, just don't unlock the wallet before blockchain is fully synced. If you staked on the fork minted amount will disappear but it will stake back very fast so you will not lose anything. If you have a backup copy of wallet.dat you will never lose your coins, nothing to worry about. |
|
|
|
Here are the nodes I am connected to right now if that helps.
104.193.43.106:18775
108.61.18.91:18775
69.197.161.122:18775
72.31.27.129:18775
104.218.234.125:18775
24.85.126.229:18775
89.87.101.239:18775
23.235.237.212:18775
65.50.68.22:18775
Also there are official nodes: addnode=node1.truckcoin.net
addnode=node2.truckcoin.net
addnode=node3.truckcoin.net
addnode=node4.truckcoin.net |
|
|
|
|
Show Posts
