Now it still doesn't work like was wrote in comment. Please, check it.
Topic: [ANN][NYC] NEW YORK COIN at 2017 MACY'S THANKSGIVING DAY PARADE IN NYC! - page 104. (Read 141357 times)
August 19, 2018, 09:07:21 PM
Now it still doesn't work like was wrote in comment. Please, check it.
August 19, 2018, 09:03:29 PM
If you are running a 1.3 wallet/node you must UPDATE IMMEDIATELY!
I did it:
http://nyc.mypool.club/ NYC v.1.3.1
August 19, 2018, 11:29:31 AM
Alright everyone, updated wallets are starting to get out.
If you are running a 1.3 wallet/node you must UPDATE IMMEDIATELY!
Follow the instructions found here https://github.com/NewYorkCoin-NYC/nycoin/releases/tag/v1.3.1.13 to get your new node up and running. This build is currently WINDOWS ONLY but we will have an OSX build on the shelf as soon as humanly possible.
If you are a miner or running a pool you can find the updated codebase now in the master branch at our github repo https://github.com/NewYorkCoin-NYC/nycoin.
The 1.3.1.13 codebase allows for connections to all wallets/nodes old and new on the NYCoin network.
Thank you all for your patience and cooperation,
MrSlosh
If you are running a 1.3 wallet/node you must UPDATE IMMEDIATELY!
Follow the instructions found here https://github.com/NewYorkCoin-NYC/nycoin/releases/tag/v1.3.1.13 to get your new node up and running. This build is currently WINDOWS ONLY but we will have an OSX build on the shelf as soon as humanly possible.
If you are a miner or running a pool you can find the updated codebase now in the master branch at our github repo https://github.com/NewYorkCoin-NYC/nycoin.
The 1.3.1.13 codebase allows for connections to all wallets/nodes old and new on the NYCoin network.
Thank you all for your patience and cooperation,
MrSlosh
August 19, 2018, 10:38:04 AM
1.3.1.
I need to update the pool wallet from 1.3 to 1.3.1?
Yes. New code has been officially pushed to master branch at https://github.com/NewYorkCoin-NYC/nycoin. New binaries will be available soon.
anyone mining on the older code base please update immediately. Anyone running a 1.3 node please update to 1.3.1 as soon as binaries are posted.
Thank you all for your patience. We'll get these issues sorted directly.
MrSlosh
August 19, 2018, 09:11:26 AM
1.3.1.
I need to update the pool wallet from 1.3 to 1.3.1?
August 18, 2018, 09:15:43 PM
Alright everyone, Prohashing, NYC.mypool, and Hobbyistpool are now on the 1.3 codebase. I am getting new wallet builds out as quick as I can, if you want to build the wallet yourself you can find the codebase here https://github.com/NewYorkCoin-NYC/nycoin/tree/v1.3.1. If you are mining NYCoin in any capacity please switch over as soon as possible.
This codebase will accept connections from all current and previous NYCoin wallets and the dns seeders have been rebuilt to cache all stable nodes. We have reached out to Master Mining, Mining-Dutch, and Coincave to have them update as well.
Once I get new wallet builds out and a decent node list built up I will submit a payment to Yobit to (hopefully) get them on board. Trade Satoshi is already on board and we are still waiting to here from other exchanges.
Thank you all for your patience. We should have a corrected network soon. I will let you know as soon as new desktop wallets are available.
NYCoin is the best!
Slosh
This codebase will accept connections from all current and previous NYCoin wallets and the dns seeders have been rebuilt to cache all stable nodes. We have reached out to Master Mining, Mining-Dutch, and Coincave to have them update as well.
Once I get new wallet builds out and a decent node list built up I will submit a payment to Yobit to (hopefully) get them on board. Trade Satoshi is already on board and we are still waiting to here from other exchanges.
Thank you all for your patience. We should have a corrected network soon. I will let you know as soon as new desktop wallets are available.
NYCoin is the best!
Slosh
August 18, 2018, 02:15:47 PM
Hey there!
This is exactly what we are trying to figure out ourselves! Can I get a screenshot of your pool daemon version? It seems there is some network segmentation going on. We are trying to link all the nodes back together.
NYC.MyPool.club with NYC 1.3:
I found your network.
What other pools and cryptomarkets have supported this update?
So far we've got yourself, Prohashing, and Hobbyist on the pools (coincave.nl is updating too). We've informed mining-dutch and mastermining as well.
We've got Tradesatoshi confirmed and we're waiting to hear from Exrates and Frei-exchange. I've got a payment ready to go for Yobit to upgrade but I am really working to get this issues resolved first.
We've got a fundraiser going to get Coinomi on board (https://blog.nycoin.community/new-york-coin-donation-drive/) but they want 2 BTC and it's difficult to part people from their crypto for any reason.
We're getting there. The easiest solution to the problems we are having now would be to get everyone on the new codebase but we understand some people do not handle change well and for some reason hesitate to trust strangers on the internet
All joking aside, we're busting our butts on this one.
Slosh
EDIT: Removed unnecessary image.
August 18, 2018, 02:10:04 PM
I really like Coin New York, it was really amazing until I was amazed to see it and nothing very special besides Coin New York.
August 18, 2018, 01:25:40 PM
For those experiencing issues with mining and pools, we are working diligently to solve the issues and get all wallets on the same page. The codebase for 1.3 will find and connect with all nodes, new and old, but for some reason it is giving preference to the newer code base nodes. I am currently reviewing the old and the new codebases to determine the root cause of the connection issues.
For those using the current issues to push their preference in mining pools, please keep in mind that we are all in this together and as long as no single pool controls more than 50% of the hashrate we are good to go. Please have patience while we work through these issues. Also keep in mind that Hobbyist has graciously offered his pool service to help us work through these issues which is why his pool is bearing the brunt of the issues and orphans. The issues we are facing now did not present themselves while we were testing on the testnet.
We are close to having a resolution, please bear with us as we work to stop this madness!
For those using the current issues to push their preference in mining pools, please keep in mind that we are all in this together and as long as no single pool controls more than 50% of the hashrate we are good to go. Please have patience while we work through these issues. Also keep in mind that Hobbyist has graciously offered his pool service to help us work through these issues which is why his pool is bearing the brunt of the issues and orphans. The issues we are facing now did not present themselves while we were testing on the testnet.
We are close to having a resolution, please bear with us as we work to stop this madness!
August 18, 2018, 05:56:05 AM
NEW YORK COIN SCRYPT MINING POOL
PPLNS Payout
Fee 0%
https://newyorkcoin.mastermining.net/
FAST SIGN UP HERE
We have good blocktimes performance.
PPLNS Payout
Fee 0%
https://newyorkcoin.mastermining.net/
FAST SIGN UP HERE
We have good blocktimes performance.
August 17, 2018, 08:00:55 PM
Oh my!
Hobbit mining something in its own branch. Please stop this madness!
Current difficulty: 1475
Current unit: 4592766
http://nyc.mypool.club/index.php?page=statistics&action=pool
Check this in our blockexplorer: http://nyc-block.mypool.club/
Hobbit mining something in its own branch. Please stop this madness!
Current difficulty: 1475
Current unit: 4592766
http://nyc.mypool.club/index.php?page=statistics&action=pool
Check this in our blockexplorer: http://nyc-block.mypool.club/
August 17, 2018, 07:39:57 PM
Hey there!
This is exactly what we are trying to figure out ourselves! Can I get a screenshot of your pool daemon version? It seems there is some network segmentation going on. We are trying to link all the nodes back together.
NYC.MyPool.club with NYC 1.3:
I found your network.
What other pools and cryptomarkets have supported this update?
August 17, 2018, 06:06:23 PM
Once again, it does not work properly. http://Https://hobbyistpool.ddns.net/nyc/index.php Ie. again or again.
/// We are investing issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Findblocks disabled, new blocks will not show up in the frontend
Blockupdate disabled, blocks and transactions confirmations are delayed ///
And what about miners?
It is clear that the problem with the wallets to version 1.3 on the pool.
I support NYC from the ground up. And I will continue to support mining and its ties with the founders.
Now there is not enough nerves and payment for electricity on the hobbyistpool.
We do not have electricity for free. Payback of equipment is also an option.
I got up at http://nyc.mypool.club/index.php
the only one is credible
I guess NYC miners will support.
This official pool at least does not buggy and an adequate founder of it. As you can see.
In general, let's get together on an official pool without FEE http://nyc.mypool.club/index.php
There is optimal for automatic complexity for everyone.
/// We are investing issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Findblocks disabled, new blocks will not show up in the frontend
Blockupdate disabled, blocks and transactions confirmations are delayed ///
And what about miners?
It is clear that the problem with the wallets to version 1.3 on the pool.
I support NYC from the ground up. And I will continue to support mining and its ties with the founders.
Now there is not enough nerves and payment for electricity on the hobbyistpool.
We do not have electricity for free. Payback of equipment is also an option.
I got up at http://nyc.mypool.club/index.php
the only one is credible
I guess NYC miners will support.
This official pool at least does not buggy and an adequate founder of it. As you can see.
In general, let's get together on an official pool without FEE http://nyc.mypool.club/index.php
There is optimal for automatic complexity for everyone.
August 16, 2018, 10:28:14 PM
If you have any contact with the pool operators please encourage them to update their daemon to version 1.3. The network problems we are encountering now are due to mining pools not updating to the latest code. We will continue to see problems with the network until all miners and pools have updated their daemons.
Hello Friend!
So why I don't see connections with 1.3?
Hey there!
This is exactly what we are trying to figure out ourselves! Can I get a screenshot of your pool daemon version? It seems there is some network segmentation going on. We are trying to link all the nodes back together.
August 16, 2018, 05:23:31 PM
If you have any contact with the pool operators please encourage them to update their daemon to version 1.3. The network problems we are encountering now are due to mining pools not updating to the latest code. We will continue to see problems with the network until all miners and pools have updated their daemons.
Hello Friend!
So why I don't see connections with 1.3?
August 16, 2018, 04:23:55 PM
I can not open the official website and almost your website you created has no green security lock, I worry about this. There are usually dangers to unprotected websites.
August 16, 2018, 03:27:28 PM
MrSlosh !
At your request, contacted the main founder from 2014 NYC and supervising the main mining pool NYC http://nyc.mypool.club/index.php /
Answer. Everything under control. Everything is visible and remade in advance. We see the scoundrels.
And the most interesting for the NYC community - the development of programmers under his sensitive guidance for android systems is completed - MOBI. You just run the train. After 1.5 weeks after testing, lay out for the planet. No problem.Thank you for understanding.
At your request, contacted the main founder from 2014 NYC and supervising the main mining pool NYC http://nyc.mypool.club/index.php /
Answer. Everything under control. Everything is visible and remade in advance. We see the scoundrels.
And the most interesting for the NYC community - the development of programmers under his sensitive guidance for android systems is completed - MOBI. You just run the train. After 1.5 weeks after testing, lay out for the planet. No problem.Thank you for understanding.
August 16, 2018, 12:18:14 PM
NEW YORK COIN SCRYPT MINING POOL
PPLNS Payout
Fee 0%
https://newyorkcoin.mastermining.net/
FAST SIGN UP HERE
We have good blocktimes performance.
PPLNS Payout
Fee 0%
https://newyorkcoin.mastermining.net/
FAST SIGN UP HERE
We have good blocktimes performance.
August 16, 2018, 10:42:29 AM
If you have any contact with the pool operators please encourage them to update their daemon to version 1.3. The network problems we are encountering now are due to mining pools not updating to the latest code. We will continue to see problems with the network until all miners and pools have updated their daemons.
This update is extremely important as the older daemons are not secure and are susceptible to a variety of timewarp attacks that could lead theft or worse.
If you are a miner/pool operator please update your daemon as soon as possible to ensure the network is secure and stable for years to come.
This update is extremely important as the older daemons are not secure and are susceptible to a variety of timewarp attacks that could lead theft or worse.
If you are a miner/pool operator please update your daemon as soon as possible to ensure the network is secure and stable for years to come.
At the official mining pool of the NYC http://nyc.mypool.club/index.php there are no problems with the blocks.
Blocks are being investigated. http://nyc-block.mypool.club/
The miners are successfully mined.
Support NYC and make money by mining. Moreover, the complexity is now minimal.
But with the pool https://hobbyistpool.ddns.net/nyc/index.php the second day of the big problem.
Who has problems or is suspected - go to the official pool without FEE http://nyc.mypool.club/index.php
Yes ! Yes sir!
///Since (most probably) ProHashing re-enabled their mining pool towards our network, after updating their coin daemon to v1.3.0, it seems like we are suffering from network segmentation.
Probably due to the fact that when they started mining, their own coin daemon did not have connections to older nodes (v1.3 rejects nodes older than 1.2.0.x), they didnt broadcast to those older nodes.
Also miners on the older nodes didnt connect back to the 'new network' via an intermediate 1.2.0.x.
The issues, as far as we've seen, fix themselves in time, as nodes reconnect to other nodes all time. This means that they also sync up, doing a reorganize.
It seems the more 1.3 nodes that came into being and the fewer 1.2 nodes available the pre 1.2 nodes monopolize the connections to the remaining 1.2 nodes.///
Blocks are being investigated. http://nyc-block.mypool.club/
The miners are successfully mined.
Support NYC and make money by mining. Moreover, the complexity is now minimal.
But with the pool https://hobbyistpool.ddns.net/nyc/index.php the second day of the big problem.
Who has problems or is suspected - go to the official pool without FEE http://nyc.mypool.club/index.php
Yes ! Yes sir!
///Since (most probably) ProHashing re-enabled their mining pool towards our network, after updating their coin daemon to v1.3.0, it seems like we are suffering from network segmentation.
Probably due to the fact that when they started mining, their own coin daemon did not have connections to older nodes (v1.3 rejects nodes older than 1.2.0.x), they didnt broadcast to those older nodes.
Also miners on the older nodes didnt connect back to the 'new network' via an intermediate 1.2.0.x.
The issues, as far as we've seen, fix themselves in time, as nodes reconnect to other nodes all time. This means that they also sync up, doing a reorganize.
It seems the more 1.3 nodes that came into being and the fewer 1.2 nodes available the pre 1.2 nodes monopolize the connections to the remaining 1.2 nodes.///
August 16, 2018, 06:02:36 AM
At the official mining pool of the NYC http://nyc.mypool.club/index.php there are no problems with the blocks.
Blocks are being investigated. http://nyc-block.mypool.club/
The miners are successfully mined.
Support NYC and make money by mining. Moreover, the complexity is now minimal.
But with the pool https://hobbyistpool.ddns.net/nyc/index.php the second day of the big problem.
Who has problems or is suspected - go to the official pool without FEE http://nyc.mypool.club/index.php
Yes ! Yes sir!
///Since (most probably) ProHashing re-enabled their mining pool towards our network, after updating their coin daemon to v1.3.0, it seems like we are suffering from network segmentation.
Probably due to the fact that when they started mining, their own coin daemon did not have connections to older nodes (v1.3 rejects nodes older than 1.2.0.x), they didnt broadcast to those older nodes.
Also miners on the older nodes didnt connect back to the 'new network' via an intermediate 1.2.0.x.
The issues, as far as we've seen, fix themselves in time, as nodes reconnect to other nodes all time. This means that they also sync up, doing a reorganize.
It seems the more 1.3 nodes that came into being and the fewer 1.2 nodes available the pre 1.2 nodes monopolize the connections to the remaining 1.2 nodes.///
Blocks are being investigated. http://nyc-block.mypool.club/
The miners are successfully mined.
Support NYC and make money by mining. Moreover, the complexity is now minimal.
But with the pool https://hobbyistpool.ddns.net/nyc/index.php the second day of the big problem.
Who has problems or is suspected - go to the official pool without FEE http://nyc.mypool.club/index.php
Yes ! Yes sir!
///Since (most probably) ProHashing re-enabled their mining pool towards our network, after updating their coin daemon to v1.3.0, it seems like we are suffering from network segmentation.
Probably due to the fact that when they started mining, their own coin daemon did not have connections to older nodes (v1.3 rejects nodes older than 1.2.0.x), they didnt broadcast to those older nodes.
Also miners on the older nodes didnt connect back to the 'new network' via an intermediate 1.2.0.x.
The issues, as far as we've seen, fix themselves in time, as nodes reconnect to other nodes all time. This means that they also sync up, doing a reorganize.
It seems the more 1.3 nodes that came into being and the fewer 1.2 nodes available the pre 1.2 nodes monopolize the connections to the remaining 1.2 nodes.///
Jump to: