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

SolidStateSurvivor

hero member

Activity: 553

Merit: 500

Solo Miner Legend

Quote from: David Latapie on July 14, 2014, 07:06:28 AM

Quote from: presstab on July 13, 2014, 10:45:47 PM

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

hero member

Activity: 658

Merit: 503

Monero Core Team

Quote from: presstab on July 13, 2014, 10:45:47 PM

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).

unick

sr. member

Activity: 504

Merit: 254

Quote from: SolidStateSurvivor on July 14, 2014, 03:50:23 AM

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

SolidStateSurvivor

hero member

Activity: 553

Merit: 500

Solo Miner Legend

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

sr. member

Activity: 504

Merit: 254

Quote from: Alex_Koekie on July 13, 2014, 10:58:27 AM

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

unick

sr. member

Activity: 504

Merit: 254

Quote from: presstab on July 13, 2014, 11:51:39 PM

Quote from: unick on July 13, 2014, 10:59:10 PM

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!

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: unick on July 13, 2014, 10:59:10 PM

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

sr. member

Activity: 504

Merit: 254

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.

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: unick on July 13, 2014, 09:43:53 PM

Quote from: David Latapie on July 13, 2014, 09:43:04 PM

Quote from: unick on July 13, 2014, 09:24:27 PM

You need to get the latest version from my github (you need to compile from source at this point).

Code:

git pull && qmake-qt5 growthcoin-qt.pro && make

Code:

git pull && qmake-qt4 growthcoin-qt.pro && make

Do not work
Makefile:897: recipe for target 'build/coincontroldialog.o' failed

I'm on Arch, not Ubuntu

this is weird, it worked before right?

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

unick

sr. member

Activity: 504

Merit: 254

Quote from: David Latapie on July 13, 2014, 09:43:04 PM

Quote from: unick on July 13, 2014, 09:24:27 PM

You need to get the latest version from my github (you need to compile from source at this point).

Code:

git pull && qmake-qt5 growthcoin-qt.pro && make

Code:

git pull && qmake-qt4 growthcoin-qt.pro && make

Do not work
Makefile:897: recipe for target 'build/coincontroldialog.o' failed

I'm on Arch, not Ubuntu

this is weird, it worked before right?

David Latapie

hero member

Activity: 658

Merit: 503

Monero Core Team

Quote from: unick on July 13, 2014, 09:24:27 PM

You need to get the latest version from my github (you need to compile from source at this point).

Code:

git pull && qmake-qt5 growthcoin-qt.pro && make

Code:

git pull && qmake-qt4 growthcoin-qt.pro && make

Do not work
Makefile:897: recipe for target 'build/coincontroldialog.o' failed

I'm on Arch, not Ubuntu

unick

sr. member

Activity: 504

Merit: 254

Quote from: presstab on July 13, 2014, 09:31:27 PM

Quote from: unick on July 13, 2014, 09:24:27 PM

I am 10 days behind on 2 nodes, it's getting there slowly!

Quote from: David Latapie on July 13, 2014, 09:17:46 PM

I have only 1 active connection. Any idea why? Could someone share a growthcoin.conf file?

You need to get the latest version from my github (you need to compile from source at this point).

you should delete your peers.dat file and if you are on a fork, you will need to reindex the blockchain by either:

1. delete blkindex.dat and rename blk0001.dat to bootstrap.dat
2. delete blkindex.dat and blk0001.dat and redownload the whole blockchain.

make copies of those files until you are back in sync again. just to be on the safe side.

Unick is there a hash I can check to see if I am on the correct chain? I am syncing now but getting close.

latest best block @ height 591581 080c39d4efe4dff6a7ba33bf7811d4112ca243640ee75128c000157f805cb747

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: unick on July 13, 2014, 09:24:27 PM

I am 10 days behind on 2 nodes, it's getting there slowly!

Quote from: David Latapie on July 13, 2014, 09:17:46 PM

I have only 1 active connection. Any idea why? Could someone share a growthcoin.conf file?

You need to get the latest version from my github (you need to compile from source at this point).

you should delete your peers.dat file and if you are on a fork, you will need to reindex the blockchain by either:

1. delete blkindex.dat and rename blk0001.dat to bootstrap.dat
2. delete blkindex.dat and blk0001.dat and redownload the whole blockchain.

make copies of those files until you are back in sync again. just to be on the safe side.

Unick is there a hash I can check to see if I am on the correct chain? I am syncing now but getting close.

unick

sr. member

Activity: 504

Merit: 254

I am 10 days behind on 2 nodes, it's getting there slowly!

Quote from: David Latapie on July 13, 2014, 09:17:46 PM

I have only 1 active connection. Any idea why? Could someone share a growthcoin.conf file?

You need to get the latest version from my github (you need to compile from source at this point).

you should delete your peers.dat file and if you are on a fork, you will need to reindex the blockchain by either:

