The Teloscope report: 1–31 December ’19

This month we have focused on doing our best to improve the WP system, with our tools and our vote.

BP Infrastructure

Performance

At the end of each month we report here about the monthly performance and status of The Teloscope Telos Block Producer. The data shown here is mainly sourced from two apps/tools: our own creation Chainspector, and Aloha BP Benchmarks.

For ten months in a row The Teloscope BP has scored the best median performance and least range spread. Our CPU execution times let us validate Txs faster, which benefits both the Tx sender and the Telos network.

Another fairly stable month for The Teloscope popularity. Just one step down from 8th to 9th in the ranking by votes, caused by one proxy that decided to drop us from its voting list (more about it later).

And as it has been one year since the launch of the Telos Network and our own BP candidate The Teloscope, we show you here our full ranking history.

Applications and Tools

Chainspector

We launched a new feature update in Chainspector.io showing all the accounts that voted for every Worker Proposal and enabling on-chain comments in them.

All Telos accounts that have voted in the same direction for the WP appear listed under the corresponding tab

This way we give the community the possibility to see who is voting and optionally to show the reasons for their particular vote, or to make other kind of remarks.

Proposers can also use the comment system to update their original Worker Proposal document, by linking to new versions or simply by making short clarifications.

Community

Worker Proposals

The first proposals that arrived to the Telos WP system date from February 2019. Since then, we have primarily focused on improving Chainspector’s related functionalities to better ease the management of any WP once launched.

We had stayed a bit away from voting for Telos WPs, because first we wanted to have both the tools and a transparent method to do it.

We wanted to evaluate all open proposals in a common and fair way, without going into too much detail about their content and objectives. That is why we thought of creating quite simple criteria, mainly related to the way they were written. Some sort of ‘formal requirements’. There were two fundamental things we wanted to notice in the content of every proposal: good (Telos) alignment and (price) fairness.

For us, alignment means that the proposal’s deliverables are mostly for the overall benefit of the Telos community, rather than benefiting few private companies or communities mainly supportive of other blockchain networks. We have nothing against private profit, but we would like to read in a Telos proposal an explanation of how that profit can also benefit a larger portion of Telos community, albeit indirectly.

And fairness means that the total amount requested from the Telos WP System comes from a measurable mathematical formula, easily understood and highlighted in the text of the proposal. That formula must allow evaluating the deviation between the value given in the proposal to each task and the market value of similar tasks.

So to make our task easier and more transparent, we created an ad-hoc spreadsheet that we shared with the Telos community. It contains the details of the process we followed (criteria tab) and all the results of our evaluation of the proposals, ordered from highest to lowest amount requested.

Two sheets, one with the results of our evaluation and other with details about criteria used

After publication of this spreadsheet, we gave a few days’ notice before starting to vote for the proposals, just in case proposers or anyone wanted to ask us or debate about criteria, issues detected, etc.

The low quality of the WPs’ writing surprised The Teloscope very negatively…

The somewhat provocative way in which we announced this took many by surprise, and even annoyed some while others even dared to accuse us of undermining the whole WP system and withdrew the support of their Telos voting proxy to The Teloscope. A really wrong accusation in our opinion, as we think it is the apathy that many show by voting yes to incomplete or unjustified proposals what could end screwing the Telos WP system up.

But apart from this little commotion, there have been many more positive comments from other people in this community, which we summarize in: “I am therefore happy that somebody stood up and opposed to the free TLOS mindset that some might have.”

Telos Birthday Week

Telos community celebrated 1 year since launch of the main network, and there’s no Telos Birthday party without a song… so The Teloscope band reunited again for the closing of the celebrations… 🎊 💃 🕺

Our stellar performance was pinned for a few days in Telos Community Telegram group! 🙏

This report has been produced by members of The Teloscope team. You can also check previous reports from The Teloscope.

The Teloscope is an independent non-profit block producer. The revenue we get from any service we provide to the network is fully invested in our BP infrastructure, as well as in tools and services for the community. Please visit our Code of Conduct to know more about these principles.

You can support us by including theteloscope among the list of BPs that deserve your vote.