Links
Youtube link: https://www.youtube.com/watch?v=hS0AyKyWL2o&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
Bi-weekly discussion on the state of reporting. This week the team also touched on Algorand update.
Whole discussion
Owen: Welcome everyone. This is the fourth reporter’s call. Just have a few updates for everyone. Let’s get into it. If I can, there we go. So, we have integrated the changes needed to report to Polygon Tellor Flex specifically. So, those changes are in the docs, in Telliot feed examples, those have been linked in discord and whatnot. There’s a new staking requirements and info in the docs as well about that. We’ve introduced, thatnks to Mike, encrypted files for all of your account information private keys and whatnot. Also, now if you’re using the supported client, the Python client, there’s the ability to stink up your reporter with everyone else and this is to reduce the number of reverted transactions and transactions that are going through where you don’t get a reward, but they still go through for submitting the value. It essentially syncs up which query ID that you’re reporting to and this is also good for us because it provides some variation in what’s being reported. Because right now a lot of, it’s just ETH/USD. And then also there’s a lot of command line interface updates, so definitely want to check out the docs for those. Tally’s going to be talking a little bit about what’s going on with Algorand. I’m still working on a payment contract for Ricochet exchange. And then we have, if you check out on the discord, we’re still moving things forward with a few different users; League-Dao, Morphware and you can go check out some of the repositories that we’re linking down there, like data specs. It’s pretty interesting about forming the specifics of what kind of data that you can put on chain. The other thing too is, Mike is working on a listener dashboard. I think he wants that ready for EthDenver, so that should be coming out soon as well. Tally, do you want to say some things about Algorand.
Tally: Sure. Hey reporters. This next two weeks and pretty much also as well leading up to EthDenver, I’m working on compiling, testing and deploying an equivalent or as close to an equivalent of Tellor Flex on Algorand. In that process also as well I’ll be working on scheduling submission of values with a simple designer and then as we progress, in this time we’re exploring, I think, I know I called it a fork, I would probably call it more modification in terms of how much will change to the code base. We’re exploring modification to PyTelliot to make it more suitable for the sort of blockchain and smart contract language that Algo has. For context, Algorand is quite different than Ethereum, they by design, they intentionally, they use different consensus algorithm and without a different smart contract language, without even a different mechanism for addresses and APIs, and contract language itself. So, it’s still a work in progress and still something to think out, but it’s a situation where the long-term goal is to have integration with an algorithm build of Tellor on Algorand with integration of in cohesion with the greater Tellor ecosystem.
Owen: Sweet. Yeah, quick call this time, but let us know if you want anything included in the next one in the reporter’s channel on discord. Thank you.
