TradeOS Litepaper
TradeOS Litepaper
TradeOS LitepaperTradeOS - BountyBay Meme DEX Guideline
TradeOS Litepaper
TradeOS LitepaperTradeOS - BountyBay Meme DEX Guideline
  • TradeOS
    • 💱Introduction
    • Problem Statement
    • TradeOS Protocol, by BountyBay Labs
    • Key Applications
    • Roadmap
  • Appendix
    • Proof-of-Delivery
    • Join US - TO Da Moon!
Powered by GitBook
On this page
  1. TradeOS

TradeOS Protocol, by BountyBay Labs

PreviousProblem StatementNextKey Applications

Last updated 2 months ago

【Key Players】

  • Service/Product Buyers: initiate the Demand, specify the required deliveries, and escrow transaction payment to TradeOS Vault contract.

  • Service Providers: complete demand and submit zk-empowered "Proof-of-Delivery" to the Vault contract. The Vault contract automatically pays out the staked payment once the requirements are met, no need for any centralized intermediaries with the minimized bidirectional handshake risks.

  • ZK-based 'Proof-of-Delivery': TradeOS supports ‘Proof-of-delivery’ submitted by any verified provider. By leveraging web proof technologies, zkTLS removes the need for traditional API integration, enabling the trustworthy extraction of real-world data from various platforms.

By leveraging on-chain data, zkTLS and TEE-TLS technologies to produce privacy-preserving "Proof-of-Delivery" for off-chain activities, the Vault smart contract can identify the completion of required activities and pay automatically. The need for centralized intermediates are completely removed. You own your own data, and the all value on top of it.