Inferix Decentralized GPU
  • Overview
  • Tokenomics
  • Introduction
    • Rendering network using crowdsourced GPU
    • Rendering verification problem
  • Decentralized visual computing
    • Client Apps plugin
    • Client API and SDK
    • Manager node
    • Worker node
    • Decentralized storage
      • Data categories
      • Multi-level 3D polygon data
      • Polygon digester
      • Decentralized storage
      • Decentralized cache
    • Data security with FHE and TEE
      • Verifier data security enhancement with FHE
      • Worker and Manager data security enhancement with FHE
    • Decentralized federated AI
      • Federated learning with TensorOpera
      • Meta LLaMA
      • Stable Diffusion
      • Other AI models
      • Inferix AI
  • Inferix Testnet 1
    • Inferix GPU Solutions
    • Adding GPUs to the Network
    • Renting GPU Devices
    • GPU Staking
  • Future development
    • PoR and NFT minting for graphics creative assets
    • ZKP and PoR communication
    • Inferix RemotePC
    • Rendering professional network
  • Terms of Service
    • Privacy Policy
    • Airdrop Terms of Service
Powered by GitBook
On this page
  1. Decentralized visual computing
  2. Decentralized storage

Data categories

3D data stored in the Inferix system includes:

  • Geometry data of 3D models, characterized by polygons that form the shape of objects. Depending on the render engine, different formats may be used. The higher the number of polygons, the more detailed the rendering result will be; however, the render time will also increase, and more storage space will be required.

  • Texture data, which is the surface image of the object. Inferix uses data formats with the best compression algorithms for GPUs, such as Basis and KTX, alongside common formats like JPEG, PNG, TIFF, or WebP.

  • Rendered results in image format

  • Rendered results in video format

  • Structural data in JSON format

PreviousDecentralized storageNextMulti-level 3D polygon data

Last updated 4 months ago