[Validator Report] Stakely x Celo — Q3 2025 Contributions

Community
1

Hi Celo community :waving_hand:

We’re sharing a summary of Stakely’s contributions to the Celo ecosystem during the last quarter (July–October 2025).

Our goal with this post is:

  1. Provide transparency about our validator performance and ecosystem contributions.
  2. Gather feedback and ideas from the community on how we can further support Celo’s mission in the coming months.

Validator Operations

  • Uptime: 100%

  • Slashing events: 0

  • Delegated stake: 1,592,506.49 CELO

  • Validator score: 100%

  • Validator profile: Stakely Validator on Celo

Technical Contributions

We maintain and fund several public goods to strengthen the Celo infrastructure:

These tools are fully open and free to use by developers, validators, and the broader community.

Community & Educational Contributions

Over the last quarter, we’ve focused on spreading awareness and education around Celo and regenerative finance in our blog through our monthly reviews, and on X via RT, quotes and threads (ex. https://x.com/Stakely_io/status/1958109110521491845).

What’s next

In the upcoming months, we’ll continue supporting the ecosystem through:

  1. Maintaining ≥99.9% uptime and transparent performance reporting.

  2. Keeping Celo Faucet & RPC Load Balancer online and improving throughput.

  3. Expanding educational materials, including staking guides, technical tutorials, and localized content in Spanish, French and English.

  4. Hosting online and in-person meetups (especially in Spain and LATAM) to connect with new users and projects aligned with Celo’s vision.

We’d love to hear from the community:
→ What kind of public goods, educational initiatives, or collaborations would you like to see next?
→ Are there specific technical improvements or integrations you think could benefit the Celo ecosystem?

Let’s keep building together!

— The Stakely Team

7 Likes
2

Awesome. The RPC endpoint is cool, what’s the underlying architecture of the load balancer? Is it open source?

3 Likes
3

Thanks!

It was initially deployed on Cloudflare Workers, but it quickly became expensive as traffic grew. Because of this, we developed our own solution using NodeJS for the health checks, header modifications, and re-routing; Redis as the cache layer, and Kubernetes for scaling and uptime reasons.
It is unfortunately not open source, although the configuration of the nodes and their weights is: https://github.com/Stakely/web3-load-balancer-configuration

2 Likes