greymass blog

Introducing Light History Nodes for EOS

The state of History API nodes on the EOS network is a growing concern. While we are all exploring long-term solutions, such as our recent sponsorship of the development of a new History Plugin, in the interim, problems continue to arise.

Over the past few weeks, the EOS ecosystem has ground to a halt several times due to the lack of these History API nodes. A few weeks ago, our main History API went offline for a brief period of time, which you can read more about here. Over this previous weekend, we brought our History API node down for approximately two hours while upgrading a switch in our datacenter. During this period of time, applications on the EOS network once again ground to a halt as the only other providers of History API nodes failed under the extreme pressure that they were now bearing.


Converting an EOS account to use a Ledger with eos-voter 0.6.x (Greymass Wallet)

Over the past few weeks we have released a number of updates for eos-voter (0.6.x), which enabled support for Ledger devices. We still haven't even official announced these releases (we're still fixing some bugs), but now that users are upgrading we feel it's important to provide a bit of guidance on how to use it.

A more formal announcement of the 0.6.x release is still in the works. For now, all recent releases can be viewed on our github page:


The value of public APIs and a look inside one of the largest - Greymass

Take a moment to think about your favorite EOS apps. Do you know which networks power them? Which API nodes they connect to? Don't feel bad if you don't — after all, API nodes aren’t really a hot topic. Like a lot of back-end technology, people don’t pay attention unless something breaks. But high-quality infrastructure and API nodes play a crucial role in EOS ecosystem, allowing for the development of apps and the movement of data across the network.

Here at Greymass, we have always put a premium on having products that provide value and the back-end technology to support them. You may know us primarily for our project eos-voter wallet, but we have also put a large amount of time and energy into ensuring that our API nodes are of the highest possible quality, with up-to-date technology that allows it to serve a significant portion of the EOS community.


eos-voter 0.5.2 - Proxy Information + Bug Fixes

Today we released a small upgrade to the eos-voter tool, featuring many bug fixes and a new interface to browse and select a BP Voting Proxy (based on the work by AlohaEOS and their regproxyinfo contract). We are pretty deep into the 0.6.0 release, but decided to release a minor build to address the issues plaguing users currently.

Changes What is eos-voter? Where to download eos-voter Feature Overview Coming Soon File Signatures Read more...

Performance and Transaction Billing on EOS: A Cooperative Effort, Not a Competitive One

In collaboration with the great teams and Block Producers Aloha EOS and EOS Titan, we recently launched the EOS Mechanics initiative in an effort to research how transactions affect the performance of EOS and interact with block production hardware. Our goal is to help optimize all block production through empirical research data, and to guide everyone towards a collectively improved EOS network.

However, we would like to stress that Block Producer relative performance is not a competition. Comparing Block Producers to each other is not the goal of this project. If such comparisons are taken into account when voting, then the project could harm the very network that it is trying to improve. This post outlines why performance improvements need to be a cooperative effort, and explains some of the issues that could be faced if a competitive route is chosen instead.