Tellor (TRB) Price

Tellor is a Layer 1 blockchain for reaching consensus on subjective data; TRB is the asset used to participate in the network. The network is run by open staking participants. Its goal is not for a single data provider to directly publish results, but for participants to submit, verify, and sign data requested by the network. On Tellor Layer, TRB is connected to participation eligibility and economic incentives: participants enter the network by bridging and staking TRB, and reporters can receive TRB rewards for submitting data. TRB in its Ethereum form and balances on Tellor Layer can be transferred through the official bridging process.

Tellor's data process begins with a data request: reporters read the requested information from internet or real-world sources and submit values; those submissions are then aggregated and verified on-chain and may enter dispute handling. Reporters are responsible for providing data, but their submission does not automatically become a final result that applications can trust merely by being submitted. Validators validate transactions, participate in consensus, propose blocks, and sign aggregated data. A reporter may also be a validator, but not every reporter is a validator; this division means submitting data and validating consensus on the on-chain result are not the same responsibility.

When at least two-thirds of Tellor validators, calculated by stake weight, sign a data point, TellorDataBridge can verify that the data came from Tellor. The threshold is calculated by stake weight rather than simply by the number of signers, so the stake weight of signers affects whether the authenticity threshold is met. “Coming from Tellor” does not mean it is automatically suitable for every application. Integrating contracts should also check the queryId, data timestamp, and business conditions for their own use case; the official example also explains that when a higher threshold is not reached, an application can require data at a lower threshold to first pass an undisputed waiting period before use.

To participate in the network on Tellor Layer, the basic path described by the official source is to first bridge TRB to that chain and then stake it; the network's principal requirements for participation setup are bridging and staking TRB. There can be up to 100 validators, responsible for transaction validation, consensus, block proposals, and data signing. Reporters, meanwhile, submit values for data requests and monitor accuracy, and can receive TRB rewards. Staking and penalty mechanisms are intended to give reporters and monitors greater economic incentives to focus on data accuracy; specific stake amounts, node operation requirements, and reward details should not be inferred from this overview page.

Yes. To transfer TRB from Ethereum to Tellor Layer, users need an Ethereum wallet holding TRB and a Tellor Layer receiving address, then enter the amount and destination address in the official Hub, approve, and submit the bridge transaction. After the deposit is completed, TRB reaches the Tellor wallet automatically only after a 12-hour security waiting period. To transfer from Tellor Layer back to Ethereum, users connect wallets on both sides and submit a withdrawal request, which also requires a 12-hour wait. The end of the wait does not mean funds have arrived at the Ethereum address: users must also request an attestation and then claim the withdrawal with the Ethereum wallet; funds arrive only after the claim is completed.

The 12-hour bridge wait is a security stage of the process, rather than an ordinary network confirmation time. Deposits are credited automatically when the waiting period ends; withdrawals, however, enter the subsequent stages of requesting an attestation and claiming after the wait. Users should therefore treat “withdrawal submitted,” “waiting completed,” and “claimed on Ethereum” as different states.

Contracts using Tellor data should first provide proof data, the validator set, and signature information to TellorDataBridge to verify that the data came from Tellor; they should then perform checks relevant to their own use case, such as confirming whether the queryId corresponds to the required question, whether the data is stale, and whether the data timestamp satisfies business conditions. These two layers of checks answer, respectively, “whether the data was actually validated by Tellor” and “whether the data can be used for this application.” The former cannot replace the latter: even if data passes authenticity verification at two-thirds of stake weight, the application must still decide its own acceptable freshness, identifiers, and risk parameters.

Tellor's data mechanism relies on multiple stages: reporting, on-chain consensus, validator signatures, and application-side validation. TRB staking and rewards connect participants' economic interests to reporting and monitoring behavior, but they do not eliminate risks such as external data sources, disputes, timeliness, or incorrect application configuration.

Tellor's official documentation can be used to learn about network participation, data integration, and TRB bridging processes. Before bridging in practice, check the wallets, destination address, and transaction steps displayed in the official Hub; developers should refer to the data integration documentation and deployed-contract references.