Topic: [ANN][SEED] SeedCoin | New Road Map - page 85. (Read 184103 times)
Just so i am on the same page , how do you lock the wallet?
Thanks for the update, with the new wallet is there any point of sending coins to another wallet as one transaction or is this issue fixed with the new release?
What's the issue with sending coins to another wallet as one transaction? I know there's an old issue with basically every POS coin where the coins are in so many pieces that you need to break it up into multiple transactions, but that's not something that can be fixed on it's own. I plan on working on a fix to the POS system itself so it doesn't create quite so many pieces in your wallet, but that will come later and certainly wont be rushed.
I'm actually wondering if sending all my seeds to my 2nd wallet is the correct move. All of the seed in my wallet has been sent there in small chunks. Do you recommend sending one transaction to the new wallet?
You can send to yourself, as in back into the same wallet--just use the receiving address. Those coins will be like new. Use the coin control feature to pick which exact coins you want to send so you can reset them as it were.
Wow! I literally just unlocked my wallet and got two transactions at the 269 percent rate! Yippee!
We're off to the races...
We're off to the races...
Thanks for the update, with the new wallet is there any point of sending coins to another wallet as one transaction or is this issue fixed with the new release?
What's the issue with sending coins to another wallet as one transaction? I know there's an old issue with basically every POS coin where the coins are in so many pieces that you need to break it up into multiple transactions, but that's not something that can be fixed on it's own. I plan on working on a fix to the POS system itself so it doesn't create quite so many pieces in your wallet, but that will come later and certainly wont be rushed.
I'm actually wondering if sending all my seeds to my 2nd wallet is the correct move. All of the seed in my wallet has been sent there in small chunks. Do you recommend sending one transaction to the new wallet?
So locking the wallet and stopping stake prior to countdown is the correct action if less than 1 seedcoin? im reading that from wiser who I don't think is the dev.
That's a strategy I highly recommend at the moment. Yes. But at the same time, the more people that do this, the fewer blocks that there will be.
There is one thing to be aware of. The very first person to stake after that clock ends will get run through the old code, and there's not much I can do about this, because I have to base the changeover on a block that already got accepted into the network. If I did it on the submitted block we'd end up in forksville again - in fact, that's exactly what happened on my first update and why everything went crazy. I learned from that mistake and we're not going there again.
So locking the wallet and stopping stake prior to countdown is the correct action if less than 1 seedcoin? im reading that from wiser who I don't think is the dev.
I am not the developer but have been following this thread closely. The reason to consider locking your wallet is that the fix doesn't go into effect until the counter runs out. This means that any small amount of coin that stakes before the counter runs out will do so at 1 percent (and then be unable to stake again for another 24 hours). Locking your wallet will hold them off from staking until after the fix takes effect and then they will stake at 269 percent. But locking the wallet is not required or anything. Large amounts of coin (larger than 1 seed) are not affected. To get a good picture of the sizes of your chunks of coin, you need to activate the coin control feature and then view it.
Even more importantly, As Cryptzo said, be sure to update your wallet to version 1.0.4.
Thanks for the update, with the new wallet is there any point of sending coins to another wallet as one transaction or is this issue fixed with the new release?
What's the issue with sending coins to another wallet as one transaction? I know there's an old issue with basically every POS coin where the coins are in so many pieces that you need to break it up into multiple transactions, but that's not something that can be fixed on it's own. I plan on working on a fix to the POS system itself so it doesn't create quite so many pieces in your wallet, but that will come later and certainly wont be rushed.
So locking the wallet and stopping stake prior to countdown is the correct action if less than 1 seedcoin? im reading that from wiser who I don't think is the dev.
so what's the status with the people who have chunks of less than 1 Seed? I was thinking about downloading the new wallet on a dif comp and sending my seeds as one bulk transaction to my 2nd wallet. Is that is something that is recommended or are things fixed now? I staked at .00001 for few days. Some clarification on the status of a) the wallet b) the staking situation; would be appreciated. Cheers
I've read back 10 pages and can't find the current state of the situation. Can someone elaborate?
Once you update to the new wallet (version 1.0. 4. 0), it's all good once this countdown (http://www.timeanddate.com/countdown/generic?p0=136&iso=20141011T06&year=2014&month=10&day=11&hour=6&min=0&sec=0&msg=Staking%20Fix&csz=1) goes to zero.
If you were having the issue of only staking 1 percent, you might consider locking your wallet until the countdown goes to zero.
cool, thanks for clarification; I'll update and lock it until the counter runs out
Thanks for the update, with the new wallet is there any point of sending coins to another wallet as one transaction or is this issue fixed with the new release?
Ok, I figured out what happened with the explorer. I sync'd a preliminary change to github for version 1.0.3.0 that had to be fixed. 1.0.4.0 fixed the problem, I created the commit, and built the wallets, and did the whole announcement, but I ended up syncing the change to the wrong (testing) branch.
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
Once again thanks for the hard work and effort put into this. When will the block explorer be back on the correct block?
As soon as they update it. It's actually a little funny, since the fork is only two blocks long. 10330 is correct. Forked at 10331.
Does this mean it's best to hold off on buying on BitTrex until you know for sure they are on the right wallet? What if seed gets purchased and they are on the wrong wallet?
when will the block explorer get fixed?
Asap, I've contacted them via twitter and pm. We're working on it.
In the meantime
/Satoshi:1.0.2/ 60013 124 63.3 % 63.3 %
/Satoshi:1.0.4/ 60013 33 16.8 % 80.1 %
/Satoshi:1.0.1/ 60013 31 15.8 % 95.9 %
/Satoshi:1.0.0/ 60013 5 2.6 % 98.5 %
/Satoshi:1.0.3/ 60013 3 1.5 % 100.0 %
That's the current distribution of wallets. People running 1.0.0, well... they've forked off into oblivion already. 1.0.2 is the old wallet that will be useless in about 6 hours. 1.0.3 is wallets that were compiled with the testing source that didn't get updated properly.
I'm trying to make sure bittrex isn't one of those three as well. If they are you can't send or receive coins from bittrex either. I might be one of the three, as I ran the 1.0.3 wallet recently enough to show up on that list, one is the explorer itself, and one is the person who staked off the github source at the time.
Still, there's a LOT of 1.0.2's
If you're not running 1.0.4, please update ASAP
Ok, I figured out what happened with the explorer. I sync'd a preliminary change to github for version 1.0.3.0 that had to be fixed. 1.0.4.0 fixed the problem, I created the commit, and built the wallets, and did the whole announcement, but I ended up syncing the change to the wrong (testing) branch.
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
Once again thanks for the hard work and effort put into this. When will the block explorer be back on the correct block?
As soon as they update it. It's actually a little funny, since the fork is only two blocks long. 10330 is correct. Forked at 10331.
when will the block explorer get fixed?
Asap, I've contacted them via twitter and pm. We're working on it.
In the meantime
/Satoshi:1.0.2/ 60013 124 63.3 % 63.3 %
/Satoshi:1.0.4/ 60013 33 16.8 % 80.1 %
/Satoshi:1.0.1/ 60013 31 15.8 % 95.9 %
/Satoshi:1.0.0/ 60013 5 2.6 % 98.5 %
/Satoshi:1.0.3/ 60013 3 1.5 % 100.0 %
That's the current distribution of wallets. People running 1.0.0, well... they've forked off into oblivion already. 1.0.2 is the old wallet that will be useless in about 6 hours. 1.0.3 is wallets that were compiled with the testing source that didn't get updated properly.
I'm trying to make sure bittrex isn't one of those three as well. If they are you can't send or receive coins from bittrex either. I might be one of the three, as I ran the 1.0.3 wallet recently enough to show up on that list, one is the explorer itself, and one is the person who staked off the github source at the time.
Still, there's a LOT of 1.0.2's
If you're not running 1.0.4, please update ASAP
so what's the status with the people who have chunks of less than 1 Seed? I was thinking about downloading the new wallet on a dif comp and sending my seeds as one bulk transaction to my 2nd wallet. Is that is something that is recommended or are things fixed now? I staked at .00001 for few days. Some clarification on the status of a) the wallet b) the staking situation; would be appreciated. Cheers
I've read back 10 pages and can't find the current state of the situation. Can someone elaborate?
Once you update to the new wallet (version 1.0. 4. 0), it's all good once this countdown (http://www.timeanddate.com/countdown/generic?p0=136&iso=20141011T06&year=2014&month=10&day=11&hour=6&min=0&sec=0&msg=Staking%20Fix&csz=1) goes to zero.
If you were having the issue of only staking 1 percent, you might consider locking your wallet until the countdown goes to zero.
so what's the status with the people who have chunks of less than 1 Seed? I was thinking about downloading the new wallet on a dif comp and sending my seeds as one bulk transaction to my 2nd wallet. Is that is something that is recommended or are things fixed now? I staked at .00001 for few days. Some clarification on the status of a) the wallet b) the staking situation; would be appreciated. Cheers
I've read back 10 pages and can't find the current state of the situation. Can someone elaborate?
Ones coins are staked they cant stake again for 24 hours? or 1440 blocks? Please only answer if you are certain. also, with my pc off I still gain weight right?
+1
Ok, I figured out what happened with the explorer. I sync'd a preliminary change to github for version 1.0.3.0 that had to be fixed. 1.0.4.0 fixed the problem, I created the commit, and built the wallets, and did the whole announcement, but I ended up syncing the change to the wrong (testing) branch.
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
Once again thanks for the hard work and effort put into this. When will the block explorer be back on the correct block?
As soon as they update it. It's actually a little funny, since the fork is only two blocks long. 10330 is correct. Forked at 10331.
when will the block explorer get fixed?
Ok thanks for the help the update fixed it, for future sake which are the files to delete a blockchain and where are they located?
Ok, I figured out what happened with the explorer. I sync'd a preliminary change to github for version 1.0.3.0 that had to be fixed. 1.0.4.0 fixed the problem, I created the commit, and built the wallets, and did the whole announcement, but I ended up syncing the change to the wrong (testing) branch.
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
Once again thanks for the hard work and effort put into this. When will the block explorer be back on the correct block?
As soon as they update it. It's actually a little funny, since the fork is only two blocks long. 10330 is correct. Forked at 10331.
The windows wallets will sync a little slower. If you get stuck yeah, just close and reopen. And if you're not running 1.0.4 then update immediately.
My wallet is stuck at block 3445.... it a windows wallet..... what steps do I take to correct this?
Did you update to the latest wallet 1.0.4.0?
Sometimes just closing the wallet and restarting it can help also.
Jump to: