Topic: [ANN][NYC] NEW YORK COIN at 2017 MACY'S THANKSGIVING DAY PARADE IN NYC! - page 103. (Read 141357 times)

newyorkc magic, baby!!!

It's like it was magic!

The NYC network is so resilient that all damage caused by flawed 1.3 code will immediately work itself out. My missing unconfirmed sends hanging on Coinomi for 3-4 days will now magically confirm. The NYC network is time-tested and proven!

Upon extensive, lengthy beta-testing AND UNDER THOSE CONDITIONS ONLY should a fork be considered. 2Q/3Q 2019? I guess it depends when we have fully working codebase. Then we will need lengthy testing and review. And finally implementation.

At the moment that is not a concern. We just need to get the network running smoothly again. We think we have identified the root cause of the issue and will be testing it over the next month. This will not happen again.

Once we have discussed things in full we will post an update on what happens next. For now, lets just get the ship corrected and continue to move forward.

I went return to the old version of NewYorkCoin:

http://nyc.mypool.club/

The old version of the wallet does not use any nodes with version 1.3

The compatible nodes:

54.38.176.26:56072
45.116.233.4:22267
80.30.209.149:62153
90.9.74.201:60523
104.220.9.85:64928
213.32.6.132:33086
165.227.90.8:47830
173.174.215.56:11121
187.36.179.153:1883
172.221.70.230:64186
69.167.149.46:17435
62.213.219.34:39781
98.166.85.71:59548
37.97.227.182:47846
108.41.162.231:5160
39.116.239.43:50923
188.165.213.202:37652
76.95.178.229:41778
188.165.252.85:52438
173.249.3.92:57520
136.243.83.33:24698
95.216.36.90:47070
72.205.17.64:61083
157.161.128.51:17020
212.125.247.47:37360
104.239.230.131:35022
220.162.148.67:37464
111.30.46.177:36731
24.214.72.252:17020
206.189.61.229:59199
107.191.46.207:53266
18.216.0.44:43314
68.193.67.18:60028
94.177.201.91:51044
37.187.146.24:47338
50.225.198.67:58923
217.175.201.130:10619
88.99.2.95:53622


And course the my stable node is available:

163.172.222.175:9033

In the meantime, please remove the ANNOUNCEMENT and FORK Q&A from Community website. These hard-forks seldom go well (as you probably know). And investors have stayed away. No need to keep the guillotine hanging...

I appreciate you saying so. Our current issues haven't helped that view of myself.

Let me know what you hear from Coinsprofit, I hope to hear from him soon. Once we get this ship righted let's hash this out and move forward.

Slosh

It is such a simple solution. Publish as a BETA-TEST wallet/code rather than a "hard-fork". Beta testing goes well, after 3-6 months with no issues, nothing troubling in stats THEN YOU ANNOUNCE FORK. You're a smart guy - I met you. You already know this.

https://blogs.msdn.microsoft.com/seliot/2011/04/25/i-dont-always-test-my-code-but-when-i-do-i-do-it-in-production/

As a miner who also happens to be a software architect for a fortune 500 company that tests the hell out of our code using unit, integration and End-to-End tests I understand that the test environment can never replicate the real world in anything but the simplest of use cases.
Users with little-to-no understanding of software development are not very forgiving but from what I can tell due diligence was applied in this scenario.

Moonshot

Speaking of Test before implement, did you realize that the original "devs" tried to do a 97 million nyc premine but failed because they didn't use testnet and couldn't find their way through an if block? Not to mention the first two blocks that were supposed to be returned to the community are still in block 1 and 2? We've already done more testing on nycoin than anyone else in the past has. We even update the original test suite for our 1.2 update since all the values were still using btc and ltc values and all the tests failed.

If you were actively looking at the code you may come to realize that test coverage for a codebase like this is a bit challenging, particularly when testnet and mainnet don't react the same way in terms of difficulty adjustment as testnet always returns low diff blocks to account for low hashrate.

We've been testing, with every code change we make, but like in all things in life mistakes are made, things are overlooked, and sometimes inconveniences arise. How we handle those inconveniences defines who we are as people in a way.

Did you reach out to Coinsprofit yet?

