Hey Y'all,

I need to thank both @nightraven and @MMOStars for coming forward and backing the story that Noso is, NOW, either a scam, or a bunch of people in panic mode trying to recoup a very bad investment of time. There was a time when this coin had a future

In my previous message on this thread I was probably a bit too technical, or just a bit too rambly...

Nonetheless, I think that @nightraven was a lot more eloquent and for that I thank him a lot!!

Cheers,
Gus

Hi there Y'all,

I was, many moons ago, part of the Noso team.
I was a developer and I did a bunch of cross language libs(Pascal, C#, Python and PHP) to access the TCP/IP Protocol and the raw data of the block files and I coded the first (Edit)explorer in CakePHP.
The wallet code and all the surrounding tool's code is so bad that I never touched any of it. I couldn't follow the immense qty of functions/procedures spread over a myriad of source files(No OOP at all). It was just a very hard spaghetti to follow.
I pushed really hard to try and get the only Dev to evolve on his not so good coding skills and to bring other programming languages under the Noso umbrella.
For that and for telling some harsh truths to power I was rewarded with a ban from the Discord server(I got really irate many months before that and had already left the GitHub Org).

And the truths are quite blaring in the face of a self named cryptocoin:

• Noso is centralised: Without the seed nodes, and when the seed nodes go bust, the whole network ceases to work
• Noso is not verifiable: Every transaction should have the public key present in order to validate the signature. For some obscure reason, when building the block, that key is replaced with the Sender's address
• Noso uses MD5 as the hashing algorithm: The fact that it's so easy to create collisions by simply changing one to three bytes on the block file is very scary
• Noso uses Pascal Short Strings: If you're a programmer and understand that between length and capacity, there is the space for memory garbage to be stored in the block files, this makes what was said above, about MD5 even more plausible
• Noso has a government: In order to participate on this government you must pay to acquire one or more GVT tokens. Paid democracy... Is that still democracy?
• Noso software executes orders from centralised person in power: The software has code paths that will restart your wallet after triggering an upgrade on itself. But if it can do this, what else could the only dev code in to do with your coins?
• Noso freezes assets: Some assets have been frozen because they are perceived to be mined via GPU. The responsibility of a mining algorithm to be GPU/ASIC resistant lays squarely on the shoulders of the dev/dev team. Blaming the miners for pushing the boundaries is like a very bad parent blaming it's own child for the mistakes he does!!

And these are the few things that I so hardly fought to make the only dev of this coin to realise he should correct. But alas, here we are and now, Noso is even listed... OMFG, how did this happen?!?!?

The bullet points above are the most blatant issues with this coin. I could go on forever about the fact that the code is complete spaghetti. That said spaghetti is now so entangled that even the only dev is now suffering the pain and has not released any new version in quite a while. And the 1 or 2 times he did attempt at testing new code changes present on the GitHub repo, the main net has always collapsed.

So, yeah, this is a cryptocoin that disrespects the ethos(still centralised) and even the math, the cryptology math(it is not verifiable).

You can try and gaslight everyone else with any rhetoric about this and that, but the buck stops at the code itself, and me, as an Object Pascal programmer of more than 15 years experience, I'll say that the code is rotten to the core.

But hey, continue trading this "wonderful" coin that is... How did you put it?

Yeah, let's go with that!!!

Cheers,
Gus

---

P.S.: Gus a.k.a Gustavo 'Gus' Carreno, everywhere else.