Flare

Flare exists to give smart contract functionality to assets on chains that do not support it — Bitcoin, XRP, Litecoin and others. Rather than asking those chains to change, it builds infrastructure for observing them and acting on what it sees.

Two protocols do the work

One provides decentralised price data supplied by many independent providers. The other allows the chain to verify that a specific event occurred on another blockchain — a payment made, a transaction confirmed — so contracts can act on external state without a custodial bridge holding funds.

Why non-programmable assets are a real market

Very large amounts of value sit on chains with limited or no smart contract capability. Their holders cannot lend, hedge or automate without moving to a wrapped representation on another chain, which introduces custodial risk. Solving this without wrapping is genuinely useful.

Verifying external state is harder than reading a price

A price feed reports a number many parties can check. Confirming that a specific transaction occurred on another chain requires the network to reach consensus about another chain's history, which is a harder problem and where designs in this category typically fail.

Data providers are the trust assumption

Both protocols rest on independent participants supplying accurate information, incentivised by rewards and penalties. As with every oracle, the security question is how many independent providers there genuinely are and how difficult they would be to corrupt collectively.

What to weigh

A well-defined problem with a coherent approach. Its success depends on holders of non-programmable assets actually wanting DeFi functionality enough to use a separate network for it, which is an adoption question rather than a technical one.