Quote from: programmerdan on February 19, 2018, 04:11:59 AM

Quote from: happenZ on February 18, 2018, 09:55:33 PM

Average hashrate climbed to 220 h/s, mainly from Google Cloud Platform and Amazon Web Services. I hope you have 20 CPUs or ten 1080 TIs at home to compete with them. Yes, you read correctly, you can mine it with GPUs on linux too (https://bitbucket.org/guli13/arionum-gpu-miner), it's even more efficient than a CPU! Decentralization is zero at the moment and the network very weak, vulnerable to 51% attacks. Three to five addresses have 60-80% of nethash for weeks now.

Didn't see anyone else reply to this but it seems important to mention

This isn't BTC. Fees are fixed, common, known and non-variable (same rule against all transactions). Block size is variable based on past block's nearness to size cap. But, what decides transaction inclusion? Miners? Nope. Nodes. So, the health of the network -- its vulnerability, so to speak, is controlled by the distributed nodes, not the miners. 50-60-70% "mining" ownership doesn't confer any special power to determine block direction. If they run a solo mining gig and attempt to alter transaction / mempool, all the other nodes will reject them. It'd be good to do a more rigorous analysis on the vulnerabilities, risks, and benefits of this approach vs. the BTC approach, but the traditional mining-based 51% rule quite literally does not apply here.

Hope that helps a bit.

So if I understood correctly, you just said a few nodes can stage a 51% attack with a lot less bad apples in the team than it typically is needed from potentially thousands if miners (aka a couple of pool owners). Correct?