Test before implement. That "atrocious" code has worked flawlessly for 4+ years. No hacks. Confirms every 30 seconds. Yobit (top 35 exchange) added old code. Coinomi (#1 rated alt-coin wallet) added old code. Everything works and has worked flawlessly. Just more difficult to mine these days...

Eloquently stated Slosh.  You have the full faith and support of the NewYorkCoinCommunity and as an NYC miner I fully support the direction you and the Dev Team are taking and look forward to a NewYorkCoin that is safer and more reliable for merchants and vastly more secure than the current code base with it's well known and exploitable vulnerabilities.

Moonshot

Right now we've got more issues than what's on a roadmap or website. Once we get things back on track we will re-assess the situation.

As the pool operators and developers know, Crypto is not exactly easy and when changes are made there are sometimes difficulties that arise. We are actively working on solutions while we wait for the network to correct itself (once all pools are back on the older daemons).

The biggest challenge is persevering in the face of adversity. When things get difficult to we just turn tail and run? When Coinsprofit got hacked years ago did he close up shop? When Bleutrade stopped trading NYC did everyone give up? When Coingather went down were we all running around hysterical that it was all falling apart?

If you are worried about the network holding up to the updates, make a backup of all of your data, regularly. Sort them by date if you need to, put them in cold storage. The dev team is working with a code base that hadn't been touched since 2014 with the exception of a "bad fork". What made that a "bad fork" was that the developer was run off or gave up. This coin will go nowhere if that keeps happening, which may be what you are comfortable with, I don't know, but if you want to trust a codebase from 2014 by a couple of launchers who "disappeared" then we've got bigger problems than network updates. That codebase is atrocious and a serious chore to work with. As a result, it has presented challenges to update properly and maintain proper backwards compatibility.

I'm looking to the future right now and I see it being very bright with a more modern codebase and a sleeker set of features. That future will not come by doing nothing.


As soon as I get word from all pools that the daemons are rolled back I will let everyone know.

Slosh

I have switched github/NewYorkCoin-NYC to "Beta" at newyorkcoin.net/social and reverted back to promoting nycoin/nycoin wallets, addnodes, etc. The "hard-fork" should be beta tested extensively (6+ months) with positive results before announcing any further news about a fork. It's quickly turning comical and if it continues nobody will benefit. The hard-fork is to avoid future potential network problems. But the code update has caused even worse problems. And caused them now. Not a good path to continue down.

If you have the best interest of NYC at heart, take down "Announcement" and "Fork Q&A" and put hard-fork on the back-burner (?3Q 2019 roadmap). And leave it at that until FULL TESTING has been successfully done. The NYC network is not in immediate jeopardy (other than most recent updates).

Just so everyone is kept in the loop, right now we are still waiting on Prohashing and nyc.mypool to respond to the request to roll back mining daemon versions. Once all pools have rolled back we should start to see our network issues subside.

I have sent support requests to PH and have messaged Coinsprofits but I understand that we don't all live in the same time zone so at the moment I am waiting to get responses. All other pools have rolled back their daemons.

Slosh

Coinsprofit, please post all working nodes to include in conf file (v1.0.1.1) for 2014 original code/wallet (https://github.com/nycoin/nycoin)

http://newyorkcoin.net will revert to publishing original code and wallets

As a regular wallet it doesn't seem to matter which version you are running. The new code base accepts older block generation just fine.

EDIT: Though I will say if you updated to 1.3 please switch over 1.3.1 to allow for connections to all possible nodes.

So which version should regular plp run now? 1207,13 or 131?

Hello all,

Alright... so here's the current situation:
There is some subtle difference in the 1.3 code that is preventing the blocks created by 1.3 from being accepted by older nodes even though on the surface everything looks in order. We think there may be some feature of the fork code that is somehow sneaking in early, as a result, blocks created by 1.3 are being orphaned when peered with 1.2 (and lower) nodes.

Until we can find a solution to this problem, we need everyone mining to revert back to the previous daemon. Blocks mined on 1.2 and lower are accepted by 1.3 without issue so anyone running a 1.3 wallet will still accept blocks from the older code. The hard fork scheduled in the 1.3 code is not expected to happen before late October so we have a little time to fix the issues being presented. In order to prevent further disruption to the network and potential loss of assets, the dev team feels that miners rolling back to 1.2 or lower is the best approach.

I sincerely apologize for the inconvenience this has caused to miners and users alike, the issues we face now did not arise during our testing phase. Once we have the issues resolved we will issue a statement regarding the true nature of the problems and how best to move forward.

Thank you for your patience,

MrSlosh