[RE-ANN] GrowthCoin PoW/PoS - 100% per year - Version 1.3.0.1

[unick]

okay,

I have 1 permanent node up to date, a second one that should be there in a few minutes.

If you have protocol version 60007, you don't HAVE to update to current version, but it would be a good idea to do so.

That version fails to disconnect older clients (prior 1.3.0.0) and you might find yourself on the wrong chain if an older client tries to connect to the network.

What we experienced yesterday is that an older client connected to the network, start generating a bunch of PoS blocks, built a longer chain that wasn't signed by the CP server and all those of us that accepted the CP server's version of the best block got stuck on the shorter chain!

This is now fixed has no client prior to the implementation of the new CP server will be able to connect to the network.

So if you are on a fork, you will have to reindex the whole blockchain to fix that by either deleting everything in your app folder (except wallet.dat)

or by just deleting blkindex.dat and peers.dat, and renaming blk0001.dat to bootstrap.dat.

it's always a good practice to backup your app folder before doing this kind of manipulation.

If Presstab can build a static exe for windows, that would be great.

Note that the explorer will be up to date tomorrow, it's still half way through redownloading the blockchain.

[1714165646]

1714165646

[1714165646]

1714165646

[1714165646]

1714165646

[1714165646]

1714165646

[presstab]

okay,

I have 1 permanent node up to date, a second one that should be there in a few minutes.

If you have protocol version 60007, you don't HAVE to update to current version, but it would be a good idea to do so.

That version fails to disconnect older clients (prior 1.3.0.0) and you might find yourself on the wrong chain if an older client tries to connect to the network.

What we experienced yesterday is that an older client connected to the network, start generating a bunch of PoS blocks, built a longer chain that wasn't signed by the CP server and all those of us that accepted the CP server's version of the best block got stuck on the shorter chain!

This is now fixed has no client prior to the implementation of the new CP server will be able to connect to the network.

So if you are on a fork, you will have to reindex the whole blockchain to fix that by either deleting everything in your app folder (except wallet.dat)

or by just deleting blkindex.dat and peers.dat, and renaming blk0001.dat to bootstrap.dat.

it's always a good practice to backup your app folder before doing this kind of manipulation.

If Presstab can build a static exe for windows, that would be great.

Note that the explorer will be up to date tomorrow, it's still half way through redownloading the blockchain.

No problem. Latest git commits and synced up to the current chain, double check the hash matched the one you gave me.
https://www.dropbox.com/s/5xkk8npt6enabuk/GrowthCoin-Qt.zip

Funny thing is that I just logged into my office computer through logmein and see that my GRW wallet was up and on the correct chain!

[unick]

okay,

I have 1 permanent node up to date, a second one that should be there in a few minutes.

If you have protocol version 60007, you don't HAVE to update to current version, but it would be a good idea to do so.

That version fails to disconnect older clients (prior 1.3.0.0) and you might find yourself on the wrong chain if an older client tries to connect to the network.

What we experienced yesterday is that an older client connected to the network, start generating a bunch of PoS blocks, built a longer chain that wasn't signed by the CP server and all those of us that accepted the CP server's version of the best block got stuck on the shorter chain!

This is now fixed has no client prior to the implementation of the new CP server will be able to connect to the network.

So if you are on a fork, you will have to reindex the whole blockchain to fix that by either deleting everything in your app folder (except wallet.dat)

or by just deleting blkindex.dat and peers.dat, and renaming blk0001.dat to bootstrap.dat.

it's always a good practice to backup your app folder before doing this kind of manipulation.

If Presstab can build a static exe for windows, that would be great.

Note that the explorer will be up to date tomorrow, it's still half way through redownloading the blockchain.

No problem. Latest git commits and synced up to the current chain, double check the hash matched the one you gave me.
https://www.dropbox.com/s/5xkk8npt6enabuk/GrowthCoin-Qt.zip

Funny thing is that I just logged into my office computer through logmein and see that my GRW wallet was up and on the correct chain!

thanks for the windows build - it's been updated on the github!

