I find it interesting and commendable that someone's starting their own blockchain project, going their own way in a sea of small scale forks and large scale, super business-y looking endeavours.
What makes me cautious is the bit about "open source later" for a blockchain project. The open source bit also doesn't show up on the roadmap, it's just mentioned here, in this thread, a bit like an afterthought. I'm giving you credit for providing a Linux client nonetheless, however. For closed source projects that's not always a given, unfortunately.

The closed source nature of the client also makes me extra cautious security wise, despite virustotal.

Darn! If just ChainCoin had crashed a little more, even I'd have been able to afford a masternode.

There are a lot of people installing Sentinel right now, which is likely disrupting the masternode side of the network to a noticeable degree. I expect these disturbances to die down within the coming one or two weeks, with most of it likely settling within the next few days.
On explorerz.top, at the time of this writing, I can see that there are 556 masternodes overall and 108 of them online. Be aware that the ones that aren't counted as online are either flagged as "EXPIRED" (only two), "NEW_START_REQUIRED" or "WATCHDOG_EXPIRED" (fixed by installing Sentinel). A good bunch of them is very likely running and "online" from a software perspective.

There are two things I'd definitely consider basic features of a coin claiming to be centered around the idea of decentralization:

• An algorithm that provides access to mining with everyday hardware, such as yescrypt. The reasoning is pretty clear: The more exclusive access is, the more mining will be centered around those with dedicated mining setups. Bitcoin and its corporate decision process clearly demonstrates where that leads: Anywhere, just not decentralization. With CPU-oriented algorithms, even when people with dedicated CPU-mining rigs enter the fray, there will still be a good number of people mining on their CPUs, as the accessibility for mining reaches further into casual micro-mining territory, providing at least a little bit more of a counterweight. Also, CPU power scales much less than GPU power as a function of time these years (CPUs age better), which is one of the factors that make CPU algorithms such worthy candidates in terms of casual miner enfranchisement.
• First class support for a free software environment, such as GNU/Linux or GNU/FreeBSD. In other words: At least have a Linux client from day 1. Releasing for corporate controlled platforms only, such as Mac OS X or Windows, is a statement against decentralization and flies into the face of the idea of people having control over our infrastructure and their own computers. Choosing an algorithm that doesn't depend on closed source drivers such as those from Nvidia or AMD for efficient mining would also be a plus in that regard (e.g. a CPU algorithm).

Edit: It seems yescrypt might not be as CPU-centered as it once seemed to me (a look at how Myriad coin is doing it might be worth it, though. I've mined XMY with just one CPU core, and I did get a handful of coins, so it does work). The basic point stands, though: A CPU-centered algorithm would be best for the goals of this project.

Yeah, because that would cause inflation.

Ubuntu 16.04 Wallet:

• Download location: https://drive.google.com/uc?id=0B6vvo7tvqVsYVTdYSmVSNHFreXc
• Compiled on: August 22 2017, 14:15 (UTC)
• Compiled for: Ubuntu 16.04 (will need this ppa for the db4.8 package)
• sha256 checksums & virustotal results:
  • c07f6166ee22ddd1746503152b40b08fff170fc6d7f63051430277b12894858b: bin/vivo-tx
  • c888e002dd6ae9d7f9ca01111e3bcad17e96d8ebf3e455164e2738f04232c375: bin/vivod
  • ec78afc1252f7ede2f7cb5aa7e3c1b04d8e2cc5a638dbf04839d21f552394619: bin/test_vivo
  • 8807a18c8f5b8ed1cfeb71ca833e0aa0a157f8b57e4f912fde14b6bb734e11eb: bin/vivo-qt
  • 615b0e1298816526a497a1b52f1b2d8dd8330bca8d49e4088fb8d8c544476fcc: bin/test_vivo-qt
  • 0741b1bb2e35b2706c04f8eaf52ec7b2574688738a2a0242679415fc9e1ab40a: bin/vivo-cli
  • 9fb03e64ac666604f9d10f60b18d94142255a0b519c945461b82dd525e6814c0: bin/bench_vivo
  • 7b1403160143699e3740ec01b6cdde1c78d78f737f094b738b38ad204821e33c: include/bitcoinconsensus.h
  • 538a09c9b3c4aa64819d6db11fa2b6504e01dec7a905565d92d4cb89fa9a98ef: lib/libbitcoinconsensus.a
  • cf1a3a4ede47547c87f503491a95007c49c1719095f89aefb6a1be430b5296b5: lib/libbitcoinconsensus.la
  • f10c35ce41224a232ed6f472953115f3ede4c9bd2367b3f1cb219f3f479fc24b: lib/pkgconfig/libbitcoinconsensus.pc
  • 5e2e4457f660a80667dc84d63664b0f183813e23a6ab36536be9ac852d7f71f0: lib/libbitcoinconsensus.so.0.0.0

You can get the checksums for the downloaded files, once you've extracted the archive, by running the following command while being inside the folder that was created upon extraction:

I tried transferring 0.1 DAS to Cryptopia's DA$. The wallet address already looks different than any DAS address I've encountered so far (it doesn't start with a D, but like this: 0x666e8...). It didn't even work: The command line client simply told me this:

The source code link (http://coinqwest.com/cqs/coinqwest-source.tar.gz) isn't working anymore and should be updated.

Thanks, but that's a Windows build.
I should perhaps have been a bit more clear: I am trying to get a mining operation set up on Linux, with Nvidia graphics cards, but the mining software linked in the OP post doesn't seem to compile (make immediately fails in reference to a file full of Windows paths), and even if it did compile, there's no reference whatsoever to anything Nvidia related, making me wonder whether it would even work with Nvidia cards in the first place.

As a complete outsider, I have to say that this discussion doesn't look very good, and the entire thread looks poisoned from the outset. First, it was opened by someone not officially tied to the project in question, someone who's actually at odds with it. Second, the tone of the overall discussion is very off-putting. There is talk of "dirty hippies", "faggots" or talk of "cultural appropriation" in the same statement as "it must be in your genes" by someone having made other bigoted statements in this discussion as well. Whatever the semantic breakdown of these tidbits may be, the visual is less than impressive and doesn't bear well on those who've made them or whatever they would like to represent or uphold here.