Removing one node from the authset in May

You are viewing an older update. There is a newer update available.
Previous Update: Removing one node from the authset in May
As we already made clear updates about other happenings will come by my colleague Abe Scholten.

Since the start of M3 we have had a virtual private cloud in Dubai which is way more expensive than some random AWS node. We did this to decentralize and with the expectation of medium term growth of the network.

As that hasn't panned out, but we still need to pay the bills for it and are net negative from infa costs alone, we have decided to remove the specific node from the authset and open up positions for new ANOs wanting a node.

We have been at 35% efficiency all of last year I believe, whilst prices and our application document and subsequent election into the authset would have warranted to be at 0% efficiency. We have taken this hit, because we believe in the grantpool, but at this time we simply cannot justify our expenses going through the roof.

We will see at what point we will change our efficiency because of it.
 
You are viewing an older update. There is a newer update available.
Top