RIADeFi
Refusal file · other

Why Ketju rejected Fraxtal

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. The worklist entry measures assets locked for an OP Stack rollup, not a yield product. Fraxtal currently depends on a permissioned sequencer, upgradeable Ethereum bridge proxies, a Frax-team data-availability module, and a seven-day ordinary L2 withdrawal; official materials describe future validator security rather than a live permissionless replacement. Until a separate chain grade proves an enforceable exit window and bounds emergency authority, the bridge balance is rejected as a client position.

What would reopen the file

  • Fraxtal receives a sourced Ketju chain grade with no active rejection criterion
  • Permissionless fault proofs and forced inclusion are live and a proposed-size Ethereum exit completes without sequencer cooperation
  • Every regular upgrade has an enforceable on-chain delay of at least 7 days and emergency authority is independently bounded
  • The production data-availability mechanism and recovery path become independently verifiable

Facts on file

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

← All published refusals