Last checked
RefreshEstimated news impact scores by coin. Scores are not price-change percentages.
Check failed. Showing saved news from .
Tellor’s security depends on a network of committed participants (validators, reporters, delegators, selectors, and security providers) who lock TRB into the system and assume real operational responsibilities. That commitment deserves full transparency, so we built the Tellor Operator Dashboard: http://operator.tellor.io. Read More: https://tellor.io/blog/introducing-the-tellor-operator-dashboard/
Data manipulation attacks are oracle-agnostic. They’ve hit both centralized and decentralized feeds. Tellor raises the cost through its: • Stake + slash mechanism • Permissionless participation • Full flexibility for users on how they consume the data Safe implementations treat the oracle as one piece of a larger risk model, not the entire security perimeter.
http://operator.tellor.io Tellor’s security depends on a network of committed participants (validators, reporters, delegators, selectors, & security providers) who lock TRB into the system & assume real operational responsibilities. That commitment deserves full transparency, so we built the 'Tellor Operator Dashboard'. Read More: https://tellor.io/blog/introducing-the-tellor-operator-dashboard/
"Oracles can introduce asymmetric information via systemic insider or selective disclosure. A risk seldom talked about." 👇 Read the full article: https://tellor.io/blog/oracles-and-asymmetric-information/
Tellor’s network has two core functions: validating the chain and reporting data. Each has a corresponding roles and they’re designed to be mixed and matched based on what makes sense for you. 📖 https://tellor.io/blog/introducing-the-tellor-operator-dashboard/
A working frontend example: borrow TRB against ETH collateral, using 'Tellor Pull'. The frontend pulls ETH/USD and TRB/USD straight from Tellor, updates the bridge's validator set if it's stale, and hands both attestations to the contract in one call. The contract verifies, checks loan-to-value, and releases funds. 💾 Check out the repo here: https://github.com/tellor-io/SampleTellorUserPull
Tellor’s voting power is split equally across 3 groups: 33.3% users (tips) 33.3% reporters 33.3% team This design carefully balances influence across different network roles instead of pure token weight, raising the cost and complexity of control. Read more: https://tellor.io/whitepaper/
Agents are starting to execute on-chain decisions without a human checking the inputs first. That raises the stakes on where those inputs come from. An agent can't apply judgment about whether a data source is trustworthy the way a person might glance at a chart and https://t.co/lTp47visDn
Need an oracle where the team cannot decide which data is allowed to exist? On Tellor, anyone can tip a query, stake to report it, raise a dispute on-chain, or relay attestations to another chain. None of those roles require approval, and none can be blocked by a trusted intermediary. This is how censorship resistance works in practice.
Need an oracle where the team cannot decide which data is allowed to exist? On Tellor, anyone can tip a query, stake to report it, raise a dispute on-chain, or relay attestations to another chain. None of those roles require approval, and none can be blocked by a trusted intermediary. This is how censorship resistance works in practice.
Introducing the Tellor Operator Dashboard Now Live at: operator.tellor.io Tellor’s security depends on a network of committed participants (validators, reporters, delegators, selectors, and security providers) who lock TRB into the system and assume real operational responsibilities. That commitment deserves full transparency so we built operator.tellor.io. With it every participant, current or prospective, can closely approximate their role costs, what it earns, and whether it makes sense for them before they commit. Understanding your role in Tellor’s security Tellor’s network has two core functions: validating the chain and reporting data. Each has a corresponding roles and they’re designed to be mixed and matched based on what makes sense for you: Validators run the chain infrastructure and earn 25% of network rewards. TRB holders who don’t want to run validator software can delegate their stake to a validator and earn a share of those rewards, minus the validator’s commission. Reporters submit the data the network comes to consensus on and earn 75% of network rewards, a higher share that reflects the greater technical burden and risk reporters carry. TRB holders who don’t want to run reporter software can select a reporter and earn a share of those rewards, minus the reporter’s commission. Security providers do both: they delegate to a validator and select a reporter, paying commissions on each side. The roles are composable. You can be a validator who selects a reporter, a delegator who runs their own reporter, or anything in between. The incentive structure was designed so that validators are encouraged to also run reporters but no combination is required. Every participant, in every configuration, is contributing to Tellor’s economic security. The math behind what that security costs an attacker is documented here. This is a long-term commitment, by design. When you stake TRB, rewards are added to your stake and locked for 21 days. Unstaking also takes 21 days. Your TRB is not liquid while it’s securing the network, that’s what makes the security meaningful. Use the modeler tab to model your numbers before you commit. What is it? Running infrastructure on Tellor means managing stake, commissions, reporting liveness, inactivity penalties, and dispute penalties. Until now, that math lived in spreadsheets, CLI queries, and rough back-of-the-napkin estimates. The dashboard pulls Tellor’s Mainnet and Palmito Testnet chain state and layers it with role specific tooling so you can evaluate your position clearly. A live ticker with network context (mint rate, validator/reporter power, block timing, and more) Planning scenarios tuned to your role and inputs Per-address rewards with claim history and pending balances Formula reference so every number on the site is explainable Quick links to docs, explorer, governance, and the dispute portal Feature spotlight 1. Modeler: Model before you commit The Modeler tab answers: If I run this setup, what does it cost and what do I actually make? Pick your role (Validator, Delegator, Reporter, Selector, Security Provider) then tune inputs against live chain state: Self-stake and external delegations/selections Commission rates Reporting liveness Infrastructure and API costs in USD Gas costs TRB price for cost conversion You get profit per day and annualized, with breakdowns by reward source so you can find your breakeven point, stress test different commission and liveness scenarios and decide which level of rewards justifies the security commitment you are making. Sliders and assumptions stay tied to what’s on-chain currently. Use it when you’re evaluating a new validator, debating reporter vs. selector economics, or pressure testing your setup before going live or changing how you operate. 2. Tracker: One address, full picture The Tracker tab is for operators who already have skin in the game. Enter any Tellor address (tellor1…) and see paid and pending rewards by source such as staking, reporting, commissions, tips, and related flows. Filter by 1d / 7d / 30d / lifetime, export CSV for accounting or taxes, and copy CLI commands when you want to verify or claim on your own node. Use it when you need a clear answer to “what did this address earn, and what’s still sitting unclaimed?” Built for transparency Every number ties back to the Formulas tab: assumptions, steps, and definitions so nothing is a black box. The Reference section helps you jump from economics back into operations: docs, explorer, hub, feeds, etc. Try it Head to https://operator.tellor.io/ and open Modeler or Tracker depending on whether you’re planning or reconciling. Questions, bugs, or feature ideas? Drop them in the discord. This is a living dashboard and will evolve as Tellor economics do. Tellor’s security is built on participants who understand what they are signing up for and are able to make informed decisions throughout their journey. The Tellor Operator Dashboard enables its users to do just that.
Introducing: The Tellor Operator Dashboard Now Live at: operator.tellor.io Tellor’s security depends on a network of committed participants (validators, reporters, delegators, selectors, and security providers) who lock TRB into the system and assume real operational responsibilities. That commitment deserves full transparency so we built operator.tellor.io. With it every participant, current or prospective, can closely approximate their role costs, what it earns, and whether it makes sense for them before they commit. Understanding your role in Tellor’s security Tellor’s network has two core functions: validating the chain and reporting data. Each has a corresponding roles and they’re designed to be mixed and matched based on what makes sense for you: Validators run the chain infrastructure and earn 25% of network rewards. TRB holders who don’t want to run validator software can delegate their stake to a validator and earn a share of those rewards, minus the validator’s commission. Reporters submit the data the network comes to consensus on and earn 75% of network rewards, a higher share that reflects the greater technical burden and risk reporters carry. TRB holders who don’t want to run reporter software can select a reporter and earn a share of those rewards, minus the reporter’s commission. Security providers do both: they delegate to a validator and select a reporter, paying commissions on each side. The roles are composable. You can be a validator who selects a reporter, a delegator who runs their own reporter, or anything in between. The incentive structure was designed so that validators are encouraged to also run reporters but no combination is required. Every participant, in every configuration, is contributing to Tellor’s economic security. The math behind what that security costs an attacker is documented here. This is a long-term commitment, by design. When you stake TRB, rewards are added to your stake and locked for 21 days. Unstaking also takes 21 days. Your TRB is not liquid while it’s securing the network, that’s what makes the security meaningful. Use the modeler tab to model your numbers before you commit. What is it? Running infrastructure on Tellor means managing stake, commissions, reporting liveness, inactivity penalties, and dispute penalties. Until now, that math lived in spreadsheets, CLI queries, and rough back-of-the-napkin estimates. The dashboard pulls Tellor’s Mainnet and Palmito Testnet chain state and layers it with role specific tooling so you can evaluate your position clearly. A live ticker with network context (mint rate, validator/reporter power, block timing, and more) Planning scenarios tuned to your role and inputs Per-address rewards with claim history and pending balances Formula reference so every number on the site is explainable Quick links to docs, explorer, governance, and the dispute portal Feature spotlight 1. Modeler: Model before you commit The Modeler tab answers: If I run this setup, what does it cost and what do I actually make? Pick your role (Validator, Delegator, Reporter, Selector, Security Provider) then tune inputs against live chain state: Self-stake and external delegations/selections Commission rates Reporting liveness Infrastructure and API costs in USD Gas costs TRB price for cost conversion You get profit per day and annualized, with breakdowns by reward source so you can find your breakeven point, stress test different commission and liveness scenarios and decide which level of rewards justifies the security commitment you are making. Sliders and assumptions stay tied to what’s on-chain currently. Use it when you’re evaluating a new validator, debating reporter vs. selector economics, or pressure testing your setup before going live or changing how you operate. 2. Tracker: One address, full picture The Tracker tab is for operators who already have skin in the game. Enter any Tellor address (tellor1…) and see paid and pending rewards by source such as staking, reporting, commissions, tips, and related flows. Filter by 1d / 7d / 30d / lifetime, export CSV for accounting or taxes, and copy CLI commands when you want to verify or claim on your own node. Use it when you need a clear answer to “what did this address earn, and what’s still sitting unclaimed?” Built for transparency Every number ties back to the Formulas tab: assumptions, steps, and definitions so nothing is a black box. The Reference section helps you jump from economics back into operations: docs, explorer, hub, feeds, etc. Try it out Head to https://operator.tellor.io/, and open Modeler or Tracker depending on whether you’re planning or reconciling. Questions, bugs, or feature ideas? Drop them in the discord. This is a living dashboard and will evolve as Tellor economics do. Tellor’s security is built on participants who understand what they are signing up for and can make informed decisions throughout their journey. The operator dashboard empowers its users to do just that.
Tellor Pull: A New Way To Use Tellor Tellor's newest evolution (Tellor Layer) has afforded the core team the flexibility to build new ways users can integrate Tellor. While the traditional push implementation is still the default use-case, Tellor Pull introduces an added layer of efficiency, allowing the value your protocol cares about to be fetched directly upon the user interaction on a consumer-facing app. Cryptographically attested from Tellor, verified in the same transaction, and applied immediately. Tellor Pull does not remove the need for honest reporting on Tellor. It changes when and how that reporting becomes binding for your EVM contract: at the moment of the user call, with proofs attached. What Tellor Pull enables User-driven freshness. The caller brings the latest attested report and validator signatures from Tellor into the transaction. The contract does not trust a cached storage slot; it verifies attestations through Tellor’s DataBridge and then executes the logic (lend, repay, liquidate, or settle) in one atomic step. Verification without a separate update tx. There is no standing requirement for “someone must run updateOracle() before function works.” The pull path bundles “prove this report” and “use this report” into one atomic transaction. Tellor → EVM as a deliberate bridge. Tellor remains the source of truth for reports and validator sets. The DataBridge on your EVM chain is the trust anchor that checks signatures and policy. Tellor Pull is the pattern that connects those two layers at transaction time instead of relying on a lagging mirror in storage. Where Tellor Pull fits best (use cases) Tellor Pull is aimed at protocols where the oracle read must be inseparable from the state change: Lending and borrowing - Collateral and debt math should use the price valid when the user borrows or repays, not when a keeper last wrote storage. Stablecoins and pegged assets - Mint/redeem and collateral ratio checks benefit from not splitting “fetch price” and “mint” across blocks. Cross-chain and bridge-adjacent flows - Any flow where Tellor attestations must match EVM execution without an extra relay hop for the data itself. If your app only needs a rough index updated once a day, push or cached reads may still be enough. If a single block of staleness can change who wins economically, Tellor Pull is the better default mental model. Why this matters: For builders, pull shifts oracle integration from “maintain storage freshness” to “attach proofs when the user acts.” Product flows become simpler to explain: connect wallet, pull latest acceptable report, transact. For auditors, the important question becomes: which report type and freshness rules does this integration enforce before submit, and do those match what the contract assumes on chain? Explicit modes and typed non-success results make that boundary easier to review than ad hoc fetches and silent fallbacks. For users, the win is indirect but real: fewer failed txs and less dependence on invisible keeper infrastructure to make basic protocol actions work. A push-style integration asks: "What number is in this contract slot?" Tellor Pull asks: "Can you prove this is the report Tellor attests right now—and if so, run my logic." Same reporters, same Tellor, different usage method for your protocol. Going deeper For integration steps, APIs, sample contracts, and deployment notes, use the following open-source references: Sample Integration guide: SampleTellorUserPull (w/ end-to-end borrow example) Library: tellor-io/UsingTellorPull (npm usingtellorpull) Documentation: Tellor docs Tellor Inc. — questions and contributions welcome on GitHub or Discord.
Tellor Rewards Have Fully Transitioned to Tellor Layer — Here's What That Means Tellor has reached a pivotal milestone: reporter rewards have fully transitioned to Tellor Layer. If you're a reporter still operating on legacy Tellor (Tellor 360) on Ethereum, this is your signal to migrate. From this point on, Tellor Layer will be referred to as simply, Tellor. We know this is an adjustment but moving forward when we say 'Tellor', we mean the Tellor Layer chain. What Changed Previously, Time-Based Rewards(TBR) were distributed through the legacy Ethereum-based system. With this transition complete, all reporter rewards are now issued directly on Tellor — the purpose-built, oracle blockchain that powers Tellor's next-generation oracle infrastructure. This means reporters are no longer dependent on legacy Tellor for their incentive loop. Reporting, validation, and compensation now live entirely within Layer's consensus environment, reducing latency, cutting out bridging complexity, and aligning incentives more tightly with Tellor's own security model. Why This Milestone Matters Reward distribution is central to any genuinely decentralized oracle network. Completing this transition onto Tellor means faster settlement within Tellor's own block times, lower overhead with no Ethereum gas costs for reward claims, and tighter security alignment, validators and reporters are now economically grounded in the same chain they're securing. But what it means practically depends on who you are: TRB holders You can now participate in securing the network directly. By delegating your TRB to validators and reporters on Tellor, you become a Security Provider, earning rewards while strengthening the chain's economic security. This is a new and meaningful role that didn't exist in the legacy system. Reporters If you're still staking on legacy Tellor on Ethereum, now is the time to migrate. The steps: unstake from legacy Tellor, bridge your TRB over to Tellor, then choose your role as Validator, Reporter, or Security Provider. Rewards are no longer issued on Ethereum. They live entirely on Tellor now, so staying on legacy means leaving incentives on the table. Protocols and integrators If your protocol was immutably deployed on legacy Tellor, your data feeds will continue to work, that won't change. However, with Time-Based Rewards no longer available on Ethereum, tipping becomes the primary mechanism for incentivizing reporters on legacy Tellor. If your protocol depends on fresh, reliable data, you should plan for tipping to ensure reporters have a reason to serve your feeds. Legacy Tellor continues to operate; it just requires active demand signaling now rather than passive reward distribution. Across all three groups, the common thread is the same: the protocol's economic activity has a single home now, and it's Tellor. The Bigger Picture for Tellor Tellor was built to serve as a sovereign oracle chain — one that can settle disputes, issue rewards, and govern itself without relying on any single L1 as a crutch. The rewards transition is one of the last major pieces needed to demonstrate that the chain can operate autonomously end-to-end. This is meaningful for data consumers too. As more of the protocol's critical paths move on-chain to Tellor, the trust surface becomes more auditable and verifiable. Developers integrating Tellor data can increasingly reason about the system's behavior from first principles, without needing to track the state of multiple off-chain systems. What's Next Upcoming milestones are focused on feedback received from the community, including improved timing for Reporter switching for Selectors, guardrails to prevent validators to accidentally grow over 30%, revisiting penalties and timeframes for validator jailing, expanding query support, deepening validator tooling, and continuing to grow the reporter set as Tellor's economics become more compelling. For anyone participating in the Tellor ecosystem — whether as a reporter, a TRB holder, or a protocol integrating oracle data — this is a good moment to pay attention. The system is converging, and the incentives are finally where they need to be. Follow Tellor's development on GitHub, & join the discussion on Discord.
Security is a shared effort and if the security layer fails, nothing else matters. Tellor joined the Ethereum Security QF round, giving every team member $200 USDC to fund the projects they believe in most. We can't afford to be neutral on security and neither can you. Round closes tonight. @thedaofund @Giveth
Coinbase Suspends ENS, ORDI, RAY Perpetual Futures and More Coinbase has suspended trading for multiple perpetual futures and automatically settled all open positions. Affected contracts include TRB, RARE, NEIRO, A, ME, XTZ, KMNO, RAY, STX, ENS, GMT, SNX, 1000FLOKI, 0G, ORDI, NIL, BIO, UMA, BEAM, INIT, SOMI, EGLD, CLANKER, SOPH, and BIGTIME. The platform said the move aims to streamline its derivatives lineup and improve market liquidity and quality.https://x.com/CoinbaseMarkets/status/2046583600632488142
dYdX Governance Proposal 374 has passed, approving the wind down of the JASMY-USD, KOMA-USD, LINEA-USD, ME-USD, NEIRO-USD, PIPPIN-USD, RAY-USD, TRB-USD, TRY-USD, USDE-USD, YFI-USD, and ZEREBRO-USD markets; the proposal received 91.07% YES votes.
🪇 Tellor Layer Mainnet is live! 👇 Watch a tl;dr of today's dev call: https://t.co/TzR11CAcG1
"As Tellor Layer moves closer to completion, sharing our ADRs[Architecture Decision Records] openly becomes vital. It allows the community, potential contributors, and stakeholders to engage deeply with the technical foundations of the project." 📖Read more: tellor.io/blog/introduci…
Swap safer with 1inch and @Trezor hardware wallets. Trezor users now get in-wallet access to 1inch Swap—with zero gas fees and MEV protection as standard. Another top partner integrating 1inch APIs to unite DeFi. Find out more 👀 blog.1inch.io/1inch-swap-api…
161 years after the Battle of Chickamauga—a testament to resilience, determination, and growth—we prepare for Chickamauga Testnet. Soon, we take the next step in building a stronger Tellor Layer. Stay tuned and get ready for what’s ahead!
What if your smart contracts could tap into offchain data as easily as streaming your favorite playlist? Now they can, thanks to our latest partnership with @WeAreTellor Here's the TL;DR 👇 Tellor has deployed its contracts on Lisk, giving you access to a fully decentralized…
Tellor is now deployed on @base Mainnet! Our decentralized oracle network is expanding to bring secure, permissionless data to the Base ecosystem. 🛡️ Developers on Base can now integrate censorship-resistant data feeds into their dApps. Get Started: docs.tellor.io…
Showing 50 of 82 stories · Page 1 of 2. Filters apply to the full news archive.