The ThreeFold community consists of many different roles creating a whole ecosystem that contributes to the growth of the ThreeFold Grid and makes it more reliable and stable. Today, we’re spotlighting the farming community, the backbone of the ThreeFold Grid.

🔗Who are the farmers and what exactly do these farmers do?

Think of a ThreeFold Farmer as a digital pioneer who connects their capacity to the ThreeFold Grid, becoming a cloud service provider. They come from all corners of the globe, driven by a common goal: to contribute to the growth of ThreeFold’s decentralized cloud infrastructure. Currently, we boast approximately 950 farmers running an impressive ±2500 nodes. This translates to a whopping capacity of:

• Cores: 64,290
• RAM: 434.85 TB
• SSD: 8.46 PB
• HDD: 20 PB

The farming community keeps the digital gears turning. Whether they purchase a 3Node from the marketplace or build their nodes, they’re providing essential capacity to the ThreeFold Grid. In return for their contributions, they’re rewarded with ThreeFold Tokens (TFTs), the currency of the ThreeFold ecosystem.

Farmers are rewarded based on their uptime—the number of hours, minutes, and seconds their node has been online. This data is meticulously tracked by ThreeFold’s blockchain, TFChain, and used to determine their monthly rewards. However, we’re always evolving and we just passed a vote on the ThreeFold DAO where we decided that, in the future, farmers would be rewarded based on their utilization.

ThreeFold Farmers not only provide capacity but also take the opportunity of ThreeFold being an open-source project to develop scripts and tools like a Python script for minting, a telegram for liquidity pool USDC/TFT, and Telegram channels for their local community where English is not their primary language so that they can get help when they need it, and much more.

The ThreeFold farming community is an integral part of our decentralized autonomous organization (DAO). A farmer’s participation in the DAO discussions and proposals is pivotal as we chart the course for the grid’s evolution, from our current version 3.14 release and beyond. Together, we’re actively building the grid’s future, thanks to our dedicated farmers’ collaborative efforts. Join us, share your ideas, and let’s shape the future of the ThreeFold Grid together.

🔗The Future of the Farming Community

🔗The TF Cooperative

ThreeFold is transitioning the management of TF Grid to a cooperative, empowering all of us to work toward our common goals more effectively. This shift represents a step towards a more collaborative and inclusive future for the TFGrid. As we enter the commercialization phase of the project, a cooperative model also brings a trusted form of decentralized governance and will enable us to bring more reliability to the grid.

The formation of the ThreeFold Cooperative (TF COOP) brings several planned changes for farmers and their interaction with the TFGrid:

• Democratic Governance: TF COOP introduces a system where farmers can vote on decisions based on their TFT holdings (1 TFT = 1 vote), giving them a voice in the cooperative’s direction.
• Farming Rewards: Farmers will continue to earn rewards based on the quality of their nodes and network uptime. This encourages high standards and benefits both farmers and users.
• Compliance: Farmers must follow KYC/AML (Know Your Customer/Anti-Money Laundering) rules for transparency and accountability.
• Service Level Agreements (SLAs): Larger farmers may sign formal contracts with DMCC or TF COOP, providing stability and predictability.
• Capacity Resale and Utilization Rewards: TF COOP will resell capacity and distribute profits. Farmers receive 50% of the revenue from their node utilization.
• Node Information and Transparency: Farmers can benefit from tracking more node data in the explorer, helping potential users select quality nodes.
• Governance Involvement: Farmers, as cooperative members, can impact management and operations, aligning their interests with the TFGrid’s success.

🔗Farming Pool

Farming Pools are a new feature planned for version 4.0 that helps improve trust and quality in our network. Farmers join these pools and agree to standards like uptime and response time. They can set their prices for services like storage and computing power. By staking tokens, farmers commit to these standards and risk losing some of their stakes if they don’t meet their promises. This keeps the network reliable and fair while allowing farmers more control over their services.

