[ANN][NYC] NEW YORK COIN at 2017 MACY'S THANKSGIVING DAY PARADE IN NYC!

[NewYorkCoinMiner]

Main NYC Core Developer is MrSlosh (you can PM here). You can also join Discord channel to speak with full development team: https://discordapp.com/invite/qRtkD8q

[1715300550]

1715300550

[1715300550]

1715300550

[1715300550]

1715300550

[1715300550]

1715300550

[1715300550]

1715300550

[NewYorkCoinMiner]

[NewYorkCoinMiner]

Share!

[Jason9908]

Buy NYC is to buy the future.

love NYC forever

[Jason9908]

ignore   nycscam 

[JORKpr]

 
ignore   nycscam 

[NewYorkCoinMiner]

report nycscam to moderator. spam

[nycscam]

report nycscam to moderator. spam

Spam? LOL. You have spammed this thread with utter shite and LIES.

FACT: The wallets uploaded to Github contained malware. It is discussed in this thread.  Even you have commented.

I am warning people that NYC devs are not to be trusted because ... erm .. at least one of them put trojans/backdoors into the new wallets and put them on Github.

This is a big red warning signal!

[NewYorkCoinMiner]

nycscam, NewYorkCoin is an open-source, decentralized project that attracted worldwide developer interest in Jan'18. Too many developers were allowed access to this open source project through the github repository. NYC experienced a growing pain. Nothing was ever hacked from any NYC core wallets. Please remove that incorrect statement. Nothing was ever hacked from Coinomi NYC wallets. Nothing was ever affected except the exchanges from relatively minor double-spending (Trade Satoshi, Crex24 and possibly Yobit were apparently affected). Everything published on github can be (and should be) virus checked by users. The NYC github repository was being accessed by a large number of developers and it appears one of them either swapped 1.3.1.17 wallets -or- had their password compromised which enabled swap. Again, NO NYC WERE EVER HACKED. NOBODY EVER HAS LOST NYC FROM CORE WALLETS. NYC HAS NEVER BEEN HACKED/LOST COINS. Exchanges were the only entities/wallets affected by apparent 51% attack in October. Since the 1.3.1.17 wallet swapping incident, tightened security measures have been put in place, access to github has been restricted to 3 core developers and additional measures have been implemented behind the scenes to ensure this never happens again.

NYC is growing its network hashrate (+/- 500 Ghs currently) https://www.nycnodes.com/network.html, increasing merchant acceptance worldwide (most recently expanding NYC's footprint into Thailand), trading on a new and growing exchange - BiteBTC in Singapore, and rapidly expanding its Community and overall awareness in the crypto world. NYC has a proven blockchain since 2014, offers free worldwide money transfer, is fast enough for retail-level use and has active development. New -fastsync update (v1.3.1.20) is available here https://github.com/NewYorkCoin-NYC/nycoin/releases/

MEET NYC
retail use crypto
https://newyorkcoin.net

[CaVO32]

WARNING

AppData\Local\Temp\nsa694.tmp\res\newyorkcoin-qt-64.exe

detected by Malwarebytes as Backdoor.bot

https://www.virustotal.com/#/file/b9fc07c689688c7f6e16123573e2e727fde4f9aef02d40cda56a846bee7fb9d5/detection

What in the flying fuck!!?

URGENT: HACKS!!!

THIS IS FROM THE WALLET UPLOADED TO GITHUB BY NYC DEVS A FEW WEEKS AGO. SINCE THEY WERE CAUGHT OUT; THEY REMOVED THE INFECTED WALLETS.

BUT THE RESULTS ARE HERE ON VIRUSTOTAL: NYC FAILED MISERABLY. IT IS SO CLEAR:

https://www.virustotal.com/#/file/b9fc07c689688c7f6e16123573e2e727fde4f9aef02d40cda56a846bee7fb9d5/detection

THE NYC WALLET CONTAINED MALWARE!!

DO NOT DOWNLOAD OR USE ANY WALLETS FROM THE NYC DEVS.

i can say this is really alarming. i've never seen such file like this reddish. 46 out of 67 is too much of a warning to those who will install this file.



maybe the nyc team needs to be very careful next time they publish their things. even if they have hidden intentions 

[NewYorkCoinMiner]

Coinomi mobile wallet is available also. #1 rated altcoin mobile wallet for past few years.

https://www.coinomi.com/en/



https://newyorkcoin.net



NYC Now Accepted At 100 Businesses Worldwide!

[JORKpr]

 
How did you get it.///CaVO32///
Keyword - Key - Quote from: cgt99 on October 30, 2018, 06:58:10 PM. Today ... .

