Overview
Validator Name: Lavender.Five Nodes
Operator ID(s):
storyvaloper176a2tjaqc9hxfzluuq6k6c3d7ysw8sv4arjyda-(0xf6baa5CBa0c16e648bfce0356d622Df120E3c195) [ unlocked ]
Website: https://lavenderfive.com
Twitter: https://x.com/lavender_five
Infrastructure
Type: Bare-metal (partially self-hosted)
Regions: North America + Europe
Security Certs: SOC2
Experience
Operating Since: 2020
Networks Validated: 50+
Story Mainnet Uptime: 99.9% - daily reference available at Stake STORY | Story Protocol analytics & blockchain research or https://staking.story.foundation/validators/0xf6baa5cba0c16e648bfce0356d622df120e3c195
Story Testnet (Iliad/Odyssey): Yes we are operating on testnet
Story Ecosystem Contributions
Technical Infrastructure
- Operate public and API-key authenticated RPC endpoints for both consensus and execution clients (JSON-RPC/REST/LCD) with generous trial periods
- Provide CometBFT snapshots, execution client snapshots, seed nodes, and peering services via lavenderfive.com/tools/story/overview
- Run redundant bare metal infrastructure across EU and NA with automated failovers
- Operate on testnet and provide tooling and RPC access for that as well.
Community & Apps
- Built and maintain Story Staking UI - a simplified staking interface that auto-selects operators based on uptime metrics and offers one-click staking periods + transparant APR
- Host dedicated Story network page with live metrics: lavenderfive.com/networks/story
- Previously published educational content including a blog on Story Protocol and on-chain IP and featured Tim on our Game of Nodes podcast
Why Delegate to Us?
Lavender.Five delivers a complete infrastructure package for Story: public RPC, snapshots, monitoring tools, and a user-friendly staking UI— all while being a professional SOC2 certified infrastructure company that helps another 100k users secure their stake across 50+ networks. We’re a no-BS operator with 24/7 support, strong developer relationships, and a track record of honest infrastructure pushing network and community further than with just operating nodes.