These pools can also act as hubs for supporting farmers with training and help them understand if their nodes are working well. Sales of preconfigured hardware is an additional optional function of the pools, while all pools operate as a business that takes a margin on the farming rewards of the farmers belonging to the pool. Beyond support, the added value for the farmers is that pools ensure a level of service and quality that can attract users and bring additional revenues to the farmers, including the potential of active marketing of the pool’s capacity.

🔗Conclusion

The farming community plays a key role in the smooth operation and growth of the ThreeFold Grid. These farmers shape the grid’s future by offering the capacity for a more decentralized digital world. Their work goes beyond earning rewards, as they contribute nodes to a global network and share resources and tools that strengthen the community, which will be showcased in our upcoming blogs. Thanks to their efforts, the grid is thriving and paving the way for a fairer, more connected world.

🔗Get involved:

• Join our farmer’s chat to talk with the community

• Learn about expanding the grid or adding on top of it.

• Stay updated with news and community discussions.

After introducing the ThreeFold Grid in part one and diving deep into storage and compute, we’re back with part 4 to look at the networking aspects of the ThreeFold Grid.

Computer networking is a rather complex phenomenon with a thankfully intuitive outcome: you send messages from one place to another. We all understand that our digital devices become a lot less interesting when they are not connected to the Internet. However, networking is not just Internet, and when it comes to building a new Internet, it’s important to understand what that means.

The existing Internet can be defined as a global set of networks and protocols that enable us to do things like load web pages and use apps that rely on external data. It depends on lots of underlying infrastructure, including fiber optic cables running along the ocean floor, our home routers and their connection to an Internet service provider (ISP), lots of cell service towers, and an increasing number of satellites. All of that makes the Internet possible, and it’s still required for a new Internet to function.

ThreeFold uses and builds new protocols to create a network that is interoperable with the existing Internet. These include private overlay networks, the Planetary Network based on Yggdrasil, and various interfaces to the public Internet. Let’s see how they work.

🔗Private overlay networks

Every deployment on the ThreeFold Grid belongs to a network, which is one of the Grid primitives. These networks allow data to be transmitted between workloads in a private and secure manner. They are called overlay networks because they pass traffic over some underlying network. That could be within a single node or between nodes on infrastructure provided by a farmer. The Grid uses software called WireGuard for this purpose, a simple, fast, and secure option among its alternatives.

By means of encryption, the traffic on a private overlay network is unreadable to any other device on that network. Likewise, the workloads within the private network have no visibility of the underlying network. Individuals who deploy workloads can access their networks over a secure tunnel, assuming that one of the nodes in the network is reachable from the public Internet. This is suitable for workload administration and some private applications. For public services and peer-to-peer communication, the ThreeFold Grid provides other solutions.

🔗Planetary Network

The Planetary Network is an implementation of the Yggdrasil Network, which is a next generation approach to network routing. It is a peer-to-peer solution where all traffic is encrypted and takes the shortest path to its destination. These features make it highly compatible with the ethos and goals of the ThreeFold Grid: privacy, security, and efficiency. The design also allows nodes, workloads, and users to communicate freely without relying on centralized intermediaries.

Many ThreeFold Farmers connect their nodes to a home router which blocks all inbound traffic by default. This is a sensible feature that doesn’t interfere with most Internet usage (enthusiasts who want to host their own website or a gaming server might bypass this, for example). However, nodes on the Grid need to be reachable, especially in order to receive workload definitions from deployers.

The Planetary Network solves this by accepting inbound traffic through an outbound connection to a publicly accessible peer. You can think of this like making a call to an operator and then waiting for another call to be routed to you on that line. Even if your phone is set to block all incoming calls, someone can still reach you if they can reach the operator.

This also provides a way for workloads to communicate with one another and be reachable by users. Anyone can enable the Planetary Network on their own device to access sites and services in a very secure and private way. While the ThreeFold Grid is designed to be fully interoperable with the existing Internet, the Planetary Network provides an alternative which can sit side by side in a seamless way.

🔗Reliable Message Bus

