Start Building on Flare: What You Need First
Building decentralized apps on Flare isn't complicated—but a few basics help before you jump in.
We've helped dozens of developers transition from traditional web development to blockchain. Most struggle with the same questions at first. This guide walks through what you actually need, not the theory you can read anywhere.
Our Path: From First Smart Contract to Production dApps
We didn't start as blockchain experts. Here's how we grew from experimenting with simple contracts to shipping real applications that people use daily.
First Flare Testnet Experiments
Started testing Flare's data protocols after years of working with Ethereum. The state connector concept clicked for us—getting real-world data without oracles felt different.
First Production Application Launch
Shipped a cross-chain payment tracker for a logistics company in Taipei. Eight months from concept to deployment. Learned more from that project than the previous two years combined.
Expanded Team and Training Program
Brought on three developers who'd never touched blockchain before. Created our internal training materials because existing tutorials didn't match real development workflows.
Opening Education to Taiwan Market
Those training materials worked well enough that we're sharing them. First cohort starts September 2025. Small groups only—we want actual conversations, not lecture halls.
Production Applications
Live dApps we've built and maintained since 2022. Payment systems, data bridges, asset management tools. They run quietly—which means they work.
Development Partners
Companies across Taiwan and Southeast Asia who trusted us with their blockchain infrastructure. Finance, logistics, insurance—sectors where mistakes cost money.
Developers Trained
Team members and contractors we've onboarded to Flare development. Most came from React or Python backgrounds. All shipped features within their first month.
Transactions Processed
Combined activity across our deployed contracts. Not all flashy—lots of routine data queries and asset transfers. But each one represents a working system someone depends on.
Who's Teaching This Stuff
Three people who write code daily and occasionally explain it to others.
Eirik Sandvik
Lead DeveloperBuilt web applications for twelve years before touching blockchain. Switched to Flare in 2022 after getting frustrated with Ethereum gas costs on a personal project. Now handles architecture for client systems.
Livia Toivonen
Smart Contract EngineerCame from backend Python work at a fintech startup. Learned Solidity during maternity leave in 2023—decided auditing contracts was more interesting than REST APIs. Writes most of our security documentation.
Dag Lindholm
Integration SpecialistSpent years connecting payment systems and databases—boring middleware stuff. Blockchain integration turned out to be similar patterns with different tools. Handles the part where dApps talk to real-world systems.
What Makes Flare Different for Developers
Most blockchain platforms make you choose between decentralization and real-world data. Flare's state connector and FTSO protocols change that—you get verified external data without trusting a single oracle provider.
This matters for practical applications. When a logistics company needs proof a shipment crossed a border, or a DeFi app needs accurate price feeds, you can't rely on "trust me" solutions.
Our training program starts in September 2025 because we want to prepare materials properly. We'll cover smart contract development, data integration patterns, and security practices—the stuff that actually matters when you're shipping code.
See Program Details