haha I had the same thing too, one of my old computers had a GRW client running on the right chain all along!

[unick]

Hello to all! 
I'm new to this forum and following the GRW topic for some while.

My client is of number v1.3.0.0-beta and just synced with the 1.3.0.0 node found here http://grw.blockx.info/connected-nodes. I checked getpeers, but it didn't connect to Satoshi:1.2.1 node found on the same site. I'm at block 590713, but wonder if I'm on the right fork.
Can you explain me how to check this?

Greetings,
Alex_Koekie

you should be on the right chain,

the current best block hash is 24dd855d33ba22f12ef3efbadd453f01539aed15b518f3c4882cf67f8a850f47 @ height 591791

to check if you are on the correct chain, type this in the console on the debug window

Code:

getblockhash 591791

if the hash matches the one posted, you are on the correct chain

[SolidStateSurvivor]

I have or there is a file with the block chain from May 21 zipped to download, does that work?

Let's see, I synced that block chain, I get:

getblockhash 591791

24dd855d33ba22f12ef3efbadd453f01539aed15b518f3c4882cf67f8a850f47


getblockhash 592244 (current block)

b3a388ef4ac859b6c2aa2c5a68a965633d9923e317468f7c8e352ff71a6f8301

[unick]

I have or there is a file with the block chain from May 21 zipped to download, does that work?

Let's see, I synced that block chain, I get:

getblockhash 591791

24dd855d33ba22f12ef3efbadd453f01539aed15b518f3c4882cf67f8a850f47


getblockhash 592244 (current block)

b3a388ef4ac859b6c2aa2c5a68a965633d9923e317468f7c8e352ff71a6f8301

yep, you are all good sir

[David Latapie]

Might be a good idea to delete the entire directory and build from scratch with a new git clone.