Using the Planetary Network, nodes and Grid users can send messages over the Reliable Message Bus. Notably, it is used for the delivery of workload definitions as mentioned earlier. Zero-OS supports some other RMB messages as well, for doing things like checking available capacity on a node in real time. RMB is a general purpose protocol that can be used by developers in their applications. It queries the ThreeFold Blockchain as a kind of address book for the Planetary Network, enabling nodes and users to find each other in a decentralized way.

🔗Public IPs and Web Gateways

Finally, let’s see how the Grid can offer services over the public Internet using public IP addresses and web gateways. Everytime we type a domain name into our browser, like threefold.io, it is resolved to an IP address. The browser then forms a connection with that address to retrieve the site we’re looking for. Reviving a theme from earlier, that IP must be publicly reachable.

🔗Public IPs

We’re in the midst of a shift from the older IPv4 standard to the newer IPv6 standard. While IPv6 has plenty of addresses for every device on the planet and many more, it hasn’t been universally adopted yet, and IPv4 addresses are in short supply. You likely have one assigned to your router at home, and these days, even getting a second one from your ISP can be a difficult and expensive proposition.

The ThreeFold Grid allows farmers who own blocks of IPv4 addresses to rent them out to deployers. These addresses get attached to individual workloads which are then reachable over the public Internet. A deployer could then assign their own domain name to that IP and host a website there. This is a very flexible way to make Grid deployments publicly available, but it comes at a relatively high cost.

🔗Web Gateways

Web gateways are another way to make workloads on the ThreeFold Grid available over the public Internet. In this case, the farmer may provide a domain name that points to one of their nodes which is publicly reachable. Deployers are then able to reserve a subdomain, like explorer.threefold.io is a subdomain of threefold.io, that routes traffic to their workload. It is also possible for a deployer to point their own domain to the gateway node which then routes traffic to the appropriate workloads.

We glossed over a bit in the earlier description of domain name to IP address resolution. In fact, multiple domains can point to a single IP address and this is common practice among existing web hosts. Adding similar functionality to the Grid helps to ease the demand for IPv4 addresses and is a lower cost solution for deployers than renting a dedicated IP. The web gateway also serves to enhance security and reliability of Grid-hosted services.

The gateway provides a connection from the public Internet to the secure private overlay networks that all workloads use. However, this is not a standard network connection but instead a network socket, which provides security through separation. This is something like passing along the contents of mail pieces without their envelopes. Web gateways also enable redundancy, as multiple gateways can point to the same workload, and multiple workloads can serve the same set of gateways.

When we say the ThreeFold Grid scales limitlessly, this is one of the ways that’s true. Many nodes, many gateways, many applications, and many users can all fit into this model. Deployers can start with a single virtual machine and a single public IP like in the example I’ll use to wrap up this piece below, then ramp up to a globally distributed and highly redundant system as their requirements grow.

🔗Send, receive, complete

Now we’ve seen how the ThreeFold Grid handles networking. From private and secure communication between workloads, to next generation peer-to-peer communication and full compatibility with the existing Internet, these offerings are comprehensive. Not only that, but they can be pretty darn fun to play with too.

In my own recent experience, I deployed a virtual machine on the Grid with a public IP and hosted a simple website with a map of nodes on the Grid that I’d been working on. I was able to quickly share it with some colleagues and members of the community. It went from a project I was tinkering with on my own computer to a live site on the Internet in a matter of minutes, thanks especially to the networking features of the ThreeFold Grid.

For the final piece of this series, we’ll see how everything comes together to turn computer code into a meaningful digital experience. Stay tuned!

As we’ve recently been exploring decentralized projects to see where ThreeFold is in the space and where we stand out, we thought it’s a good time to also look into how we compare to traditional, centralized cloud providers.

The cloud market is a highly complex and competitive one, currently dominated by the market leaders Amazon Web Services (AWS) and Microsoft Azure who account for more than half of the worldwide cloud revenues. This centralized nature of today’s cloud as well as its hyper-scale data center model are the cause for various issues, ranging from the monopolistic power of the few big market players and vendor lock-in effects to the incredibly high energy consumption of data centers and the limited scalability of the current model. Moreover, traditional data centers are more prone to outages and cyber attacks. We believe the ThreeFold Grid built by independent farmers around the globe and our ThreeFold P2P Cloud provide a solution to all of these issues.

