ZelFlux and what it is?

The Zel team have with this one set a new standard that is, if all the issues with it are sorted, going to revolutionize large chunks of the cloudscape.

ZelFlux can be understood in two fairly general ways, one being as a distributed computing network, the other being as a distributed operating system like Windows or Linux but running across multiple computers/servers.

But there is nothing special about operating systems, I customize my own all the time!

In 99.9% of the cases, I am aware of, operating systems are confined to the same machine or cluster if we want to get picky. Where Flux differs drastically from this is in that the components are not all physically linked and may not even be on the same continent. What this means is scope and scale beyond what most people can get their heads around.

The table above should help give you some perspective on it based on roughly month old Flux data.

What does this mean for me as a Zel holder and Node operator?

It means that you are helping to develop a product unlike anything seen before outside a few very esoteric systems. True cutting edge technology that once fully developed is going to change the way things are done in a lot of ways that will also impact well outside the crypto space.

It is a law of nature we overlook, that intellectual versatility is the compensation for change, danger, and trouble.

H. G. Wells

What is it you can do with Flux?

The short answer is: “Anything you want!”

Right now, parts of ZelFlux are running CPU based Folding at home docker images that are helping tackle COVID-19.

Data from this will not merely go towards helping to get things back to some form of normal, it will also be used to help develop the load balancing mechanisms that have to work across the whole “Flux.” So it is not just a marketing stunt used to conveniently cash in on public sentiment but a “twofer” as one of the obvious alternatives would have been some form of mining which might easily ruffle feathers in multiple places.

This phase of development is about consistent stable CPU loads across a distributed network and the steps and adjustments needed to get there.

Why is Flux so versatile?

It comes back to the way it’s set up. Rather than having everything working as one giant machine, ZelFlux is built as a host for a myriad of smaller independent applications each using its own little chunk of the overall Flux.

Applications work inside their own mini-environment called “docker” meaning that anything you can use squeeze into a docker container will work on ZelFlux.

Currently, docker containers are being limited to single port access only. However, that is likely to change once ZelFlux matures in terms of development and load balancing.

But IPFS is awesome!

Yes, it is! Despite that, it’s mainly a solution for storage and web hosting without the built-in versatility of being able to run multiple applications. You cannot, for example, run an Electrum server on IPFS or use it to run game components.

Endless use cases:

Anything you can do with a server, you will eventually be able to do on ZelFlux.

1. Secure file storage.
2. Distributed applications- DAPPS.
3. Hosting back up Electrum/ElectrumX servers for wallet services.
4. High redundancy encrypted backup services to sensitive data.
5. Complex private VPN solutions.

That is just a brief list of possible applications for ZelFlux and its distributed network. The list goes on and the above five examples are by no means an exhaustive list of all the possibilities inherent to the ZelFlux network.

The above five examples are what could be developed and deployed right now on the ZelFlux network.

So when can we expect to see more active usage of Flux?

Once load balancing matures a bit more, I can imagine several of the above use cases coming to life within a few weeks. ZelFlux is now past the proof-of-concept stage and is quickly moving towards some form of “beta” which could easily incorporate most if not all of the potential use-cases listed above.

Is there an eta on that yet?

No, this is breaking completely new ground in many ways, which means the bottleneck is manpower. There just aren’t enough hours in the day or people working on Zel, to give a responsible answer to that yet, particularly given how fluid a situation it is with open source development.

The improvements needed to kick off the next phase could already be out there with someone feeling a bit bashful about pushing their code on GitHub or it could be that “The Trunk” is the only person with the vision to really get this going and he will have to deliver the beta before someone else hops onboard.

I think I’m unique to the game ’cause of my versatility.

Ice Cube

So, how does Flux stack up against LBRY/TUBE/ETHER1? They have distributed stuff too?

The very short answer to that is it doesn’t. You need to have sufficiently similar products or concepts to stack them up in comparison.

LBRY and TUBE have decentralized storage with decent video hosting platforms. Their formats of delivery differ significantly but not in overall function. This is not something ZelFlux was custom made to take on. However, ZelFlux easily outperforms them in areas like application deployment and computational functions.

Comparing apples to apples gets difficult if you are growing one of the very first trees.

ETHER1 combines Ethereum based smart contracts with IPFS hosting on its service/master/gateway nodes somewhat similar in style to the ZelNodes ZelFlux runs on. It is in that sense the closest of the three I lined up for comparison.

In terms of versatility it comes fairly close as ETH DAPPS can do a fair number of things but as of yet, they do not support full-blown application deployment. So the adage earlier still holds true.

It’s damn hard to compare apples to apples when you have one of the first trees.

Bigpiggy01

How does all this impact me as a holder of Zel or a ZelNode operator?

This is an incredibly complex yet at the same time simple question to address in several ways:

1. You can see a use-case for the node you run that ties into the rest of the Zel ecosystem.
2. The project you have put effort into is delivering on something unique that sets them apart from not just the rest of the space but most mainstream cloud solutions.
3. You can see that you are getting what you “signed up” for.
4. No one is shilling a “product” this is a shot at building something new and unique.
5. There are uncertainties but they go both ways.

Another way of putting it is you can see the value you are helping to create through your involvement with the project.

So should I run out and buy up all the Zel now?

No, as I have written previously when writing for Zel, what you should do is join the community on Discord and while there verify for yourself that the information provided both by myself here and the Zel Team overall match up to reality.

Once you are done with that vital step of doing your due diligence, you can have a look at what you can afford to lose and then consider if you want to invest or not.

“Arguing that you don’t care about the right to privacy because you have nothing to hide is no different than saying you don’t care about free speech because you have nothing to say.”
― Edward Snowden

What should I be concerned about as a node operator or Zel holder?

All change inevitably causes a certain amount of fear, meaning that there is the potential for current cloud providers or even certain governments feeling threatened by what they do not fully understand and pursuing varying forms of legal action.

What you can do, is be active, be a reasonable voice for financial and internet privacy. Particularly with how the current tone is becoming increasingly shrill on both sides of that debate, be reasonable, be polite but firm in resisting censorship.

Setting an example is how you lead change! Given how obviously more and more agenda-driven narratives are falling to pieces at the moment, being the calm consistent yet unwavering voice of sanity will bring positive responses.

On behalf of the Zel Team,

Bigpiggy01