Team

FlareForge started as a side project. I wanted a single place where you can explore FTSOv2 feeds, backtest data-provider strategies, watch block-level network health, and poke at FAssets without bouncing between five different block explorers and a Notion doc. So I started writing it.

I'm a DevOps engineer. FlareForge gets built late at night and on weekends, between day job, family, and sleep. Progress is slow, which is fine. The kind of code that touches live oracle data and production RPC endpoints needs to be written carefully, not shipped fast.

Why Flare? Because FTSOv2 block-latency feeds, the Flare Data Connector, and FAssets are genuinely novel primitives. On-chain price data without oracles you have to trust. Verified cross-chain proofs without bridges that can be drained. Yield-bearing wrapped BTC with full collateral transparency on-chain. Most tooling for this ecosystem is scattered across GitHub repos and Notion docs. FlareForge tries to be the one place where you can see it and play with it.

What this is (and isn't). This is not a startup. No token, no fundraise, no exit plan. It's a personal project I built to learn Flare in depth and to see whether a useful public developer platform for the ecosystem could come out of one person and a weekend habit.

Everything here runs on my own hardware and my own card. The workstation that powers the indexer, the domain, the Cloudflare Tunnel, the RPC calls. No grants, no VCs, no DAO. If a feature lands, it's because I wanted it or someone asked for it on X.