While centralized cloud providers do offer some benefits, such as robust feature sets and huge customer service teams, there are a few key and important differences we think any customer would care about:

🔗Decentralization

This is the biggest and most obvious difference. Today, big tech holds a monopoly on the Internet and Cloud markets, meaning they somehow became the gatekeepers of what was originally intended to be a distributed, neutral Internet. When using AWS or Google Cloud, the data is stored in centralized data centers owned by private corporations. These data centers are susceptible to hacking and outages that can take down massive chunks of the Internet. In this system, people have become products, as they exchange their data for “free” online experiences. With ThreeFold, data is stored fully decentralized on the peer-to-peer ThreeFold Grid, where the physical hardware is owned by independent ThreeFold Farmers, and the data is owned by as well as only accessible to the person(s) who put it there. So, hackers can’t get in and due to the decentralized nature of the ThreeFold Grid, large-scale outages would be much less likely as well. Further, no organization or entity needs to be trusted and people are not treated as products – with ThreeFold’s infrastructure, the Internet is owned by the people.

🔗Limitless Scalability at the Edge

Our lightweight operating system Zero-OS makes it possible and even easy to install a node close to where the data is being consumed. There is no need for large servers, nor for heavy power supply installations. Together with our hardware partners, we’re offering 3Nodes with plug-and-play functionalities, allowing anyone to participate. This makes our model infinitely scalable at the edge. Hyper-scale data centers are not able to provide these levels of scalability and edge benefits. In order to scale their operations, centralized cloud providers need to build more data centers and take care of the related maintenance which takes time and costs billions. The traditional data center model also isn’t well suited for the edge, as this requires flexibility and close proximity to the respective data.

🔗Security

Centralized clouds are secure, but vulnerable. At ThreeFold, we pride ourselves on the levels of security we’re providing. The peer-to-peer nature of our technology means end-to-end transmission of data between parties (with no middlemen). This is a big one: Nothing is being stored or copied in central servers. Moreover, ThreeFold’s self-driving and self-healing IT removes the need for human intervention and eliminates the many back doors present in current architecture. So, security issues caused by human error and hacking possibilities both diminish greatly. In addition to that, there is the distributed storage algorithm which makes it nearly impossible for data to be lost. And much more. You can find more info on our wiki or in this forum post.

🔗Privacy

The fact that you own your data and nobody – not even us – can get access to it is key to making ThreeFold much more private than centralized cloud providers. On top of that, connections within our global overlay network, the Planetary Network, are peer-to-peer and end-to-end encrypted.

🔗Affordability

In the end, the centralized cloud is quite expensive, whereas our ThreeFold P2P Cloud is much more cost-effective. Learn more about this in our cloud pricing comparison here.

🔗Energy Efficiency

While electricity for storing and transporting data, administration, human resources, and even gas (to transport physical data-holding devices) lead to a very high energy consumption, our dispersed storage model and peer-to-peer infrastructure allow for significant energy savings. So, another big difference between ThreeFold and centralized cloud providers is that we’re up to 100x more energy-efficient.

All in all, the combination of our ThreeFold Grid and ThreeFold P2P Cloud provide significant advantages over centralized cloud providers with their hyper-scale data centers. From decentralization and infinite scalability at the edge to considerable energy savings and cost effectiveness as well as data privacy and security, our solution has much more value to offer, while solving critical issues related to centralized clouds. If you’d like to test our cloud solution yourself, take a look here. You can also start participating in our decentralized ecosystem by becoming a 3Node on our ThreeFold Grid.

An example to illustrate this challenge is the fact that up to 60% of Ethereum (the world’s second most-popular blockchain) nodes run on centralized cloud providers and 25% of them run on Amazon Web Services (AWS).

While the topic is being addressed, it isn’t being solved at scale. The good news is that ThreeFold can play a large part in solving it.