1. delete blkindex.dat and rename blk0001.dat to bootstrap.dat
2. delete blkindex.dat and blk0001.dat and redownload the whole blockchain.

make copies of those files until you are back in sync again. just to be on the safe side.

David Latapie

hero member

Activity: 658

Merit: 503

Monero Core Team

I have only 1 active connection. Any idea why? Could someone share a growthcoin.conf file?

unick

sr. member

Activity: 504

Merit: 254

The network is pretty unstable at this moment.

I am trying to sync back 3 peers, that should help to stabilize the network. they are about 80% done but sync speed seems to have slowed down.

I have only 1 peer that reports to be in sync.

I am monitoring this closely and I'll keep you guys updated. The only thing we can do for now is wait that we have a few stable and in sync nodes on the network.

almightyruler

legendary

Activity: 2268

Merit: 1092

Interesting that 162.243.13.186 is showing -1 for you, when that's the only peer I have that DOESN'T show as -1.

Also note that it has a nonzero banscore. I think the same thing is happening with you and that peer, which is happening with almost all of mine.

It's like I'm stuck in another world with 162.243.13.186, and no one else wants to talk to us...

Maybe this may offer some clues:

Code:

07/13/14 22:24:18 Misbehaving: 92.236.214.33:17177 (0 -> 1)
07/13/14 22:24:18 ProcessMessage(inv, 1441 bytes) FAILED
07/13/14 22:24:19 Misbehaving: 188.226.155.94:17177 (61 -> 62)
07/13/14 22:24:19 ProcessMessage(addr, 27 bytes) FAILED
07/13/14 22:25:28 Misbehaving: 67.211.45.68:17177 (62 -> 63)
07/13/14 22:25:28 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:28 Misbehaving: 82.9.77.178:17177 (60 -> 61)
07/13/14 22:25:28 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:28 Misbehaving: 92.236.214.33:17177 (1 -> 2)
07/13/14 22:25:28 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:28 Misbehaving: 67.211.45.68:17177 (63 -> 64)
07/13/14 22:25:28 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:29 Misbehaving: 188.226.155.94:17177 (62 -> 63)
07/13/14 22:25:29 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:52 Misbehaving: 92.236.214.33:17177 (2 -> 3)
07/13/14 22:25:52 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:52 Misbehaving: 82.9.77.178:17177 (61 -> 62)
07/13/14 22:25:52 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:53 Misbehaving: 188.226.155.94:17177 (63 -> 64)
07/13/14 22:25:53 ProcessMessage(inv, 37 bytes) FAILED
07/13/14 22:25:53 Misbehaving: 67.211.45.68:17177 (64 -> 65)
07/13/14 22:25:53 ProcessMessage(inv, 37 bytes) FAILED

Alex_Koekie

newbie

Activity: 17

Merit: 0

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: Alex_Koekie on July 13, 2014, 03:54:21 PM

67.211.45.66:17177
155.210.52.121:17177

I added these two peers, same thing unfortunately.

Code:

[
    {
        "addr" : "67.211.45.66",
        "services" : "00000000",
        "lastsend" : 1405285267,
        "lastrecv" : 1405285462,
        "conntime" : 1405285267,
        "bytessent" : 135,
        "bytesrecv" : 366,
        "blocksrequested" : 0,
        "version" : 0,
        "subver" : "",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 6
    },
    {
        "addr" : "155.210.52.121",
        "services" : "00000000",
        "lastsend" : 1405285268,
        "lastrecv" : 1405285462,
        "conntime" : 1405285268,
        "bytessent" : 135,
        "bytesrecv" : 366,
        "blocksrequested" : 0,
        "version" : 0,
        "subver" : "",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 6
    },
    {
        "addr" : "162.243.13.186",
        "services" : "00000001",
        "lastsend" : 1405285479,
        "lastrecv" : 1405285479,
        "conntime" : 1405285268,
        "bytessent" : 811740,
        "bytesrecv" : 3663879,
        "blocksrequested" : 0,
        "version" : 70001,
        "subver" : "/GrowthCoin:1.3.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 119069,
        "banscore" : 0
    }
]

I thought it may have been because I had been banned for an older version, but I'm pretty sure I didn't start growthcoin before updating.

162.243.13.186 - the only peer who can give me blocks - is still at height 119069, even after several restarts of the client, so for some reason they are not syncing either.

edit: just noticed that the two -1 peers are showing a banscore of 6 (?!)

ice00

sr. member

Activity: 296

Merit: 250

Quote from: Alex_Koekie on July 13, 2014, 03:54:21 PM

I'm currently connected to:

23.92.53.139:17177
67.211.45.66:17177
188.226.155.94:17177
155.210.52.121:17177
82.9.77.178:17177

All are version: GrowthCoin:1.3.0
None of them shows height -1.

I hope it's helpful to you.

Those are the same of me

Topic: [RE-ANN] GrowthCoin PoW/PoS - 100% per year - Version 1.3.0.1 - page 34. (Read 66388 times)