Topic: [ANN][SEED] SeedCoin | New Road Map - page 116. (Read 184103 times)
Coin is disabled at Bittrex, any estimate how long?
Apparently there isn't a block explorer for Seed. Is there anyone in this community who is not already tied up with the other development issues who knows how to build one and would be willing to take that on?
I just compiled the latest git hub source code. My wallet syncs now, but it still shows the old version.
is ok though and gives no errors.
Quote
"version" : "v0.9.1.0-50-g7baece7-dirty",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 0.05443638,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 3968,
"timeoffset" : -1,
"moneysupply" : 440.76473935,
"connections" : 16,
"proxy" : "",
"ip" : "108.64.178.11",
"difficulty" : {
"proof-of-work" : 199.37206622,
"proof-of-stake" : 0.00000095
},
"testnet" : false,
"keypoololdest" : 1412472928,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}
Typing getblock 9275ea28b52bb9b2879b4b7f731405adca8573a04e628df3dc5621a95f5058d6"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 0.05443638,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 3968,
"timeoffset" : -1,
"moneysupply" : 440.76473935,
"connections" : 16,
"proxy" : "",
"ip" : "108.64.178.11",
"difficulty" : {
"proof-of-work" : 199.37206622,
"proof-of-stake" : 0.00000095
},
"testnet" : false,
"keypoololdest" : 1412472928,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}
is ok though and gives no errors.
wallet wont sync, is this an issue that you guys know about or what up? gets stuck about halfway through.
First, make sure you have the latest version. Go to very first message of this thread to get it.
Next, follow the directions below. It worked for me
alright. If you're sure you've got the latest wallet, then open up %appdata%/seedcoin and edit seedcoin.conf (make it if you don't already have one) and put the following lines in it:
connect=185.45.192.191
connect=198.144.184.175
connect=199.127.226.221
save the file, close the wallet if it's open, and delete everything in that folder except wallet.dat and seedcoin.conf then start the wallet again.
It will take some time, as you'll be placing the entire burden of syncing on the nodes, and they probably wont allow you to connect right away since you've been on the wrong node, but it will eventually. Once you're all sync'd up then delete those lines from your seedcoin.conf or you wont be able to connect to anyone else on the network.
connect=185.45.192.191
connect=198.144.184.175
connect=199.127.226.221
save the file, close the wallet if it's open, and delete everything in that folder except wallet.dat and seedcoin.conf then start the wallet again.
It will take some time, as you'll be placing the entire burden of syncing on the nodes, and they probably wont allow you to connect right away since you've been on the wrong node, but it will eventually. Once you're all sync'd up then delete those lines from your seedcoin.conf or you wont be able to connect to anyone else on the network.
wallet wont sync, is this an issue that you guys know about or what up? gets stuck about halfway through.
You got the latest Version?
wallet wont sync, is this an issue that you guys know about or what up? gets stuck about halfway through.
Is there a working blockchain explorer for seed?
Evidently the one being used on my pool can't even find my address LOL.
Evidently the one being used on my pool can't even find my address LOL.
Back to the staking, am I better off locking my wallet 24 hours before the end of PoW so my coins don't stake. When the growth period starts I then can unlock the wallet, will the coins stake pretty much straightaway if they haven't staked for > 24 hours?
That would be my plan
Will all the coins stake at once? Or will they stake as they are ready? So for example, if I mine continuously during the mining period and stake as soon as coins mature, then wouldn't I have some coins staking at different times? I'm thinking that would be another way to make sure I'm taking full advantage of the growth period. Some of my coins wouldn't manage to stake all 7 times but some would. Someone who bought into the ICO and is not mining could potentially set this up by sending all their coins to a different wallet, like their Bittrex address, and then divide into a series of deposits back to their wallet timed every four hours or so so that they have to reset maturity and then stake at different times. Would this even work?
For the other POS coins I've had, the first time they stake (ie. if a wallet is just unlocked, or a single deposit matures), any mature coins would stake at the same time the first time. But when you get the coins back, they are split up, so the next time they stake, it would stake in multiples of smaller amounts, and split even further the next time they stake. So by the end of 7 days you stake many, many times at small amounts. I'm not sure how it'll all happen when you stake 1000 coins on day 5 and get rewarded with a chunk of 3690, but cryptzo made it sound like everyone staking would be in the same boat with lots of small multiples and possible a fraction of everyones coins not getting the final stake at 269%. If it affects everyone equally, then it's not a problem.
My PINK coins stake hundreds of times a day now, even though my initial deposits were in 2 large chunks.
Great! Then I can let the staking happen as it will knowing that at least some of my coins will get the maximum benefit from the growth period.
Back to the staking, am I better off locking my wallet 24 hours before the end of PoW so my coins don't stake. When the growth period starts I then can unlock the wallet, will the coins stake pretty much straightaway if they haven't staked for > 24 hours?
That would be my plan
Will all the coins stake at once? Or will they stake as they are ready? So for example, if I mine continuously during the mining period and stake as soon as coins mature, then wouldn't I have some coins staking at different times? I'm thinking that would be another way to make sure I'm taking full advantage of the growth period. Some of my coins wouldn't manage to stake all 7 times but some would. Someone who bought into the ICO and is not mining could potentially set this up by sending all their coins to a different wallet, like their Bittrex address, and then divide into a series of deposits back to their wallet timed every four hours or so so that they have to reset maturity and then stake at different times. Would this even work?
For the other POS coins I've had, the first time they stake (ie. if a wallet is just unlocked, or a single deposit matures), any mature coins would stake at the same time the first time. But when you get the coins back, they are split up, so the next time they stake, it would stake in multiples of smaller amounts, and split even further the next time they stake. So by the end of 7 days you stake many, many times at small amounts. I'm not sure how it'll all happen when you stake 1000 coins on day 5 and get rewarded with a chunk of 3690, but cryptzo made it sound like everyone staking would be in the same boat with lots of small multiples and possible a fraction of everyones coins not getting the final stake at 269%. If it affects everyone equally, then it's not a problem.
My PINK coins stake hundreds of times a day now, even though my initial deposits were in 2 large chunks.
Back to the staking, am I better off locking my wallet 24 hours before the end of PoW so my coins don't stake. When the growth period starts I then can unlock the wallet, will the coins stake pretty much straightaway if they haven't staked for > 24 hours?
That would be my plan
Will all the coins stake at once? Or will they stake as they are ready? So for example, if I mine continuously during the mining period and stake as soon as coins mature, then wouldn't I have some coins staking at different times? I'm thinking that would be another way to make sure I'm taking full advantage of the growth period. Some of my coins wouldn't manage to stake all 7 times but some would. Someone who bought into the ICO and is not mining could potentially set this up by sending all their coins to a different wallet, like their Bittrex address, and then divide into a series of deposits back to their wallet timed every four hours or so so that they have to reset maturity and then stake at different times. Would this even work?
+1
This is what I sent cryptzo about this buggy mandatory update.
Seedcoin's latest mandatory update is a ticking time bomb. When PoS weight changes, the current wallet will no longer accept the old historical blockchain. This could cause just minor issues like wallet not syncing, but it may also allow a malicious actor to orphan every PoS block minted and not checkpointed, since the wallet will no longer see the proper blockchain as valid.
You need to use blocktime or something, not GetTime. SEED should have future time drift protection for blocktimes, so they can only set their clock ahead by like 2 hours or 15 minutes or something like that and their blocks still be valid
As an aside, this is why you should use block height, instead of a time for forking.. it makes issues like these never even possible
Seedcoin's latest mandatory update is a ticking time bomb. When PoS weight changes, the current wallet will no longer accept the old historical blockchain. This could cause just minor issues like wallet not syncing, but it may also allow a malicious actor to orphan every PoS block minted and not checkpointed, since the wallet will no longer see the proper blockchain as valid.
You need to use blocktime or something, not GetTime. SEED should have future time drift protection for blocktimes, so they can only set their clock ahead by like 2 hours or 15 minutes or something like that and their blocks still be valid
As an aside, this is why you should use block height, instead of a time for forking.. it makes issues like these never even possible
To fork in the future, it's actually best to use block time (edit: of the best block). But yeah, grabbing the system time is not a good approach.
Yeah the grabbing of the system time was just a panic fix to stop the forking. I originally used the block time (of the block being tested) and that clearly had serious issues.
The historical blockchain will be valid at least until the weight down-stepping, which I honestly put zero thought into when I kneejerked GetTime into that thinking about the current forking issues. I'll put a fix out for this, but in the meantime the current wallet should be able to coincide with the upcoming fixed wallet without causing a major fork.
As for the edit tx42 suggested, I don't want to steal his thunder. Honestly I'm just really really tired right now and having a hard time following his admittedly very clear code. I don't want to worry about forks right now, and I can't think well enough to wrap my head around it right now. But like I told him, I will later on today.
Don't worry, I'm not going anywhere. I'll get through this. But I'm happy to have the help and another set of eyes on the code when I'm tired. So thank you for your help.
If nothing is going to blow up in the next three hours or so, a nap may be your best strategy right now. Then the code (and everything else) will look clearer. Thanks for all your hard work. I'm having an absolutely fabulous time mining seed right now
Back to the staking, am I better off locking my wallet 24 hours before the end of PoW so my coins don't stake. When the growth period starts I then can unlock the wallet, will the coins stake pretty much straightaway if they haven't staked for > 24 hours?
That would be my plan
This is what I sent cryptzo about this buggy mandatory update.
Seedcoin's latest mandatory update is a ticking time bomb. When PoS weight changes, the current wallet will no longer accept the old historical blockchain. This could cause just minor issues like wallet not syncing, but it may also allow a malicious actor to orphan every PoS block minted and not checkpointed, since the wallet will no longer see the proper blockchain as valid.
You need to use blocktime or something, not GetTime. SEED should have future time drift protection for blocktimes, so they can only set their clock ahead by like 2 hours or 15 minutes or something like that and their blocks still be valid
As an aside, this is why you should use block height, instead of a time for forking.. it makes issues like these never even possible
Seedcoin's latest mandatory update is a ticking time bomb. When PoS weight changes, the current wallet will no longer accept the old historical blockchain. This could cause just minor issues like wallet not syncing, but it may also allow a malicious actor to orphan every PoS block minted and not checkpointed, since the wallet will no longer see the proper blockchain as valid.
You need to use blocktime or something, not GetTime. SEED should have future time drift protection for blocktimes, so they can only set their clock ahead by like 2 hours or 15 minutes or something like that and their blocks still be valid
As an aside, this is why you should use block height, instead of a time for forking.. it makes issues like these never even possible
To fork in the future, it's actually best to use block time (edit: of the best block). But yeah, grabbing the system time is not a good approach.
Yeah the grabbing of the system time was just a panic fix to stop the forking. I originally used the block time (of the block being tested) and that clearly had serious issues.
The historical blockchain will be valid at least until the weight down-stepping, which I honestly put zero thought into when I kneejerked GetTime into that thinking about the current forking issues. I'll put a fix out for this, but in the meantime the current wallet should be able to coincide with the upcoming fixed wallet without causing a major fork.
As for the edit tx42 suggested, I don't want to steal his thunder. Honestly I'm just really really tired right now and having a hard time following his admittedly very clear code. I don't want to worry about forks right now, and I can't think well enough to wrap my head around it right now. But like I told him, I will later on today.
Don't worry, I'm not going anywhere. I'll get through this. But I'm happy to have the help and another set of eyes on the code when I'm tired. So thank you for your help.
Back to the staking, am I better off locking my wallet 24 hours before the end of PoW so my coins don't stake. When the growth period starts I then can unlock the wallet, will the coins stake pretty much straightaway if they haven't staked for > 24 hours?
Alright, I heard from cryptzo by PM!
He's on top of this and is looking seriously at my patch. He's just very tired. Hopefully he can muster the fortitude to knock out an update before he crashes.
This is a good sign guys. I know devs.
+1
Go Cryptzo! hang in there. Sending you virtual coffee (or whatever type of food/beverage you use for a quick energy boost)
Alright, I heard from cryptzo by PM!
He's on top of this and is looking seriously at my patch. He's just very tired. Hopefully he can muster the fortitude to knock out an update before he crashes.
This is a good sign guys. I know devs.
i send some seeds (0.143) to my wallet from minerpools , but that was before i changed the config while my wallet wasn't syncing , now my wallet is synced but did not recieve the seeds i withdraw ,
is that a fork issue and did i loose the withdrawed seeds??
is that a fork issue and did i loose the withdrawed seeds??
It's probably a fork issue.
Things are going to get ugly with the pools. They tend to make their own forks when things like this happen.
well , too bad , but tanx for help and answer
i send some seeds (0.143) to my wallet from minerpools , but that was before i changed the config while my wallet wasn't syncing , now my wallet is synced but did not recieve the seeds i withdraw ,
is that a fork issue and did i loose the withdrawed seeds??
is that a fork issue and did i loose the withdrawed seeds??
It's probably a fork issue.
Things are going to get ugly with the pools. They tend to make their own forks when things like this happen.
i send some seeds (0.143) to my wallet from minerpools , but that was before i changed the config while my wallet wasn't syncing , now my wallet is synced but did not recieve the seeds i withdraw ,
is that a fork issue and did i loose the withdrawed seeds??
is that a fork issue and did i loose the withdrawed seeds??
Jump to: