Validation
Registered relays are rewarded Torex Protocol in proportion to their useful contribution to their respective network. Our off-chain validation servers ingest trusted metrics and feed this information onto the blockchain as 'source of truth', after which permitted smart contracts then assign operators rewards.
Consensus Weight
For our first registered protocol, The Onion Router, we mirror the existing Consensus Weight metric to ascertain useful contribution for a registered relay. Consensus Weight accounts for factors such as bandwidth, and reflects the growing traffic often assigned to a newly registered relay.
Arweave Metrics
Our collected metrics are published in close-to real time on Arweave, permaweb storage powered by blockchain. These metrics then act as an endpoint for downstream smart contracts, primarily smartweave (smart contracting built directly onto the Arweave ecosystem). However, our metrics are also accessible via our request protocol by third parties.
Build on our metrics!
We’ve developed novel data structures that builders can employ to query our published metrics. Specify exact queries to retrieve data following our structure using GraphQL, following the structure outlined below: https://github.com/torex-development
Smartweave Oracle
Torex Protocol assigned for a given, fixed time period (such as a day) is apportioned for the interval since the last published metric (so a 70-minute interval between the previous metric read will mean the next set of metrics will determine Torex Protocol distribution for 70 / (24*60) of the predetermined daily distribution - find out more about our tokenomics in our tokenomics paper). A dedicated 'Torex Protocol' token is then distributed on Smartweave, which can then be read lazily by our BEP-20 distribution contract using the validator oracle.
Last updated