Tellor Tributes 백서

Tellor Tributes

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 3쪽

ion techniques, changes to the consensus protocol(e.g. cosmos sdk updates for faster blocktimes), or even changes to the Tellor system to make it more secure. Hard forks on the other hand are security based and happen if the protocol is attacked, compromised, or broken in some way. Soft Upgrades For each chain using the Tellor protocol, we can have a mapping of chainID to a valid contract address for the verification of the data/protocol. In order to change it, a new light client bridge contract with the updated code will be deployed on the EVM chain. Validators will then update the mapping, and propose a change on the consumer chain. Then after waiting 14 days (allows for users to exit if malicious), the address will be updated to the new validator contract. Hard Forks For hard forks, you will also have a way to update this proxy address for verification of the consensus mechanism. The issue here is that time is of the essence. If the validator set is compromised or a bug is found, parties will want to very quickly switch oE the oracle and upgrade. Unfortunately, the switch cannot happen quickly, but freezing should be possible.16 Plan for legacy Tellor contracts Tellor currently has users on Ethereum, Polygon, Gnosis, Arbitrum, Mantle, zkEVM, zkSync, BOB and Optimism. Tellor contracts are immutable, so users of the contracts can continue to use the contracts as they do currently. Users need to continue to incentivize reporters to stay on other chains posting data (tip) and should migrate over time as they upgrade their contracts or launch new systems. The current TRB token contract remains the same, on Ethereum. But instead of minting the time based rewards to the oracle contract it sends these rewards to the bridge contract. The bridge contract has an oracle proxy that allows legacy Tellor users to read data from Tellor (the light client contract). The reason the oracle tokens are given to the bridge is to allow a two way bridge since inflationary rewards happens on Tellor based on the bridged tokens. Conclusion Tellor is an open network where anyone can validate, report data, request any data, dispute data, and help settle disputes via staking and fees. These properties uniquely position Tellor for no 16 A library such as: https://github.com/RealityETH/subjectivocracy can be used as a dispute resolution mechanism for freezing and then voting on the results of the fork (all very costly to initiate to prevent censoring). Ultimately, you want this to be decided by the users on the chain itself and it might be a good choice to have a permissioned set (w/ a high cost still) or even a re-staking situation. friction integrations by users or AI agents alike17. Tellor is crypto-economically secure with measurable security and users can layer additional security controls. There is no one way to make protocols 100% immune to manipulation or capture but security can be layered to meet each users’ needs. Tellor ’s architecture aims to remain permissionless and censorship resistant but applications using it can choose to embody the same properties or add controls on top of it. This is similar to how applications on Ethereum can implement higher levels of control over their system without compromising Ethereum’s properties. Glossary 1. Tellor and Tellor Layer: A standalone Layer 1 (L1) blockchain built using the Cosmos SDK, designed for consensus on subjective data using tendermint and an optimistic approach. 2. Cosmos SDK: A software development kit for building blockchains in the Cosmos ecosystem. 3. Tendermint/ Comet BFT: A Byzantine Fault Tolerant (BFT) consensus algorithm used by blockchains in the Cosmos network. 4. Validator: An entity in the Tellor network that has locked a certain amount of TRB tokens to participate in block validation. 5. Reporter: An entity in the Tellor network responsible for submitting values for data requests (queryIDs). Reporters can be staked validators or other participants, depending on the network's rules. They provide data, incentivized through tips, subject to validation and potential disputes. 6. Query: A unique identifier for a data request (e.g., BTC/USD price) on the Tellor. 7. TRB Token: The native cryptocurrency of Tellor, used for staking, tipping, and governance. 8. Cycle List: A governance-controlled list of queryIDs to maintain data freshness and ensure continuous reporting. 9. Consensus Threshold: The minimum amount of agreement required among validators for a value to be considered valid. 10. Disputing: A process in Tellor where reporters' submissions can be challenged, potentially leading to slashing of their stake. 11. Slashing Event: A penalty where a portion of a validator or reporter's stake is removed due to submission of incorrect data or other violations. 12. Tipping: A system where users can tip reporters in TRB tokens for submitting data for specific queryIDs. 13. Relayer: An entity that transmits data from the Tellor to other blockchains, facilitating cross-chain data accessibility and usage 14. Robust Data Usage: A data verification method in Tellor where values agreed upon by a supermajority of reporters are instantly deemed reliable for real-time use. 15. Edge Data Usage: A method of using Tellor where submitted values are presumed correct if not disputed over a period of time, and/or X% of validators signed oE. 16. Light Client Bridge: A mechanism for relaying Tellor data to other blockchains. 17. Validator Nonce: A unique number used once by validators to prevent replay attacks. 17 Unlike other oracles, the team does not have to approve new data feeds or whitelist users or data reporters, instead AI agents can handle submitting a data specification to the community and tip to start getting data without the team intervention.
프로젝트로 돌아가기