🔗Why should blockchains make this move?

The blockchain movement, as mentioned, is very heavily tied to the movement around decentralization. Cryptocurrencies represent the move away from centralized banks as the authorities and gatekeepers around money – just as ThreeFold and similar projects represent the move away from centralized clouds as the authorities and gatekeepers around data. The thing is, if blockchains are to rely on centralized cloud for hosting, they aren’t truly embodying decentralization.

Understandably, many blockchains have chosen centralized cloud providers in the past because there wasn’t much of an alternative. But now, the Decentralized Cloud (DeCloud) movement has changed all of that.

Here is how some specific audiences can benefit:

🔗For Node Operators

Any full node or validator node can run on ThreeFold’s Peer-to-Peer (P2P) Cloud, making that particular Blockchain even more community-owned, and more decentralized from an IT/cloud level. Any node operator can choose to run their nodes from any farmer location on the ThreeFold Grid, totally peer-to-peer between the chosen farmer and the node operator. The deployed workloads are computed in a P2P manner, no middle party involved.

🔗For dApp Developers

Web3/Blockchain developers can use ThreeFold’s P2P Cloud - offering both compute and storage - to build and power their applications in a truly decentralized cloud infrastructure, both blockchain-native and cloud-native. A strong advantage here is that developers have the ability to leverage Kubernetes, Docker, S3, and other cloud-native tools (all compatible / integrated with the ThreeFold) to power and optimize their data processing capabilities, as well as the overall functionality of their dApps. But the sweet spot is that it is deployed on a decentralized IT infrastructure, close to where users would be located.

🔗But why choose ThreeFold over other DeCloud projects?

There may be bigger names in the space, but ThreeFold’s technology and offerings are much more comprehensive than the rest. ThreeFold provides decentralized storage, compute, and network all under one roof (whereas most other projects offer only one of the three) and as mentioned, we have created an environment for developers which is highly-compatible to the developer tools and solutions they use today. Further, ThreeFold is building new infrastructure from the ground up (rather than relying on extra space in data centers) and the technology is truly peer-to-peer.

We already have a number of partners in the space who recognize these advantages.

Any blockchain protocol or dApp, whether operating DeFi, NFTs, DEXs, etc, will at some point need to leverage the power of the decentralized cloud and escape from centralized cloud providers. We’re seeing some of that adoption from a decentralized storage side with IPFS, which has been adopted by many dApps, and others – but as a developer, you will have to think twice, not just about where your/your users’ data is being stored, but also about how (and where) your app is computed and powered.

Participate now in our quest to fully decentralize the Internet by becoming a node on our grid or buying TFT.

🔗What is compute?

While storage and network are fairly intuitive concepts – where data lives and how it gets around – compute is about the more mysterious realm of data processing and ultimately computer programming. Don’t worry though, you don’t need any technical abilities to gain a deeper understanding of what’s happening behind the scenes when we use apps or interact with web sites.

As mentioned in the first part of this series, compute is basically what happens with data once it reaches its destination. Compute gives data relevance, by processing it according to the instructions provided by developers in their source code. When talking about what the ThreeFold Grid offers in terms of compute, it’s mostly about how the code that developers produce gets executed in order to provide the services we enjoy.

With ThreeFold, this actually happens for the most part using the same tools and systems provided by traditional cloud services, meaning that it’s highly compatible with existing cloud applications. What really makes the Grid different is that it’s been designed to provide a level of efficiency and security that simply isn’t possible without starting “from the ground up”. Before we get into specifics of compute offerings built into ThreeFold’s Zero-OS, let’s briefly explore what computing is.

🔗Playing with zeroes and ones

Everything a computer’s central processing unit does is based on a limited set of instructions that includes basic mathematical functions, logical operations, and ways to control the flow of a program. At their core, computers are really just automated adding machines that execute specified operations on whatever input they receive. It may be hard to believe that simple math creates all of the vibrant digital experience we enjoy, but at a certain low level, that’s the truth.

