updating to the new version has cause about 2k of my coins to not reappear once re-synced
is it a problem with minting?
is it a problem with minting?
you can use "repairwallet" to find your lost coins.i have try to do it.and received the lost coins.
Topic: [RESURRECTION] Bringing Life to Growthcoin (GRW) , MADATORY UPDATE TO 1.3.0 - page 4. (Read 34596 times)
June 03, 2014, 12:49:15 AM
you can use "repairwallet" to find your lost coins.i have try to do it.and received the lost coins.
June 03, 2014, 12:08:47 AM
updating to the new version has cause about 2k of my coins to not reappear once re-synced
is it a problem with minting?
is it a problem with minting?
June 02, 2014, 08:51:20 AM
staking is slowly.
Is this a question or a comment?
it is a question.
,but my connections are 9.the new wallet says:warning:checkpoint is too old.
are you fully sync yet? if you are not, the message is normal. Once you will be up to date, the message will not show anymore.
not fully sync yet.
June 02, 2014, 08:19:00 AM
staking is slowly.
Is this a question or a comment?
it is a question.
,but my connections are 9.the new wallet says:warning:checkpoint is too old.
are you fully sync yet? if you are not, the message is normal. Once you will be up to date, the message will not show anymore.
June 02, 2014, 01:50:21 AM
staking is slowly.
Is this a question or a comment?
it is a question.
,but my connections are 9.the new wallet says:warning:checkpoint is too old.
June 02, 2014, 01:38:16 AM
staking is slowly.
Is this a question or a comment?
it is a question.
,but my connections are 9. June 02, 2014, 12:26:10 AM
staking is slowly.
Is this a question or a comment?
June 02, 2014, 12:24:59 AM
Out of curiosity, why is the new reindexing necessary?
To enable fast start, the block hash was added to the index. So the reindexing does that with the new source code.
June 01, 2014, 10:27:36 PM
staking is slowly.
June 01, 2014, 09:12:39 PM
Hey all, just to confirm, 1.3.0 is the latest version (that unick was working on), right? If so, is there anything we need to be aware of before doing the update (any problems?)?
Thanks!
Thanks!
One thing you should know is that a full blockchain reindex is required, meaning that you need to delete the existing blk*.dat files from your computer and let it sync again.
other than that, no serious issues came up yet,
be sure to make a copy of your wallet (as always) before upgrading.
Got you. Thanks for this!
Out of curiosity, why is the new reindexing necessary?
June 01, 2014, 08:25:46 PM
Hey all, just to confirm, 1.3.0 is the latest version (that unick was working on), right? If so, is there anything we need to be aware of before doing the update (any problems?)?
Thanks!
Thanks!
One thing you should know is that a full blockchain reindex is required, meaning that you need to delete the existing blk*.dat files from your computer and let it sync again.
other than that, no serious issues came up yet,
be sure to make a copy of your wallet (as always) before upgrading.
June 01, 2014, 08:16:53 PM
Hey all, just to confirm, 1.3.0 is the latest version (that unick was working on), right? If so, is there anything we need to be aware of before doing the update (any problems?)?
Thanks!
Thanks!
June 01, 2014, 08:05:35 PM
Ok, try this instead: http://grw.blockx.info/grw_bootstrap_20140529.tar.gz
Make sure to clean all your appdata folder (except your wallet.dat of course)
put in this bootstrap.dat before starting the client (if you started the client make sure to delete any blk* files in that folder.
then start your client.
With the bootstrap.dat file, your client will recreate the index and get the missing blocks from the network.
alternatively you can force the connection to good nodes by making sure to remove the peers.dat file and starting your client with the -connect=IP switch. you try any of this page nodes running version 1.3.0.0
http://grw.blockx.info/connected-nodes
Make sure to clean all your appdata folder (except your wallet.dat of course)
put in this bootstrap.dat before starting the client (if you started the client make sure to delete any blk* files in that folder.
then start your client.
With the bootstrap.dat file, your client will recreate the index and get the missing blocks from the network.
alternatively you can force the connection to good nodes by making sure to remove the peers.dat file and starting your client with the -connect=IP switch. you try any of this page nodes running version 1.3.0.0
http://grw.blockx.info/connected-nodes
Thanks!
I'm trying both, in different computers. The bootstrap is recreating the index.
EDIT: -connect=IP has worked! Thanks!
Excellent, I'm glad you got it sorted out
June 01, 2014, 08:04:45 PM
a community take over, well there may be hope for the world yet.....
i glanced at the source, when i have time i will build it and check it out....
appears a lot of work went into it....
the origainal client would not pay out stake due to a few issues.....
i glanced at the source, when i have time i will build it and check it out....
appears a lot of work went into it....
the origainal client would not pay out stake due to a few issues.....
Wallet is staking now. still, more work is required, as stakes are coming in too fast (if you have a few mature blocks, you will see).
anyhow, welcome back to the community
June 01, 2014, 08:01:22 PM
I know this was a long time ago, so I guess I can't get it back now, but is there a -salvagewallet or switch I could use to get these coins back?
Status: 0/unconfirmed
Date: 2014-02-20 03:00
To: GUxT3aUvKrFV84aASf9GCs7uvnDMTPVoon
Debit: -600.00 GRW
Transaction fee: -0.20 GRW
Net amount: -600.20 GRW
Transaction ID: f71436bfada384c553cb9dcffab1ff2da6990ddd85eb10a5790d8b4f53ebc1e8
They just sit there in the transaction list, unconfirmed. :-/
Status: 0/unconfirmed
Date: 2014-02-20 03:00
To: GUxT3aUvKrFV84aASf9GCs7uvnDMTPVoon
Debit: -600.00 GRW
Transaction fee: -0.20 GRW
Net amount: -600.20 GRW
Transaction ID: f71436bfada384c553cb9dcffab1ff2da6990ddd85eb10a5790d8b4f53ebc1e8
They just sit there in the transaction list, unconfirmed. :-/
if that was a transaction that never got accepted, a backup and repairwallet could restore those coins, or a salvagewallet should do it. If those were mined on a fork... chances are they will be lost.
June 01, 2014, 06:54:48 PM
a community take over, well there may be hope for the world yet.....
i glanced at the source, when i have time i will build it and check it out....
appears a lot of work went into it....
the origainal client would not pay out stake due to a few issues.....
i glanced at the source, when i have time i will build it and check it out....
appears a lot of work went into it....
the origainal client would not pay out stake due to a few issues.....
June 01, 2014, 06:42:53 PM
I know this was a long time ago, so I guess I can't get it back now, but is there a -salvagewallet or switch I could use to get these coins back?
Status: 0/unconfirmed
Date: 2014-02-20 03:00
To: GUxT3aUvKrFV84aASf9GCs7uvnDMTPVoon
Debit: -600.00 GRW
Transaction fee: -0.20 GRW
Net amount: -600.20 GRW
Transaction ID: f71436bfada384c553cb9dcffab1ff2da6990ddd85eb10a5790d8b4f53ebc1e8
They just sit there in the transaction list, unconfirmed. :-/
Status: 0/unconfirmed
Date: 2014-02-20 03:00
To: GUxT3aUvKrFV84aASf9GCs7uvnDMTPVoon
Debit: -600.00 GRW
Transaction fee: -0.20 GRW
Net amount: -600.20 GRW
Transaction ID: f71436bfada384c553cb9dcffab1ff2da6990ddd85eb10a5790d8b4f53ebc1e8
They just sit there in the transaction list, unconfirmed. :-/
1) Bakcup wallet.dat
2) From console (Debug) run "repairwallet"
June 01, 2014, 05:53:58 PM
I know this was a long time ago, so I guess I can't get it back now, but is there a -salvagewallet or switch I could use to get these coins back?
Status: 0/unconfirmed
Date: 2014-02-20 03:00
To: GUxT3aUvKrFV84aASf9GCs7uvnDMTPVoon
Debit: -600.00 GRW
Transaction fee: -0.20 GRW
Net amount: -600.20 GRW
Transaction ID: f71436bfada384c553cb9dcffab1ff2da6990ddd85eb10a5790d8b4f53ebc1e8
They just sit there in the transaction list, unconfirmed. :-/
Status: 0/unconfirmed
Date: 2014-02-20 03:00
To: GUxT3aUvKrFV84aASf9GCs7uvnDMTPVoon
Debit: -600.00 GRW
Transaction fee: -0.20 GRW
Net amount: -600.20 GRW
Transaction ID: f71436bfada384c553cb9dcffab1ff2da6990ddd85eb10a5790d8b4f53ebc1e8
They just sit there in the transaction list, unconfirmed. :-/
June 01, 2014, 12:42:59 PM
Ok, try this instead: http://grw.blockx.info/grw_bootstrap_20140529.tar.gz
Make sure to clean all your appdata folder (except your wallet.dat of course)
put in this bootstrap.dat before starting the client (if you started the client make sure to delete any blk* files in that folder.
then start your client.
With the bootstrap.dat file, your client will recreate the index and get the missing blocks from the network.
alternatively you can force the connection to good nodes by making sure to remove the peers.dat file and starting your client with the -connect=IP switch. you try any of this page nodes running version 1.3.0.0
http://grw.blockx.info/connected-nodes
Make sure to clean all your appdata folder (except your wallet.dat of course)
put in this bootstrap.dat before starting the client (if you started the client make sure to delete any blk* files in that folder.
then start your client.
With the bootstrap.dat file, your client will recreate the index and get the missing blocks from the network.
alternatively you can force the connection to good nodes by making sure to remove the peers.dat file and starting your client with the -connect=IP switch. you try any of this page nodes running version 1.3.0.0
http://grw.blockx.info/connected-nodes
Thanks!
I'm trying both, in different computers. The bootstrap is recreating the index.
EDIT: -connect=IP has worked! Thanks!
June 01, 2014, 12:41:56 PM
I don't remember seeing the explorer over 20 active connections, this is looking great.
Plus like Ice said, I rarely see orphans or yet to see a fork since the update.
Those patches really helped the network
Plus like Ice said, I rarely see orphans or yet to see a fork since the update.
Those patches really helped the network
Jump to: