It’s been another exciting week at Cypherglass, and since we believe that the EOS token-holders own a part of every Block Producer, we like to let folks know what’s going on. We’ve gradually moved back up the Block Producer positions from 30th to 26th, and we will keep moving up. We are particularly happy with our position in that it is based on many smaller token-holder votes, the folks that we feel really make EOS great. In our constant quest to be the best, we’ve also done some cool things to our environment this week. This doesn’t represent everything we did, but we like to call out some of the bigger items we accomplished.
- Cypherglass Lens was released very late last week, so it didn’t make it into last weeks update. Take a look at it if you haven’t already. It’s truly the safest and easiest way to vote, but please only use it to vote for excellent Block Producers that are always transparent. :-)
- Work is fully underway on our Cypherglass Glass portal. The first rev will enable users to see exactly where Block Producer nodes and headquarters are located on a very cool map interface.
- We upgraded our production environment to NodeOS mainnet-v1.0.8. We tested it thoroughly in our lab last week, made a few changes to our environment setting based on that testing and felt safe to deploy.
- We began testing NodeOS mainnet-v1.0.9.
- While testing 1.0.9 Block.One released 1.0.10 with some fixes for 1.0.9. We are now testing it in our lab.
- We added a Blockchain Backup node to our environment. This node creates and holds copies of the whole blockchain and is updated regularly. In case there is a problem and we have to roll-back to a point in time on the blockchain, this allows us to do it within fifteen or twenty minutes. The blockchain is getting bigger and bigger so if we had to rebuild the whole blockchain it could take more than a day. Whew. Glad we have this up and running.
- Added port 80 to our API node at the request of several developers.
- Fixed and tested the History API on our proxy nodes. A recent change to the software caused many history_api nodes to have problems. While our nodes stayed up through the problems, one side effect was that our history_api no longer held data back to the beginning of the main-net chain. That is now fixed and even the first transactions ever made can be seen through our api.
Have a great weekend and remember you can always learn more about Cypherglass here: