Tellor Developer Call April 25th 2022 

By Tamsay | Tellor | 27 Apr 2022


Links 

Youtube link: https://www.youtube.com/watch?v=lYNGcuPc8Cc 

Official links: https://linktr.ee/Tellor 

 

Summary 

Announcing a couple of talks by Nick, discussion about Tellor360 and the treasury vote. Josh bids his farewell, while the team is looking for front-end devs. Still working on RNG, Ricochet, Diva and Morphware integration. Telliot is getting constant bug fixes, which makes it more resilient. The GasPrice oracle and the Tip Listener are both getting into final shape, while Tellor on Algorand also looks good. 

 

Whole call  

Nick: Alright, welcome everyone, Tellor dev call, I have no idea what week this is. It's sometime in April here in Maryland. Things we're working on; I guess still just buttoning up a lot of stuff, kind of the same kind of things as last week. We had on Friday another Tellor 360 brainstorming session; I think most of you guys here were there, but we did post it online, other people can go look at that we'll probably be buttoning up. I'm working on like the white paper of changes if you will, that we'll go off of for kind of what code changes we're going to make and then probably over the next few weeks we'll start coding. I think it'll be simple just basically since we're like upgrading a live system worth you know, millions and millions of dollars, we write a whole bunch of tests and take it slow. Because it can break, we don't want it to break, so we'll make sure that it doesn't break. That's why it won't be a rush, but it'll be fun and that'll probably be. Prepare for that doc, probably next week we'll push it out. Other things; this week that I'll be doing, tomorrow I'm on Infura's community call. If you guys want to come on that, it's not like noon I think and then I'm speaking at the global DeFi conference. It's a virtual conference on Thursday I think they gave me like an hour so I got to fill a whole hour with content, which is fun. That'll be good, those are some of the big things on my plate and then we're just going to be helping you guys out. Josh, would you like to go first? 

Josh: Yeah, so looking into the subgraph issue that I was having, like I said it failed on deployment so once I figured that out, I just wanted to fix that last little bug, so that way we can get the treasury stuff rendering. I mean everything renders and everything's fine it's I'm getting the pickiest like the dates that are off due to the treasury IDs, but once that's done then just start a process of documentation for all the funded projects. My idea to start as far as like a good starting point for all that would just be writing some really good readmes and then to make sure include like next steps and I guess, where I was planning on going with everything and hopefully it leaves a good how-to for the next step. 

Nick: Yeah, for you community members, who don't know, Josh will be leaving us at the end of the week, so you guys can give your goodbyes to Josh. That said, if you're a front-end developer and if you know the graph or any if you've seen like the voting pages treasury page, fun to feed page, Josh does all those, so if you want to help out let us know. But yeah, that sounds good we have a call at one today so. 

Josh: Yeah, I was actually going to ask is that a good starting point but more specifically we're going to go into. 

Nick: Yeah, that sounds good we're just going to take our time and record it all so we know what you do, how to change things and then yeah. So, that actually reminds me the thing that we should talk about probably first and foremost; so, the vote failed. For those of you guys that haven't been paying attention we were voting on should we issue a new treasury. We were going to double the rate and issue also new treasury. It failed. It's not that big of a deal, that one vote failed, because of quorum so we need 5% of all token holders to vote, we only had 4%.  

Brenda: Yeah, we needed 1% to vote for it, it wasn't like everybody voted against, it was just quorum. 

Nick: Yeah, so we need to rally the troops. It's actually not a big deal that treasury couldn't pass, but it would be a much bigger deal if like we're trying to upgrade to Tellor360 and we can't pass the vote. You know, so we really want to get people delegating and used to voting kind of as we make these changes once Tellor360 hits. I think we're actually removing all votes the only, the only thing that you'll be voting on after that would be disputes, which don't have a quorum so this is like the last of the issues but we have to you know, if we're assuming like September, October a vote for Tellor360, we have to make sure that people know how to do it and that they kind of delegate or can help us pass it. You know as far as we'll probably kick it off again next week, we'll have the biz devs actually start reaching out, try and find some big holders like one whale could easily push us over the edge and then you could always do like the drastic approach, you know probably if this one doesn't pass, we'll wait two weeks and then do something where you get a hundred bucks if you go vote. It's like we'll pay for your gas and a hundred bucks or something until we hit quorum. 

Brenda: For the treasury it's a good exercise so that we can get delegated votes for 360. But honestly if there's no appetite, I think that eventually, we just, okay then, there's no treasury. Because you know we feed you or you know I think we really cater towards all of our users and this was something that we thought was going to be taken up by the community a lot more, since you don't have to be a miner, literally just have to stake but if there is no appetite or people just don't know about it then you know hopefully, we can make a push for the next few weeks and then after that I feel like it's I don't know if I will be willing to keep pushing. 

