Interested in trading on the dYdX Chain? Trading Rewards and the 6 month Launch Incentive Program is live
Trade Now
About Ops
Structure Overview
Framework and roles defining our DAO.
Mandates
Key mandates guiding our DAO.
AMA Recordings
Recorded DAO discussions.
Resources
subDAO Handbook
A guide to building the future of dYdX governance
Finance
Overview of dYdX Ops subDAO's financials.
Legal Documents
Overview of dYdX Ops Legal Documentation
Feedback Form
Use this form to detail your issue with our platform
dYdX Chain
Mintscan
dYdX Chain explorer
Documentation
Mainnet relevant documentation
Careers
Blog

Q&A with Lavender Five: RPC & Validator OGs of the dYdX Chain

dYdX Ops
Jul 15, 2025

Introduction:

Lavender Five is one of the most recognizable infrastructure providers in Cosmos, and one of the earliest supporters of the dYdX Chain. From validator operations to a robust RPC setup, they’ve helped build and sustain networks from the ground up. With deep roots in Cosmos and a reputation for shipping solid infra with minimal noise, they’re the quiet force behind many mission-critical systems.

We sat down with Gijs from the Lavender Five team to talk about what drives them, how they think about decentralization, and what it really takes to operate RPC and validator services at scale.

Disclaimer: This interview was conducted over a live call and has been edited for clarity and flow. While we’ve done our best to capture the key points and tone of the conversation, some details may differ slightly from the original discussion.

‍

Q: Can you give us a quick overview of what Lavender Five does and how you contribute to dYdX?

‍

Sure. Lavender Five is a Web3 infrastructure firm that focuses on two core areas: validator services and RPC infrastructure. We’ve been operating since around 2020 - 2021, starting with early Cosmos chains like Osmosis and Secret, and now run infra for more than 60 networks - including Solana, Aptos, Celestia, and of course, dYdX.
‍
We’re a small but tight-knit team of three - myself, James, and the founder Dylan. All three of us are technical, and although we each have different focus-aread, we all work hands-on across every chain we support. That means all of us  understand the stack, run infra directly, and take part in every upgrade and issue.
‍
On dYdX specifically, we’ve been contributors since the early testnet days, running a validator and offering public and commercial RPC endpoints. We’ve seen the chain grow from a technical idea to a live network with serious adoption, and we’re proud to be a part of that.

Q: You run infrastructure for a huge number of chains — how do you manage the technical load?

A lot of it comes down to having a solid architecture. We have a consistent way of operating the machines, and a proxy/cluster layer that sits on top. Once that’s in place, adding new networks becomes fairly trivial - you just need to handle the quirks of each binary.

We also don’t split things up across big teams. All three of us know every single network we work with - which RPCs are running, how the contracts work, and so on. That gives us a kind of depth that’s hard to match in larger orgs where things are more siloed.

‍

Q: What originally drew you to the dYdX Chain?

When dYdX v4 was announced, it was one of the few products in crypto that was actually making money. Back then, most chains were just handing out tokens and hoping something stuck. dYdX had product-market fit, actual revenue, and a serious technical challenge they were taking on.

We also knew some of the folks helping build the chain and saw they were going to make use of underused features in the Cosmos SDK - that was exciting for us. We like working with teams that are trying to do something new on the tech side, not just copying what’s already out there

Q: What advice would you give to someone looking to run a public RPC or become a validator?

Be clear about your motivation. Are you doing it for fun, as a side project, or as a business? Running an RPC or validator as a business isn’t easy. You need to love systems architecture and be ready to deal with disk failures, internet outages, or late-night alerts.

Start small. Run on a testnet, stake your own tokens, and get your hands dirty. It’s about building experience and figuring out how to stay calm and effective when things go sideways.

Don’t expect it to be easy, and definitely don’t expect it to be super profitable right away. This kind of work is technical, stressful, and often thankless. You’ll be woken up at 3am to fix something that broke and no one will even know you did it. But if you enjoy that kind of challenge, it can be super rewarding. We always say this is kinda like DevOps with even more fire drills. If that sounds fun to you, then go for it. You get to work with awesome builders from the earliest stage which is a joy in and of itself.

Q: What’s something about Lavender Five that people might not know?

We have a tool page: lavenderfive.com/tools - that has everything you need to get started with dYdX or other networks: mainnet info, testnet links, endpoints, guides, and more. It’s one of our most visited webpages.

Also, you can follow us on Twitter: @lavender_five

‍

Conclusion

Thanks to Gijs and the Lavender Five team for sharing their story and insights.

Stay tuned for more Validator & Service Provider Spotlights!

‍

Disclaimer:

The content of this document (this “Document”) is provided for general informational purposes only. This Document represents the views and opinions of the author of this Document, and does not necessarily represent the views or opinions of the operator of this website or its affiliates (collectively, the “Ops subDAO”). Reference to any specific strategy, technique, product, service or entity does not constitute an endorsement or recommendation by the Ops subDAO or any of its agents or representatives. Use of any strategies, techniques, products or services, or engagement with any entities referenced in this Document may involve material risks, including risks of financial losses arising from the volatility, operational loss or non-consensual liquidation of digital assets. 

The content of this Document does not constitute, and should not be considered, or relied upon as, financial advice, legal advice, tax advice, investment advice or advice of any other nature, and you agree that you are responsible for conducting independent research, performing due diligence and engaging a professional advisor prior to taking any financial, tax, legal or investment action related to the foregoing content. The content of this Document is not an offer, solicitation or call to action to make any investment of, or purchase, any financial or crypto instruments, assets or related services, of any kind. The Ops subDAO makes no representation, assurance or guarantee as to the accuracy, completeness, timeliness, suitability or validity of any information in this Document or any third-party websites that may be linked herein. 

By accessing this Document and taking any action in connection with the information contained herein, you agree that the Ops subDAO is not responsible, directly or indirectly, for any errors, omissions or delays related to this Document, or any damage, injury or loss incurred in connection with use of, or reliance on, the content of this Document, including any specific strategy, technique, product, service or entity that may be referenced in this Document. dYdX Chain services and products are not available to persons or entities who reside in, are located in, are incorporated in, or have registered offices in the United States, Canada and other restricted jurisdictions (in accordance with the Terms of Use.

‍

Connect with Us

Dive deeper into the dYdX Operations subDAO community. Engage in discussions, stay updated with announcements, and be part of the dYdX Chain.

Twitter
Forum
Discord
Copyright © 2025 dYdX Operations subDAO
Privacy NoticeTerms of Use