For over a month already, there has been a Teloscoin Masternode Installation guide available at Teloscoin Forum.

If you are planning on setting up one and need some guide, then check from there.

This guide however only gives you instructions on how to set it up, and nothing more, and since there been quite a lot of following questions in the Discord Channel, I am going to add a bit of a troubleshooting guide in here:


Why isn’t my node giving me rewards?

is often asked in Discord channel, and reasons can be many, but here are some of them.

It might take a long time before you receive your first reward, especially if you are setting up a 100k node.

The more master nodes there are, the longer it takes for the first reward, or even the next reward to come.
Or to be more precise, more Telos Coins are attached to Master Nodes, longer it takes, meaning that one master node with 1 Million collateral, is the same as there existing 10 Master nodes with 100k Collateral.

And in Telos there is quite a lot of coins attached to Master Nodes, so rewards are slow.

To Check the current average times etc. you can check statistics from masternodestats.info

Another reason why you are not receiving rewards is since your node is one way or other not working properly.

There are loads of people who try to set up their master nodes to some low-cost minimum performance VPS, but you need to understand that if your server doesn’t meet the requirements, they might appear to be functioning normally, but not receive any rewards.

Thing is, there are so many reasons why this might happen, and there are even scenarios where a perfectly fine working node might not receive any rewards.

You might be using too little RAM or virtual RAM, which results in your node being a bit too slow.
Thing is, when rewards are distributed, it is done through consensus between nodes.

Idea is that each node will contact other nodes and say to them “Hey, how about me win the reward this round” and then these nodes continue contacting other nodes telling “Hey, node X suggested himself to be the winner, okay for you too?”, but then at some point there comes a situation where the other node answers “Sorry, I am already planning on giving my vote to Trump” and then the Node X loses.

Figuratively speaking the idea is that you start calling with a phone to your friends and speaking them through the phone to vote for you, and if you speak slow, your talk stutters, and you are using old-style phones where it takes longer to dial, then the guy who speaks fast and perfect and pushes only one button to call his friends, is able to get more people to his side before you are, and hence you keep losing the vote all the time.

This is exactly what can happen to your node. So while everything looks like they are functioning normally, you are not getting rewards, since your node is too slow to ever win the consensus on its side.

A slightly similar situation can happen with a perfectly fine working master node too, for thing is, all nodes have this independent auto banning system. Idea is that if some node tries to contact your node, and the connection isn’t very good, by other words slow replies, then your node will automatically ban this node leaving space for some better and faster node to connect to it since connection spots are limited.

While your node is working perfectly fine, if it however tries to reach to a node on other side of the globe, it is likely that the connection is slow and bad, and to keep connection good and faster, it will automatically ban connections from this node, so closer, better-connected nodes can connect to it and network stay fast.

So basically even if your node is working perfectly fine, but it happens to be in such a spot that connections to every other node are simply bad, as in too far away, then it will get banned by all those others until there comes closer nodes with better connections nearby.

In addition to these, you could also be getting rewards too often, which indicates your node might have either forked itself away, or it might have connected with nodes that have forked away.

To rule this possibility out, you need to check your latest transaction HASH from your wallet and compare it with Telos Explorer. The address in this article is the one that was in the Master node guide, so if it is not working, keep checking from the Teloscoin forum for a new one’s address.

Notice when comparing the HASH, that Explorer might not be showing the newest block yet. At least some Explorers have been waiting for blocks to verify for a certain amount of times before actually displaying them, resulting in explorer showing for example 50 blocks behind, meaning that when you go and check your HASH, and you don’t find it, it doesn’t mean you are at wrong fork yet, it might just mean that Explorer isn’t showing that new blocks yet. Hence, either wait or compare some older blocks HASH.

Also, you can check the Block number and compare what is explorers’ newest block number to see if Explorer is behind in its showing or not.

Catching up with the next Lucky 7 article.

This article was published on July 30th, and it is about Greenbox.

This article will give you a bit of an introduction to Greenbox without going into too much detail and you could basically send this article for someone to introduce him to the Greenbox.

Find the article from Cryptoacid’s new address:

Cryptoacid.wordpress.com

Just today it was announced in the Discord channel that there is now a Master Node competition going on for the next 10 days.

The competition idea is to get Telos nodes to spread all around the world to have a more stable network.

To achieve this, or to at least find out the current situation, anyone with a Telos node can now win 1000 Telos, as long as it is located in a country that hasn’t been listed as a winner yet, excluding Germany, and as long as we are talking of a VPS or own server, so that excludes Blueboxes out of the competition as well.

There is one winner per country, but the same person can win a prize from several countries if he is the first one to tell that he has a node running on a country that has not been claimed yet.

However, it is not enough to just say that you have a node in some country but you need to prove it, and in addition, this node must have been running for at least 7 days.

However, since this is a 10-day long competition, it means that you could actually set up your node to one such country that has not been claimed yet and then 7 days later claim that prize, supposing of course someone else does not do that before you.

To prove that your node has been running for 7 days, it has to be seeable through https://masternodes.online/ or https://explorer.teloscoin.org/ or https://masternodestats.info/

And to claim for a win, you need to do that in the Community Discord I suppose, or at least that is where the first ones have done so.

At the time of writing this, which is roughly 1 hour after the competition was announced, 5 countries have been claimed so far: the USA, Canada, France, Finland, Poland.

Catching up with some old articles to report to you now comes Lucky 7s article from July 25.

This article is telling a bit about stats and giving some other good info too, like where to check the current ROI for different Tiers etc. so well worth a read even some of the stuff is already outdated, but even the outdated stuff is good to have for historical reasons, since it shows what the situation was bit after the mandatory fork.

To read the whole article, head on to, notice this new address, as cryptoacid.com have moved to a new address:

Cryptoacid.wordpress.com

Alejandro Finol has written yet another article which is talking about the recent price drop on Telos as well as some competitions that used to be still going on when the article was written, for, unfortunately, I am telling you about this article with about a two-week delay.

Anyway, Alejandro Finol did do some pretty accurate estimation in his past article about Telos price movement, hence it is worth keeping an eye on what he is talking about the Telos.

Read the article from HIVE BLOG