Links 

Youtube link: https://www.youtube.com/watch?v=9PzIcXWZH1g&ab_channel=Tellor 

Project website: www.tellor.io 

Twitter: https://twitter.com/WeAreTellor?s=20 

Discord:  https://discord.com/invite/n7drGjh 

Reddit: https://www.reddit.com/r/TellorOfficial/ 

Summary 

Covered multiple topics, mostly talking about future steps, and also diving deeper into the available bounties. Stressed the importance of an active community in shaping Tellor. Multiple great questions were asked about Tellor X and also what the plans were, how the team envisions the next steps.

Whole discussion 

Mike: Hey everybody, welcome to Tellor community call, it is December 7th. Big week this week. Tellor X is live. The Tellor AmpleForth integration went live as well. Lots achieved over the last few weeks, it’s been a crazy few weeks and here we are. I know that the price performance is not reflective of all the work that we’ve done, which has been a big bummer. We’re annoyed by it too. You got to numb yourself to these kinds of things because when you least expect it the price of disappoints you, but here we are. We have a lot to be excited about. What other... So, we have some bounties and stuff that we’re interested in expressing to you guys, so check those out. We have some monitoring tools that we are really interested in building out. I know people have been asking for certain things and we need your help taking on some of those tasks. Where do they go to check out the bounties?  

Nick: I think the website, right?  

Ryan: Scroll down all the way to the bottom of the fresh website.  

Mike: Well, speaking of that, we have a new website live that you guys should all familiarize yourselves with, including myself. Yeah, there’s a nice new bounty section there. I can picture it now. Sorry about that. But yeah, the website is live, I don’t know if you guys might have noticed there was a couple hiccups in the first day of the launch, but the website is live right now. We do have some features that aren’t live yet, but we’re sort of having internal discussions on where we want to go in terms of how ambitious we want to be with the next iteration of the website’s capabilities. But anyway, let us know what you think of the current website, let me know if you guys have any input. 

Spuddy: Everybody loves it. Everybody loves anything you do. 

Mike: That’s not true, that’s definitely not true.  

Nick: I feel like they’re positive most of the time on our random stuff, as far as anytime you push out something like this is new. 

Spuddy: Sorry, I’m Spuddy, I’m off-screen. 

Mike: Oh, they know who you are. The new website looks really nice, it really represents our new brand, our new style and we hope that it’s the messaging is much clearer for our users and we hope that it’s much more shareable for you guys. One thing to stay tuned for on right now around December 15th we should be updating the video that’s on the website with a nice animated how Tellor X works video. Right now, Ryan did a good job of putting in a placeholder for us, where you walk through how it works, but that’s just a placeholder while we have this animation video getting created. We’re really excited about that; I know you guys have been asking for these types of visual graphics for a while and I think you’re going to love it. I think it’ll be really nice to put on reddit and just share around on YouTube. What else, I think we have tonight, we have a Tellor space, Ryan do you want to share information about the Tellor Space? Come on, you’re doing a giveaway. 

Spuddy: Yeah, check out my tweet for a giveaway if you’re in the space, you are entered. Actually you’re not entered unless you want to do all the stuff that I said in the tweet. 

Ryan: It’s at 9-o'clock tonight, Eastern time. If you’re not familiar with spaces, it’s just a live chat on twitter, so if you have a twitter account, and you just go to our account, you click on our profile picture, there’ll be like, just kind of a purple aura around, that means that the twitter space is live and happening and it’s an AMA on Tellor X, so any questions you have about Tellor X, how you can participate or just anything at all it’s on your mind we are going to answer it and hopefully it’s going to be a good time.  

Mike: Yeah, just shop up, it helps us out, I mean it’s one of those things where if other people see that there are other people in it, they’re more likely to join it, and hop in, so even if you guys don’t really have any questions because you’ve been here at all of our community calls, still hop in, ask us questions, join the call. 

Brenda: Come get to know Ryan and Nick and Spuddy better if anything.  

Mike: What else, should we just hop into the questions?  

Ryan: Let’s do it.  

Nick: I think, another announcement. So, we’ll be scheduling, I think it’s December 22nd, we’re going to be doing a live call, just on Tellor values, so this we’ve done them internally as a team a lot, but we’re actually just going to make this one public, so we want you guys to join, we’re going to be talking about the why of Tellor. It’ll be the same place and hopefully you guys can come and we can just, we’re going to take turns talking about why we’re here and what we want to see Tellor do in the future and what kind of the ultimate vision is.  

Mike; Yeah, we want your input, why are you here, how you want it to be.  

