hashbear
Newbie
 Offline
Activity: 19
Merit: 0
|
 |
October 10, 2014, 10:12:16 PM |
|
My wallet is stuck at 10316. Anyone else?
Can you do a getblockhash 10316 in the help > debug window ? Thanks 22:49:36  getblockhash 10316 22:49:36  7c40af3676b764055e574890e902875f9694ac8c489b3fe5c6b728f80086e51f Looks like I was in sync with the block explorer at 10308: 1b23a0db47bc082a0e03b2cb70a58bf914bdc7779354cce8affa8be5fe62b164 But not at 10309: f5aaa41ee22463a35bdd6d4947f4ffa12cb7b05cccaf2eabe7fab6a37fd1cf82 The wallet was built from the latest on git and I unlocked it at about that point. Do I need to resync? |
|
|
|
|
|
|
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
barabbas
Legendary
Offline
Activity: 1162
Merit: 1000
|
|
October 10, 2014, 10:15:25 PM |
|
What are the projections now for the final number of coins by the end of the "growth period"? 10 million? 100 million? 1,000 million? (I believe they call them billions in the US)
|
|
|
|
|
wiser
Legendary
Offline
Activity: 1806
Merit: 1029
|
|
October 10, 2014, 10:17:25 PM |
|
I have some buy orders in, but the price is holding higher than I was expecting, considering the issues so far and the negative posts. It will be an interesting experiment regardless.  It's a tough decision, actually, because you know the price will go down the next day just from the increased supply. However, if you wait until the next day, then you miss out on a staking period. Right now I'm just kind of watching it. You know how they say only invest what you can afford to lose... I'm about at that "can afford to lose" limit, but still tempted... EDIT: Hoo Boy! Glad I didn't buy 20 minutes ago! |
|
|
|
|
|
klopper
|
|
October 10, 2014, 10:18:13 PM |
|
What are the projections now for the final number of coins by the end of the "growth period"? 10 million? 100 million? 1,000 million? (I believe they call them billions in the US)
I would say ~3-7 million... but it really depends on how many keeps staking7 |
|
|
|
|
barabbas
Legendary
Offline
Activity: 1162
Merit: 1000
|
|
October 10, 2014, 10:21:01 PM |
|
What are the projections now for the final number of coins by the end of the "growth period"? 10 million? 100 million? 1,000 million? (I believe they call them billions in the US)
I would say ~3-7 million... but it really depends on how many keeps staking7 Really? And someone who started with just 6 seed could get to 1 million by himself? in what short of calculations you base your estimate? |
|
|
|
|
|
cryptzo (OP)
|
|
October 10, 2014, 10:26:02 PM |
|
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 >.<
|
|
|
|
BeerPimp
Member
Offline
Activity: 94
Merit: 10
|
|
October 10, 2014, 10:30:01 PM |
|
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 >.<
Once again thanks for the hard work and effort put into this. When will the block explorer be back on the correct block? |
|
|
|
|
|
travis72682
|
|
October 10, 2014, 10:31:26 PM |
|
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?
|
|
|
|
coinking
Legendary
Offline
Activity: 927
Merit: 1000
|
|
October 10, 2014, 10:33:23 PM |
|
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
|
|
|
|
|
DenisZabar
|
|
October 10, 2014, 10:37:07 PM |
|
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 |
|
|
|
tylerderden
Copper Member
Legendary
Offline
Activity: 1162
Merit: 1025
|
|
October 10, 2014, 10:43:45 PM |
|
when is this 269% kicking in?
|
|
|
|
|
goodgryphon
Member
Offline
Activity: 111
Merit: 10
|
|
October 10, 2014, 10:45:22 PM |
|
My wallet is stuck at block 3445.... it a windows wallet..... what steps do I take to correct this?
|
|
|
|
|
wiser
Legendary
Offline
Activity: 1806
Merit: 1029
|
|
October 10, 2014, 10:49:26 PM |
|
My wallet is stuck at block 3445.... it a windows wallet..... what steps do I take to correct this?
This: 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 >.<
|
|
|
|
|
BeerPimp
Member
Offline
Activity: 94
Merit: 10
|
|
October 10, 2014, 10:50:37 PM |
|
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. |
|
|
|
|
|
cryptzo (OP)
|
|
October 10, 2014, 10:53:35 PM |
|
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.
|
|
|
|
|
cryptzo (OP)
|
|
October 10, 2014, 10:55:31 PM |
|
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 >.<
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. |
|
|
|
goodgryphon
Member
Offline
Activity: 111
Merit: 10
|
|
October 10, 2014, 10:57:17 PM |
|
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?
|
|
|
|
|
BeerPimp
Member
Offline
Activity: 94
Merit: 10
|
|
October 10, 2014, 10:59:03 PM |
|
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 >.<
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? |
|
|
|
|
|
travis72682
|
|
October 10, 2014, 11:00:20 PM |
|
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 |
|
|
|
coinking
Legendary
Offline
Activity: 927
Merit: 1000
|
|
October 10, 2014, 11:04:46 PM |
|
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? |
|
|
|
|
