Lavender.Five Nodes

We take a pragmatic approach to running validators. At the most basic level we utilize bare metal servers with a minimum of 2 full nodes per network. Each server is with a different provider, Cherry, Ionos, PhoenixNap, DigitalOcean, AWS, Hetzner, OVHCloud, or MEVspace, spread across multiple geographic locations. All servers follow strict access policies via SSH keys and we use hardware validator key storage if possible.

Within the cosmos Ecosystem we supplement this with Horcrux as our remote signing solution, with 3 signers. What this means in practice is ALL nodes have to go down, or 2 signers, before we miss a single block. On other networks Lavender.five leverages automated node creation to have close to no downtime in server emergencies or maintenance.

We combine This with a 24/7 redundant monitoring setup so that you do not have to worry.

Lavender.Five aims to vote on every single governance proposal and participate in forum and other discussions as much as possible. We go further where needed, example contributions are Cosmos Replicated security advanced feedback and our Active feedback on Aptos improvement proposals.

Our vales – **Wholesome and Pragmatic**
More and more people are drawn to the promise of web3. Yet, as an industry, we have miles to go. At Lavender.Five, we leverage our expertise to provide a transparent perspective on the state of blockchain technology. We pride ourselves on our forthright governance approach and our commitment to accessibility for all communities we serve.

Nothing in the real world is black & white. People face complex decisions and problems to solve every day—even the most experienced of us struggle sometimes. We believe in taking an iterative, incremental, and realistic approach to improving software day by day—WITHOUT EVER cutting corners.

Lavender.Five supports builders!