RIADeFi
Refusal file · other

Why Ketju rejected FAssets (Flare Network)

Memo v1Published by Ketju Research

A registry memo, published verbatim and versioned. Superseded versions are recorded, never edited away. A rejection is a judgment for Ketju's client base and thesis, not a universal safety claim. Not investment, legal, tax, or compliance advice.

The memo

REJECTED ON TWO STANDING FACTS: A MANUAL-MULTISIG CUSTODY LAYER THE DESIGN ITSELF WAS MEANT TO REMOVE, AND A SCOPE GAP BETWEEN THE PRODUCT NAME AND WHAT IS ACTUALLY LIVE. FAssets is Flare Network's over-collateralized, agent-based bridge for non-smart-contract assets, verified by Flare's own decentralized Data Connector rather than a small custodian — a genuinely different architecture from WBTC- or BTCB-style wrappers on paper. But a "Core Vault" added in a 2025 upgrade reintroduces manual multisig custody, signed off by named entities cooperating with the Flare Foundation, on top of the agent design that is supposed to be FAssets' core differentiator, and Flare's own documentation frames this as a deliberate, temporary tradeoff. Separately, only FXRP is confirmed live; FBTC remains unlaunched, so the roughly $158M tracked under this entry should be read as effectively XRP-only exposure today, not the diversified multi-asset backing the FAssets name implies.

What would reopen the file

  • FAssets v2's trusted-execution-environment-based automation ships, removing the Core Vault's manual multisig custody dependency
  • Agent registration is confirmed genuinely permissionless, or the verification criteria are fully disclosed and shown to be non-discretionary
  • FBTC or another additional asset reaches confirmed mainnet production status, with this entry's scope updated to match actual live backing
  • Twelve consecutive months with no Core Vault signer compromise, agent-default cascade, or Alert Mode activation

Facts on file

Verdict
Rejected
Exposure
other
Chains examined
Ethereum
Memo version
v1
Reviewed
Next review

← All published refusals