Nick: Definitely want your input. And then the other thing, we got some Eth Denver acceptances today, the team will for sure now be out there, so let us know, hopefully you guys have applied and are planning on going, but if it’s two months away, but it’ll come quickly. So, let us know if you guys want to meet up. 

Mike: We are sponsoring just to clarify that, but we just never know how many tickets you get with the sponsorship, but we have a bigger team than that and we didn’t know who was going to be get accepted because it’s one of the tougher, one of the more desirable events if not the most desirable Eth event ever. 

Nick: That one and the dev con.  

Mike: What is dev con.  

Nick: I don’t even remember.  

Mike: So, super stoked about that. Okay, questions.  

Question1: What are the next upcoming integrations or development steps, or partnerships you can talk about?  

Nick: We’re actually trying to push everybody through the integrations channel in discord. This is a new thing that we’re really pushing. We want it to be as open as possible, because we want you guys to help us integrate them, we want you to look at their code, and we want you to audit it. We want you to help build, so go look at the integrations channel on discord and you can see we’re making channels for people. For instance, probably the one that’s super close, we’re building out with Morphware, where we have them a nice little feed, we’re testing on Rinkeby with them now. They’re doing what, like cloud computing prices, we’re bringing on chain. So, it’s a super cool, interesting one. I mean, there’s a lot of other ones there, so just go have a look and we’re trying to keep it as non-closed source as we can, where we’re talking founders. Go there, start spreading rumors.  

Mike: If you go to a DAO’s discord, because we’ve experienced this on the other end, where we were like, we want to connect with one of these projects to talk about oracles, you have to, there’s usually a governance section or an integration channel or something like that where you just have to publicly say hi, who can we talk to about oracles and it becomes this open public conversation. This is one of those things that we started to experience a lot this year and we liked it and we wanted to do that as well. That way it’s much more transparent.  

Spuddy: And there’s a history of those conversations in discord, what we’re saying.  

Nick: And they take a while though. I mean if somebody comes to you with a smart contract, they say hey I want to integrate you and integrate Tellor, what that means is first we see if it’s feasible, then we start coding, then you integrate it, then you test it and they send it off for an audit and then you test it some more and then six months to a year later it’s actually live on the network. So, these are slow, slow builds. Don’t expect partnership announcements as soon as somebody posts in the discord. 

Spuddy: Which is what other people do, what other projects do when we know they do that literally you... 

Nick: It’s exciting to see because now projects are starting to come to our discord and ask to integrate Tellor. This didn’t happen a year ago, it was us personally meeting people and trying to get them to integrate us and that now they’re starting to come and they’re people are asking, and it’s exciting.  

Mike: We had the Olympus, we had Rye come in, Stephan from Rye come in.  

Nick: They’re like, we heard about Tellor and we want it integrated, sounds good. This is awesome, this means we’re doing something right.  

Mike: So, you guys got to be on your best behavior now that you’re basically, you’re hosts of the Tellor house, Tellor community. You never know who might show up and judge us based off of our memes.  

Question2: What will be the strategy for promoting the project by the end of the year? 

Mike: I think we’re going to switch, not really switch, but we’re going to, I think the plan is going to be to focus a lot more on direct marketing approach and doing a lot more, going into these communities and refining our pitch. This is something that we’re going to start working on early in January. Making sure we have our pitches down and actually going out into these communities and being a little bit more structured around it, not that we haven’t been doing that, but I think just being, we’ve got to be better at it and more efficient at it and do more of it. Other than that, we’re going to continue everything that we have been doing, like we were just mentioning, we are gaining momentum with people coming into our channel and that’s because of the promoting efforts that we’ve done. People are hearing about us and people are liking what we’ve built, and I think things like Eth Denver is going to be huge. It might seem like just one big event, but it’s one big event that’s going to do have a huge ripple effect in terms of who knows about Tellor. Just a lot of continuing the same thing we’re doing and just sort of taking it to the next level of maturity.  

Question3: What are the next steps in Tellor after Tellor X?  

