DOCSEARCHbyAlgolia
Submit Docs

LooPIN Documentation

website·Indexed 32 days ago

https://docs.loopin.network

Documentation for LooPIN, a decentralized computing network. Includes guides on GPU provider integration (AWS, Lambda Cloud, FluidStack), $LOOPIN tokenomics, Proof-of-Computing-Power-Staking (PoCPS), and tutorials for deploying AI models like Llama3, FaceFusion, and GPT-SoVITS.

Tokens
16.2K
Snippets
60
Records
126
Agent score
61%

What's inside LooPIN

  1. Overview of GPT-SoVITS Voice Cloning

    GPT-SoVITS is an advanced text-to-speech (TTS) and voice transformation model capable of cloning voice timbres with minimal input. It supports Mandarin, English, and Japanese. A 5-second sample can achieve 80-95% similarity, while a 1-minute sample significantly improves fidelity to mimic a real human voice. Key features include zero-shot TTS, minimal-sample refinement, and a WebUI toolset for voice accompaniment separation, automatic training set segmentation, and Chinese automatic speech recognition (ASR).

  2. Overview of PinFi Protocol

    PinFi is a Physical Infrastructure Finance protocol designed to pool, distribute, and finance computing resources across decentralized networks. It aims to make AI computing power more accessible and affordable through a 'Dissipative Liquidity Pool' concept that matches real-time demand with excess supply, utilizing smart contracts to manage coordination, pricing, and liquidity.

  3. Understand $LOOPIN token utility

    The $LOOPIN token is used for two primary functions within the ecosystem: staking for network validation and governance for protocol decision-making.

  4. LooPIN token standards and cross-chain protocol

    LooPIN tokens are native standard tokens on both supported chains:

    • Ethereum: Based on the OpenZeppelin ERC20.sol contract.
    • Solana: Based on the standard Solana-program-library (SPL) token contract.

    Cross-chain transfers are handled via the Native Token Transfers (NTT) protocol developed by Wormhole, which allows for seamless transfer while maintaining ownership and contract upgradability.

  5. Understand PinFi and its role in Decentralized Computing Networks

    PinFi is a conceptual framework that merges Decentralized Physical Infrastructure Networks (DePIN) with Decentralized Finance (DeFi), expressed mathematically as PinFi = DeFi(DePin).

    It addresses the underutilization of resources in traditional Decentralized Computing Networks (DCNs)—where often only a small fraction of GPUs are active—by replacing centralized order book pricing with automated market-making (AMM) systems. This approach creates a dynamic pricing equilibrium between GPU providers and users, improving resource liquidity and monetization.

  6. LooPIN Network Architecture and Components

    LooPIN is the first project implementing the PinFi protocol. It functions as a 'network of networks' (Decentralized Computing Network Ensemble or DCNE) that integrates DeFi mechanisms to optimize computing resource utilization. The network consists of five primary components:

    1. Liquidity Pools: Permissionless, censorship-resistant pools categorized by resource type (e.g., GPUs, TPUs). These are established via smart contracts on the blockchain.
    2. Decentralized Computing Network Ensemble (DCNE): The aggregate of all permissionless liquidity pools provided by independent computing providers.
    3. Providers/Miners: Users who provide hardware devices and stake tokens to a liquidity pool. They use a Proof-of-Computing-Power-Staking process to validate their contribution and earn block rewards.
    4. Clients/Users: Users who consume computing resources from the liquidity pools and are also eligible for block rewards for their participation.
    5. Verifiers: Entities that use the Proof-of-Computing-Power-Staking scheme to validate that devices are actually providing secure and reliable services.

  7. Bypass CGNAT and network restrictions for Loopin rigs

    When you cannot modify port mapping rules or are behind a Carrier-Grade NAT (CGNAT), you can use a VPS with a public IP and a VPN (such as ZeroTier, Tailscale, or Wireguard) to redirect traffic to your rigs. This setup allows external access to rigs that lack a direct public IP.

    Prerequisites:

    • A VPS with a direct public IP.
    • ZeroTier or a similar VPN installed on both the VPS and the rigs.
    • IPv6 must be disabled on the rig(s).
    • Basic Linux command-line and networking proficiency.

  8. Sell computing resources in the LooPIN mainnet

    Computing resource selling has been adjusted to reduce unused time and prevent token price arbitrage:

    • Selling Resolution: Resources must be sold in increments of 1 day.
    • Selling Period: Minimum of 1 day; maximum of 7 days.
    • Collateral: To prevent malicious arbitrage, the collateral requirement has been increased from 1x to 100x the value of the sold GPU hours.

  9. Sell computing resources in the LooPIN mainnet

    Sellers can offer computing resources with the following constraints in the mainnet phase:

    • Selling Resolution: 1 day.
    • Minimum Selling Period: 1 day.
    • Maximum Selling Period: 7 days.
    • Collateral Requirement: Sellers must provide collateral equal to 100x the value of the sold GPU hours to prevent token price arbitrage and ensure network stability.

  10. Provide liquidity for Computing Power Pools

    To reduce price volatility and increase the depth of liquidity pools, LooPIN requires liquidity providers to stake LooPIN tokens. In the mainnet phase, the staking requirement has been increased from 24 hours to 7 days of computing power for each machine added to the liquidity pool.

  11. Set up a secondary SSH service on a VPS

    To maintain access to your VPS while modifying network settings, it is recommended to run a secondary SSH service on a custom port (e.g., 2222).

    Warning: Before proceeding, open at least two active SSH sessions and run htop in each to prevent timeouts and ensure you can recover if the primary SSH connection fails.

    # 1. Copy existing SSH configuration
sudo cp /etc/ssh/sshd_config /etc/ssh/sshd_config_custom

# 2. Edit /etc/ssh/sshd_config_custom:
# - Comment out 'Port 22'
# - Comment out 'Include /etc/ssh/sshd_config.d/*.conf'
# - Add 'Port 2222'

# 3. Create systemd service file: sudo nano /etc/systemd/system/sshd-custom.service
# Add the following content:
# [Unit]
# Description=OpenBSD Secure Shell server (custom instance on port 2222)
# After=network.target
# 
# [Service]
# ExecStart=/usr/sbin/sshd -D -f /etc/ssh/sshd_config_custom
# ExecReload=/usr/sbin/sshd -t
# KillMode=process
# Restart=on-failure
# RestartSec=42s
# 
# [Install]
# WantedBy=multi-user.target

# 4. Enable and start the service
sudo systemctl daemon-reload
sudo systemctl start sshd-custom.service
sudo systemctl enable sshd-custom.service

  12. Install ComfyUI on LooPIN GPU instances

    To deploy ComfyUI on a LooPIN GPU instance, clone the repository, install the required Python dependencies (including xformers), and set up the ComfyUI-Manager extension for custom node management. To expose the ComfyUI web interface (port 8188) to the public internet, use a Cloudflare tunnel.
    # Clone ComfyUI
git clone https://github.com/comfyanonymous/ComfyUI.git && cd ComfyUI

# Install dependencies
pip install xformers!=0.0.18 -r requirements.txt --extra-index-url https://download.pytorch.org/whl/cu121 --extra-index-url https://download.pytorch.org/whl/cu118 --extra-index-url https://download.pytorch.org/whl/cu117

# Install ComfyUI-Manager
cd /workspace/ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Manager.git

# Install Cloudflare tunnel
wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb
dpkg -i cloudflared-linux-amd64.deb