In the final part of this series, we will be looking at the differences and similarities with the technology applied in both Telos and EOS networks. We have looked at the comparisons in the dApp developer feature in the first part of the series. Next, we looked at comparisons in governance in the second part of the series.

This part of the series goes into the technology powering both chains. It will also directly touch on the benefit for Telos. Now the reason is because EOS mainnet has launched so everyone has seen some of the limitations with the technology implementation. Telos will be launching soon and has taken some of the experiences from EOS to include these extra technological implementations at launch.

Now there is no guarantee that it will work exactly the way the guys that worked on the technology have envisioned it, but at least it gets the ball rolling. Since there is a lot of flexibilty on the Telos chain, changes can be implemented pretty quickly to fix anything that will negatively impact the network.

I do not want to forget to give credit to Douglas Horn, the architect and author of the Telos whitepaper, and also the Telos Launch Group (TLG) that have worked tirelessly without any pay to bring the Telos idea from something on paper to actual reality. I really pray that all of them will be rewarded greatly for all their effort in Jesus name. Amen!

Lets jump right in to the comparisons in terms of technology between Telos and EOS.

1) Rotating Standby Block Producers (BPs) :

In Telos, the top 30 standby BPs are regularly rotated into block production to test readiness. They are paid 50% the BP flat-rate.

Benefit: Improved network resiliency

In EOS, this is not implemented.

2) Removing non-producing BPs:

In Telos, any BP that misses >15% of its assigned blocks in a given schedule is kicked off and replaced with a standby BP.

Benefit: Improved network resiliency.

In EOS, BPs cannot be removed for not producing. Multiple non-producing BPs could lock up the network.

3) Removing non-compliant BPs:

In Telos, BPs that are not compliant with minimum requirements or other rules are disqualified from service after 24 hours of non-compliance.

Benefit: Improved BP compliance.

In EOS, BPs cannot be removed for noncompliance.

4) Inverse-weighted voting:

In Telos, voters must vote for 30 BPs in order to receive the full weight of their staked votes. Voting just 1-4 BPs yields <1% of vote weight.

Benefit: Voting for a small number of BPs is discouraged.

In EOS, votes receive the same weight despite number cast. This allows large wallets to cast more weight to their affiliated BPs.

5) Stage-net:

In Telos, BPs are required to spin up a network to test all new code changes for >24 hours before moving into production (except critical security patches).

Benefit: Advance testing of new code in live environment.

In EOS, this is not implemented.


In Telos, IPFS will be implemented at launch for governance and shortly thereafter for dApps and users utilizing a IPFS resource token. Multiple IPFS services may exist.

Benefit: Users and dApps will be able to store data on IPFS instead of just

RAM and TX memos for better resource use.

In EOS, this is not implemented.


In Telos, REX has been pre-approved in governance so that it can be implemented once the developers and BPs agree it is ready.

Benefit: Better resource usage and staking rewards for users.

In EOS, a referendum is expected to be necessary before REX can be implemented.

As we end this series, I hope that this has clarified what Telos is trying to achieve. Again, this series was not put together to say that Telos will be a better network, but that whatever Telos achieves through these additional features in dApp development, governance, and technology will benefit the whole EOSIO community. Cheers!

Search like you do on google and earn Presearch tokens

Use your spare CPU on your device and help researchers solve hard problems and earn Boid tokens

Subscribe to me on YouTube.

Follow me on twitter.

Follow me on Medium.

Follow me on Steemit.

Follow me on whaleshares.

Follow me on Trybe.

Join the Telos conversation and get more info!






2 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 5 (2 votes, average: 5.00 out of 5)
You need to be a registered member to rate this.
(200 total tokens earned)