you can always use explorer.nycoin.info if the .community explorer is down

What crap do you want one of us to weigh in on?

Alright since there are a couple of you that would rather FUD than do anything constructive, let me try to address some of what you are talking about.

First, the image from Virustotal.com. If you look closely you will see those are results from a file named 98798rerge.exe. This file is not associated with NYCoin and none of the github downloads that are currently published include this executable. I don't know where it comes from nor why you are posting it here.

Concerning the block validation code, reecelander referenced a commit that was old. The actual code that is in the master repo can be found here https://github.com/NewYorkCoin-NYC/nycoin/blob/master/src/main.cpp#L2699-L2713

What this code does is optional, hence the GetBoolArg(). This is part of the fast-sync functionality which allows a user to download the blockchain at a much faster rate from scratch. It does this in part by bypassing the validation checks for every single block that comes in while syncing. Now you may think that this is cause for alarm but if you remember your blockchain basics you will know that if you change anything in one block, you change the entire blockchain. You can find a refresher article here https://medium.com/coinmonks/blockchain-for-beginners-what-is-blockchain-519db8c6677a, specifically pay attention to the Chaining the Blocks section. So checking against the checkpoints prevents someone from replacing large chunks of the code and if you dig into our code a bit further, you will see we stop the fast sync before the last checkpoint which means even if someone were to replace all the blocks in the fast sync phase, it would fail as soon as it came out. The code changes, which are again optional, do not present a significant additional threat to the blockchain though they are on the surface, a bit less secure. Ideally, you want to check every single block to be sure you have everything proper but we understand some people don't want to wait and for someone to maliciously change the entire blockchain, they would also have to get a majority of the nodes to go along with what they were doing.

Regarding the infected releases, we are not the only crypto community to be affected by github hacks. One of the people who had access to the github had their account compromised without our knowledge and since github doesn't have the same sort of security or restrictions on releases, they were able to replace our releases with executables that were modified using a fairly basic RAT injection program. When another user pointed this out, we immediately pulled the builds from github and published new, clean builds as quickly as possible. Any claim that the NYCoin devs had anything to do with the recent 51% attack or the malware infection is patently false and those that continue to push that narrative are likely part of the same group of people that launched the attacks in the first place.

If you actually want to discuss code changes and development with the NYCoin dev team, please join us on Discord as we don't frequent this forum and only here about this kind of FUD second hand. https://discord.gg/zTKMrmQ

We welcome constructive discussion of the coin and its use case and we kindly ask that those who try to discredit the team or the project to please find something better to do with your time like having a civil conversation with the development team. Again, the dev team does not frequent this forum so if you want to discuss the actual code, come see us on discord.

Thanks,

MrSlosh

Hey gang,

We're working out some issues on our end that are related to the previous attack we had on the network. We removed the builds from github because they had been replaced with infected versions by an unknown third party.  Once we get github 100% secured we will get new wallet builds out.

As far as the exchanges go, they will open up once they feel safe to do so. Yobit has stated in their troll box that they are not going to update, that comes from DominekHerzog himself.

