Bitcoin Forum
November 30, 2022, 07:19:52 AM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 [112] 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 ... 264 »
  Print  
Author Topic: [ANN][CRW] CROWN (MN-PoS) | Platform | NFT framework | Governance | Masternodes  (Read 316235 times)
adorid
Sr. Member
****
Offline Offline

Activity: 445
Merit: 250


View Profile
February 08, 2017, 05:15:45 PM
 #2221

Used node list and full resync bring me back to the long chain.

Did you resync the old chain or download the new chain and then resync?

I copied Inferno node list, deleted everything under crown folder and downloaded from zero

1669792792
Hero Member
*
Offline Offline

Posts: 1669792792

View Profile Personal Message (Offline)

Ignore
1669792792
Reply with quote  #2

1669792792
Report to moderator
1669792792
Hero Member
*
Offline Offline

Posts: 1669792792

View Profile Personal Message (Offline)

Ignore
1669792792
Reply with quote  #2

1669792792
Report to moderator
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1669792792
Hero Member
*
Offline Offline

Posts: 1669792792

View Profile Personal Message (Offline)

Ignore
1669792792
Reply with quote  #2

1669792792
Report to moderator
1669792792
Hero Member
*
Offline Offline

Posts: 1669792792

View Profile Personal Message (Offline)

Ignore
1669792792
Reply with quote  #2

1669792792
Report to moderator
defunctec
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000



View Profile
February 08, 2017, 05:36:05 PM
 #2222

Used node list and full resync bring me back to the long chain.

Did you resync the old chain or download the new chain and then resync?

I copied Inferno node list, deleted everything under crown folder and downloaded from zero


I just checked my local wallets and I seem to have the same problem.
The old chain must still be dominant
sidhujag
Legendary
*
Offline Offline

Activity: 2044
Merit: 1004


View Profile
February 08, 2017, 05:44:33 PM
 #2223

Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online

Can you please help us with that? It would be greatly appreciated. Seems they are not on Twitter.

Based on your tweet you are saying that syspool has not updated its daemon and they are causing your fork? But have you even been to syspool recently? It's not even online because sys is merge mined with btc and the pool is just used for our internal testing mostly when we have new features. Sigwo is the guy who manages it and I think he wanted to do major updated (pertaining to Segwit) and took it down for now, I'll have to catch up with him.
defunctec
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000



View Profile
February 08, 2017, 05:53:18 PM
 #2224

Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online

Can you please help us with that? It would be greatly appreciated. Seems they are not on Twitter.

Based on your tweet you are saying that syspool has not updated its daemon and they are causing your fork? But have you even been to syspool recently? It's not even online because sys is merge mined with btc and the pool is just used for our internal testing mostly when we have new features. Sigwo is the guy who manages it and I think he wanted to do major updated (pertaining to Segwit) and took it down for now, I'll have to catch up with him.

Yes your right, it's not syscoin. I can't even find the pool anymore, probably because of the reasons you mention.
crackfoo
Legendary
*
Offline Offline

Activity: 3052
Merit: 1123



View Profile WWW
February 08, 2017, 05:56:59 PM
 #2225



I totally see where you're coming from.  Traditional views are that you should always allow your users to be able to access an exchange if you fork.

Give us a couple of hours to come back to you on this.  It would be a lot easier to just go with the longer chain.

I've tried several times now to get on the "short" chain but I already end up going back to the long one.... which is where the bulk of the clients are and where all the hashrate is....

What is the problem your having updating exactly?

eh? thought it was pretty plain. Everytime I sync, I go to the long chain.... even if I put in nodes from chainz explorer...

ZPOOL - the miners multipool! Support We pay 7 FLUX Parallel Assets directly to block rewards! Get paid more and faster!
defunctec
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000



View Profile
February 08, 2017, 06:00:51 PM
 #2226



I totally see where you're coming from.  Traditional views are that you should always allow your users to be able to access an exchange if you fork.

Give us a couple of hours to come back to you on this.  It would be a lot easier to just go with the longer chain.

I've tried several times now to get on the "short" chain but I already end up going back to the long one.... which is where the bulk of the clients are and where all the hashrate is....

What is the problem your having updating exactly?

eh? thought it was pretty plain. Everytime I sync, I go to the long chain.... even if I put in nodes from chainz explorer...

I've only just caught up with what's going on, i'm with you now and have the same issue.
SixOfFive
Sr. Member
****
Offline Offline

Activity: 630
Merit: 257


View Profile
February 08, 2017, 06:22:30 PM
 #2227

Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?
crowncoin_knight
Hero Member
*****
Offline Offline

Activity: 805
Merit: 500


View Profile WWW
February 08, 2017, 07:28:41 PM
Last edit: February 08, 2017, 07:56:18 PM by crowncoin_knight
 #2228

Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?

Yes you can help and everyone who is on the short chain, can you guys pls put more hash so we can surpass the 1.3th s which is being thrown currently on the long chain?

That would be appreciated!

And those on long just stop for few hours!  Wink