This is what I did (I am on 1.3.0.0-beta, not v1.3.0.0, I don't know why it did not compile to the latest version). I take quite a lot of time. My trading plan involved selling today, I am not sure I'll be able to... :/

By the way, I started a comparison feature of familiar high-PoS. The goal is not competition (X is best than Y) but cross-fertilisation (X has feature A but not feature B that Y has; let's add it). Inspiration is the improvement in 3D video card after 3D benchmarks arrived in the 90's. I only added feature that are unambiguously beneficial (bold part, the italic part are just information and prone to change).
Proof-of-stake List - Features comparison (it is a multitabbed spreadsheet and this tab is a new one).

[SolidStateSurvivor]

Might be a good idea to delete the entire directory and build from scratch with a new git clone.

This is what I did (I am on 1.3.0.0-beta, not v1.3.0.0, I don't know why it did not compile to the latest version). I take quite a lot of time. My trading plan involved selling today, I am not sure I'll be able to... :/

By the way, I started a comparison feature of familiar high-PoS. The goal is not competition (X is best than Y) but cross-fertilisation (X has feature A but not feature B that Y has; let's add it). Inspiration is the improvement in 3D video card after 3D benchmarks arrived in the 90's. I only added feature that are unambiguously beneficial (bold part, the italic part are just information and prone to change).
Proof-of-stake List - Features comparison (it is a multitabbed spreadsheet and this tab is a new one).

Maybe we could upload the block chain for you. Mine seems to be complete.

[David Latapie]

Might be a good idea to delete the entire directory and build from scratch with a new git clone.

This is what I did (I am on 1.3.0.0-beta, not v1.3.0.0, I don't know why it did not compile to the latest version). I take quite a lot of time. My trading plan involved selling today, I am not sure I'll be able to... :/

By the way, I started a comparison feature of familiar high-PoS. The goal is not competition (X is best than Y) but cross-fertilisation (X has feature A but not feature B that Y has; let's add it). Inspiration is the improvement in 3D video card after 3D benchmarks arrived in the 90's. I only added feature that are unambiguously beneficial (bold part, the italic part are just information and prone to change).
Proof-of-stake List - Features comparison (it is a multitabbed spreadsheet and this tab is a new one).

Maybe we could upload the block chain for you. Mine seems to be complete.

I added a "Optimal block size" column on Proof-of-stake List - Features comparison. The blockchain location would be great, especially if a canonical URL (an URL that doesn't change) is available. I would mention it for any coin. Thanks for the proposal.

But that won't fix the fact the I can't compile 1.3 final.

[SolidStateSurvivor]

I added a "Optimal block size" column on Proof-of-stake List - Features comparison. The blockchain location would be great, especially if a canonical URL (an URL that doesn't change) is available. I would mention it for any coin. Thanks for the proposal.

But that won't fix the fact the I can't compile 1.3 final.

Maybe a monthly blockchain.zip on the http://grw.blockx.info? Is there room for such an option? I could help maintaining it, keeping it up to date.
With the blk0001.dat, blkindex.dat and, database <DIR> maybe? Just a suggestion. Or maybe even twice a month, it would make it easier for newcomers to
GRW and people who need to fix their wallets.

[dengnizaidongji]

I added a "Optimal block size" column on Proof-of-stake List - Features comparison. The blockchain location would be great, especially if a canonical URL (an URL that doesn't change) is available. I would mention it for any coin. Thanks for the proposal.

But that won't fix the fact the I can't compile 1.3 final.

Maybe a monthly blockchain.zip on the http://grw.blockx.info? Is there room for such an option? I could help maintaining it, keeping it up to date.
With the blk0001.dat, blkindex.dat and, database <DIR> maybe? Just a suggestion. Or maybe even twice a month, it would make it easier for newcomers to
GRW and people who need to fix their wallets.

good idea.

[unick]

Maybe a monthly blockchain.zip on the http://grw.blockx.info? Is there room for such an option? I could help maintaining it, keeping it up to date.
With the blk0001.dat, blkindex.dat and, database <DIR> maybe? Just a suggestion. Or maybe even twice a month, it would make it easier for newcomers to
GRW and people who need to fix their wallets.

I was thinking about something similar, but instead of uploading a copy on the server, I was thinking creating a Torrent for it.  We would need at least 3 good seed nodes at all times, more is better.

Is there people willing to keep up some seed nodes?

[David Latapie]

Maybe a monthly blockchain.zip on the http://grw.blockx.info? Is there room for such an option? I could help maintaining it, keeping it up to date.
With the blk0001.dat, blkindex.dat and, database <DIR> maybe? Just a suggestion. Or maybe even twice a month, it would make it easier for newcomers to
GRW and people who need to fix their wallets.

I was thinking about something similar, but instead of uploading a copy on the server, I was thinking creating a Torrent for it.  We would need at least 3 good seed nodes at all times, more is better.

Is there people willing to keep up some seed nodes?

I could handle it, at least for the first week (home PC, not server, that's why - even if open 24/7)
As soon as you have the canonical URL (i.e. URL is always the same, even when the file changes), PM me.

[David Latapie]

Code:

#http://grw.blockx.info/connected-nodes
#file must be exactly "growthcoin.conf", case included
addnode=203.20.114.252
addnode=128.199.191.230
addnode=188.226.240.91
addnode=92.236.214.33
addnode=69.17.241.165
addnode=69.17.241.165
addnode=67.211.45.68
addnode=83.226.173.228

I plan to link to the post from the high-PoS comparison matrix. Please confirm it is correct and add suggestion. I'd welcome a more permanent solution.

[SolidStateSurvivor]

Maybe a monthly blockchain.zip on the http://grw.blockx.info? Is there room for such an option? I could help maintaining it, keeping it up to date.
With the blk0001.dat, blkindex.dat and, database <DIR> maybe? Just a suggestion. Or maybe even twice a month, it would make it easier for newcomers to
GRW and people who need to fix their wallets.

I was thinking about something similar, but instead of uploading a copy on the server, I was thinking creating a Torrent for it.  We would need at least 3 good seed nodes at all times, more is better.

Is there people willing to keep up some seed nodes?

I'm sure some of us can seed, now and then, after all, some of us use torrents several times a week, I know I do. The torrent will change every month, but maybe the link could always remain the same.

[unick]

Code:

#http://grw.blockx.info/connected-nodes
#file must be exactly "growthcoin.conf", case included
addnode=203.20.114.252
addnode=128.199.191.230
addnode=188.226.240.91
addnode=92.236.214.33
addnode=69.17.241.165
addnode=69.17.241.165
addnode=67.211.45.68
addnode=83.226.173.228

I plan to link to the post from the high-PoS comparison matrix. Please confirm it is correct and add suggestion. I'd welcome a more permanent solution.

this seems ok

EDIT:
But for a more permanent solution you can use the DNS seed nodes

actually these nodes are hardcoded in the source, I successfully connect to peer without any config file


the 2 permanent seed nodes are:

Code:

seed.grw.blockx.info
seed1.grw.acidpool.com

[unick]

Maybe a monthly blockchain.zip on the http://grw.blockx.info? Is there room for such an option? I could help maintaining it, keeping it up to date.
With the blk0001.dat, blkindex.dat and, database <DIR> maybe? Just a suggestion. Or maybe even twice a month, it would make it easier for newcomers to
GRW and people who need to fix their wallets.

I was thinking about something similar, but instead of uploading a copy on the server, I was thinking creating a Torrent for it.  We would need at least 3 good seed nodes at all times, more is better.

Is there people willing to keep up some seed nodes?

I'm sure some of us can seed, now and then, after all, some of us use torrents several times a week, I know I do. The torrent will change every month, but maybe the link could always remain the same.

That's the thing I'm not sure yet, if the link could remain the same while the file (.torrent) changes every month, I will investigate. I know I will setup a permanent node for this.

[Alex_Koekie]

Strange things happening....

I'm on the right blockchain, i used the getblockhash command. Thanks Unick!

Current shows: getblockhash 592973 - 0000000cd886aa4eb844f5354e21cdc3a2e9af26cea2f18c7db09e904ca31aa8

Using the betaclient from here: https://www.dropbox.com/s/5xkk8npt6enabuk/GrowthCoin-Qt.zip
"version" : "v1.3.0.0-beta",
"protocolversion" : 60007,
"walletversion" : 60000,

But I'm only getting orphans when staking. Some go up to 10 confirmations and then get rejected.

[unick]

Strange things happening....

I'm on the right blockchain, i used the getblockhash command. Thanks Unick!

Current shows: getblockhash 592973 - 0000000cd886aa4eb844f5354e21cdc3a2e9af26cea2f18c7db09e904ca31aa8

Using the betaclient from here: https://www.dropbox.com/s/5xkk8npt6enabuk/GrowthCoin-Qt.zip
"version" : "v1.3.0.0-beta",
"protocolversion" : 60007,
"walletversion" : 60000,

But I'm only getting orphans when staking. Some go up to 10 confirmations and then get rejected.

this is the wrong version

you should have protocol 70001

please download the pre-release version (1.3.1.0) from this link https://github.com/iamunick/growthcoin/releases

the version you should read in your client is 1.3.0.1

[scryptographer]

Strange things happening....

I'm on the right blockchain, i used the getblockhash command. Thanks Unick!

Current shows: getblockhash 592973 - 0000000cd886aa4eb844f5354e21cdc3a2e9af26cea2f18c7db09e904ca31aa8

Using the betaclient from here: https://www.dropbox.com/s/5xkk8npt6enabuk/GrowthCoin-Qt.zip
"version" : "v1.3.0.0-beta",
"protocolversion" : 60007,
"walletversion" : 60000,

But I'm only getting orphans when staking. Some go up to 10 confirmations and then get rejected.

this is the wrong version

you should have protocol 70001

please download the pre-release version (1.3.1.0) from this link https://github.com/iamunick/growthcoin/releases

the version you should read in your client is 1.3.0.1

I just grabbed the Qt from the github link, and I get

Code:

"version" : "v1.3.0.0-beta",
"protocolversion" : 60007,
"walletversion" : 60001,