So much material to sift through. My question probably already answered. Is it true that I can lock my wallet up and my GB will still work?
Jury is out on that but my personal belief is that you need to have it "unlocked for staking" for it to operate properly. Others would say you just need to unlock it the one time when its started though. OK, I guess that setting is secure enough. Would getting a better router help with my connections? I have only 8, but I think the problem is on my end because none of my wallets have any more than 13 connections. Doesn't sound right at all. I assume you have done the usual checks, firewall settings of OS/router, port forwarding ? All I've done is open up the proper ports in the virtual server on my router. The router is like 5 or 6 years old...I have allowed private connections in my firewall but not public connections for my wallets with my OS firewall. Am I supposed to allow public connections? You should open port on router AND firewall from os. Right now only outgoing connections are possible, getpeerinfo in debug should confirm this. |
|
|
|
So much material to sift through. My question probably already answered. Is it true that I can lock my wallet up and my GB will still work?
Jury is out on that but my personal belief is that you need to have it "unlocked for staking" for it to operate properly. Others would say you just need to unlock it the one time when its started though. OK, I guess that setting is secure enough. Would getting a better router help with my connections? I have only 8, but I think the problem is on my end because none of my wallets have any more than 13 connections. Doesn't sound right at all. I assume you have done the usual checks, firewall settings of OS/router, port forwarding ? |
|
|
|
Masternodes get 50% of rewards from normal users.
Does this means that users get 50% of reward and the other 50% goes to masternodes ?
Correct. GBands do other services for the network that are important, rather than stake, and must be paid for their work, as well That's clear. I will set up a masternode, the more ppl are staking the more interesting it gets. Now if I only get my crash solved... |
|
|
|
|
Masternodes get 50% of rewards from normal users.
Does this means that users get 50% of reward and the other 50% goes to masternodes ?
|
|
|
|
Also if you are going to stake, what's the optimum size of inputs? 1 coin? 5? 10? 50? 100? 500?
Will be transferring from c-cex with its annoying email confirmation so tiny inputs will be a pain but worth it if every 5 coin input is staking rewards of 1-9 coins occasionally
Thanks
No idea what optimum size is, I just let the wallet split the stacks until I think it takes too much time to stake. thanks ButtCrack how do you let the wallet split them up? I'm about to send coins from c-cex shall I send in one block or send a few at a time? Thanks again jk Each time a stack stakes it will split in half, so leaving you with 2 new stacks. Sending from xchange in small amounts is what some ppl do. I prefer using coin control for splitting/combining. I guess in the end it depends on how much coins you have to split, I have too many or was simply too lazy so I started with 1 stack. Now 2 days later I already have 28 stacks. And now I have 84 stacks, multiple rewards coming in per hour. So amount of stacks and rewards coming in is speeding up. |
|
|
|
|
Just a quick post.
Current wallet maybe ugly as hell but stakes like a champ and no problems.
Have it running almost 24/7 since launch.
On average multiple rewards coming in every hour.
Typical my wallet weight is about 40-50 % of network weight.
Nice !
|
|
|
|
Yes. By not hashing right to the edge of the allowed clock drift, orphans are less likely to occur.
Great, downloading and upgrading as we speak ! |
|
|
|
lol superhereo's.
Yes, if you wanna go hardcore, smaller smaller smaller. At least 80% of my blocks are less then 2k and about 50% less then 1.5k to 500.... but you do need a shit ton of coins (100k?) to really make that strategy work.
I keep scratching my head when people on cryptsy troll box are complaining about not staking often enough with 500k+ HYP and blocks of 10-15k each. MAybe just goes to show more blocks is better. Don't you need both ? More tickets more chances but when stacks compete does the one with high weight wins from low weight stacks ? Not necessarily. The one with high weight only has more chances, it doesn't mean that it will win. Every block has a unique set of parameters that are hashed, and the result depends only on chance. A hash can be much lower than the bits threshold even for a block with a small weight (while other big blocks haven't produced such a small hash). Yes I know, I also have rewards coming in after just 9 or 10 days. But still in general and to use your words : "The one with high weight only has more chances, it doesn't mean that it will win" And that's what matters when it comes trying to max out your staking. So the more stacks and the higher the weight the better. |
|
|
|
Whats the impact of "Changed default hashdrift to 45 seconds", does the new wallet stake more often because of this ? It means that the wallet will hash 45 seconds into the future instead of 60. The only input parameter that will change for every consequent second is the timestamp of the future coinstake transaction. If the coinstake hash will be found at the 45-th second, the wallets whose machines have time lag in the range of 15 seconds won't reject the transaction because of the 60 seconds maximum drift. So this feature gives more room for the coinstake transaction not to be rejected. The next 45 hashes will be created after the hashing interval of the default 22 seconds. As the only parameter that changes is the timestamp, 23 hashes from this new hash set will be exactly the same as in the previous one. So it should reduce getting orphans if I understand correctly ? |
|
|
|
Ok, just pushed a major change to solve connection issues. Please close wallet and make sure your conf has:
maxconnections=999
Then reload client
lol I set my max con to 50 simply because I had well over 70+ nodes connected. Please don't cap it yet. Give us a few days of seeding. The more the better I am trying to sort out why my wallet crashes, so I have to do some try and error. Not sure what the problem is, but I have the same problem with some other qt wallets that are the same as GB. When running on my spare box, no problems, but too much cpu load for my poor P4 cpu. |
|
|
|
Ok, just pushed a major change to solve connection issues. Please close wallet and make sure your conf has:
maxconnections=999
Then reload client
lol I set my max con to 50 simply because I had well over 70+ nodes connected. |
|
|
|
Also if you are going to stake, what's the optimum size of inputs? 1 coin? 5? 10? 50? 100? 500?
Will be transferring from c-cex with its annoying email confirmation so tiny inputs will be a pain but worth it if every 5 coin input is staking rewards of 1-9 coins occasionally
Thanks
No idea what optimum size is, I just let the wallet split the stacks until I think it takes too much time to stake. thanks ButtCrack how do you let the wallet split them up? I'm about to send coins from c-cex shall I send in one block or send a few at a time? Thanks again jk Each time a stack stakes it will split in half, so leaving you with 2 new stacks. Sending from xchange in small amounts is what some ppl do. I prefer using coin control for splitting/combining. I guess in the end it depends on how much coins you have to split, I have too many or was simply too lazy so I started with 1 stack. Now 2 days later I already have 28 stacks. |
|
|
|
Also if you are going to stake, what's the optimum size of inputs? 1 coin? 5? 10? 50? 100? 500?
Will be transferring from c-cex with its annoying email confirmation so tiny inputs will be a pain but worth it if every 5 coin input is staking rewards of 1-9 coins occasionally
Thanks
No idea what optimum size is, I just let the wallet split the stacks until I think it takes too much time to stake. |
|
|
|
lol superhereo's.
Yes, if you wanna go hardcore, smaller smaller smaller. At least 80% of my blocks are less then 2k and about 50% less then 1.5k to 500.... but you do need a shit ton of coins (100k?) to really make that strategy work.
I keep scratching my head when people on cryptsy troll box are complaining about not staking often enough with 500k+ HYP and blocks of 10-15k each. MAybe just goes to show more blocks is better. Don't you need both ? More tickets more chances but when stacks compete does the one with high weight wins from low weight stacks ? |
|
|
|
Whats the impact of "Changed default hashdrift to 45 seconds", does the new wallet stake more often because of this ? |
|
|
|
No, it uses Variance Staking, which scales coinage. Currently it's around 1-9 usually int64_t GetProofOfStakeReward(int nHeight, int64_t nCoinAge, int64_t nFees)
{
int64_t nMultiplier = 100 * CENT;
int64_t nSubsidy = (((nHeight % 9) + ((nCoinAge % 100000) * 33 / (365 * 33 + 8))) + 1) * nMultiplier;
return nSubsidy;
} I completely suck at maths. Can anyone give a 1 or 2 examples with some nrs. in simple English so I and other who suck at maths have a better understanding how this works ? Stakes are between 1 and 9 BUCKS Hmmmmm, these are determined by coinage ? What does "scales coinage" means, normally big stacks = high coinage, but not in this case ? Thanks for your patience ! |
|
|
|
No, it uses Variance Staking, which scales coinage. Currently it's around 1-9 usually int64_t GetProofOfStakeReward(int nHeight, int64_t nCoinAge, int64_t nFees)
{
int64_t nMultiplier = 100 * CENT;
int64_t nSubsidy = (((nHeight % 9) + ((nCoinAge % 100000) * 33 / (365 * 33 + 8))) + 1) * nMultiplier;
return nSubsidy;
} I completely suck at maths. Can anyone give a 1 or 2 examples with some nrs. in simple English so I and other who suck at maths have a better understanding how this works ? |
|
|
|
I have set up a public node with hallmark.
PM sent with ip, can you confirm ?
confirmed. 5m wcc sent. Coins received and 2 blocks forged. |
|
|
|
|
I have set up a public node with hallmark.
PM sent with ip, can you confirm ?
|
|
|
|
|
Show Posts
