(deb/systemd only, sorry loki-launcher folks)

Launcher already watches the storage server for lock ups

the storage server manages acces to the local copy of the blockchain, right?

Monitors the web server

Anyone notice the bot is reporting a lot of late uptimes of late? I have been getting a few however they appear false positives

Pricer
https://www.reddit.com/r/privacy/comments/f9utbt/thoughts_about_loki/

It seems his personal mission to slander the project in any way possible. I'm not sure why tbh. His arguments are odd

any comments on this

"A lot of projects that build anonymous overlay networks on top of the internet, such as Loki, are well-intentioned but claim to be mixnets when they are not because they do not “mix” packets in any meaningful way that prevents attacks."

https://medium.com/nymtech/how-nym-improves-on-traditional-mixnet-designs-219cd36724a0
Lungdoge
It seems his personal mission to slander the project in any way possible. I'm not sure why tbh. His arguments are odd

Who knows.. He may be involved in another established privacy project like Tor or something else and sees Loki as a threat. He seems to be trying awefully hard to attack the credibility of the project

While the claim about Loki currently is true, there are things that are not

Lungdoge
It seems his personal mission to slander the project in any way possible. I'm not sure why tbh. His arguments are odd

He's broken record playing a sad tune. Just repeats the same garbage and same posts without attempting to obtain any substantiation for what he's repeating. Troll sadly inflicted with Tourette's.

rtide
any comments on this

It is true, loki does not currently mix packets afaik.

dwarner5522
Who knows.. He may be involved in another established privacy project like Tor or something else and sees Loki as a threat. He seems to be trying awefully hard to attack the credibility of the project

He’s with a competitor that wants to charge for mixnet access (and I think they’re the ones that don’t even use a privacy blockchain, so your payment exposes you)

they are right, we used the term mixnet incorrectly, we havent been using that term for 6 months now though

I love the attention, the fact trolls are out is even better.

TechnicalTumbleweed
MixMode is the term being used?

It’s the current term we use for session: “MixMode is a future project attempting to build a traffic analysis resistant layer for Session which operates on top of the existing low latency onion routing infrastructure. In order to achieve this, MixMode will build upon ideas drawn from two existing systems: Bitmessage and mix networks.” From 6.6.1 in the session whitepaper

My understanding is mixnet comes with some performance degradation. MixMode used to obfuscate packet size will be optional and will operate in conjunction with Lokinet, not optional to obfuscate routing (caveat being this is a closed Session)? I assume similar UX performance degradation will be present to mixnets with MixMode? I don't see Lokinet posing a perceptible performance issue for message traffic given the latency it has demonstrated but I can't appreciate what the MixMode and mixnet performance concerns are at the moment. Sorry if I've confused anyone... including myself here.

I'll let someone more knowledgable answer your questions but wanted to give some broadstrokes for any one that's interested in following along.

It's not pressing but useful when it comes to the nuances of the decision making process when using a specific protocol or feature comes into play. There's always give and take based on what benefit is provided for a given cost. If they start to lay down equations I may have to put the brakes on. 😉

They are much slower indeed. Also, in order for a mixnet to preserve privacy, there should be "constant" traffic

Yes I read about sizing (padding) and running fake traffic through. Not a fat free approach for sure.

I think the answer probably lies in optioning the level of privacy to meet the users requirements as opposed to forcing the highest level on everyone. Similar to open and closed sessions.

This could be a viable option in the future when both protocols are implemented. I suspect true mixnet traffic would be super low.

Lokinet also won't be solely handling Session traffic.

i have some problem on our service nodemy node is running and block synced 100% i check contain in different node is same responsebut it can't find in block explorer but balance still lock for stakedit was running smooth more than 60 days but right now i confuse what happen ?https://lokiblocks.com/service_node/f4dfa018e81e62cff290354d2e6208c5ad4dddeb142412b05a6c1e4769a4fb3e

current, i stoped and killall lokid for save state

looks like its deregistered https://www.lokisn.com/sn/f4dfa018e81e62cff290354d2e6208c5ad4dddeb142412b05a6c1e4769a4fb3e

ManZer
but balance still lock and node is fine

Yes after deregistration you enter a 30-day lock period with no rewards.

SERVICE NODES SUMMARY:Current Block: 478,020Num of Running Nodes: 1,040Versions: 6.1.4 (90.00%), 6.1.0 (5.87%), 6.1.1 (2.50%), 6.1.2 (1.06%), 6.1.3 (0.58%), Service Node Stake Requirement: 18,333.607 LOKIBlock Reward for Service Node: 14.301 LOKIAvg daily Reward: 9.901 LOKIHours between rewards: 34h 39mTotally Contributed: 20,650,742 LOKI% of Circ. Supply: 44.756%Open for contribution: 4 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 5 (http://www.lokisn.com/status/decomissioned)

SERVICE NODES SUMMARY:Current Block: 478,110Num of Running Nodes: 1,038Versions: 6.1.4 (89.98%), 6.1.0 (5.88%), 6.1.1 (2.50%), 6.1.2 (1.06%), 6.1.3 (0.58%), Service Node Stake Requirement: 18,332.003 LOKIBlock Reward for Service Node: 14.301 LOKIAvg daily Reward: 9.919 LOKIHours between rewards: 34h 36mTotally Contributed: 20,612,474 LOKI% of Circ. Supply: 44.671%Open for contribution: 4 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 5 (http://www.lokisn.com/status/decomissioned)

SERVICE NODES SUMMARY:Current Block: 478,306Num of Running Nodes: 1,039Versions: 6.1.4 (89.99%), 6.1.0 (5.87%), 6.1.1 (2.50%), 6.1.2 (1.06%), 6.1.3 (0.58%), Service Node Stake Requirement: 18,328.512 LOKIBlock Reward for Service Node: 14.3 LOKIAvg daily Reward: 9.909 LOKIHours between rewards: 34h 37mTotally Contributed: 20,631,917 LOKI% of Circ. Supply: 44.708%Open for contribution: 4 pools (http://www.lokisn.com/status/awaiting_contribution)Decomissioned nodes: 3 (http://www.lokisn.com/status/decomissioned)

EL LOCO

at that block height given, your funds will unlock and you should be able to immediate restake