TPRO Network Documentation

Description

This repository contains official documentation for TPRO project. We recommend you to read this pages on official website. If you see any problems or misleading parts of this document, tell use about it in Github Issues or consider making contributions yourself.

Table of Contents

• Abstract

• Introduction

• Objectives and Design Considerations

  • Design Considerations

    • Delegation of Processing Power

    • Delegation of storage

    • Data providers vs resource providers domain gap

    • TPRO at the center

    • File sizes

    • Replication

    • On-chain reporting

  • Design Overview

    • TPRO network overview

  • Design Objectives

• Proposed Solutions

  • Models

    • Publishing model scheme

    • Retrieving model scheme

    • Publishing model instance

    • Storing model instance

    • Previewing model instance

    • Purchasing model instance

  • Tokenomics

    • Publishing tokenomics scheme

    • Retrieving tokenomics schehme

    • Publishing tokenomics instance

    • Storing tokenomics instance

    • Previewing tokenomics instance

  • Simulations

    • Performing simulation

    • Publishing simulation results

    • Storing simulation results

    • Previewing simulation results

    • Purchasing simulation results

  • Analysis Reports

  • Lifetime Events

  • Rewarding

    • Rewarding model providers

    • Rewarding tokenomics providers

    • Rewarding simulation operators

    • Rewarding analysts

    • Rewarding storage providers

    • Rewarding processing providers

    • Rewarding TPRO

    • Further incentivization

  • Proofs

    • Proof of Offer (PoO)

    • Proof of Storage (PoS)

    • Proof of Purchase (PoP)

    • Proof of Simulation (PoSIM)

• Managing Risks

  • Lack of adoption

  • Unfair rewarding

  • Unfair randomness

  • Lack of permament storage

  • Repackaging instances

  • Pirating instances

  • Defective uptime

Contributing

For contributions submitting documentation for the current stable release, submit it to the corresponding branch. For example, documentation for TPRO 0.3 should be submitted to the 0.3 branch. Documentation intended for the upcoming release should be submitted to the master branch.