Aleksandar
Even bots spamming will only happen if theres users to spam to.

Haha yep.. coming of the bots means there's ppl they are after. Like you said that's a won race..

looking forward to public group set by ourselves

Yep, it will be a busy but interesting year if they can fix the bugs by spring and focus on features like this for summer

Lots to look forward to

Wallet integration, community channels, multiple ids, full PoS, LNS, ...

make snode to support you guys!

Oh, snode, never mind.

SERVICE NODES SUMMARY:Current Block: 465,115Num of Running Nodes: 1,007Versions: 6.1.4 (85.50%), 6.1.0 (7.15%), 6.1.1 (4.17%), 6.1.3 (1.99%), 6.1.2 (1.19%), Service Node Stake Requirement: 18,571.821 LOKIBlock Reward for Service Node: 14.345 LOKIAvg daily Reward: 10.257 LOKIHours between rewards: 33h 34mTotally Contributed: 20,273,001 LOKI% of Circ. Supply: 44.286%Open for contribution: 5 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 1 (http://www.lokisn.com/status/decomissioned)

SERVICE NODES SUMMARY:Current Block: 465,149Num of Running Nodes: 1,007Versions: 6.1.4 (85.50%), 6.1.0 (7.15%), 6.1.1 (4.17%), 6.1.3 (1.99%), 6.1.2 (1.19%), Service Node Stake Requirement: 18,571.172 LOKIBlock Reward for Service Node: 14.345 LOKIAvg daily Reward: 10.257 LOKIHours between rewards: 33h 34mTotally Contributed: 20,273,001 LOKI% of Circ. Supply: 44.285%Open for contribution: 6 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 1 (http://www.lokisn.com/status/decomissioned)

Can somebody explain me how I get operator fee == 10% for a node that it's staking requirement => "staking_requirement": 19236365167303, and "portions_for_operator": 1844674407370955264 ?

what kind of magic do I have to do to get 1844674407370955264 => 10%? :D

Any one have a preferred version of Linux to start to learn how to run a SN?

just go with Ubuntu LTS version

It seems like ubuntu is so much more straightforward..why do people use debs?

Ubuntu uses debs. Debian is a stable os as well, also uses debs

The Deb version is what I was suggesting, which can be installed on several oses

And cli wise on a vps you won't be able to tell the difference

If you go with Ubuntu use at least 18.04.

SERVICE NODES SUMMARY:Current Block: 465,428Num of Running Nodes: 1,013Versions: 6.1.4 (85.59%), 6.1.0 (7.11%), 6.1.1 (4.15%), 6.1.3 (1.97%), 6.1.2 (1.18%), Service Node Stake Requirement: 18,565.847 LOKIBlock Reward for Service Node: 14.344 LOKIAvg daily Reward: 10.195 LOKIHours between rewards: 33h 45mTotally Contributed: 20,384,494 LOKI% of Circ. Supply: 44.521%Open for contribution: 4 pools (http://www.lokisn.com/status/awaiting_contribution)No decomissioned nodes

SERVICE NODES SUMMARY:Current Block: 465,528Num of Running Nodes: 1,017Versions: 6.1.4 (85.64%), 6.1.0 (7.08%), 6.1.1 (4.13%), 6.1.3 (1.97%), 6.1.2 (1.18%), Service Node Stake Requirement: 18,563.94 LOKIBlock Reward for Service Node: 14.344 LOKIAvg daily Reward: 10.155 LOKIHours between rewards: 33h 53mTotally Contributed: 20,458,819 LOKI% of Circ. Supply: 44.681%Open for contribution: 3 pools (http://www.lokisn.com/status/awaiting_contribution)No decomissioned nodes

SERVICE NODES SUMMARY:Current Block: 465,683Num of Running Nodes: 1,016Versions: 6.1.4 (85.73%), 6.1.0 (7.09%), 6.1.1 (4.13%), 6.1.3 (1.87%), 6.1.2 (1.18%), Service Node Stake Requirement: 18,560.987 LOKIBlock Reward for Service Node: 14.343 LOKIAvg daily Reward: 10.165 LOKIHours between rewards: 33h 52mTotally Contributed: 20,439,312 LOKI% of Circ. Supply: 44.634%Open for contribution: 3 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 1 (http://www.lokisn.com/status/decomissioned)

SERVICE NODES SUMMARY:Current Block: 465,770Num of Running Nodes: 1,015Versions: 6.1.4 (85.71%), 6.1.0 (7.09%), 6.1.1 (4.14%), 6.1.3 (1.87%), 6.1.2 (1.18%), Service Node Stake Requirement: 18,559.33 LOKIBlock Reward for Service Node: 14.343 LOKIAvg daily Reward: 10.174 LOKIHours between rewards: 33h 50mTotally Contributed: 20,418,139 LOKI% of Circ. Supply: 44.586%Open for contribution: 3 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 2 (http://www.lokisn.com/status/decomissioned)

Just had a node go offline on 6.1.4, just restarted it but worth noting. No idea why..

I had one today too

Maybe storage sever segfault caused that

It's a good time to wait for 6.1.5 😊

Jason
logs?

-- Logs begin at Sat 2019-10-19 04:10:58 CEST. --Feb 10 21:10:59 LBox5 index.js[1041]: Lokinet pid got out of sync!Feb 10 21:11:29 LBox5 index.js[1041]: Lokinet pid got out of sync!Feb 10 21:11:59 LBox5 index.js[1041]: Lokinet pid got out of sync!Feb 10 21:12:29 LBox5 index.js[1041]: Lokinet pid got out of sync!Feb 10 21:12:40 LBox5 index.js[1041]: SOCKET: Client connected.Feb 10 21:12:44 LBox5 index.js[1041]: SOCKET: got sudo journalctl -u lokid.servi ce -afFeb 10 21:12:44 LBox5 index.js[1041]: SOCKET: Sending to lokid.Feb 10 21:12:44 LBox5 index.js[1041]: blockchainRAW: unknown command: sudo journ alctl -u lokid.service -afFeb 10 21:12:58 LBox5 index.js[1041]: SOCKET: Client disconnected.Feb 10 21:12:59 LBox5 index.js[1041]: Lokinet pid got out of sync!

Sounds like a loki launcher issue

Damn, okay @VectorZer0 Something to look into perhaps

Looks like I get many pings of failures with a success randomly, not sure if that is what is suppose to happen