Documentation
HomeDocsDiscordContact
  • What is Tashi?
  • Lightpaper
  • Nodes
    • Node Architecture
    • Node Types
    • Node Specifications
  • Protocol
    • Overview
      • Tashi’s Discovery
      • Performance Analysis
    • Consensus
      • Network Traversal
      • Fairness
    • MeshNet
  • Resources
    • Github
    • Discord
    • FoxMQ
      • Features
      • Roadmap
      • Quick Start - Direct
      • Quick Start - Docker
      • Configuration Files
      • CLI Options
        • Command - Run
        • Command - AddressBook
        • Command - User
    • DePIN
      • Worker Node Install (Docker)
Powered by GitBook
On this page

Nodes

PreviousLightpaperNextNode Architecture

Last updated 10 months ago

Tashi's DePIN strategy requires the coordination of peer-provided nodes. Our fundamental objective is to provide what is currently only available through centralized cloud-based solutions to game developers and publishers via our DePIN service strategy, using our innovative fully on-DAG gaming technology, while ensuring no degradation in gamer experience and adding no friction.

In Web2 there are services like BitTorrent, which is a peer-to-peer shared storage solution. This approach is acceptable for the use case it satisfies, but does not come with any guarantees about availability, performance, or security.

In Web3, we ensure a more reliable execution of services by overlaying the resource layer of services with an orchestration layer that adds availability monitoring, dynamic incentives, and validation of job execution. This Web3 approach ensures that game player demand is met. This is how we move centralized cloud-based gaming infrastructure into a network of underutilized peers and still meet the needs for availability, performance, and security.

Cover

Node Architecture

How do nodes make Tashi's DePIN go?

Cover

Node Types

What are the different Node types and roles?

Cover

Specifications

What do I need to run a node?