<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tellor Core on Medium]]></title>
        <description><![CDATA[Stories by Tellor Core on Medium]]></description>
        <link>https://medium.com/@tellor?source=rss-3d2211a8ac6b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*losCEos6N68CYQZ0JBBaag.png</url>
            <title>Stories by Tellor Core on Medium</title>
            <link>https://medium.com/@tellor?source=rss-3d2211a8ac6b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:07:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tellor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tellor Security 201 — Updated]]></title>
            <link>https://tellor.medium.com/tellor-security-201-updated-d5ee5de7985b?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5ee5de7985b</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Thu, 17 Mar 2022 17:43:17 GMT</pubDate>
            <atom:updated>2022-03-17T17:43:17.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3w9UjZmB81OSCowNXVa-bA.png" /></figure><p><strong>Tellor Security 201 — Updated</strong></p><p>The Tellor oracle is a decentralized network of reporters dedicated to providing data to various chains. Having been live for several years now, with several upgrades, Tellor has become quite the robust system, consistently driving towards decentralization and security. This article should give you a solid understanding of the current crypto-economic guarantees underlying the system and even the best ways to attack it and how much it will cost.</p><p><strong>A Primer On Blockchain Security</strong></p><p>Looking at the best projects in the cryptosphere, ‘security’ isn’t defined by a single feature or one line of code, but by an aggregate of several attributes designed to prevent any potential misuse of the network and any tangent attack vectors. Before we jump into Tellor’s system, we’re going to clarify some pieces about blockchain security in general, notably on L1s or L2s like Ethereum that we’re built on, so we can clearly differentiate between attacks on Tellor vs attacks on the base protocol layer, both of which would shut down Tellor.</p><p><strong>Lack of Finality</strong></p><p>Ethereum isn’t fast. It’s faster than Bitcoin, but in general, blockchains are inherently slow compared to centralized systems. This is because in order for the state of the network to reach consensus, it is generally recommended to wait for a certain amount of confirmations. Even when the block-time is faster, waiting for several blocks to be added successfully (confirmations) will always be slower than a centralized system. Taking Ethereum for example, according to the whitepaper seven confirmations should be enough to confirm the transaction (about 2 minutes). On first pass this doesn’t sound too unreasonable, but oftentimes exchanges and others who want to be really sure will wait for over 30 confirmations!</p><p>This means that if you have an application that needs to run real time on Ethereum and will make updates according to the change in state, each change in state opens an attack vector. In the long run, you introduce a lot of risk because executing in real time can lead to unexpected or unwanted outcomes . It’s the nature of this decentralized space that we need to acknowledge more, especially in DeFi. Transactions just take time and if you want to leverage a distributed consensus network, you will have to be patient.</p><p>This is important for oracles because speed is always of concern. People want the price of X and they want it very quickly (similar to what they are used to in web 2.0 with instant connectedness, instant gratification, etc). The problem is that oracles, (even centralized ones) won’t be “finalized” to the off-chain viewer until well after it’s real time. As we’ll see with Tellor and with base layer protocols, security and time cannot be separated. There hasn’t been a solution to the “scalability trilemma” and making a secure and decentralized system comes at the price of speed.</p><p><strong>The dreaded 51% attack</strong></p><p>As a quick review, a 51% attack occurs when a miner/validator (or group of them) controlling more than 50% of the network can abuse the system by</p><p>1. Preventing new transactions</p><p>2. Reversing old transactions</p><p>3. Adding new transactions that aren’t valid (e.g. printing Ether)</p><p>Basically it’s the cost to produce every block for a certain period of time; this is why the cost to 51% attack is measured in dollars/time or cost to break for 1h, 1 day, etc. This is critical for oracles (or any smart contract on Ethereum), because mining every block on Ethereum doesn’t always lead to reversions or forks. The more nefarious attack for a system is simply not allowing certain transactions to go through, namely price updates or calls to our oracle contract. The reason it’s so dangerous is that Ethereum as a whole would still function, your app would just be inaccessible and stale. <strong><em>This means that no matter how secure your on-chain oracle is, if the base chain you are on is controlled by one group of people, they can prevent you from updating your oracle.</em></strong></p><p>If you had to guess how much it would cost to successfully perform a 51% attack on Bitcoin today, you’re probably thinking of some ridiculous amount. This is, however, not the case at all. In fact, relatively speaking, it’s quite cheap to perform a 51% attack on Bitcoin. When we think of most protocols that are built on top of layer 1 protocols, such as Bitcoin or Ethereum, you can actually come up with an estimated cost to successfully attack that protocol based on several factors, including market cap, hash rate, miner costs, block-time, etc. For example, the cost to successfully conduct a 51% attack on Bitcoin’s network for one hour (or 6 blocks) in March of 2022 is about $1,512,736. This is with a market cap of $773 Billion, making the cost 0.0002% of the market cap to break Bitcoin for an hour. If you want to look at the estimated cost to break other protocols, you can visit <a href="https://www.crypto51.app/">Crypto51’s website</a> for more information. To save you the trip, the cost to break ETH is roughly the same as BTC and the cost to break BSV for an hour is a mere $3,000. So if you have a smart contract on Ethereum that needs a price update within 5 minutes, it only costs someone $126k to completely guarantee that you don’t get an update.</p><p><strong>Cost to Break Analysis</strong></p><p>There are three ways to break Tellor:</p><p>· Break Ethereum or prevent contract calls to Tellor</p><p>· Vote an incorrect disputed value as correct</p><p>· Stall the Tellor system so it becomes unusable for customer needs (<em>by disputing all values or by reporting all bad values</em>)</p><p>The first avenue to break Tellor has been explored above in the 51% attack of a network. But the second and third paths to successfully attack and break the Tellor oracle are determined by several factors:</p><p>· P = Price of Tellor TRB tokens (assume USD)</p><p>· MC = Market Cap of Tellor</p><p>· Average time in between blocks in the Tellor system.</p><p>· SA = Staking amount for reporting (currently 100 TRB)</p><p>· VS = Voting Share of honest tokens</p><p>· CTB = Cost-to-Break</p><p><strong>Cost to Break a Tellor Vote</strong></p><p>For the vote, multichain Tellor has moved beyond just a simple token weighted vote. The cost to break the vote is a little bit more complicated now than just 51% of the market cap. For Tellor systems on various chains, the governance system set up is based on the input of four different stakeholders in the Tellor system:</p><ul><li>Token holders on that chain (H)</li><li>Reporters (R)</li><li>Users (U)</li><li>The Tellor core team (T)</li></ul><p>Assuming equal weightings (as is currently the case), the cost to break (CTB) the network is:</p><p><em>CTB = min(2)(CTB(H),CTB(R),CTB(U),CTB(T))</em></p><p>or simply <strong>the cost to break two of the four individual pieces</strong>.</p><p>To calculate out each individual piece next, we’ll start with breaking the token holder portion:</p><p><em>CTB(H) = VS * MC</em></p><p>This means that if you buy up enough votes to 51% attack the voting system, you can potentially break a dispute vote on Tellor. This is why community is everything for Tellor. It’s very important for the system to have a high percentage of its community voting in order to stave off parties trying to vote bad values through. Unfortunately for an attacker, even just breaking a simple vote doesn’t break Tellor; Tellor has a caveat of multiple dispute rounds. This means that if a vote goes in favor of the attacker, any participant can pay to challenge the vote outcome . This process goes on ad-infinitum as the system will need to repeatedly vote and hopefully get more and more votes to beat the attacker. Therefore, the only way that a party will be able to actually break Tellor is if they gain 51% of the tokens in the Tellor system and are able to break a second stakeholder vote.</p><p><em>CTB(R)= VS * (# Reports all time on system)</em></p><p>For each new report (data submission) on Tellor, the reporter is rewarded a non-transferrable “reporter token” that allows it to vote in Tellor governance. The token is non-transferrable, but a smart contract wrapper over the reporter could be used to enable transferability. If this were the case (we have yet to see any evidence of this), the cost to break this piece of the vote would be the cost to buy 51% of the reporter tokens. If the wrappers are not present, the cost to gain 51% of these values would be the cost to report 51% of the values on the network (assuming full voting by historical reporters). If the reporters do not have a high voting share, you could report less. To formalize this:</p><p>CTB(R) = Voting Share(Reporters) * (Gas cost per report * (# of reports on system+1))</p><p>For example, if at the time an attack is initiated there are 10,000 reports by voting reporters on a Tellor system, the attacker would need to report 10,001 additional reports to gain 51% of the reporter vote. As with the CTB(H) piece, you would need to maintain this ratio (reporting 1 for 1 with honest voting reporters) over the various rounds of disputes.</p><p>For the next piece, the cost to break the user set is formalized as:</p><p><em>CTB(U) = VS* (Cost to Bribe user set)</em></p><p>In the Tellor system, the governance contract can vote on a “user set”, or a list of users/protocols who rely on the Tellor system. Adding and removing new users is done through the governance system and this array of users represents 25% of the voting share. Granted, users do not have to be a part of the user set to use Tellor, however for users wishing to have a say in the governance process, they should request to join via a governance proposal. The cost to break this set is simply the cost to bribe 51% of the users in the set or to double the size of the user list adding malicious users. The latter should be unlikely given a functioning and watched system, however the first may have a price. The users in this set will have smart contracts that rely on Tellor, so they would likely not want the system to go under, however bribes can happen even if the cost is high. As with all bribe costs, it’s relatively unknown if the number is feasible or if the bribe costs are simply impossible. That said, this portion of Tellor’s governance represents a piece of governance where hopefully those using Tellor are likely to preserve it.</p><p>The last piece is the cost to break the team’s voting share:</p><p><em>CTB(T) = Cost to bribe/compromise Tellor Team account</em></p><p>This portion is pretty simple. Obviously it’s just the cost to hack or buy off the core Tellor team. Currently it represents 25% of the voting power, however the plan is to reduce this amount over time as the other user’s voting share continues to go up. Since Tellor is deployed on different chains, the governance on one-chain does not affect the governance on another chain, so the reduction of team voting share on one chain will not mean that all chains will be reduced equally. As better voting tools, delegation strategies, and community efforts come into effect, the cost to break Tellor via a voting attack will be drastically reduced.</p><p>Overall, the cost to break a vote in our mind seems both unfeasible and also unnecessary. Most protocols will use Tellor in such a way that they will not even rely on the final vote of a system to matter. They will simply use a value and if it gets disputed, they will just request it again and use the next value. For these reasons, other attack vectors may play more of a role.</p><p><strong>Cost to Stall Tellor — Mining Bad Values</strong></p><p>Depending on how protocols use Tellor, stalling the Tellor system is likely the most viable attack vector. Similar to breaking BTC or ETH, the cost to break Tellor via stalling is measured in time, so CTB/hr or CTB/day. If a user requires a query every 10 minutes, a party will just need to break (or stall) Tellor for 10 minutes and then they succeed in the attack. Education of users on waiting for several confirmations is key to preventing a stalling attack. Just as building things that should be realtime on Ethereum is a bad idea, it’s also a bad idea on Tellor, so making sure that projects build the right kind of projects for utilizing Tellor (and a given network in general) is the first and probably most important security measure we can take.</p><p>Here’s how we calculate the cost to break Tellor for one block. Staking (and value of the TRB token) gives the Tellor oracle network its real security. The formula is simple:</p><p><em>CTB/ Block = Cost of submission + Cost of staking</em></p><p><strong>Cost of Submission </strong>= The gas or transaction costs on a given network. This is minimal compared to staking costs on most networks, however as speed becomes an issue, it can factor in on more expensive networks.</p><p><strong>Cost of Staking = </strong>staking requirement. Currently on Polygon (and for other near instantaneous chains), the stake amount is 10 TRB, however this is a customizable amount for each chain. The faster the chain, the lower the stake amount can be. An important concept to note is that <em>faster block-times on a chain mean increased security Tellor.</em></p><p>If you want to stall Tellor to prevent any values from getting through, you would have to report a value theoretically every block. In reality, the way it would work is that someone would put up a bad value, get disputed, put up another bad value, get disputed, and so on. Basically if at any point in the process, someone submits a good value, they would need to dispute the good value. However, assuming parties are actively monitoring and ready to dispute, reporting every block (so no one can submit a good value) is insanely expensive with Tellor’s model. A more practical choice would just be to dispute all values coming through.</p><p><strong>Cost to Stall Tellor — Disputing All Values</strong></p><p>The other option to stall Tellor is to simply dispute every block. The current cost to dispute is hardcoded for each Tellor deployment and then goes up based on either the number of dispute rounds for a specific dispute or the number of disputes on a given query ID:</p><p>baseFee = base dispute fee (currently 1 TRB on polygon)</p><p>openDisputes = number of open disputes on a given query ID</p><p>voteRounds = vote Round number for given dispute</p><blockquote>if (voteRounds == 1) {</blockquote><blockquote>_fee = baseFee * 2**(openDisputesOnId- 1);</blockquote><blockquote>} else {</blockquote><blockquote>_fee = baseFee * 2**(voteRounds- 1);</blockquote><blockquote>}</blockquote><blockquote>_fee = min(_fee, stakeAmount)</blockquote><p><em>In plain English, the cost to dispute is the base dispute Fee, but it doubles with each open dispute on that queryID. The cost to dispute a vote result also doubles each time. The max cost of the dispute Fee however is the stake amount.</em></p><p>The reasoning for this is that we want initial disputes to be cheap, however if someone is trying to spam the system with disputes, they should have to pay more. Since anyone can simply buy more TRB and re-stake, the cost is capped at the stakeAmount. In the future, liquid markets for borrowing TRB will make the ability for new stakers to simply borrow (or buy) new TRB at a cheap rate since each time they would be disputed will lead to a doubling of their stake (the dispute fee goes to the wrongly disputed reporter). This incentive would mean that as long as the voting mechanism is secure, parties will rush to stake new reporters and report on that queryID in the case of a censorship via disputes.</p><p>Therefore, to simplify it, the cost to break Tellor via disputes is similar to the cost of breaking it via submitting every value:</p><p>CTB / hr= StakeAmount * blocks / hour</p><p>On Polygon for example (2 sec blocks) and assuming a $20 price (currently, this would be:</p><p>10 TRB * 20$ * 1800 blocks per hour = $360,000 / hr which puts Tellor at the same cost to censor as Ethereum a few years ago. Strategies such as using multiple queryID’s, allowing for very long delays, or even making a censorship strategy unprofitable from the users side can greatly increase the security as well.</p><p><strong>Conclusion</strong></p><p>So it costs a lot to break Tellor. If you’re actually talking about getting bad values on chain, it’s going to cost you in the tens of millions of dollars to break the voting and will cost you $360,000/ hr to report bad values or dispute all values for a given ID. The Tellor network is secure for participants who use the lack of finality in the system properly, allow for disputes to settle and for proper wait time(or confirmations) between reports if the system comes under attack. The best way to protect your protocol is by acknowledging its vulnerabilities and adding processes to mitigate risks. A good design and transparent, measurable security of its own and third party components are only a few of the key items to consider.</p><p><em>If you need data in your smart contracts and you’re thinking about using Tellor, reach out to </em><a href="https://discord.gg/DxSG2bPECw"><em>Discord</em></a><em> and we’d be happy to discuss the pros and cons as well as the necessary steps to building a robust data feed for your system.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5ee5de7985b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tellor Returns To EthDenver]]></title>
            <link>https://medium.com/tellor/tellor-returns-to-ethdenver-3c7354374fcc?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c7354374fcc</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 23:45:26 GMT</pubDate>
            <atom:updated>2022-02-03T16:17:37.796Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvgM_tNkC-DwD95ZhebyeQ.png" /></figure><h3>We Can’t Wait!</h3><p>While this year’s conference in the Mile High City holds special importance for many simply due to the fact that it is the first major in person event since before the pandemic, and a community favorite, and as such is feeding an immense hunger we can all relate to — hanging out with like-minded people! It’s especially important for us as well. This will be the first major in-person event that Tellor sponsors and has a large presence at. In fact we are flying out the majority of our team to participate.</p><p>Other than Devcon (remember those??) EthDenver is many of the team’s personal favorite as far as events in the space go. The last two we attended was in 2018 and 2019, and Tellor was either non-existent or had just launched during those. So, it is with immense pride that we return with 2 years of mainnet experience under our belts, some blue-chip user integrations, and a talented and tight knit team.</p><p>Other than meeting old friends and making some new ones, we are excited to meet this new crop of builders/hackers and help in any way we can. We have a good bit of experience as participants at hackathons (Tellor started out as a hack!) and as a team of battle-tested and experienced developers and bizdevs.</p><p>That said, we have some tips for you guys who are attending their first EthDenver. And we’ll follow that up with everything you’ll need to know to integrate Tellor’s Oracle into your hack projects.</p><h3>Tips on how to get the most out of your EthDenver experience:</h3><ul><li><strong>Be open minded to other ideas</strong> — working on someone else’s idea and new protocol</li><li><strong>Build on one of the sponsored projects</strong> — cuz they’re there! This is the perfect opportunity to get direct and enthusiastic support. We’ll have a sponsor table and hope to help everyone we can.</li><li><strong>Focus on building relationships</strong> — Don’t be shy! Who you meet can be more important than even finishing your projects on-time. Your project may not be more than a weekend hack, but the relationships you make can launch a career.</li></ul><h3>Everything you need to know to use Tellor in your project:</h3><ul><li>Tellor is a permissionless network of staked reporters who compete to provide your data and earn rewards. Bad actors are punished by anyone willing to pay a dispute fee.</li><li>We’re live on Ethereum mainnet and Polygon. If you need an oracle on another network, talk to us!</li><li>You can think of Tellor as a question and answer machine. “What is the current price of Dogecoin in USD?” or “What was the average temperature in Denver, Colorado yesterday in degrees Fahrenheit?”. Reach out to the team for help forming your query, or see the <a href="https://github.com/tellor-io/dataSpecs">dataSpecs repo</a>.</li><li>It’s easy to install Tellor’s <a href="https://github.com/tellor-io/usingtellor">oracle user contracts</a> into your project with `npm install usingtellor`. Then you can import the UsingTellor contract into your own contract to start retrieving data.</li><li>If you want a test oracle to play around with, try out Tellor’s <a href="https://github.com/tellor-io/TellorPlayground">Playground</a>.</li></ul><p>How to get in touch with us before/during/after EthDenver:</p><ul><li>Joining our Discord is the #1 way to get the best get supported and build a relationship with the Tellor team and community. <a href="https://discord.gg/asf4EHaVGm">https://discord.gg/asf4EHaVGm</a></li><li>If you’re hacking in person, Tellor is sponsoring EthDenver this year and so we’ll have a booth and plenty of team around to talk with you, just swing by the 3rd floor.</li><li>Follow Tellor on Twitter our DMs are open: <a href="https://www.twitter.com/wearetellor">https://www.twitter.com/wearetellor</a></li></ul><p>Remember — you’re only as decentralized as your data. And Tellor is the most secure way to put any real-world data onchain. We can’t wait to see what creative ways you integrate our data into your projects. Until then!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VskjC5tY9mX13pE2" /></figure><p>PS. Applications are still open if you haven’t registered yet!</p><p><a href="https://www.ethdenver.com/"><strong>https://www.ethdenver.com/</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c7354374fcc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/tellor-returns-to-ethdenver-3c7354374fcc">Tellor Returns To EthDenver</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Deploy Tellor on an EVM Chain]]></title>
            <link>https://medium.com/tellor/how-to-deploy-tellor-on-an-evm-chain-c0243c60a98f?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0243c60a98f</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Fri, 21 Jan 2022 22:00:29 GMT</pubDate>
            <atom:updated>2022-01-21T22:00:29.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f4jUpRqVTHuKGnTMoccbBQ.png" /></figure><p>So, your EVM chain is all ready to go, but one key component is missing…</p><p>…a decentralized oracle!</p><p>Well, you’re in luck because the oracle experts at Tellor have released a version that can now be implemented on any EVM compatible chain!</p><p><strong>Here is a guide on how to spin up your own version of Tellor:</strong></p><p>First, let’s start off with the basics to see if Tellor is even a good fit for your chain:</p><p><strong>How Tellor Works</strong></p><p>Tellor is an oracle protocol built to enable maximally decentralized data feeds to any chain. To read the full whitepaper on how it works head here: <a href="https://docs.tellor.io/">https://docs.tellor.io</a> .</p><p>For a quick refresh, let’s go over the basics:</p><p>- A “reporter” deposits some amount of money(tokens) in a contract</p><p>- They can then post data on-chain through the Tellor contract (it can be anything, e.g. BTC/USD price feed, fantasy football scores, transaction details from another chain, etc.)</p><p>- If the reporter lied, anyone can pay a dispute fee to challenge the submission (if they lied, they get slashed, if not they get the fee). It’s up to a governance contract (e.g. a vote) to determine the validity.</p><p>- Once the user thinks enough time has passed waiting for disputes (or if they check it themselves some way), they use the data.</p><p>To give a more concrete example:</p><p>- Harry &amp; Justine want to bet on the price of a <a href="https://makersplace.com/3fmusic/zenith-1-of-1-79761/">rare Shakira NFT.</a></p><p>- Luckily for them, Harry’s stepson, Cody, is a shadowy super-coder and knows about an exciting new chain that just launched Tellor. He writes smart contracts for fun when he’s not working his day job, so he offered to help them out.</p><p>- Cody writes them a contract where they both deposit some <a href="https://www.liquity.org/">LUSD</a> and then it locks itself for two weeks. If the price of the NFT goes up, Harry gets the pot and vice-versa.</p><p>- Upon completion, they call a function to “tip” a few bucks to the query for this data, and then they wait. Within a few minutes (they’re on some blazing fast chain), a Tellor reporter sees the request and posts the change in price over the two weeks.</p><p>- It’s not looking good for Harry’s bet, but that’s besides the point. There’s nothing he can do to stop the contract. They wait an hour for disputes and Harry knows that if he makes a false dispute, someone else will just report it and he’ll still lose money, so his schemes are futile. Justine wins the bet and lives happily ever after :)</p><p>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;This is the power of Tellor&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;</p><p><strong>Deploying Tellor</strong></p><p>So how do you become that exciting new chain?</p><p>Launch the following smart contract: <a href="https://github.com/tellor-io/tellorFlex">https://github.com/tellor-io/tellorFlex</a> (it has a hardhat deploy script, but it’s just one contract, so it shouldn’t be too difficult)</p><p>You’ll need four constructor arguments:</p><p>1. governance address</p><p>2. staking token</p><p>3. stake amount</p><p>4. reportingLock</p><p>For choosing the governance address, you can of course just launch it with a single address, but this would be akin to having all of the disputes and variables managed by one address, so we suggest you don’t do this in production (sort of defeats the whole “decentralization” thing).</p><p>A recommended solution would be to either use a prebuilt one (e.g. our<a href="https://github.com/tellor-io/polygonGovernance"> polygon governance contract</a>) or you can write your own.</p><p>**Know that the governance address is in charge of the validity of disputes (slashing reporters if necessary), and changing the final two variables (stakeAmount and reportingLock)**</p><p><strong>On choosing the staking token:</strong></p><p>This is a super cool part of Tellor…you don’t even have to use TRB! Of course it would be great if you do and would likely get you support from the current reporter set that holds TRB, but if you don’t have a bridge from Ethereum or dislike us for some reason, you’re more than welcome to use any ERC20 coin.</p><p><strong>For choosing the staking amount and reporting lock, they’re based on several things:</strong></p><p>a) What token you pick as your staking amount (the amount will be in that token)</p><p>b) How fast the chain is</p><p>c) Balancing the desire for more reporters with the security of individual reports</p><p><strong>**NOTE</strong>: If you have a high staking amount, you will likely get less reporters, but each report will be monetarily more secure. The reporting lock controls how long each reporter is locked for after a given report (the max dispute period).</p><p><strong>As an example:</strong></p><p>- Assume stake amount of 10 tokens and a reporter lock of 12 hours.</p><p>- If a reporter stakes 3 times, they can report once every 4 hours, 4 times, once every 3 hours.</p><p>- If you want more reporters, you can lower the barrier to entry by reducing the stake amount.</p><p>- If you have a fast chain, you need to make sure that you can have enough stakers to provide all the data your users may want. If it costs 10k for one stake and you want minute updates on data, this could get very, very pricey if there is a 12 hour lock on each report</p><p>**We’ll be happy to help you pick and go over the details, but as an example, Tellor uses 10 TRB and a 12-hour lock on Polygon.**</p><p>Once you’ve chosen your variables, launch away!</p><p><em>That’s it! Congrats! You deployed Tellor!</em></p><p><strong>Reporting Data to the Smart Contract</strong></p><p>Now you have to run a reporter to actually do something productive with your deployment. It’s a function you can just call with any software (e.g. an Airflow instance, an automated script, etc.), but you can also run<a href="https://docs.tellor.io/tellor/telliot/telliot"> telliot, our reporting software.</a></p><p>You’ll have to change the configs to point to your node’s RPC and the new address, but stake your tokens (telliot does this for you if they’re in your wallet) and that should be about it if you want to use the basic data feeds that are built in.</p><p>If you need some custom script/ data feed, you can always just write your own addition to telliot and run it.</p><p>You can find examples of those here: <a href="https://github.com/tellor-io/telliot-feed-examples">https://github.com/tellor-io/telliot-feed-examples</a> (they’re just python scripts to tell the reporter where to get the data / how to format it).</p><p><strong>Have Fun being decentralized!</strong></p><p>Now your chain has Tellor on it! Congrats and definitely reach out if you have any questions or need support. Looking forward to seeing Tellor grow to every ecosystem and hopefully we’re making it as easy possible to do so.</p><p><a href="http://www.tellor.io/">www.tellor.io</a></p><p>info@tellor.io</p><p><a href="http://www.github.com/tellor-io">www.github.com/tellor-io</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0243c60a98f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/how-to-deploy-tellor-on-an-evm-chain-c0243c60a98f">How to Deploy Tellor on an EVM Chain</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tellor Year In Review — 2021]]></title>
            <link>https://medium.com/tellor/tellor-year-in-review-2021-4f118aa579ea?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f118aa579ea</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Wed, 29 Dec 2021 20:36:21 GMT</pubDate>
            <atom:updated>2021-12-29T20:36:21.596Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tellor Year In Review — 2021</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wAe5swYeGo0PYLR-uINpw.jpeg" /></figure><p><em>From the lows of having to fork the entire protocol, to the highs of a Coinbase listing, key integrations, and a huge upgrade launch, 2021 proved to be quite a roller coaster of emotion, for a young startup like Tellor. Young…in human years of course. But in crypto years? An aged fine wine at this point.</em></p><p><em>Time for the recap:</em></p><h3>Q1</h3><p>Coming off the heels of a global pandemic and tumultuous election year, the entire crypto industry was ready to get back to business, and start back up with the IRL activities. Little did we know how REAL it was about to get.</p><p>2021 was first notably kicked off by bringing our incumbent design contractor, Ben, onto the team to formulate a consistent, sleek, &amp; professional design throughout Tellor’s outward appearance, so this was a big win for us. Also highlighting the top of the year was the launch of Chorus protocol, a project that set out to empower local communities by giving them the ability to make their own semi-stable coins with customizable monetary parameters, and of course, to utilize Tellor’s oracle. CTO Nick Fett’s passion for economics was given life, and although perhaps a bit ahead of its time, Chorus served as a proving ground for Tellor building their own vertical users — something we imagine happening much more in the future as Tellor establishes itself more as a DAO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_M5N3zJ-EUwrSdoeEs26Dg.png" /><figcaption>Tellor’s ‘Name that Tune’ gathering quite the attention</figcaption></figure><p>While still not ready for IRL events, Tellor sponsored Encode club and ETH Denver 2021, with the latter representing the pinnacle of ambition for virtual conferences. EthDenver created a virtual space for people to interact with each other’s avatars.</p><h3>The Great Migration</h3><p>On Feb. 15, Tellor suffered a <a href="https://medium.com/tellor/trb-migration-fd8ebe320b02">major setback</a> during the upgrade to v2.6.1. While the event was surely one we wish never occurred, it has proven to enhance our resilience, robustness around our processes, and demonstrated an ability to bounce back as a project and community, and ultimately has left us better off in the long run.</p><h3>Q2</h3><p>The beginning of Q2 was spent primarily on righting the ship in terms of getting our token holders migrated to the new unfrozen contract, and shoring up any processes that could prevent another scenario like this from ever happening again. Important as this was, we viewed it as an unfortunate distraction from getting on with the work we really wanted to be doing, working on the future of Tellor, and integrating with users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jyndaa2GBRbQcyw5Q8zwfg.png" /></figure><p>Liquity uses Tellor After months of setting up the implementation, Liquity’s use of Tellor as its fallback to Chainlink couldn’t have come at a better time. Not only did this help ease people’s concern about Tellor’s ability to bounce back, but the fact that Liquity was unable to change the code once it was launched, solidified us as a reliable solution that could be relied upon as a trustless source of information.</p><p>Sharing the spotlight with Liquity in our highlights of 2021, Coinbase announced its listing of TRB, finally bringing US-based traders of TRB a highly reputable and liquid market to utilize.<br>Keeping in stride with this momentum, our first proposal to the Ampleforth community was submitted, starting the pathway for our next official user.</p><p>In an effort to keep up with the ever evolving crypto ecosystem, two new versions of Tellor were introduced. Fellowship, to interact with L2 solutions, such as Polygon and BSC, and TellorX, the next big upgrade for Mainnet.</p><p>Tellor remained in the hackathon game with ‘Scaling Ethereum &amp; HackMoney’ finding interesting use cases and keeping our name fresh in the minds of the developer community.</p><p>On the media side, Tellor’s partnership with Mousebelt allowed us to get thoughtful discussions between Nick and other notable figures in the space. If you haven’t watched them yet, <a href="https://www.youtube.com/playlist?list=PLuJHbmh0kCXUVDDLUQOdS5d8pNIqsW-kh">we highly recommend you do</a>, and if you have, revisit them as it’s practically impossible to absorb all that dropped knowledge in one-go.</p><p>Last, but certainly not least, the next wave of the team joined Tellor. We finally locked in longtime miner and TRB shill, Spuddy, and the beloved ‘Tally the Tellor Intern’ as full-time hires as well as solidity dev extraordinaire, Tim!</p><h3>Q3</h3><p>The second half of 2021 was finally getting back to altitude, allowing us time to really hunker down and continue our planned trajectory. <a href="https://medium.com/tellor/moving-from-admin-key-to-dao-tellors-parachute-smart-contract-aba4cc9d71fb">The admin key was finally removed again</a>, TellorX was sent in for the audit, some of the team hopped on a plane for their first IRL in a longtime, ETH CC, and we acquired a new batch of highly talented Tellorians with Lauren, Josh, Owen, and Mike (aka Clamdad)</p><h3>Q4</h3><p>Closing out the year strong, the Tellor team got its own IRL time together during Tellor week, where we all flew into to HQ out in Maryland and bonded in ways Zoom could only dream of achieving.</p><p>In a test of perseverance, persistence, and under large scrutiny, the Ampleforth proposal, after having first been rejected, was revived after addressing some key concerns regarding the data we were interpreting for submission. Going from a failed snapshot vote, to in-depth discussion in AMPL’s governance channel, we were finally able to convince the community that adding Tellor was a positive for Ampleforth. Spanning over a year in discussions to be implemented, on Dec. 3, <a href="https://medium.com/tellor/ampleforth-oracle-usage-an-amplified-look-db8597767cf6">the idea became a reality</a> .</p><p>After having a blast in Paris during EthCC, Brenda and Ryan jumped at the opportunity to do it all again in the beautiful city of Lisbon, continuing the presence of Tellor in the community of developers at EthLisbon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nHFd1jI0N01PEUSet8jMZA.png" /></figure><p>Last, but certainly not least, <a href="https://tellor.io/blog/Tellor-Successfully-Launches-its-Newest-Blockchain-Oracle-on-Ethereum">TellorX was successfully launched</a> without a hitch. A much anticipated upgrade of the Tellor protocol addressing key pain-points of Tellor’s scalability limitations including moving from POW-&gt;POS for increased speed/efficiency, adding byte-data for robustness of data request types, and flexible code for multi-chain implementations. The sum of all of which capped off a year to remember and set the stage for 2022 to be the year of the swoosh.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f118aa579ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/tellor-year-in-review-2021-4f118aa579ea">Tellor Year In Review — 2021</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ampleforth Oracle Usage — An Amplified Look]]></title>
            <link>https://medium.com/tellor/ampleforth-oracle-usage-an-amplified-look-db8597767cf6?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/db8597767cf6</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Mon, 06 Dec 2021 19:21:15 GMT</pubDate>
            <atom:updated>2021-12-06T19:21:15.709Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Ampleforth Oracle Usage — An Amplified Look</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2HuyDu9cdDFNTMUJ9sIxEQ.png" /></figure><h3><strong>Introduction</strong></h3><p>Tellor is pleased to be working with Ampleforth to provide price data into its smart contracts. For those that don’t know how Tellor works, we’re a decentralized oracle that uses a network of staked data reporters who compete to fetch off-chain data and place it on-chain.</p><p><a href="https://www.ampleforth.org/dashboard/oracles">Ampleforth is now using Tellor to bring on two values:</a> <em>the AMPL/USD value and the US Personal Consumption Expenditures (a key measure of inflation).</em></p><h3><strong>AMPL 101</strong></h3><p>Ampleforth is the developer of AMPL, the first rebasing currency and a key DeFi building block. The AMPL protocol adjusts total supply daily based on market conditions. The AMPL protocol is based on its own unique primitives that make it uniquely poised to denominate stable contracts. Unlike stablecoins, AMPL does not rely on traditional banks or lenders of last resort. Each day, AMPL’s unique, rules-based protocol translates price volatility into supply volatility in a fully transparent manner. To put its rebasing model in perspective, consider this example: if AMPL is trading over a dollar, more AMPL is minted. If AMPL is trading under a dollar, AMPL is removed from circulation. Since price * supply = value (or Mkt cap for coins), if more people want to buy, the price will go up. In order to keep the price at a consistent level of denomination, the system automatically increases or decreases supply so that the equation holds. Ampleforth calls this process “rebasing.”</p><h3><strong>Why they need oracles</strong></h3><p>In order for AMPL to do its daily “rebase,” it requires a price of AMPL/USD on-chain so that the protocol knows how to adjust the supply. It doesn’t peg directly to the dollar, but rather an inflation-adjusted dollar. Using the US Personal Consumption Expenditures Price Index, it can track the value of the US dollar versus costs. This means that AMPL will still hold a stable value versus goods and services, even if the US dollar collapses in value. There is no reliance on traditional banks or lenders of last resort to guarantee liquidity.</p><h3><strong>Design</strong></h3><p>The supply change is referred to as supply rebase and is applied daily at 2 AM UTC. The price used to compute the deviation from the market price is the volume weighted average of AMPL trades over the 24 hours of the previous day from midnight to midnight UTC across all markets/exchanges and pairs.</p><p>Tellor becomes the third oracle to power AMPL price feeds, joining Chainlink and Ampleforth itself. The median (or average, if there are only two) will determine the daily rebase to ensure the most accurate outcome each day.</p><h3><strong>Conclusion</strong></h3><p>Overall, Tellor is thrilled to be working with such a great team and project. Ampleforth is a pioneer in token economics and its team’s passion and drive toward decentralization is obvious. AMPL has established a robust system and uses most of the <a href="https://medium.com/tellor/best-practices-for-oracle-users-on-ethereum-1ad9e2a43c3b">best practices for oracle users on Ethereum</a>. The next steps taken to further decentralize the protocol and create more robust price feed will keep AMPL as one of the most cutting edge projects around.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db8597767cf6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/ampleforth-oracle-usage-an-amplified-look-db8597767cf6">Ampleforth Oracle Usage — An Amplified Look</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Time to Vote!!]]></title>
            <link>https://medium.com/tellor/time-to-vote-b41743a4830?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b41743a4830</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Tue, 23 Nov 2021 19:08:30 GMT</pubDate>
            <atom:updated>2021-11-23T20:33:55.765Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>….Now what?</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXZQbMftp8DZ5W_krxJXQQ.jpeg" /></figure><p><em>The time has come to make your voice heard for quite possibly one of the largest updates to date for Tellor: </em><strong><em>Tellor X</em></strong><em>. However, due to the decentralized nature of Tellor, the upgrade won’t be able to go through unless the community votes in favor for the upgrade.</em></p><p><em>Let the following be a guide for those who are looking to vote, but not sure where to start or have never voted before on Tellor.</em></p><h3><strong>Basic Steps:</strong></h3><ol><li>Go to voting page: <a href="https://www.tellorscan.com/vote">token vote link</a></li></ol><p>2. Click the button that says “Connect” (top right corner)</p><p>3. Depending on which wallet you have TRB in, connect to the corresponding wallet. Most wallets are compatible with either MetaMask or WalletConnect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mB_FCc02f8q3TzuK" /><figcaption>MetaMask and WalletConnect work with most but NOT ALL wallet options.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VKiTggrBRQ5v_-e-" /><figcaption>WalletConnect to other wallets via QR Code</figcaption></figure><p>4. If you are connected, your public key will appear.</p><p>5. Click ‘Yes’ or ‘No’ to vote!</p><p>6. Upon clicking the “vote TRB” button, the wallet will ask you to confirm this transaction.</p><ol><li>Make sure you have ETH to pay for the gas of this transaction!</li></ol><p>If the above steps are not working for you, there are a few scenarios that might affect the above steps. If you fall under one of these categories, read on for more information…</p><h3><strong>Having issues with the above steps?</strong></h3><p>There are few scenarios that may affect your ability to go successfully go through the basic voting steps — the following should provide you with more trouble shooting depending on which wallet you are using.</p><h4><strong>Ledger Wallet</strong></h4><p>First, make sure you are updated to the most recent ledger <strong>firmware v2.35.0. </strong>This can be done easily through the Ledger Live desktop app.</p><p>Next, you’ll need to <a href="https://metamask.zendesk.com/hc/en-us/articles/360020394612-How-to-connect-a-Trezor-or-Ledger-Hardware-Wallet">connect to MetaMask</a>. After you have successfully connected to your Ledger to MetaMask, then go to: <a href="http://tellorscan.com/migrate">http://tellorscan.com/vote</a></p><p>Make sure you open the Ethereum app settings on the Ledger and enable ‘blind signing.’ And don’t forget to confirm the transaction on the physical Ledger device after confirming it on MetaMask!</p><h4><strong>Coinbase Wallet</strong></h4><p>If you are unable to connect via WalletConnect on the Voting page, you might first need to import into Metamask using the ‘import wallet’ in settings.</p><h4><strong>Trust Wallet</strong></h4><p>If you are unable to connect via WalletConnect on the Voting page, you might first need to import into Metamask using the ‘import wallet’ in settings.</p><h4><strong>My Ether Wallet</strong></h4><p>If you are unable to connect via WalletConnect on the Voting page, click the following link for more resources <a href="https://www.myetherwallet.com/access-my-wallet">MEW Support</a></p><h4><strong>Other Wallets</strong></h4><p>If your wallet is still having trouble connecting — contact your wallet’s support about interacting with contract data. If your wallet is TRB compatible, it should have this functionality. Possibly a setting that needs to be turned.</p><h4><strong>Vote Using Etherscan</strong></h4><p>You can also interact directly with the contracts on Etherscan if you are having issues with connecting to the tellorscan.com/vote link:</p><p>Go to the following link on Etherscan: <a href="https://etherscan.io/address/0x88dF592F8eb5D7Bd38bFeF7dEb0fBc02cf3778a0">https://etherscan.io/address/0x88dF592F8eb5D7Bd38bFeF7dEb0fBc02cf3778a0</a></p><p>1. Make sure your metamask is on mainnet and the wallet that contains your old TRB</p><p>2. Click on “Contract”</p><p>3. Click on “Write as Proxy”</p><p>4. Click on “Connect to Web3”</p><p>5. Make sure it connects with the wallet that contains your old trb</p><p>6. Click on “Vote” (function 12)</p><p>7. In the field labeled ‘_disputeId (uint256)’ put: ‘78’</p><p>8. In the field labeled ‘_supportsDispute (bool)’, enter ‘True’ for a yes vote or ‘No’ for a no vote</p><p>7. Click “Write”</p><p>8. Follow your wallet’s prompts to process the tx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b41743a4830" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/time-to-vote-b41743a4830">Time to Vote!!</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tellor to Launch Newly Designed Oracle on Ethereum Mainnet]]></title>
            <link>https://medium.com/tellor/tellor-to-launch-newly-designed-oracle-on-ethereum-mainnet-f44e5d633c25?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f44e5d633c25</guid>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Fri, 19 Nov 2021 15:45:45 GMT</pubDate>
            <atom:updated>2021-11-19T15:45:45.141Z</atom:updated>
            <content:encoded><![CDATA[<h4>A new oracle design, decentralized governance and treasury features adds even more robustness to Tellor.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jn1h9ZW2wUshbOoXCFV6ng.png" /></figure><p>The Tellor team is excited to announce the release of the next generation in oracle design.</p><p>After almost a year of planning, designing and building what has been nicknamed TellorX, we’re ready to launch the vote for community approval.</p><p>The vote to upgrade Tellor will start on Tuesday November 23rd and run seven days until November 30. Voting can be done here:<a href="https://www.tellorscan.com/vote"> https://www.tellorscan.com/vote</a></p><h3>A next generation oracle</h3><p>Since the initial mainnet release of Tellor in 2019, the team and community has continued to work towards decentralization.</p><p>Tellor’s goal in pushing oracle design forward has been largely focused on unstoppability, flexibility, and becoming truly community driven.</p><p>In June, the<a href="https://tellor.io/static/media/tellorX-whitepaper.f6527d55.pdf"> TellorX whitepaper</a> was released. This outlined a new direction in DeFi oracles that mixes new tokenomics, more decentralization and lower token minimums to broaden the members of our community who can get involved.</p><p>In September, we sent the<a href="https://medium.com/tellor/tellorx-goes-to-external-audit-c6acf7d4dc40"> TellorX code to audit</a>. After updates and continued feedback from the community, the team is now ready to launch!</p><h3>Innovation behind TellorX</h3><p>The new Tellor expands cross-chain compatibility and gains the ability to support virtually any data request.</p><p>The upgrade also includes a new staking pool, Tellor treasuries, which is a way for token holders to participate in Tellor’s monetary policy and receive staking rewards for doing so.</p><p>The new oracle design also moves from proof-of-work to a proof-of-stake model for data reporters. The minimum holding requirement to become a data reporter decreases to 100 TRB from 500 TRB.</p><h3>How to get involved</h3><p>Most importantly, we need all Tellor TRB token holders to vote YES on the upgrade to TellorX. Starting on November 23 this can be done here:<a href="https://www.tellorscan.com/vote"> https://www.tellorscan.com/vote</a></p><p>After a period of seven days, voting will be closed for a period of 48-hours for any disputes. If there are no disputes to be resolved, the Tellor team will then implement the new upgraded version and deploy on mainnet.</p><p>If you’re building a blockchain project that needs an oracle to put data on-chain for smart contracts, reach out to us. We would love to help!</p><h3>About Tellor</h3><p>Tellor is a permissionless community of token holders, data providers, and validators. Together, we cryptographically secure putting real world data on-chain. Our goal is to build the most secure, unstoppable oracle in DeFi for a more open digital economy. Tellor helps a mix of DeFi projects including stablecoins, insurance, options and derivatives and lending applications with accessing secure, trustless data. Visit us at<a href="http://tellor.io/"> tellor.io</a> or<a href="https://discord.gg/n7drGjh"> discord</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f44e5d633c25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/tellor-to-launch-newly-designed-oracle-on-ethereum-mainnet-f44e5d633c25">Tellor to Launch Newly Designed Oracle on Ethereum Mainnet</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decentralization: How Tellor does it.]]></title>
            <link>https://medium.com/tellor/decentralization-how-tellor-does-it-84280b6405d2?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/84280b6405d2</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[tellor]]></category>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Mon, 18 Oct 2021 16:59:31 GMT</pubDate>
            <atom:updated>2021-10-18T16:59:31.796Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wR-rHVFcD7G-Xf7RHBCTw.png" /></figure><h3><strong>TL:DR</strong></h3><ul><li>No ICO or Pre-mine</li><li>Fair Distribution</li><li>Permissionless Nodes</li><li>Decentralized Governance</li><li>Transparency</li></ul><p><em>From inception Tellor has prioritized being as decentralized as possible. But this concept of “decentralization” is pretty broad, and using the term as a slogan holds little weight without providing specific details. This blog post aims to concisely provide these details and more insight on the ways in which Tellor does this decentralization thing, and why. As we shift to a more DAO-like structure these efforts and decisions will be the foundation of making it possible for our community to run the protocol. Without further ado here’s how Tellor does decentralization:</em></p><h3><strong>No ICO or Pre-mine</strong></h3><p>A fair launch of a token is pivotal to the future abilities to become a decentralized project. ICOs were anything but fair.</p><p>In a nutshell, for an ICO (initial coin offering) a project would write a whitepaper describing the project they intended to build, pre-mine (create out of thin air) millions of tokens, set a large amount aside for the team, and pre-sell the rest at a discount to VCs and general public, then get listed on exchanges and dump the market. They would raise millions of dollars before they wrote any code. Tellor was built in the wake of the ICO craze and so we were keenly aware of the issues of them: no transparency, improper treasury management, lack of long term incentives, unfair token distribution, and more. We chose to fund our project in a way that required us to deliver, have long term commitment to the project, and not end up with the majority of tokens. So we chose a dev-share. In our case, we get 10% of the minted reward tokens that fuel the mining/data reporting network.</p><h3><strong>Fair Distribution and DEXes</strong></h3><p>Without a pre-mine the Tellor oracle network launched to mainnet with effectively zero supply. As mining events occurred, new tokens were minted every ~10 minutes. Anonymous people would hear about our new project, join our community and ask to participate as a miner and it spread from there. 90% of the tokens went to the miners. We never pursued paying for exchange listings or hiring market makers but preferred the true organic liquidity that DEXes provided even if it made it difficult for whales to buy large amounts. For more on our thoughts about this see our article about the <a href="https://medium.com/tellor/the-delusion-of-liquidity-ba7617d73226">delusion of Liquidity.</a></p><h3><strong>Permissionless Nodes</strong></h3><p>The spirit of open-source and transparency is a strong value held by the crypto-sphere in general. This value is deeply ingrained in the fabric of the Bitcoin community. Equal access to the infrastructure that operates the public ledger is seen as a public good. Unfortunately this value has been lost on many in the crypto community at large, and some oracles. They may, for example, include a permissioned structure (whitelisting) to participate as a node and/or to use the data. By doing this, you are creating a chokepoint of trust where an entity’s discretion is required to give permission. The Tellor oracle network is open and anonymous to anyone who wants to buy and stake TRB in order to participate as a Data Reporter and once the data is on chain is open to any smart contract to read.</p><h3><strong>Decentralized Governance</strong></h3><p>Decentralized governance implies that control over the protocol isn’t beholden to any small group or single entity, even if benevolent. Tellor uses token weighted voting and although this is not the perfect solution for governance, we do a couple very important things right: First, we do not hold an “admin key,” which would render any other decentralization efforts pointless. Secondly, as mentioned, we did a fair token distribution at launch, no ICO or premine, and so the Tellor core team does not hold a majority share of the token supply, in fact we currently hold only ~4.5%. The current quorum for passing governance proposals is 10% and so we can not unilaterally pass things through.</p><h3><strong>Transparency</strong></h3><p>We think the best way to grow a strong and engaged community is to include them and make public most of what we are doing. This is the heart of our “We are Tellor” motto. Since Tellor launched in 2019, we’ve done weekly community calls giving updates on what we are working on, and recently greatly increased our transparency by moving most of our internal development and business discussions, from private telegram chats to our public discord channel.</p><p>If you find our approach unique and meaningful, <a href="https://discord.com/invite/n7drGjh">please join our discord </a>and introduce yourself — <strong>you are among friends.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84280b6405d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/decentralization-how-tellor-does-it-84280b6405d2">Decentralization: How Tellor does it.</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TellorX Goes to External Audit]]></title>
            <link>https://medium.com/tellor/tellorx-goes-to-external-audit-c6acf7d4dc40?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6acf7d4dc40</guid>
            <category><![CDATA[tellor]]></category>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Fri, 03 Sep 2021 17:54:08 GMT</pubDate>
            <atom:updated>2021-09-03T17:54:08.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQSWHe9qZAEuPjHBMgljgg.png" /></figure><p><strong>The team has sent the code for TellorX to audit, a major milestone for launching the newest version of the decentralized oracle.</strong></p><p><em>Since the initial mainnet release of Tellor, we continue to work towards building an unstoppable oracle. An oracle that’s censorship resistant, as decentralized as possible, and above all has clean well-functioning code.</em></p><p><em>Tellor is extremely excited to release the next evolution of the Tellor oracle, TellorX, in the coming months. To get to that point, one of the major milestones is an external code audit of what the Tellor team and community have built.</em></p><h3><strong>TellorX As a Next Gen Oracle</strong></h3><p>TellorX is a new direction for DeFi oracles that mixes new tokenomics, more decentralization and lower token minimums to broaden the members of our community who can be data reporters (and earn more TRB in the process!). It also shifts Tellor’s oracle from PoW to a stake-to-play system.</p><p>TellorX expands on cross-chain compatibility and data submissions in bytes, making the data that can be reported and put on-chain much more flexible and robust. It also includes a new staking pool, Tellor treasuries, which is a way for token holders to participate in Tellor’s monetary policy and receive staking rewards for doing so.</p><h3><strong>Importance of External Audits</strong></h3><p>No matter how careful a core team is when building code for a new release like TellorX, there are blindspots.</p><p>Vulnerabilities, security issues and bugs can result in a compromised Tellor oracle, and TRB token. The goal for the external audit is to catch most of these before TellorX goes live. It’s nearly impossible to ensure a perfect, unhackable code base, but external audits should prevent major bugs down the road. Code audits also add an objective, third-party perspective that doesn’t come from the core developers.</p><p>We wouldn’t launch TellorX without this kind of deep external audit, and know that improvements will come from it — making it well worth the time and effort to complete the audit.</p><h3><strong>What’s Ahead</strong></h3><p>Assuming a straightforward external audit (no doubt tweaks will be needed), TellorX will launch in Q4 2021 after continued testing and community approval.</p><p>The community’s feedback on previous iterations and the upcoming TellorX, plus the data reporter interface (Telliot) has been crucial for us to fine tune and add functionality.</p><p>As always, we have <a href="https://www.tellor.io/bounties">bounties available</a> for the community to keep testing and improving Tellor.</p><p>We have seen more and more excitement from the community and other blockchain projects that can use TellorX as a more flexible, decentralized oracle. We can’t wait to launch it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6acf7d4dc40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/tellorx-goes-to-external-audit-c6acf7d4dc40">TellorX Goes to External Audit</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving from Admin Key to DAO —  Tellor’s Parachute Smart Contract]]></title>
            <link>https://medium.com/tellor/moving-from-admin-key-to-dao-tellors-parachute-smart-contract-aba4cc9d71fb?source=rss-3d2211a8ac6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/aba4cc9d71fb</guid>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Tellor Core]]></dc:creator>
            <pubDate>Wed, 11 Aug 2021 17:38:37 GMT</pubDate>
            <atom:updated>2021-08-11T18:15:55.817Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Moving from Admin Key to DAO — Tellor’s Parachute Smart Contract</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ek3xQtDqQrTKkGRWott9jQ.jpeg" /></figure><p>Most blockchain projects have some sort of centralized control (admin key) that allows a developer or founding team to make decisions on the smart contracts underpinning their work. Many projects take steps to secure these admin keys, but still, the admin key yields a large amount of power to the hands of very few. Decisions over user balances or replacing code can be made unilaterally.</p><p>We’re excited to announce a new approach to re-DAO-ify Tellor. We’re taking these steps to fulfill the long-term vision of Tellor as fully trustless and unstoppable.</p><h3>What are the risks with an admin key?</h3><p>In the early stages of a project an admin key is great for building and making sure the system functions as intended, however admin keys take away much of the trustlessness and decentralization of blockchain technology. It relies on faith that the admins won’t abuse their powers. Worst-case, rug pulls happen and a team member is hacked or takes users’ funds and disappears.</p><p>To eliminate this centralized point of risk, a small minority of projects remove the admin key by sending it to a burn address. This creates a new set of challenges. What if there’s an error in how the project is built and how is it fixed? What if the community votes for a bogus change to the project? And if the project comes under attack, what are the control measures to make sure the attacker doesn’t succeed when time is of the essence?</p><p>The risk of facing government regulation is also a wide open question for ‘centralized’ projects with an admin key. The regulators may take out projects that have a ‘kill switch’ in the form of an admin key. DeFi projects that have centralized ‘custodial’ control over users and their funds face heat, especially in the form of legislation. If regulators can find a centralized party or group of people, they will grab hold.</p><h3>Tellor’s Parachute Smart Contract</h3><p>At Tellor, we’re familiar with the tradeoffs. Having initially built Tellor with an admin key in place, then sending it to a zero address last October, and subsequently encountering a fatal error forcing us to fork to a new contract giving us admin keys back — we’ve learned a lot along the way.</p><p>Tellor’s core philosophy is to be the most decentralized, censorship-resistant oracle. This long-term view of the project allows the team to make decisions that may be new or different. But these structural changes are designed for the success of the larger blockchain community. We want to build a flourishing ecosystem and set an example for those that want to build towards this goal.</p><p>As of Wednesday, August 11, 2021, Tellor <a href="https://etherscan.io/tx/0x9252fd591d24e866b6b7edca35c26f0ad3e97c7e5d68f2ae7ad5178e91f2aa4c">has sent its admin key to a smart contract called Parachute</a>.</p><ul><li><strong>Check the code here: </strong><a href="https://github.com/tellor-io/parachute">https://github.com/tellor-io/parachute</a></li><li><strong>Parachute contract address:</strong> <a href="https://etherscan.io/address/0x83eB2094072f6eD9F57d3F19f54820ee0BaE6084">https://etherscan.io/address/0x83eB2094072f6eD9F57d3F19f54820ee0BaE6084</a></li></ul><p>This helps Tellor become more decentralized while also creating a fallback in case a catastrophic event happens in the future.</p><p>So what does it mean for Tellor and the community? Throughout the normal operation of the Tellor oracle, the Parachute smart contract will sit idle or unused — so not much changes. In the case of an underflow attack, broken mining and reporting, or Tellor updates to something non-functional, the Parachute will pass admin rights to the Tellor team to take the necessary actions.</p><p>This new feature of the Tellor protocol creates a more decentralized project, while adding a narrow set of fail-safes; events that would allow the Tellor team to gain back control to fix bugs or rectify attacks with clear and transparent logic, driven by code.</p><p>To be clear this doesn’t give the Tellor team backdoor access to critical pieces of the project. The admin key is completely out of the founder’s control now and in the hands of the community through token governance mechanisms.</p><h3><strong>The Bigger Picture</strong></h3><p>Many projects, at some point, will face the tradeoff between control and decentralization. We’d encourage any project that is interested in going the DAO route to consider a Parachute that fits their own criteria.</p><p>In the early days of a project, it may make sense for the founders to keep control in order to have a stable deployment and quickly adapt post launch. However we hope our use of a parachute style contract will influence these projects to “take the leap” as early as possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aba4cc9d71fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tellor/moving-from-admin-key-to-dao-tellors-parachute-smart-contract-aba4cc9d71fb">Moving from Admin Key to DAO —  Tellor’s Parachute Smart Contract</a> was originally published in <a href="https://medium.com/tellor">Tellor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>