TPRO Network Documentation

Description

This repository holds the original TPRO design documentation (2022-2024): the network design, the economic simulations and the pool mechanics. It is published at doc.tpro.network. If you see any problems or misleading parts, tell us in GitHub Issues or consider contributing.

The TPRO token (2026)

Since 22 September 2026 the TPRO token lives on Base. Everything current about the token (contract, supply, allocation, locks, legacy addresses) is on tpro.network/token; every official channel and address is on tpro.network/official. The token contracts, the snapshot tool and the claim page are in TPRO-Network/tpro-token.

Chain	Address	Status
Base	0xBc2029b41cedf44CFdD7BaeE9c50B02bf0c8f79C	the TPRO token (verified on Basescan)
Ethereum	0x3540abe4f288b280a0740ad5121aec337c404d15	legacy since the snapshot of 21 September 2026, no liquidity
Polygon	0xd24157aa1097486dc9d7cf094a7e15026e566b5d	legacy child token

Holders of record claim 1:1 on claim.tpro.network until 22 September 2029. We never DM first and never ask for keys, signatures or transactions on Ethereum.

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

• Economic Simulations

  • Form

    • Project Selection

    • Liquidity Configuration

    • Allocation Rounds and Vesting

    • Supply Strategy Configuration

    • Secondary Market Configuration

  • Simulations

    • Simulation Step

      • Randomness Within the Scenario

      • DEX

      • CEX

      • Vesting

    • Primary Market Strategies

      • Random Sale

      • Aggressive Random Sale

      • Incremental Doubling Sales

      • Extended Profit Multiplier

      • Incremental Profit Doubling

    • Secondary Market Agents

      • Base Agent

      • Low Advanced

      • Moderately Advanced

      • Very Advanced

      • Speculator

  • Scoring Engine

    • Allocations

    • Demand

    • Availability

    • Short-term Price

    • Long-term Price

    • Additional Metrics

    • Detailed Results of the Simulation

• $TPRO Pool

  • Liquidity Pool

  • Dynamic Fee

    • Mechanism Parameters

    • Mechanisms Mathematical Specification

  • Impermanent Loss Protection Mechanism

    • Mechanism Parameters

    • Mechanisms Mathematical Specification

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.