presstab
Legendary
 Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
 |
June 17, 2014, 03:30:44 PM |
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine  Have you also had success staking with the daemon rather than the Qt gui? |
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
unick (OP)
|
|
June 17, 2014, 03:33:18 PM |
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine Have you also had success staking with the daemon rather than the Qt gui? No, I always used the Qt GUI for PoS and the daemon for PoW. But I don't see why it shouldn't work either way |
|
|
|
|
liteuser
|
|
June 17, 2014, 04:21:18 PM |
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine Have you also had success staking with the daemon rather than the Qt gui? I have successfully staked with the lastest build of the daemon. But I'm continously forking. I have to stop the daemon, restart with -reservebalance=999999, repairwallet to remove orphans and return to the correct fork and then restart the daemon. Sometimes I cannot connect to any peer since they close the connections: they say closed socket or connection timeout. |
|
|
|
|
ice00
|
|
June 17, 2014, 04:28:17 PM |
|
I had to lanch the program with reservebalance=987654321, attending it synch and then make a reservebalance false on console..
It generates lot of POS blocks, but no one are accepted by network so far.
|
NXT: 1408301140704352478
EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
|
unick (OP)
|
|
June 17, 2014, 04:36:13 PM |
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine Have you also had success staking with the daemon rather than the Qt gui? I have successfully staked with the lastest build of the daemon. But I'm continously forking. I have to stop the daemon, restart with -reservebalance=999999, repairwallet to remove orphans and return to the correct fork and then restart the daemon. Sometimes I cannot connect to any peer since they close the connections: they say closed socket or connection timeout. This is new, I haven't got stuck on a fork since adding the checkpointing node. Have you tried just to let your client do it's thing? When generating PoS blocks, they still have to be accepted by the network, so what you refer to as a fork might just be that those blocks were not all confirmed and a better block was accepted instead of yours. If you let the client go, it should reorganize by itself and clean get back on the right fork. repairwallet won't get you back on the correct fork. All it does is repair your wallet by removing orphans and fixing mismatched coins (transactions no accepted by the network but marked as spent in your wallet) so this steps has no influence over you getting back on the right fork. The connection timeout issue is something I haven't had time to dig deeper in. but likely not an issue for what you are describing. And reserve balance is only used to mark a certain amount has not available for minting. So I really suspect that what you refer to as forking is just orphaned blocks and should normally be fixed by itself. The other thing that might be happening, is that if you generate PoS block BEFORE being fully synced to the network, you might indeed get stuck on a fork. I'll try to get that fixed for the next release. the quick fix for that is to start your client with -reservebalance=99999999 |
|
|
|
|
liteuser
|
|
June 17, 2014, 04:48:56 PM |
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine Have you also had success staking with the daemon rather than the Qt gui? I have successfully staked with the lastest build of the daemon. But I'm continously forking. I have to stop the daemon, restart with -reservebalance=999999, repairwallet to remove orphans and return to the correct fork and then restart the daemon. Sometimes I cannot connect to any peer since they close the connections: they say closed socket or connection timeout. This is new, I haven't got stuck on a fork since adding the checkpointing node. Have you tried just to let your client do it's thing? When generating PoS blocks, they still have to be accepted by the network, so what you refer to as a fork might just be that those blocks were not all confirmed and a better block was accepted instead of yours. If you let the client go, it should reorganize by itself and clean get back on the right fork. repairwallet won't get you back on the correct fork. All it does is repair your wallet by removing orphans and fixing mismatched coins (transactions no accepted by the network but marked as spent in your wallet) so this steps has no influence over you getting back on the right fork. The connection timeout issue is something I haven't had time to dig deeper in. but likely not an issue for what you are describing. And reserve balance is only used to mark a certain amount has not available for minting. So I really suspect that what you refer to as forking is just orphaned blocks and should normally be fixed by itself. The other thing that might be happening, is that if you generate PoS block BEFORE being fully synced to the network, you might indeed get stuck on a fork. I'll try to get that fixed for the next release. the quick fix for that is to start your client with -reservebalance=99999999 I guess you are right. I get stuck generating PoS blocks, and maybe I am too impatient to allow them to reorganize. The problem is that sometimes I lost the connection (have 0 connected nodes) and I keep generating PoS blocks. I will try to wait a little longer and see what happens. |
|
|
|
|
unick (OP)
|
|
June 17, 2014, 06:58:40 PM |
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine UPDATE: I did get a stake with the latest build. it took just under 9 days. On a side note, it always took around midway to max stake weight to get a valid PoS block with GRW. So I'd say you should have yours in around 2 days from now. |
|
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
June 19, 2014, 02:58:05 AM |
|
|
|
|
|
|
unick (OP)
|
|
June 19, 2014, 03:12:16 AM |
|
done, I was currently working on that file to add Fast stake |
|
|
|
|
|
dengnizaidongji
Sr. Member
Offline
Activity: 266
Merit: 250
Colossuscoin - the future of payment methods
|
|
June 19, 2014, 04:55:37 AM |
|
can you try to do the same with ByteCoin, the coin need not to be synced for a long time and the new users can save time to use it.we can learn with it.
|
Colossuscoin - the future of payment methods
|
|
|
dengnizaidongji
Sr. Member
Offline
Activity: 266
Merit: 250
Colossuscoin - the future of payment methods
|
|
June 19, 2014, 04:56:34 AM |
|
it is a good news,but we should look for more exchange place. |
Colossuscoin - the future of payment methods
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
June 19, 2014, 03:18:41 PM |
|
Unick I recommend that you clean out the /src/obj folder on github so that I don't have to clone it and can build from scratch no problem  |
|
|
|
|
unick (OP)
|
|
June 19, 2014, 03:32:22 PM |
|
Unick I recommend that you clean out the /src/obj folder on github so that I don't have to clone it and can build from scratch no problem Good catch, it's done thanks |
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
June 19, 2014, 07:12:45 PM |
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning |
|
|
|
|
unick (OP)
|
|
June 19, 2014, 07:22:51 PM |
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent  , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right? |
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
June 19, 2014, 07:28:55 PM |
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right? Yep 9 days. I tend to think it is correlated because it came through just an hour or two after I rebuilt, but it could also be coincidence. |
|
|
|
|
unick (OP)
|
|
June 19, 2014, 07:31:46 PM |
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right? Yep 9 days. I tend to think it is correlated because it came through just an hour or two after I rebuilt, but it could also be coincidence. it might be, but we'll see on next round of staking... It mostly always took around 9 days to successfully stake a block. It's a good thing if that fixed it! EDIT: we might know sooner, I just checked and I have 3 blocks from the 13th, only 6 days old! I will rebuild my client and see what happens |
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
June 19, 2014, 07:54:39 PM |
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right? Yep 9 days. I tend to think it is correlated because it came through just an hour or two after I rebuilt, but it could also be coincidence. it might be, but we'll see on next round of staking... It mostly always took around 9 days to successfully stake a block. It's a good thing if that fixed it! EDIT: we might know sooner, I just checked and I have 3 blocks from the 13th, only 6 days old! I will rebuild my client and see what happens We need to work on an RPC command that will list all of the blocks held by a wallet. That would be super useful. Almost like the coincontroldialog without the coincontrol. |
|
|
|
|