Take a messaging app as an example. Within a computer, all of the text, emojis, and images we see are represented by numbers. When we search for some text within a chat, matches are determined by checking if the numbers corresponding to the words we typed are equal to some numbers corresponding to words that appear in the chat history. This information is then converted into the list of results we see on screen.

In this context, compute is mostly responsible for organizing all of our messages based on the individual or group we were talking with, the time that the message happened, and whether or not we’ve opened it yet. Typically, a messaging app stores data both on our local devices and on a back end in the cloud. Compute is also how the service decides to copy messages you sent on one device to other devices where you have the same app installed.

Here is an important distinction about how the ThreeFold Grid operates. In a traditional cloud environment, it is impossible to know for sure what is happening on the backend, even if you are the one running the service. The administrative access retained by the cloud provider can be used for surveillance and tampering that can be very difficult or impossible to detect.

Zero OS offers a unique assurance that no one can abuse the Grid in this way, because it operates autonomously with no facilities provided for human intervention. In order to utilize compute capacity on the Grid, individuals and organizations deploy their choice of several “primitives,” or basic components, that provide an environment for code to be executed and create the magic we experience as online applications.

🔗ThreeFold Compute Primitives

Since we’re getting a bit into the technical weeds here, we’ll just take a brief look at each primitive and what makes it special.

🔗Zmachine

Zmachine is a lightweight virtual machine (VM) implementation that’s been developed in a uniquely efficient way by ThreeFold. VMs are essentially computers within computers, allowing multiple operating systems to run on a single physical system. A common example is running the Windows operating system on a Mac that’s already running MacOS.

In the cloud world, virtual machines are a classic way to manage complex deployments with flexibility and resilience – by packaging different components into different VMs that can be run side by side and moved between different physical servers with ease. While VMs have been replaced in many cases with the new container paradigm, which we’ll cover next, they are still widely used and provide a simpler solution than containers that’s sufficient for many use cases.

🔗Flist

The Flist is a next generation container format which extends the industry standard Docker container concept in an efficient and secure way. It is supported directly at the operating system level on Zero OS, and in its latest version on ThreeFold Grid 3.0, provides a unique advantage over traditional containers via the use of mini virtual machines.

Containers provide greater efficiency and flexibility than VMs, by sharing parts of the host operating system between containers rather than duplicating the full operating system for each component. This, however, means that containers typically come with less of an assurance that different workloads and their data remain isolated from each other. By employing mini VMs, the Flist concept provides better isolation than traditional container systems while retaining the advantages that containers offer over full VMs.

🔗Kubernetes

Containers usually represent small parts of a full solution, which are created, interconnected, and destroyed on an ongoing basis. Kubernetes is the industry standard container orchestration system, and it’s used to manage many of the largest and most complex cloud deployments. Kubernetes solutions are defined through configuration files that specify the types of containers, how updates are handled, and the network architecture both between containers and with the outside world.

Multiple physical servers or VMs are typically used for a Kubernetes “cluster” which provides redundancy and scalability. The ThreeFold Grid provides a lightweight Kubernetes VM that can be used to create clusters according to specific needs. Kubernetes users can, for the most part, simply bring their existing configuration files and recreate their deployments on a Grid based cluster seamlessly.

🔗Wrapping up

Taken together, the compute primitives offer a comprehensive alternative to existing cloud compute providers. Users of Docker, Kubernetes, and virtual machines can bring their deployments to the Grid with a minimal amount of migration effort. This is distinct from other decentralized cloud projects, which either offer a single solution like Kubernetes or a completely new environment that developers must adapt their code to run within.

Better yet, each compute offering on the ThreeFold Grid benefits from the unique efficiency and security features of Zero OS, as well as the unique aspects of the primitives themselves. Thanks again for joining me on this journey into the wonderful world of ThreeFold technology. In the next episode, we’ll cover the last element of the cloud infrastructure triad: network.

• ThreeFold Forum
• ThreeFold Main Chat
• ThreeFold Farmers Chat
• ThreeFold Testing Chat
• ThreeFold Foundation GitHub
• ThreeFold Tech GitHub