crackfoo
Legendary
*
Offline Offline

Activity: 3052
Merit: 1123



View Profile WWW
February 08, 2017, 07:32:13 PM
 #2229

Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?

Yes you can help and everyone who is on the short chain, can you guys pls put more hash so we can surpass the 1.3th s which is being thrown currently on the long chain?

That would be appreciated!

There more like 905.6 TH/s on the long chain... that is a lot of miners. which is why, IMO, shouldn't it be the correct one? My pool has CRW off or it's be another 2-300TH....

ZPOOL - the miners multipool! Support We pay 7 FLUX Parallel Assets directly to block rewards! Get paid more and faster!
crowncoin_knight
Hero Member
*****
Offline Offline

Activity: 805
Merit: 500


View Profile WWW
February 08, 2017, 07:35:21 PM
Last edit: February 08, 2017, 07:53:24 PM by crowncoin_knight
 #2230

Before infernoman went to sleep he was very sure the short one is the correct one. Why dont those miners running on long, just stop until the short gets ahead?

he is the guy who put the code together, so I tend to believe he is correct

Be great if those miners who are not running on the short chain https://chainz.cryptoid.info/crw/#!extraction just stopped mining. I am offering a bounty for lost funds.

crowncoin_knight
Hero Member
*****
Offline Offline

Activity: 805
Merit: 500


View Profile WWW
February 08, 2017, 07:42:40 PM
 #2231



Mergedmining is this your pool? 600 th s?

https://chainz.cryptoid.info/crw/extraction.dws?3.htm

SixOfFive
Sr. Member
****
Offline Offline

Activity: 630
Merit: 257


View Profile
February 08, 2017, 08:01:32 PM
 #2232



Mergedmining is this your pool? 600 th s?

https://chainz.cryptoid.info/crw/extraction.dws?3.htm

Correct (mergemining.com)
crowncoin_knight
Hero Member
*****
Offline Offline

Activity: 805
Merit: 500


View Profile WWW
February 08, 2017, 08:01:51 PM
 #2233

Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?

Yes you can help and everyone who is on the short chain, can you guys pls put more hash so we can surpass the 1.3th s which is being thrown currently on the long chain?

That would be appreciated!

There more like 905.6 TH/s on the long chain... that is a lot of miners. which is why, IMO, shouldn't it be the correct one? My pool has CRW off or it's be another 2-300TH....

crackfoo, would it be possible to direct the 2 x 300th to mergemining pool of sixoffive? We give you a bounty  Smiley We know this pool got it right

M8BWNNRFMNdak68c
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


View Profile
February 08, 2017, 09:41:42 PM
 #2234

verifymessage 17iZgAE3cSEYxynXa1g5GmbxFEj1HPpLDc IPEuwZKPEEZrh3mvqCXLPiph9v8nonFVGqeyqIHJPJ4aVkQfenG4c/sqlNmk5AixEbQTiDEtUiU/r/YEsgSMGYM= "I stop mining now in favour of the short blockchain. i control around 1 PH. so i loose at least 8 hours of mining. a compensation would be nice: 17iZgAE3cSEYxynXa1g5GmbxFEj1HPpLDc"

defunctec
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000



View Profile
February 08, 2017, 10:18:08 PM
 #2235

verifymessage 17iZgAE3cSEYxynXa1g5GmbxFEj1HPpLDc IPEuwZKPEEZrh3mvqCXLPiph9v8nonFVGqeyqIHJPJ4aVkQfenG4c/sqlNmk5AixEbQTiDEtUiU/r/YEsgSMGYM= "I stop mining now in favour of the short blockchain. i control around 1 PH. so i loose at least 8 hours of mining. a compensation would be nice: 17iZgAE3cSEYxynXa1g5GmbxFEj1HPpLDc"



You could instead point that 1Ph to a pool that's mining the short chain?
If not, please work out an estimation of your losses.. Thanks
M8BWNNRFMNdak68c
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


View Profile
February 08, 2017, 10:42:38 PM
Last edit: February 08, 2017, 11:23:06 PM by M8BWNNRFMNdak68c
 #2236

no, its merged in my own pool software, i can not switch to other pools on the fly Sad
the explorers show an actual difference of 2154 CRW for these 8 hours
plus additional time we need until the solution

but because of the netsplit, etc.. it think 50% of this will be fine..
and i also don't want a "refund", just a bounty, so maybe 10% will be perfectly ok..
infernoman
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
February 08, 2017, 11:31:07 PM
 #2237

no, its merged in my own pool software, i can not switch to other pools on the fly Sad
the explorers show an actual difference of 2154 CRW for these 8 hours
plus additional time we need until the solution

but because of the netsplit, etc.. it think 50% of this will be fine..
and i also don't want a "refund", just a bounty, so maybe 10% will be perfectly ok..

Thank you for understanding, I'm doing my best now to get everything back in line. mergedmining.com is on the right fork. and im getting infernopool there now. once we pass the old fork it will be much easier for miners to reconnect to the correct chain and start mining successfully.
urban_idler
Member
**
Offline Offline

