ThirdFi.org
  • Introduction to ThirdFi
  • Product
    • ThirdFi Developer
      • Overview
      • Swap API
      • Invest API
        • Market Weighted Index - MWI
        • Low-risk Crypto Index - LCI
      • Earn API
      • Pay API
      • Borrow & Lend API
      • Price Oracle
        • Price Oracle API
        • Price Oracle WebSocket
        • Price Oracle Use Case
      • Developer Dashboard
      • Developer Sandbox
      • Testnet Faucet
      • Webhook
      • Use Case
        • DeFi Alert
        • Price Alert Chrome Extension
      • FAQ
    • ThirdFi v2
      • Vision & Mission
      • Overview
        • How does it works?
        • Economic Model
      • Technical Overview
        • Network Architecture
        • Node Operations
        • Data Management and Security
        • Consensus and Security
        • Differentiators
        • Use Cases and Applications
      • Token Model
        • Proof of Trading (PoT)
        • T-Node
        • $THI
        • $oTHI
        • Conversion of $oTHI to $THI
    • Data to Earn Program
      • Introduction of Data-to-Earn
      • How to participate as a Data Provider?
      • Ways to collect Data Points
      • Reward Hash (Explanation)
      • Reward Hash (Technical)
      • How to verify your Reward Hash?
    • Roadmap
  • Disclaimer
  • Grants
    • Request For Builders
      • Season 1
  • Let's connect
    • Blog
    • Twitter
    • Discord
    • Linkedin
    • Youtube
    • Link3
Powered by GitBook
On this page
  1. Product
  2. Data to Earn Program

Reward Hash (Explanation)

Hash within Hash

PreviousWays to collect Data PointsNextReward Hash (Technical)

Last updated 10 months ago

Reward Hash - [Unleash the infinity of transaction randomness]

  • Each Booster requires users to pay for transaction hash for "Reward Hash" generation.

  • Every Reward Hash generated stands a chance to get rewarded in 100 USDT

How does that transaction Reward Hash work?

  • In order to create a pure random hash that can’t be manipulated, ThirdFi created a reward hash function that uses ‘hash within hash’

  • This hash is a 32 bytes hexadecimal similar to transaction id(transaction hash). The hash is computed from tokenid, msg.sender, block.chainid, boostCount[tokenid], block.timestamp and blockhash(block.number).

  • Therefore, a purely randomized hash that is purely random and can’t be manipulated (with exception of 51% network attack or manipulating sequencer)

For more information, please read more details on Reward Hash (Technical)

Rewards Pool

Phase 1: Booster rewards

Phase 2: <coming soon>

Phase 1: ThirdFi ID and Booster rewards

Any Booster Transaction Reward Hash generated from either ThirdFi ID mint or Booster ending with “abc” OR “123” are entitled to $100 reward from the prize pool.

Check on .

How to Verify your Reward Hash
Reward Hash by "Hash within Hash"