Nick: Can we tell the name we’ve branded it, so far Tellor Flex. Yeah, you have to say like that, but it’s, we’re going to be putting Tellor on other chains. A lot of people obviously know we’re going to go over to Polygon, we have a simplified structure already over there, but we’re going to be putting something that’s really good over there and then we’re going to be putting it on Algorand and then we’re going to be probably putting it on a bunch of other chains. We’re going to make Tellor so easy to launch a Tellor system, that hopefully other chains on their own start launching Tellor systems without even telling us, and it’s that, that’s the goal as far as how big Tellor can be. It’s not just that Tellor can be an oracle for every project, it’s that each chain can launch their own Tellor and each chain can have their own reporters and their own system, and it’s going to be an awesome structure, so we’re working on that. There’s a Tellor Flex repo, go have a look at that, the other thing too, that we’re going to be working on is, I’m going to be updating the bounties today. We just want, we upgraded to Tellor X, there’s a lot of people who, the whole system is new, so we need people to try out being a reporter, let us know how hard the documentation is, and how we can get it better. There’s going to be people that we want to go integrate Tellor, like just go build something awful, that you know, go build some “say gm on the blockchain”, or say you know you want to put the price or some sports score in your smart contract just for fun because then tell us how hard it is, tell us what, where we can do better in the documentation as far as figuring that out, because those are some things that whenever you do upgrade some of the core pieces of your contracts like we did with Tellor X, a lot of the documentation broke and we’re still kind of figuring out the best way to tell people how to integrate them. So, that’s what we’ll be doing and then also we talked a little bit about monitoring tools, if you are a front-end dev and want a bounty or know a front-end dev, the best monitoring tools are never built by the core team, it’s always people who are actually using it and community members who build what they want to see. Even in the past, Mike and... he had awesome monitoring tools whenever he was running a reporter he had the best ones, was the number... or Dune has some awesome dashboards up for different things you know, if you’re a holder, try and think about what you guys want to see, because that’s what other people probably want to see too, so if you want to build a front-end monitor and reach out and we’ll give you a bounty for it.  

Mike: Next one. 

Question4: Could you or do you plan to make a road-map of Tellor?  

Mike: No, we never, we don’t do roadmaps. 

Nick: Stay away from roadmaps.  

Spuddy: If a project has a roadmap, it means they don’t actually want to do this stuff on the roadmap.  

Mike: No, it’s true. Roadmap is just basically... 

Spuddy: If they’re going to do it, wouldn’t they, they would just do it, it wouldn’t be on a roadmap. 

Mike: Yeah, roadmaps are fake. On a serious note, it’s because things move too fast, and any roadmap becomes really stale very quickly, so we’d rather... our approach is to just tell you every week what we’re doing. It’s way better than a roadmap, because right now we’re like, okay, let’s think what we’re going to do for the next 12 months. We would make up most of it. You’d have to because we just don’t know what we’re going to be doing in 8 months.  

Nick: 12 months ago, there were what, four employees? We had just launched Tellor v2, it was just really different.  

Question5: Web3 and Tellor together. What will this bring us in the future? 

Mike: I love that one. World peace. 

Nick: Spuddy? 

Spuddy: The metaverse.  

Nick: Yeah, I don’t get it.  

Ryan: You don’t get the question?  

Mike: It’s too broad.  

Spuddy: I’ll pass on our behalf.  

Ryan: Spuddy passes.  

Ryan: You kind of touched on this, but maybe we can reiterate.  

Question6: Is the intent for PyTelliot to be modular and adaptable so that developers can add additional code to create more efficient reporting? If so, will this not restrict all retail investors, reporters who are keen to report, but are restricted to the base build PyTelliot?  

Mike: Alright PyTelliot guys, who wants to take that? 

Telly: I have an answer, I have an answer. It actually works out really well, because it’s modular, but what one thing, the modularity doesn’t imply is that if someone else builds, it means you can’t use it. So, if someone else, it’s all open-source software, it’s all free software, so if someone else builds a data feed that you want to use, technically they could say that they’ll copyright it, but we would really frown upon that so I would say like 95% of the time if someone builds a data feed and you want to report to it, you’ll be able to use the same code that they use. Let me know if I missed anything.  

Nick: Dr Bapst, anything?  

MikeSr: I agree 100%, if you just look at the repos, there’s two repos. There’s something called Telliot core, which doesn’t do a whole lot, except to provide all of the core functionality, and then there’s a separate repo for the feed examples. So... 

Nick: Which one Mike Bapstro?  

MikeSr: Doesn’t do much. No, the reporter is completely separate. Does not do any reporting, there’s no reporting algorithms in there, so if you’re free to write your own, you’re free to use Telliot core, you’re free to fork Telliot core and do something different. It’s all free.  

Nick: Yeah, and it’s in Python, so if you guys are devs who want to build new data feeds and you’re a Python dev, reach out, we love, we have a bunch of new ideas for good data feeds and we love your help.  

Question7: How are you ensuring decentralization of the reporters and in turn reported values, or is this not required as the main goal to have accurate data which the dispute framework ensures? If only one or two reporters are submitting all reports throughout the day, how is Tellor any different to ChainLink centralization of data feeds?  

