Pinned Tweet
[BOUNTY PROGRAM]
Searching for RPCs, Oracles, Bridges doesn't have to be complicated.
Doing good for web3 doesn’t have to be complicated.
Contribute to Chain.Love open-source database → help builders → earn a bounty.
🧵(1/2)
Chain.Love began as a practical answer to a real infrastructure need: reliable public RPC access for builders.
Proud to see that work included in Protofire’s 10-year look back. Congratulations to the team.
Chain.Love retweeted
The Protofire team will be in Warsaw on September 9–10, and we’re opening a few slots for B2B meetings while we’re in town.
If you’re a bank, CASP, asset manager, fintech, Web3 protocol, or infrastructure team building around DeFi, tokenization, RWA, stablecoins, or onchain finance more broadly, we'd like to hear what you're working on.
We're setting aside 30-minute architecture fit meetings: what you're building, where the technical and infrastructure pressure actually sits, and whether Protofire is the right partner to design, build, or run the systems behind it. We've delivered 250+ projects since 2016, so most of these conversations start from something we've already shipped.
In Warsaw on September 9–10? Send us a message to set up a meeting.
Chain.Love retweeted
Spent the day filling holes in the @chainloveweb3 Web3 provider database: 161 empty cells across 113 providers, every value taken from the provider's own site or GitHub org.
Four PRs:
github.com/Chain-Love/chain-…
github.com/Chain-Love/chain-…
github.com/Chain-Love/chain-…
github.com/Chain-Love/chain-…
Chain.Love retweeted
The Forest team’s been in the trenches, making Forest's Ethereum-compatible JSON-RPC faster, and faster, and faster. Check out the latency on these RPC calls from @chainloveweb3
1/ April contributor rewards are live!
This month, rewards went to contributors who helped expand and maintain the Chain.Love open-source infrastructure database across providers, networks, APIs, and related ecosystem data.
Small contributions compound when the database keeps growing.
2/ The April update is now published in our GitHub Discussion:
github.com/Chain-Love/chain-…
Thanks to everyone contributing to ChainLove and helping make Web3 infra easier to discover, compare, and navigate.
We added almost every network we could map to ChainLove.
Good luck counting them💚
Now you can jump between chains, explore available infra providers, and compare RPCs, explorers, indexers, oracles, bridges, dev tools and more from one place.
Soon, developers won’t be the ones choosing infrastructure. Agents also will.
But the current Web3 stack isn’t built for that:
> fragmented providers
> inconsistent APIs
> too much manual integration
🤯
2/
MCP Gateway is a step in that direction.
A unified interface where agents can:
> discover
> access
> interact with infra
Same providers. Different interface.
chain-love.gitbook.io/mcp-mo…
We’ve been tracking contributors to ChainLove every week. Contributions and their how.
And a few patterns became obvious:
> most contributions don’t come from “top devs”
> people start small (fix → add → improve)
> consistency beats skill
2/
What surprised us most:
Good infra data is not built by experts alone — it’s built by people who care enough to update it.
That’s how 78,000+ providers start to make sense.
We publish weekly stats + breakdown here:
github.com/Chain-Love/chain-…
Okay, it's not a secret anymore, but...
Starting next week, Chain.Love Toolbox will automatically launch across all networks in our database🤯
Every chain → its own live infra hub
Every provider → instantly discoverable
One interface. One standard. Pure💚
Our Italian friend says:
“No news, good news.”
Meanwhile us shipping updates every week:
🤌 …so are we doing this wrong?
We did a slightly crazy thing.
We took all networks.
Put them into one instance.
Now you can scroll through 78,000+ providers / agents in one place.
Just imagine that for a second - everything, across all chains, in a single view.
👇
2/
It’s a bit of a mess.
But a beautiful one.
Take a look:
app.chain.love/toolbox/apis















