Happy Saturday and howdy from the Cypherglass Infrastructure team! We dropped down to position 42 this week which has been a tough blow to our infrastructure. It’s anxious to make blocks, and is encouraged that we moved up one to position 41 today. It’s been a very slow week here at Cypherglass, as several people have been out on vacation, sick, and dealing with family emergencies. Nevertheless, the intrepid infra team has been diligently supporting and maintaining our world class architecture. Let’s take a look at what happened this week:

It’s official… Block.One poached our developer Leo Ribeiro (Just kidding, we were very supportive of Leo’s move, Congrats Leo!). Due to a conflict of interest, and time, Leo will no longer be able to turn out amazing products like Windshield, Lens and Glass for Cypherglass. We know it’s best for the EOS network, but we are still sad to see Leo go. Certainly a testament to Leo’s programming prowess (and our keen eye for talent) that big brother swooped in and grabbed him. If you know someone who loves making cool EOS tools tell them to hit us up. Along with other block producers, we saw some problems while testing new versions of NodeOS. We tested versions 1.1.3 and 1.1.4 in our lab, and saw enough issues that we chose to stay on version 1.1.1. Block.One worked directly with several BPs and released versions 1.1.5 and 1.1.6 which seem to have resolved the problems that we were seeing. Upgrading nodes, and then rolling back, required a lot of effort this week. We attempted to swap out RAM in our Kansas City production Cisco UCS blades this week, but saw some incompatibility problems that caused us to stick with the old RAM. Since our design is completely redundant, we didn’t experience an outage. We are still working with hardware vendors to resolve the problem, and swap over to the new RAM. Another item that occupied a decent number of cycles for us this week was an issue with NodeOS version 1.1.1. If a node is up for a long time, and has a lot of connections to other nodes it becomes less responsive. We spent good amount of time monitoring and restarting nodes to keep them up and responsive to the community needs.

So in terms of maintaining a block producer infrastructure, that’s what we call a quiet week. No 2 AM alarms going off, no emergency calls from other BPs, just a nice steady week of feeding and watering the nodes.

Please feel free to reach out to us if you have any questions about what we are doing to make the EOS network and community better.

— The Cypherglass Infrastructure Team

Learn more about Cypherglass on our Steemit channel here. Join us in discussions on our Telegram channel here. Or check our our website at http://www.cypherglass.com