Links
Youtube link: https://www.youtube.com/watch?v=hSIDc6_CW5s
Official links: https://linktr.ee/Tellor
Summary
Online meeting about the application of Tellor 360. Running tests in the system and overcoming obstacles, underlying error messages. New updates in Tellor 360 as well as in the treasury. Investing in Bitcoin and Ethereum (updates, fees, surveillance:how to detect frauds etc.).
Whole call
Nick: All right. I have one TellorDEV call again. Somebody’s entering, so we’ll have some feedback right now. All right! So big things as of last week. So, I think it was just last week we kicked off the treasury, right?! So that’s live you can go invest in the treasury now. We’ll give you guys an update sometime. See how much fills up. Five percent return in three months, so if you’re going to hold TRB for three moths you might as well go get five percent return on it. It’s super cool! Some other things, I guess we’re working on. We started Tellor 360. So we’re… Let me know, my internet connection says it’s unstable, so let me know if I cut out. But anyway Tellor 360 is the DEV, that party is coming. I scheduled the audit today. It’s sort of like signing up for a marathon. Before you start training, you’re like just sort of held to it , but it’s gonna be mid-July, so we got two months to button up everything. My goal would be by the end of June, obviously you can still, we’re gonna still continue to test and everything through the audit, but my goal would be to finish all the contracts. Have them like compiling. We all sort of review them and agree and then June, mid-June to mid-July is just testing. We’ll launch it on Ring Fee or maybe not on launching it on Ring Fee. That we’ll save that, but we’ll just be you know local testing. Launch it, kind of a fork and see how that works, so… Other things on our plates: We’ll be updating using Tellor, so I’m buttoning up some tests on that, and then I’ll update the NPM package. There were some issues in between using Tellor vs. Tellor X vs.
TellorFlex and so just made some changes there. So if you are using Tellor things might change. Yeah! Anything else that I guess we worked on, big things! So the RNG is out. Right Tim?!
Tim: Yes, it is.
Nick: But I think our buddy “Chain-link God” may have improved it. Right!
Tim: Yeah! So there’s one slight modification we can make, that should improve things.
Nick: Yeah! I mean it was, I don’t think he actually found a bug in it, like I think it was pretty good, but just him bringing it up (like) we were like (yeah) if we actually enforce a certain scenario I guess it would. So I mean what the thing was basically like if the Bitcoin block (had) if you chose a time stamp for the where you’re matching up the Bitcoin and Ethereum time stamps, if the Bitcoin block closest to that was really old, like 5 minutes old or something. Like you could theoretically be than, it would be easier to modify the hash. Just if the Bitcoin one came after or came before. Right!
Tim: I think it was really that, you know Bitcoin Block times are 10 minutes.
Nick: Yeah!
Tim:… and then Ethers every like 10 seconds or 12 seconds. So you could have, so the random number generator works by you’re looking at a certain time stamp and you take the next block hash for Bitcoin and Ether after that time stamp. And so the the Ethereum block hash will come like immediately, then the next Bitcoin block cash will come in five minutes on average.
Nick: Yeah!
Tim:… so by that time now the Bitcoin miner knows exactly what that Ether block cash is. So now it’s just up to the Bitcoin miner . So I think the improvement we can make is you could use the most recent Ether block hash right before that Bitcoin block hash and that time the Ether block hash isn’t actually set in stone.
Nick:But and I mean the Bitcoin block you sort of you would never be able to complete at the proof of work mining, if you were changing it 10 seconds before.
Tim:Yeah! Right!
Nick:Like you would have to have what like a 10 x the whole Bitcoin you have, to have like 90 percent of the Bitcoin hash power.
Tim:So yeah…
Nick:That’s gonna happen.
Tim:Yeah!
Nick:…so I think just making it that little change will then work as expected. So…
Tim:Yeah… It has a lot to do with just playing with time and what information is known at a certain point in time.
Nick:Yeah, so… We can make those changes. I think that you should be able to make those changes in like what an hour. If that…
Tim:It’s a slight change on what we already have. So yeah…
Nick:(Yeah) The big question: “Should we give him a bounty?”.
Tim:I know… Yeah, maybe?! Just because that’s funny.
Nick: I think it would be. I said we sent a 100 bucks at CRB just first…
Owen:… then we can send him a shirt as well.
Tim:Yeah!
Nick: Well apparently (yeah). Isn’t that how you (we) bought off Chris Black Tellor Core Contributor.
Owen:Yeah, that’s what I’m saying. Yeah, he’s a like just robo man.
Nick:Yes! So, all right! We’ll send him a bounty and do that . Yeah, but what are you guys working on? Owen?
Owen: I have a lot of catch-up to do, because I was out Covid last week. So I need to work on DIVA things. Getting just things kind of like seamless with the TIP listener. So we can help Vlad test things , kind of like end-to-end with Thalia side and get back to Darshan. Just look at what he was running into some JavaScript stuff, where he’s testing, getting the values that are reported with PI Telly on his Typescript Demon for more core stuff… And then I was looking at Chrome’s PR. The tests are failing. I like reran them a few times like it’s failing, because (like) gasps by circle now. It’s failing, because (like) historical price tests were Kraken. So, making another issue for that and then the original one that I was failing on was this like where it’s this assert function within the actual TIP the autopay test, which I’ve seen before, which is like sporadic for some reason. So, I’m trying to get that one to come up again, but it’s giving me all these other test errors, which is “no bueno”, so I just need to check out this and then I may need to give back 360 things to like Tim and other people, just because I have to do a bunch of catch up. But we’ll see. I’ll let you know at the end of the week.
Nick:All right! Akram?
Akram: I worked on the Tail Yet. Trying to… I added a wait period flag that you can , you know instead of (because) the TIP listener was making too many calls and the report is running every seven second, so it’s I guess an adjustment that a reporter can make, if you wanted to slow it down, so it makes less calls. In addition to that I found two extra costs, that I was able to get rid of and do without. So, I did that.
Nick:When you’re ready?
Akram: The problem is the tests are failing on like I don’t know… It has nothing… I don’t think it has to do anything with the changes I made, but like the API is timing out and so forth. On the other tests that we had passing previously, so I’m trying to figure out if we can solve that. Aside form that I switched the tests like a lot of. There’s still two left . Two brownie tests and there’s an issue with that. The tests are failing, because I don’t know. The ASYNC is not like tearing down after each test. For some reason it’s keeping the loop going. I’m trying to figure out how to close the loop, the ASYNC loop, before it goes to the next test. Another thing is the script that we talked about last week.
Nick:Yeah…
Akram:For a spotty , but that was I know you said it was supposed to be just a single probably file script, but you know it’s kind of building out to be a bigger thing. So, I don’t know, maybe if it’ll need a REPO a separate REPO, aside (from) instead of adding it to tell you, just to keep things clean.
Nick:Yeah! We can probably go ahead and make a REPO. You should be able to.
Akram:OK, yeah! (And) I think I want to finish that out. Today I’ve been working on it all weekend, so it’s taken longer than expected , but hopefully today I’ll be done with it.
Nick:Awsome!
Tally Wiesenberg:Is that the TIP listener you’re saying ?
Akram:This is getting your time stamp submissions that you made to see which ones are eligible, so you can go claim your tip?
Tally Wiesenberg: Ah,ok!
Akram: I found a nice example on the DOCS of WEB3, that PIE and it was a good one. I think you’ll like it, after I’m done with it!
Nick:Cool!
Akram:That’s it! All right Tim!
Tally Weisenberg: That’s my Jupiter, sorry!Never mind!
Tim: Yeah! I’m working on Tellor360 and in particular the staking rewards, right now. So, yeah! So, the model I’m looking at is : I’m building it right now. Is like a drip. So you have like a pool filling up with staking rewards and then you drip. It has a drip rate to everyone who’s staked and the alternative to that would be just splitting all rewards up to all stalkers as soon as the reward is sent over to the staking contract, but if we want to also use vote count. So pay out based on voting participation. I think the time drip, the slow drip model would work with that.
Nick: Yeah! What I mean you have a safe assumption, so there’s a seven day withdrawal period.
Tim:Yeah!
Nick:… but you can assume that it’s not like people are going as long as you’re doing payouts, like within every seven days. Like you can assume people aren’t going to be moving in during the drip period or whatever. So it doesn’t have to be super fast.
Tim:Okay! Cool! I (was) that was kind of my thinking too. That seven day wait period.
Nick:Yeah…
Tim:…gives us a way to build in like a cost I guess.
Nick:Yeah! Like you’re not going to be staking and unstaking just to get rewards.
Tim:Yeah! Exactly!
Nick:So…
Tim:So, I’m mostly able to copy the structure of like Sushi swaps farming rewards.
Nick Fett: Yeah…
Tim: So a lot like that. So, yeah! That’s what I’m working on right now. (The) Doing the contracts and then I’ll do testing and then any other 360 work needed after that.
Nick:Okay! Cool!Let me know if you got anything more…
Tim: Yeah…
Nick:Cool! Tally?
Tally Weisenberg:Hey! Last week I was working on internal docs for AL GRAND. Setting up reporters and well deployment reporters.
Nick Yeah…
Tally Weisenberg:Reporters deployment, all that stuff. Scripting in general for Tellor 360.
Oh, Tim! Do you have a before each that you set up already for testing or have you not gone to testing yet?
Nick:For Tellor 360 he’s going to be on something completely different Tally.
Tally Weisenberg:Okay! Never mind…
Nick:Yeah, okay…
Tally Weisenberg:Just didn’t want to do repeats.
Tim:Okay! I’m in flux right now.
Tally Weisenberg:Okay, so with that said like I’m writing before each. So, jut want to make sure that we don’t repeat ourselves.
Nick:We also have to do that piece other than you Tally.
Tally Weisenberg:Okay!
Nick:Only that Tellor 360 repos can deal with all those with all those upgrades and voting on it. So…
Tally Weisenberg: Okay! Gotcha! Yeah! Yeah, so testing on that repo and I wrote a data spec for file coin deal status, which is sort of alludes to the proofs that we learned about in Tim’s presentation, but it’s sort of more like exposed kind of property of the file coin network and so I wrote the data back. And I’m working on a slide of the example using that data spec and then maybe after that Italian implementation, but that’s what I’m working on.
Nick:Super cool! All right… And Spuddy? Anything?
Spuddy:Not really.
Nick:Spuddy says not really. We need basically as soon as possible, we need to reduce the node hits. I don’t want Spuddy’s nodes.
Spuddy:…temporarily go back to before the template has a quick fix.
Nick:Yeah… We are going to go back to not using the chip listener, because we’re basically killing all our nodes.
Spuddy: How many coins is it?
Nick:I can look up I think it’s like 225 000 a day or something like that. So we’re up there, yeah…
Owen: (Is that) Do we have a a flat amount that we can use for a month or a day?
Nick:So like I have it up to 225 000 a day and we’ve been hitting that one and then it’s basically all Spuddy. (And) I think (you know) like I cannot up it obviously. No problem, but like I think it’s like getting we should be able to not.
Owen:And what’s that for how many reporters ?
Nick:It’s like two or three…
Owen:Two or three… and that’s for a day?
Nick:Yeah, so… Well (we’ll) we got to cut back a lot. We’ve the old Telly reporter, so I mean the goaling one like we … I did… That was like one of the constant struggles, was just making it, reducing it, because like a lot of people who would try and spin it up normal users. Like it’s… Like I even have to pay in fear for that amount. You know the usual limit is you know a fraction of that. So you usually want to keep it to where like a user doesn’t have to pay 50 bucks a month to Infur to run this thing or at least there’s some sort of option for them to not have to pay that.
Spuddy:So, much that I use my own node…
Nick:Yeah… Yes, it’s funny saying it was you. Just have to run your own node, but the others… Elliot… So you know like I want to make it so we don’t have to do that here. Although maybe it’s being good stewards of the space. We force people to run their own nodes.
Spuddy:Oh, no it’s amazing! You can just hit it as much as you want. Yeah, it’s great.
Nick:So we might have to again just spin it back up.
Okay! Anything else guys?I think that’s about it, but I think the next I (also) want whenever people get some free time talk to some people on it. (I) We need a data spec for like an EVM bridge. So, like how do you call a contract on another EVM chain? It’s super easy! That aspect would just be the chain ID, the contract address and then the function call. It would return data. But somebody was asking for that in the Hackathon and I was like we should totally have this as a data spec. It would be super easy and then another one: Some people like another person asked (in) to tell your channel and for the Hackathon and then other people have asked in the past how to get test net TRV? We should eventually make a faucet , but it should I mean, it would be super easy I think. You know because we have whatever Spuddy owns 95 percent of the RAMP supply. Just sit there and go for it. So, you just fund it and then have you’re allowed to pull once a day and you get a thousand TRV. Something like that. (So) Anyway so those are some fun ideas and then I’m gonna fix that treasury. There’s a problem with the treasure. Some dates on the treasury website going to fix those today and then the community is asking for more front ends. Just to show projects using Tellor. We could do that. I was thinking like simpler or like they’re like: “Oh, if we have trouble like updating it or something like that”. What’s the TV, because if they post like UMAs this is how many people people are using it, this is the TLV in them. The problem with all those is like it’s such a pain to maintain those UMAs. Is all like their own Hackathons, so it’s like we could do that and make it look pretty, but like I was thinking maybe we just do like included in like the quarterly review or something like that. At the bottom to have like that way it suffices for what they’re looking for, but it doesn’t look like it’s sort of up to date or we’re not standing by it, that this is the the list of projects using Tellor and if you want to get in and I also just wanted to be selective. Like this is a portion of the ones using it. We don’t endorse these projects. If you have projects using Tellor, you can try and get it in here, but if you’re scammy we’re not going to put you in here. Because that’s the problem we’ve always had with people and any time (and) you know even when we first lunched Telly . Read like a partner section on our website then projects would want to get on the partner section and it was like this is no. So we we took it off. Anyway… All right guys! Thanks for being here. Let me know if you need me.
