Stakely contributions update: IP Faucet + Public Story RPC/JSON-RPC Load Balancer + Ecosystem Reports

Validators
,
1

Hi Story community :waving_hand:

Following up on our intro thread, we wanted to share a short update with public metrics for our Story IP Faucet, our public Story RPC/JSON-RPC Load Balancer, and the community resources we’re maintaining.

1) Story IP Faucet (Mainnet) — Metrics snapshot

Link: https://stakely.io/faucet/story-ip

Our goal with the faucet is simple: help builders and community members get a small amount of IP for gas when they need to interact with the network.

Current public stats (as displayed on the faucet page on Jan 28, 2026):

  • Faucet amount: 0.0003 IP

  • Remaining faucet balance: 19.28 IP

  • Total requests: 5

  • Last activity: 8 days ago

How it works (anti-abuse flow): address → captcha → tweet verification → receive tokens.

Video tutorial:
https://x.com/Stakely_io/status/2013584057402032437

2) Story APIs — Public RPC & JSON-RPC Load Balancer

Link: https://stakely.io/web3-api-load-balancer/story

We’re running a public load-balanced endpoint for Story to improve reliability for devs and apps by distributing requests across multiple nodes/providers.

Endpoints

Key features

  • Node monitoring

  • Request retrying (fallback after timeout)

  • CORS enabled

  • Intelligent caching

  • Request re-routing

  • Distributed deployment

Balanced nodes
The page includes a live list of balanced nodes/providers (with sync height and status). At the time of writing, it includes providers such as Stakely, Cosmic Validator, Polkachu, and It Rocket.
We also welcome community contributions to the load balancer configuration via GitHub:
https://github.com/Stakely/web3-load-balancer-configuration

3) Weekly Story reports (community updates)

We publish quick weekly updates so delegators/builders can keep track of the network and ecosystem highlights:

Feedback / requests

If there are specific metrics you’d like us to include next (faucet usage, RPC health indicators, latency, error rates, etc.), tell us what would be most useful and we’ll incorporate it.

Thanks for reading!