Tradesatoshi will make an announcement when they have all the information possible (we've done everything we can on our end). If they exchanges are short on NYC they are not going to open up until they have the coin to cover any losses. When we hear something we will let everyone know.

Slosh

Yes. I did not mean to imply that this was part of the same attack, just that this sort of thing has been going around and we're not unique (clearly).

Looks like we may have been swept up in this

https://www.trendmicro.com/vinfo/ph/security/news/cybercrime-and-digital-threats/github-hacked-spreads-malicious-syscoin-windows-installers

Sounds exactly like what we were experiencing. 

Needless to say, we've enabled 2fa for all org members and have reset our passwords.

New builds will be available soon.

in the binaries I pulled it showed a date modified of 10-28, which is well beyond when it was built. Also double checked the checksums of what was up versus what I built and published, no match. pulling github history now.

The original archives I published are still showing up as clean from my drive so this is a recent development. The 10-18 date above was me misreading the date you gave me.

bloody hell... pulling the binaries for now. nice catch. If it was modified on 10-18 then that coincides with our recent attacks. will put up fresh builds as soon as possible.

Considering none of our recent builds have a -64 after the filename, I don't know. I'm already looking into our github repo, I will check out those files too.

Oof... is that a recent download? I'm checking our github files currently

The first request I sent them was on August 4th. They have received more than one request from the dev team and have not responded to any of them. Any response you get from them at this point is just lip service.

All exchanges (as far as I know) are updated with the exception of Yobit. They have more or less said they are not going to update.

The other exchanges are assessing damage from the recent attack and will open back up when they feel it is safe to do so. This is not rhetoric or speculation, we were attacked and serious damage has occurred. We are in a recovery stage now and once the dust settles we will see where we stand and what kind of damage was done.

We are officially on a more secure codebase now, but the attack occurred before the security measures were in place so the exchanges are understandably cautious.

Slosh

At this time, the team had requested that exchanges lock down their wallets due to a pre-fork attack on our network. The only exchange we have not heard back from regarding updates is Yobit. As far as we know, all other exchanges have updated to the new chain.

We are working with the exchanges to get them back online and mitigate any issues that were caused during the pre-fork shenanigans. I am hoping we can get everyone back online and up to speed very soon so we can continue to grow. I appreciate everyones patience in this matter.

MrSlosh

Hey NYC family,

We have officially passed the fork block. Everything seems to be running smoothly currently with the exception of the Coinomi daemon crashing. We are getting it sorted with them now and they should be back up and running without too much delay.

Thank you all for your support! We look forward to a brighter, more secure future for NYCoin. If anyone encounters any issues (other than what has been addressed recently) please reach out to a team member and we will get things sorted as soon as we are able.


Slosh

Hey NYC family,

We have officially passed the fork block. Everything seems to be running smoothly currently with the exception of the Coinomi daemon crashing. We are getting it sorted with them now and they should be back up and running without too much delay.

Thank you all for your support! We look forward to a brighter, more secure future for NYCoin. If anyone encounters any issues (other than what has been addressed recently) please reach out to a team member and we will get things sorted as soon as we are able.


Slosh

Hello NYCoin community! I hate to copy and paste announcements but this one is long and important and was just posted to discord.


In the past day or so a LOT of NYCoin has hit the exchanges at stupid low prices. This has spurred quite a bit of excitement and as a result, volume on exchanges has shot up dramatically. At the same time, an unknown actor has hit our network with a comparatively large amount of hash rate constituting more than 75-80% of our overall network rate. With that increased hash, blocks from known, verified mining pools have become orphaned leaving a lot of transactions in a conflicted or unknown state. This seems to be especially on transactions that are moving a large amount of nycoin off exchanges into personal wallets.
At this time, the dev team believes this is a coordinate attack on our network in an attempt to double spend coins or generally wreak havoc on our network as a whole. We do not know who the miner is nor what their actual intention may be but the recent events have raised quite a bit of suspicion that this is not coincidental.
It is recommended, until further notice, to refrain from depositing or withdrawing from exchanges, or sending large quantities of coin in a single transaciont until we can regain control of the situation.

If you want to assist in stabilizing the network and preventing such an attack from continuing to occur, we need to muster all hash power possible to the mining pools. If you have a mining device that can handle scrypt, point it at a NYC mining pool such as Hobbyistspool, nyc.mypool, Miningdutch,or Mastermining. If you can rent hashpower, even just a few GHs for a week or more, please point that hash power at a valid mining pool. If you can rent a small amount for a day, do it.
This type of attack is specifically what the upcoming fork is meant to help prevent.

We have noticed in the past day that the hashrate spikes have been coinciding exactly with large amounts of NYCoin dropping on exchanges for ultra cheap prices. This has raised some serious red flags and we are starting to get more reports of large quantity transactions not making it to their destinations. We are working with Tradesatoshi on current tickets regarding such transactions.


Once we have more information we will let everyone know, until then, be safe out there. You can monitor hashrate fluctuations from our stats page here https://stats.nycoin.info/d/000000001/nycoin-mainnet?refresh=30s&orgId=1. I would advise against depositing or withdrawing from any exchange when there is a sudden, unusual surge in hashrate.

Since I am not on here as frequently, you can find me in the discord server here https://discord.gg/RDan5rT or send me a private message.

If you have a large amount of coins at Trade Satoshi (where the recent volume madness has occurred), they are fork ready. Crex24 recently updated as well but the volume hasn't hit there yet.

We will get through this together. Be careful out there!
Mr Slosh

Hello NYCoin community! I hate to copy and paste announcements but this one is long and important and was just posted to discord.


In the past day or so a LOT of NYCoin has hit the exchanges at stupid low prices. This has spurred quite a bit of excitement and as a result, volume on exchanges has shot up dramatically. At the same time, an unknown actor has hit our network with a comparatively large amount of hash rate constituting more than 75-80% of our overall network rate. With that increased hash, blocks from known, verified mining pools have become orphaned leaving a lot of transactions in a conflicted or unknown state. This seems to be especially on transactions that are moving a large amount of nycoin off exchanges into personal wallets.
At this time, the dev team believes this is a coordinate attack on our network in an attempt to double spend coins or generally wreak havoc on our network as a whole. We do not know who the miner is nor what their actual intention may be but the recent events have raised quite a bit of suspicion that this is not coincidental.
It is recommended, until further notice, to refrain from depositing or withdrawing from exchanges, or sending large quantities of coin in a single transaciont until we can regain control of the situation.

If you want to assist in stabilizing the network and preventing such an attack from continuing to occur, we need to muster all hash power possible to the mining pools. If you have a mining device that can handle scrypt, point it at a NYC mining pool such as Hobbyistspool, nyc.mypool, Miningdutch,or Mastermining. If you can rent hashpower, even just a few GHs for a week or more, please point that hash power at a valid mining pool. If you can rent a small amount for a day, do it.
This type of attack is specifically what the upcoming fork is meant to help prevent.

We have noticed in the past day that the hashrate spikes have been coinciding exactly with large amounts of NYCoin dropping on exchanges for ultra cheap prices. This has raised some serious red flags and we are starting to get more reports of large quantity transactions not making it to their destinations. We are working with Tradesatoshi on current tickets regarding such transactions.


Once we have more information we will let everyone know, until then, be safe out there. You can monitor hashrate fluctuations from our stats page here https://stats.nycoin.info/d/000000001/nycoin-mainnet?refresh=30s&orgId=1. I would advise against depositing or withdrawing from any exchange when there is a sudden, unusual surge in hashrate.

Since I am not on here as frequently, you can find me in the discord server here https://discord.gg/RDan5rT or send me a private message.

If you have a large amount of coins at Trade Satoshi (where the recent volume madness has occurred), they are fork ready. Crex24 recently updated as well but the volume hasn't hit there yet.

We will get through this together. Be careful out there!
Mr Slosh

For everyone using the 1.3 wallet, please download and install the mandatory update located here https://github.com/NewYorkCoin-NYC/nycoin/releases/

We are still testing the block generation to be 100% sure that all issues are resolved before we sound the all clear for miners so if you are mining solo or have your own pool refrain from using 1.3 until we finish testing.

Thanks,

Slosh

For everyone using the 1.3 wallet, there is a new release out that is mandatory. https://github.com/NewYorkCoin-NYC/nycoin/releases/

We are continuing to test the block generation of 1.3 (initial tests went well) so if you are actively mining please use the wallet versions 1.2 or below for now. Once we are sure all block gen issues are fixed we will sound the all clear for miners as well.

Again, if you are using the 1.3 wallet, be sure to download version 1.3.1.17.


Thanks,

Slosh

Disagree. We have almost 2 months before the scheduled fork height. Plenty of time to get things sorted.

Also can you please remove your posts about the fork being cancelled. You did not discuss that with the dev team at all and it's likely causing some FUD.