Here you are not too lazy to carry a blizzard and just download a normal wallet 1.3.1.20 https://github.com/NewYorkCoin-NYC/nycoin/releases/
It would be better to do the work and promote the coin. No words - there were expressions.

[ICee712]

WARNING

AppData\Local\Temp\nsa694.tmp\res\newyorkcoin-qt-64.exe

detected by Malwarebytes as Backdoor.bot

https://www.virustotal.com/#/file/b9fc07c689688c7f6e16123573e2e727fde4f9aef02d40cda56a846bee7fb9d5/detection

What in the flying fuck!!?

URGENT: HACKS!!!

THIS IS FROM THE WALLET UPLOADED TO GITHUB BY NYC DEVS A FEW WEEKS AGO. SINCE THEY WERE CAUGHT OUT; THEY REMOVED THE INFECTED WALLETS.

BUT THE RESULTS ARE HERE ON VIRUSTOTAL: NYC FAILED MISERABLY. IT IS SO CLEAR:

https://www.virustotal.com/#/file/b9fc07c689688c7f6e16123573e2e727fde4f9aef02d40cda56a846bee7fb9d5/detection

THE NYC WALLET CONTAINED MALWARE!!

DO NOT DOWNLOAD OR USE ANY WALLETS FROM THE NYC DEVS.

i can say this is really alarming. i've never seen such file like this reddish. 46 out of 67 is too much of a warning to those who will install this file.

https://i.imgur.com/oobRh1Y.png

maybe the nyc team needs to be very careful next time they publish their things. even if they have hidden intentions 

WTF??

I have never seen a set of results as bad as these.

NYC is known as a scamcoin anyway,  I guess this shows exactly what the NYC team's game is.

NYC Scam Alert

[reecelander]

How can you fail so many tests?

https://cdn.pbrd.co/images/HPBnzC2.png

and you've added this to the code, main.cpp (2699)

see https://github.com/NewYorkCoin-NYC/nycoin/commit/0bb4504566f2e0bd2026bc8ac35046b8d0000aff

   

Code:

// Shortcut checks for almost all early blocks
    if(chainActive.Height() < SKIP_VALIDATION_HEIGHT)
    {
        const CChainParams& chainParams = Params();
        // hit all the checkpoints but skip most of the rest
        std::map<int, uint256>::iterator cpItr = chainParams.checkpoints().MapCheckpoints.find(block.GetHeight());
        // if the current block is not found in the checkpoints list, skip it
        if(cpItr == chainParams.checkpoints().MapCheckpoints.end())
        {
            return true;
        }
    }

This tells the wallet to skip blocks if they are not found in checkpoints!!

?

You had the 51% attack, so has that fucked the whole chain? how can we trust this shit?

[NewYorkCoinMiner]

[MrSlosh]

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

Code:

 // Shortcut checks for almost all early blocks
    if(chainActive.Height() < SKIP_VALIDATION_HEIGHT && GetBoolArg("-fastsync", false))
    {
        const CChainParams& chainParams = Params();
        // hit all the checkpoints but skip most of the rest
        std::map<int, uint256>::const_iterator cpItr = chainParams.Checkpoints().mapCheckpoints.find(chainActive.Height());

        // if the current block is not found in the checkpoints list, skip it
        if(cpItr == chainParams.Checkpoints().mapCheckpoints.end())
        {
            return true;
        }
    }

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

[Hobbyist]

MrSlosh is correct guys.  The recent events are unfortunate.  The way I see it, we were hit with two attacks on NYC. 

#1  The 51% - Someone timed this right, pre-fork.  The fork was intended to update the code to minimize the effects of such and attack.
#2  The replacement of the GitHub releases.  I'd have to go back to find it now but NYC was not the only repo on GitHub to suffer from this attack. Other Repos were also replaced with malicious binaries.

Both these seem to hit around the same time but I don't think it was the same attacker. Again, just my opinion.

We have hardened the GitHub repo as best we can and we are post-fork so the updated code can help with the 51% problem.

Standard Internet advise,  Check any downloaded binary before execution... Think "Trust No One" here.  Verify the source, checksums, Anti-virus scan, exc.

The team has been working to get more mining pools to merge mine NYC to help raise the nethash rate and make 51% attacks more difficult. 

[Hawk01]

Guys, are there still any chances left that Yobit will open the NYC wallets?

[khalidiasiri]

Guys, are there still any chances left that Yobit will open the NYC wallets?

I think Yes. Look at this...

https://pasteboard.co/HPJeNvn.jpg

[nycscam]

you hear me,faggot who pishit nickname nycscam,I know where you are and who you fuck,you're a girl.you shaved with nyc for big bucks,you, you goof, fate will not help,and the four write shit that nobody reads,you even fuck who do not need obosanny fag.

what?