noise23
Legendary
Offline
Activity: 968
Merit: 1002
|
|
July 12, 2014, 12:21:21 PM |
|
I've upgraded daemon at grw.acidpool.com today and found that the latest version shows totally different net hashrate. New version shows "netmhashps" : 27.30817205 and the older one which I still have on another server shows "networkhashps" : 100869782 So right now grw.acidpool.com shows Net Hashrate 27.31 MH/s and grw.multi-pool.info which i think on the older daemon version shows Net Hashrate 100.87 MH/s Just wondering which is the correct one?
|
|
|
|
ice00
|
|
July 12, 2014, 12:25:30 PM |
|
So right now grw.acidpool.com shows Net Hashrate 27.31 MH/s and grw.multi-pool.info which i think on the older daemon version shows Net Hashrate 100.87 MH/s
Yes, grw.multi-pool.info not use the latest source for daemon
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
noise23
Legendary
Offline
Activity: 968
Merit: 1002
|
|
July 12, 2014, 01:23:42 PM |
|
So right now grw.acidpool.com shows Net Hashrate 27.31 MH/s and grw.multi-pool.info which i think on the older daemon version shows Net Hashrate 100.87 MH/s
Yes, grw.multi-pool.info not use the latest source for daemon Well, new version also shows weird Est. Avg. Time per Block in MPOS - 1 min 55 sec so i switched the pool back to the older daemon just to be on the safe side.
|
|
|
|
unick (OP)
|
|
July 12, 2014, 02:05:22 PM |
|
there seems to be a fork, so just be careful. I run multiple daemons and I have 1 at ~100 MH/s and the other at about 27 MH/s
all same version
I have to go out today but I'll try to investigate if I can find some time
|
|
|
|
SolidStateSurvivor
|
|
July 12, 2014, 02:30:27 PM |
|
with HBN at 100% and GRW at 100%, it's like we ride the same bus... so we could crank up the volume a tiny bit to 150% or be crazy and jump it to 1000% just for the sake of Grrrrowing 1000% probably will kill GRW value very fast. Increase to 150% or so could be a good idea though I agree, let's not get crazy and push this coin to 10 or 1 Sat by giving it 1000% a year. 100-150% sounds better then, but I'm kinda ok with 100% Which 100% coin was first, this or HBN? Hmm, let me check. HBN pre-dates GRW by 7 days, July 24th. GRW Block 1 on Aug 1 in the ~ Nazi4U wallet address with 666 Transactions. So they are kind of equal, hmm then it's ok to take the POS to 110-150% annually, I guess. And just when I wrote that unick now has 666 posts, hmm. Some things are out to get me.
|
Founding member of Hashmeisters Inc...
|
|
|
ice00
|
|
July 12, 2014, 02:53:33 PM |
|
there seems to be a fork, so just be careful. I run multiple daemons and I have 1 at ~100 MH/s and the other at about 27 MH/s
all same version
block status: grw.multipool.info: 588548 grw.acidpool.com: 588548 grw.blockx.info:588019 my pc open wallet (latest soorce): 588548 mybe actually the two pools are on the same fork.
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
ice00
|
|
July 12, 2014, 03:01:13 PM |
|
I just remember that this mornig I have a strange thing in pc wallet. I open it and let syncronized (it has to download 10 hours), but when it need only 4 hours of block to donwload, it stops and connection was only 1. In log there was lot of connection faild, but maybe this is the point after that it bloocks to download blocks: 7/12/14 08:59:47 trying connection 115.77.185.99:17177 lastseen=2.4hrs 07/12/14 08:59:47 ERROR: mempool transaction missing input 07/12/14 08:59:47 ERROR: mempool transaction missing input 07/12/14 08:59:48 ProcessSyncCheckpoint: sync-checkpoint at 8b0b626dfc2bd0247a597056e63d30d287b0fd29078562ef3d6a02d2b5e6d964 07/12/14 08:59:48 Flushing wallet.dat 07/12/14 08:59:49 Flushed wallet.dat 611ms 07/12/14 08:59:49 Misbehaving: 64.188.164.77:17177 (46 -> 47) 07/12/14 08:59:49 ProcessMessage(checkpoint, 109 bytes) FAILED
I close the wallet, delete peers.dat, opens it and all goes fine.
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
unick (OP)
|
|
July 12, 2014, 03:32:56 PM |
|
Ok,
I think I got this figured out. A big thanks to Tranz for helping debug.
I saw a node connected with version 1.2.1 (previous version) and I assume this node generated a bunch of PoS blocks.
The thing is that the old version doesn't recognize the actual checkpoint server's signature. so generating a bunch of block created a new chain and splintered the network in two forks.
So I will issue a check to disconnect old peer from the network. The only thing is it couldn't be a worst timing as today I'm unavailable.
I will try to find a spot and some time to work on this but it might take a while.
The outcome will be a required update of the client and maybe a redownload of the block chain
Again sorry for the trouble this is causing, I have failed in issuing the correct check of version that would have rejected old clients and could of prevented this issue!
Stay tuned and thanks for your patience
|
|
|
|
SolidStateSurvivor
|
|
July 12, 2014, 04:10:22 PM Last edit: July 12, 2014, 07:10:22 PM by SolidStateSurvivor |
|
We shouldn't forget that PoS is first meant to protect and carry on the blockchain, so if someone never opens their wallet to support the blockchain, he could be "taxed" for it.
Maybe it's a good idea to base PoS reward on wallet online time? e.g. if during block maturity period wallet was online 24/7 all the time it gets 100% of PoS reward but if wallet was offline for some time reward decreases accordingly. For example if PoS rate is 150% and wallet was online all the time block gets full 150% PoS reward, but if it was online only 6 hours/day it gets only 37.5%, etc. People will be motivated to keep their wallets online and also we will be safe from sleeping "millionaire" accounts sudden huge pos reward dump. I would totally stop using a coin which wallet I had to have online for 24/7, say 15-60 mins a day, but def. 24/7, I have other wallets I can't have on at the same time plus I do other things with my few computers I have. I'd have to get a Rasp Pi just for that reason then.
|
Founding member of Hashmeisters Inc...
|
|
|
SolidStateSurvivor
|
|
July 12, 2014, 07:11:23 PM |
|
So it looks like it's just forking away, then. Block explorer has stopped @ block #588019 some 9 hours ago, at the time of writing this.
|
Founding member of Hashmeisters Inc...
|
|
|
Jamesco
|
|
July 13, 2014, 05:55:26 AM |
|
So just wondering, is there a way to get on the right chain manually or will we have to wait for the update?
|
|
|
|
dengnizaidongji
Sr. Member
Offline
Activity: 266
Merit: 250
Colossuscoin - the future of payment methods
|
|
July 13, 2014, 10:34:28 AM |
|
|
Colossuscoin - the future of payment methods
|
|
|
SolidStateSurvivor
|
|
July 13, 2014, 01:40:04 PM |
|
So just wondering, is there a way to get on the right chain manually or will we have to wait for the update?
I made a small attempt, but it jumped onto the wrong one, anyway. I tried using noirc=1 and just connect= to a correct peer.
|
Founding member of Hashmeisters Inc...
|
|
|
ice00
|
|
July 13, 2014, 02:56:35 PM |
|
The pool has find lot of orphans in an hours and with the new wallet there was essentially no more orphans so far. My pc wallet has find lot of POS, so I look to connections and now it has only 2 nodes.
Maybe I start to think that the wrong fork is becoming the more powerful.
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
SolidStateSurvivor
|
|
July 13, 2014, 02:57:32 PM |
|
The pool has find lot of orphans in an hours and with the new wallet there was essentially no more orphans so far. My pc wallet has find lot of POS, so I look to connections and now it has only 2 nodes.
Maybe I start to think that the wrong fork is becoming the more powerful.
Yeah, almost sounds like it.
|
Founding member of Hashmeisters Inc...
|
|
|
David Latapie
|
|
July 13, 2014, 03:28:15 PM |
|
We shouldn't forget that PoS is first meant to protect and carry on the blockchain, so if someone never opens their wallet to support the blockchain, he could be "taxed" for it. +1. Interest is a reward for securing the network and we should never forget that. On a more general note, I believe we should encourage cross-fertilisation amond the high-PoS family (PHS, HBN, GRW, NOBL (soon), CAP, TEK, HYP and maybe others). I think armin22 is considering creating a common website for all these PoS. A "feature comparison list" would help knowing which coin has yet to add which feature. Then a price/interest/number of coin ratio could be used as an incentive for spreading out the investment. Or and could someone give a growthcoin.conf example? I have only one connection on my wallet
|
|
|
|
Alex_Koekie
Newbie
Offline
Activity: 17
Merit: 0
|
|
July 13, 2014, 03:58:27 PM |
|
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
|
|
|
|
ice00
|
|
July 13, 2014, 04:09:54 PM |
|
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. The 1.2.1 is to not use as it is the one that create problems at it use an old version of the coin. Maybe blockinfo is on wrong fork.
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
baby222
|
|
July 13, 2014, 04:12:13 PM |
|
100%per year too high
|
|
|
|
ice00
|
|
July 13, 2014, 04:23:43 PM |
|
The two pools are still on the same fork as they are at blocks 590,738.
For the people that have problem in syncronization try the two address of the pools as nodes
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
|