Activity: 87
Merit: 10


View Profile
February 08, 2017, 11:47:25 PM
 #2238

I am just catching up on what's going on -- been working at the job that pays the bills...  

For those following this -- since it gets hard to follow from the stream and also in the internal Crown Slack, I will offer a summary of what I think happened and is happening.  Other members of the Crown team are welcome to affirm or correct me if I miss something or get something wrong -- but I think some of the guys in Europe are getting some sleep after a long day.

SUMMARY
1.  The Crown update which the team released had enforcement turned on -- meaning that the new nodes rejected connections from the old nodes.
2.  In the process of testing the team had not discussed (to my knowledge) whether enforcement should be turned on or not -- because enforcement was one of the many features which hadn't worked in the old code.
3.  The team's plan was to do a managed fork at block number set for approximately next Monday Feb 13th -- but instead has been working to manage the unintended fork which occurred as miners and thones began running on the new code release.
4.  Due to the fact that large miners hadn't updated their wallets yet -- NOT THEIR FAULT -- they were told they would have some time, and I believe that not all of the pools had necessarily been contacted before the fork happened.  
5. Due to enforcement being on in the release, the fork was a necessary result of the first miner who started running the new code. And because at that initial point, after the first mining installed the new code, less hashing power was working on the fork/network/blockchain which the new release mines on -- the fork which the new nodes and new code is running on has a shorter blockchain.
6.  The default way that a node knows which blockchain is valid is by it's length -- so this un-anticipated fork has created a blockchain which is (or was until al little bit ago in my understanding) being mined by miners running the old buggy code.  So as long as the blockchain mined by old-buggy code is longer -- it will be preferred as "valid" by the wallets.  This is part of the logic of mining and wallets -- the longer chain is always the one which has more compute power invested in it and right... except...
7. BUT in this case the longer chain is running on old buggy code, and going with the longer chain would only punish the folks who updated their code, which includes CCEX, the exchange.  

8. So some of the team members have purchased hash power and are aiming it at pools running the new code -- and the pools which hadn't updated (once again -- not their fault, but ours for having enforcement on in the release), have been contacted.

9. CURRENTLY:
    Chainz & CCEX show the fork being mined on the new code:     https://chainz.cryptoid.info/crw
    Blockpioneers shows the fork being mined with the old code:    http://crw.blockpioneers.info/index.php
    The has rate for the shorter chain / new code is higher than for the old code / longer chain.  So the new code chain is catching up.

10.  The core team takes full responsibility for fucking up on the enforcement.  No dancing around it.  We didn't realize that infernoman was going to build a new codebase where things actually worked just like they were supposed to.  And I think infernoman may have surprise himself.  

11.  I would like to thank the members of the core team who were working and sweating managing this process today.  

12.  There will always be mistakes and surprises and the key to this being a successful team and project will be in how we deal with the mistakes and surprises -- and how we communicate with the community.  This fork was an unforced error on our part -- that is disappointing to us and no one should really be happy about it... but the team and community have responded constructively and pivoted -- and while the problem isn't resolved yet -- everything is moving in the right direction.  

Hopefully that makes sense.

And for what it's worth, one of the lessons of all of this is that IN THE NEXT RELEASE ENFORCEMENT WILL BE TURNED OFF INITIALLY....Wink
 
infernoman
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
February 09, 2017, 01:05:15 AM
 #2239

Alright to get through this fork issue, i'm going to be working with xpool and mmpool to try and get all of us on the correct chain. @mmpool could you please update to the latest version on github? the update disabled enforcement as well as cuts off 0.9.5 nodes and updates the alert keys to the proper keys.
infernoman
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
February 09, 2017, 01:10:49 AM
Last edit: February 09, 2017, 07:44:36 AM by infernoman
 #2240

Working on building the new clients now. If you build your own clients please update NOW. MINERS ! Please wait until we've figured out the forking issue before starting to mine.


Wallets coming online now. https://github.com/Crowndev/crowncoin/releases/tag/v0.12.0.61

You'll notice that the protocol version has been increased
    "version" : 120060,
    "protocolversion" : 70040,

pi@raspberrypi:~/.crown $ crown-cli getblockhash 1246157
60d4bc8a12731505e889940a367cb48cfca3c69be6cb4e2771be36a12d282e31

For a list of already updated nodes confirmed to be on the right chain. More will be added as they come online.
https://www.whatsmydns.net/#A/crw.infernopool.com

ARM - https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.1-arm-linux-gnueabihf.tar.gz

32bit windows - https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.3-i686-w64-mingw32.tar.gz

64bit windows - https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.4-x86_64-w64-mingw32.tar.gz

32bit linux - https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.5-i686-pc-linux-gnu.tar.gz

64bit linux - https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.6-x86_64-unknown-linux-gnu.tar.gz

OSX - https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.7-x86_64-apple-darwin11.tar.gz


Pages: « 1 ... 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 [112] 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 ... 264 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!