RIADeFi
Refusal file · other

Why Ketju rejected Noble

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. Noble is an application-specific asset-issuance chain, not a passive protocol investment. Its current documentation identifies CometBFT Proof of Authority and no governance module; a designated Noble Maintenance Multisig can execute arbitrary authority messages, software upgrades, IBC recovery, and parameter changes. That concentration is an intelligible tradeoff for regulated issuers, but it fails the settlement-control floor for a blanket client allocation and must be decomposed into chain, issuer, and IBC dependencies.

What would reopen the file

  • Noble receives a sourced chain grade with a disclosed validator set, NMM signer threshold, independence map, and enforceable upgrade delay
  • The Noble Maintenance Multisig loses arbitrary execution or every privileged action receives at least 7 days of on-chain notice
  • The exact client asset and IBC or CCTP exit route receive separate approved profiles and pass a proposed-size test
  • Any authority, consensus, IBC, or issuer incident opens an immediate review

Facts on file

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

← All published refusals