There has been a buzz about the coming EOSIO software fork, Telos. One of the things that keep coming up is the comparison between Telos and EOS projects. Some people have been asking whether Telos is trying to take users and dApps from EOS. A user on Reddit actually commented on one of my posts and I quote, “Lol, Telos is like when your ex tries to take your friends but you have been there since day one…silly exes.”

The above expression is truly how some people in the EOSIO stratosphere view Telos so I believe it is the job of any person that loves what Telos is trying to accomplish to engage and answer these people in a clear and consice manner. I have been trying to put the comparisons together until Douglas Horn, the architect and author of Telos white paper posted one on the Telos telegram group which anyone that is interested in Telos can join @

These comparisons were not put together to make Telos look better than EOS, but to show the improvements that Telos will be making using the EOSIO software code. If the implementation on Telos works well, it will bring value to the whole EOSIO ecosystem.

In the first part of this series, we will be looking at the comparison in dApp developer features.

1) Open Source Software requirement:

Telos allows developers to deploy either open source or proprietary contracts. Developers of proprietary dApps can use arbitration to pursue protection against unauthorized use of proprietary code. Proprietary code does not enjoy the same freedom from liability that open source software does.

In EOS, all dApps must be open source according to the current EOS Constitution.

2) InterPlanetary file system (IPFS):

In Telos, IPFS is used for storage of WPS (Worker Proposal System) and Ratify/Amend documents. IPFS for dApp and user usage (paid with a tradeable IPFS resource coin) will be available shortly after launch.

In EOS, IPFS is not implemented. Storage is through RAM allocation or block memos.

3) System-wide DNS (Domain Name System):

In Telos, Trail service is a system-wide DNS service integrated at the system level that dApps can use for multiple purposes.

In EOS, no DNS is implemented.

4) Token Standards:

Telos TIP-5 token standard adds several ERC-20-like functions to EOSIO tokens. Actions like allocate allow tokens to be airdropped for the price of an “airgrab” with RAM costs borne by recipients at their discretion and reclaimed by publisher when not claimed.

EOSIO token standard has limited funtions.

5) Snapshots:

Telos will support an “original” snapshot at block 6 million and regular current snapshots (every month or two) will be maintained at network or Telos Foundation expense to facilitate airdrops.

In EOS, the RAM cost for airdrops is at each dApp’s expense.

6) New user accounts:

In Telos, at least the first 1 million new user accounts will be paid for by the Telos Foundation and/or WPS. Funds may be allocated to dApps for direct onboarding provided they apply common-sense protections against abuse.

In EOS, new accounts are the expense of the users themselves or dApps that onboard them. There are very few dApps that allow people create new free accounts., the organization that created the EOSIO software code said they will be creating wallets that will allow for free accounts but it is not out yet.

7) Voting:

In Telos, TIP-5 tokens can implement built-in voting capabilities using Trail service.

In EOS, there is no built-in voting for tokens.

8) Initial Resource Costs:

In Telos, NET and CPU are less expensive because TLOS is less costly than EOS and each TLOS carries 3X the resource power due to lower token supply. Additionally, the GoodGrant program will stake the first year+ of NET and CPU to selected dApps deploying on Telos to reduce or eliminate the up front cost of deployment until business is stabilized. Telos Foundation RAM grants are also available to reduce initial RAM purchase costs for selected dApps.

In EOS, dApp developers bear the cost of NET, CPU, and RAM.


In Telos, RAM price is managed by Bancor algorithm, but speculation is strongly discouraged through Telos Foundation RAM Administration published guidance price (PGP) and limited price support from TF RAM Administration and block producers. RAM will be sold to dApp developers at PGP when trading >15% above it.

In EOS, RAM price is managed by Bancor algorithm. Speculation has been a problem. No favored pricing for dApps.

In the next article, I will be looking at the governance of both chains. I hope with these comparisons, it will remove some of the fog so that anybody can see the Telos network for what it is trying to achieve in this space.

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!






4 votes, average: 5.00 out of 54 votes, average: 5.00 out of 54 votes, average: 5.00 out of 54 votes, average: 5.00 out of 54 votes, average: 5.00 out of 5 (4 votes, average: 5.00 out of 5)
You need to be a registered member to rate this.
(410 total tokens earned)