Leea Labs
  • 👋Welcome to Leea Labs
  • Intro to Multi-Agent Systems
  • Leea Platform
  • Integration guides
    • SDK and How to Integrate (Your first agent)
    • Use agents through public API
  • Agent Protocol Architecture
  • Data streams & real-time events
  • Limitations and Challenges for Agents solved by Leea
  • F.A.Q.
    • F.A.Q. Multi-Agents AI Systems
    • F.A.Q. Leea Protocol
  • Protocol Architecture
    • Leea Protocol introduction
    • Architecture overview
    • Security
    • Network and Virtualization
    • Node provider requirements
    • How to connect your node
Powered by GitBook
On this page
  • Setting up Node Agent
  • Node audit
  1. Protocol Architecture

Node provider requirements

Providers in the Leea Protocol are individuals or organizations that contribute their computational resources—such as CPUs, GPUs, storage, or entire data centers—to the decentralized network via the Node Agent app. They play a key role in supplying the computing power that clients require for various tasks, such as AI training, machine learning, data processing, and more.

Key roles and utility:

  1. Resource Contribution:

    • Providers offer their idle or underutilized hardware to the Leea network. This includes personal computers, servers, GPUs, or entire data center clusters. Doing so allows the network to scale dynamically based on client needs.

  2. Monetization of Idle Resources:

    • One of the core benefits for Providers is the ability to monetize unused computing resources. By joining the Leea Protocol, Providers can earn rewards by renting out their hardware to clients who need computational power for various tasks.

  3. Dynamic Pricing and Control:

    • Professional Providers have access to advanced management tools, allowing them to set dynamic pricing for their resources. They can adjust the minimum and maximum limits for resource availability through the dashboard or API, ensuring they maintain control over how their hardware is utilized.

Setting up Node Agent

Before getting started, please review the table with minimal hardware requirements.

Minimal hardware requirements

  • VT-x/AMD-V enabled in BIOS

  • IOMMU/VT-d enabled in BIOS (for GPU passthrough)

  • 100mb/s network bandwidth

  • Static public IP (optional)

Windows hosts
Linux hosts
MacOS hosts

Hyper-V extension installed

4GB RAM

4 Cores

128 GB disk free space

KVM-compatible distribution

4GB RAM

4 Cores

128 GB disk free space

Apple M1 processor or newer

4GB Ram

128GB disk free space

Registering in network

To register on the network, you need to create an account in Leea Protocol and stake XXX $LEEA tokens in your wallet. During the testnet phase hardware providers should receive test $LEEA with the faucet option provided.

Agent setup

Installing the Leea Node Agent is simple: download and run the installation file with administrator rights. The Leea Node Agent will check the hardware requirements and make the agent available in the Leea Protocol.

The node will also appear in the dashboard, where you can edit the quotas allocated to each node.

Quotas settings

By default, we allocate half of the node's specifications for the Leea Protocol load, but this number can be changed. You can do this in the UI or run the agent with the following flags:

./agent -c=4 -r=10 -s=200

Where:

  • -c — cores quota

  • -r — ram quota

  • -s — disk quota

Agent statistics

You can view the agent usage statistics within the dashboard and through the agent's UI.

Node audit

Anyone can run the Leea Agent on almost any computer, providing great flexibility. However, this also introduces certain risks, as the node physically remains under its owner's control and relies on its local network.

The Leea Protocol mitigates most of these risks through slashing mechanisms. To further enhance security, a small portion of resources on each node is reserved for auditing purposes.

Node Audits involve checking various host parameters, some of which include:

  • Node status

  • Network bandwidth

  • Number of CPU cores

  • Amount of RAM

  • Brand and model of equipment

  • Number of running guest VM processes

PreviousNetwork and VirtualizationNextHow to connect your node

Last updated 7 months ago

Node audit occurs continuously providing reliable data to prove the validity of

slashing in case of disputes.
Node Agent UI