MikeSr: I mean, I think that it’s open source software, and the cost of the stake has gone way down for becoming a reporter, anybody can become a reporter. We’re glad to help people get started, using the example reporter that we have, and I think we have a lot of reporters right now, does anybody know that number how many people are reporting?  

Ryan: It’s 59.  

MikeSr: Pretty decentralized.  

Nick: Well, I think, we don’t know who they are, it’s actually a super interesting conversation, very topical, because Vitalik actually wrote a paper, or an article called “End game”, you guys can go look it up, but he does like the game theory for stakers in the future and he says eventually it’s you’re going to need really big, he has it printed out. You’re going to need really big hardware to run a node and to be a staker and everything like that. It’s actually going to lead to economies of scale will naturally centralize it, you can imagine if the best Tellor reporter if there are economies of scale, you would be a Tellor reporter on every single chain that Tellor’s on and you would be very efficient doing it for almost minimal profit, because you could submit as soon as somebody requested it and you would have knowledge and it would make sense that it would naturally centralize over time. Obviously, this is years and years away, that Tellor is a success, but the difference in an Ethereum setup and a Tellor setup versus say a ChainLink setup or the old EOS setups is that anybody can always come on and become a reporter. So, even if you do centralize it and there’s only two guys who are all of your Tellor reporters, it’s actually still trustless, because you can dispute them all the time, so anybody can. It’s decentralized verification of the data, which not necessarily even of the reporting and then the only thing if there were two guys, and this is how Vitalik even claimed it, the worst thing they could do is actually just go offline and sort of freeze the network for a little bit, but then obviously anybody, since it is an open network, anybody can bring up the stakes and start reporting again. So, it’s not like a big problem, you would just want to make sure that you have a backup in case that they fall back, but go read the End game paper. Actually, very similar problem we have here, I think in the meantime you want to make sure that it doesn’t get too centralized too fast, because it’s sort of frowned upon. It can still work as a centralized piece, but you want to, from a point of building a community, the more you can spread the rewards around the more you can provide, there are multiple people reporting, these are multiple visions for the future of Tellor, that’s a good thing to have and I think just making sure that we have different clients, different reporters who are all over the globe reporting on different things, and different types of data. I think we’re doing a good job just incentivizing it, just building up from how we talk about it within the community. I hope that was a good answer.  

Ryan: That was a great question. Great answer.  

Question8: Is it possible to add analytics to the Tellor website where we can see where, what and why Tellor oracle is being used. AmpleForth feed is a great example. It would be awesome to see how Tellor enables a process in this system.  

Nick: Yeah, I think we had talked about, we want to build some monitoring tools. We’ll definitely be doing it, still trying to figure out where we’re going to put them, but yeah. I think it’s also really easy with whenever you have a “what’s this data being used for”, because over time you’re going to see there’s different monitors that people want, like the monitors that AmpleForth wants are different than the monitors that a PyTelliot reporter would want and are different probably than the monitors that a token holder would want. So, hopefully over time we can have all of them sort of separate and sort of hone down to what each person wants. 

Ryan: This one’s actually going outside the box and talking about the google forms. 

Question9: Can you make these question input boxes on the form a multi-line box, so much room on the page and so little playing. 
Ryan: I will look into that and make it a better experience, no problem. Thanks for pointing that out.  

Telly: I like that question. But I didn’t ask yet.  

Ryan: That’s it for the questions. Nick and Mike, did you guys get your Minnie mouse ears yet? Because... 

Brenda: Oh, wait, you guys were supposed to wear that the whole call.  

Ryan: No, that’s not visual. Going to be the next community call. 
Brenda: Next Tuesday. That’s what’s fair guys.  

Nick: We lost the bet, and we have to put on Charger’s Minnie mouse ears on a call. 

Brenda: Ryan, give the background. What was the game and what was the issue?  

Ryan: The two teams that we are big fans of, the Chargers and Steelers played on Sunday night football, it was a great game, Chargers came out on top, they now have to wear these... Oh yeah, beautiful.  

Mike: They’re so pretty.  

Ryan: And I don’t have to wear a terrible or swing a terrible towel and sing the first line of what was the song?  

Mike: Renegade by Sticks. 

Ryan: Trying to get me sexy. Really dreading that.  

Brenda: So, translating on your calendars next Tuesday, Nick and Mike will pay their bet.  

Nick: I’ll take it off whenever I’m doing, oh, next Tuesday we’re going to do the treasury call too, so be sure to come back.  

Brenda: It’s going to be great. 

Nick: I’ll take them off when we’re talking about Tellor treasuries. 

Mike: But we can just be funny because it’s sharing. Did you hear about the Tellor treasuries?  

Ryan: Cool, that’s it, thanks everyone for popping on, see you next week, bye.