Nick: No, I completely agree. I mean yeah to me getting this thing to pass is more so just an exercise in voting. Yeah, so I'm excited for when Tellor360 hits and we don't have to do these voting exercises. You know, the more you can just let people do what they want to do the better. So, if you guys have any thoughts, any community member listening has any thoughts on how to get, go rock the vote let us know. Alright, Tim, how’s life? 

Tim: Life is good. So, I'm working on getting some RNG tests to pass, so that's my first priority and then also going on this week is updating Ricochet contracts. They made a bunch of changes to their contracts and they were using an old version of Tellor, so I'm going through and updating their new code base to use our modern Tellor. 

Nick: Sweet. 

Tim: And then also we have updates to the Diva payment contract and we're meeting with Diva tomorrow to go over those changes. So, I know might be updates then. 

Nick: Both of these I mean it's whether it's Ricochet or Diva we've just worked on for months and months it's like, I think. So yeah, taking forever but hopefully we can get them all squared away here quickly. 

Tim: The tricky thing with Ricochet, it's just a big repo and a lot of different changes that need to be made across different tests and contracts. I guess we're hopefully looking at a finish line here for these projects. 

Nick: I actually, I was looking at Tornado Cash a little bit this weekend and if you take out the token piece and everything, it's like 120 lines of code. It's tiny and I'm like yeah, it's like such a. You're just, this is amazing, great job guys. You know whenever somebody can have like a nice sync function, there's a comment next to it like this does this, but barely any, it's just kind of... 

Tim: It goes a long way. 

Nick: Yeah, it's so much more approachable. So, keep it small guys. Cool, Owen? 

Owen: Hey, so it is kind of nice because the Morphware, I mean that's basically all of our stuff is done and it's just we're waiting on them now to test like reading in the reported values for their query ID in their typescript daemon. For their Morphware client kind of thing so Darshan said he's going to get back to me on that. The main things right now for Telliot are fixing bugs from Spuddy, got a few of those handled last week but he finds new ones which is good. And the testing is almost done. The switching the test to use a local node for Telliot core almost done, six of the nine test files are finished so Lauren and Akrem, when you guys are done or if you need help on getting those because that's basically on your plate now. So, just let me know about that. So, Tally your pr is good to go except for the latest feedback. So, we'll merge that when it's done and then at some point, we're going to be testing Akrem’s tip listener a bunch. This week ideally, I think that's about it. 

Nick: Cool, lots of stuff so, Tally? 

Tally: Hey, I finished the data spec in the query type and test it, or this is the pr that we're talking about, I haven't checked my feedback yet but aside from that it's implemented and tested for the gas price oracle new query type. As I've been going along, I've also been developing a process doc doc. Right now, it's just like a list of steps but maybe we'll turn it into a checklist, maybe not and maybe it'll be internal or external. I don't know. Aside from that the next is to work on the data well. Next is to implement the feedback but after that is continue to build a data source for it and the rest of the classes that come with the process. And on Algorand we're really, really close to done. We have six end-to-end tests left and after that is on my end at least, is the write-up of the white paper. Yeah, that's the immediate task for me is the white paper. Which is sort of hand in hand with the readme. 

Nick: Yeah, cool looking forward to it. So Akrem? 

Akrem: Finish the template listener based on the autopay contract and just finishing up the test. I'm actually incorporating the browning test just to get that done so the other tests for Telliot core should be easy after that. There was one thing I don't know if it's, I know the contracts are already deployed I don't know if there's a chance to add getting the length of the tips list in order to. Basically, the checker checks if there is a balance or a tip for reward but it doesn't check if it's been claimed already. Having the length would help with that unless you know if, especially if, you're leaving the reporter run overnight it could just keep reporting even though the tip is already covered for. 

Nick: Yeah, add it in. 

Akrem: Is that cool? Yeah, I can do that. 

Nick: I think that's pretty good, yeah make a pr to add it and it should be quick. 

Akrem: Perfect, okay that and I guess the Telliot core stuff like I said and the wrapping up Algorand and that's it.  

Nick: Cool, wow that's super exciting. Yeah, and Brenda do you need anything or I mean you're working on the docs for autopay or did you do that already? 

Brenda: I think I did that already. Yeah. 

Nick: Well, Tim was supposed to entertain everyone today with the presentation and then he's letting you all down. What, next week Tim? 

Tim: Next week building the suspense. 

Nick: What are you presenting next week? 

Tim: Presentation on file coin. 

Nick: Alright, presentational file coin. So, yeah you just have to join next week. Cool, well yeah that's about it, talk to you guys later. 

How do you rate this article?

3



Tellor
Tellor

In this blog I will post transcriptions of videos made by the Tellor team.

Send a $0.01 microtip in crypto to the author, and earn yourself as you read!

20% to author / 80% to me.
We pay the tips from our rewards pool.