Noble

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

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.

Kill criteria: the events that revoke this verdict
• 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

The research file

Mechanism and client claim

Noble is a Cosmos SDK chain optimized for issuance and interchain transfer of stablecoins and real-world assets. A permissioned CometBFT validator set produces blocks, while IBC moves native issued assets to connected chains and Circle CCTP supports USDC transfer routes. The worklist’s approximately $128M measures assets associated with the chain, not a fungible Noble yield claim. A client normally holds a specific USDC, USDN or other issuer token whose backing and redemption remain separate from Noble consensus.

Control, governance, and legal perimeter

Official specifications label the consensus model Proof of Authority. Noble does not use a token-holder governance module; instead its Authority module assigns privileged operations to the Noble Maintenance Multisig. The command set supports arbitrary message execution, software upgrades, IBC client recovery, parameter changes and ownership transfer. Validators still supply liveness and CometBFT finality, but they do not eliminate the multisig’s application authority. Circle and other issuers retain freeze, mint, burn and redemption powers over their assets in addition to the chain controls.

Incident and operating record

Noble publishes upgrade histories, genesis files, code and module documentation and has processed substantial stablecoin transfer volume. No unreconciled consensus loss was identified in the reviewed source set. That clean record is positive but does not change the explicit authority design. Software upgrades and IBC client recovery are expected operational actions, while an institutional grade asks whether a client can exit before a privileged change and whether signer and validator independence are measurable. The current source set does not establish an enforceable delay or permissionless replacement for the NMM.

Exit, liquidity, and failure path

A holder exits through an issuer redemption, IBC transfer, CCTP burn-and-mint route, exchange, or secondary market depending on the exact asset. Every path adds a separate dependency: Noble liveness, NMM parameters, source and destination IBC clients, relayers, Circle attestation, issuer eligibility, or market liquidity. Chain TVL does not establish that any one route can carry a proposed-size exit. An authority-led IBC recovery may restore a client but is itself proof that privileged coordination can alter the relevant communication state.

Comparison and decision

Holding USDC on Ethereum keeps Circle issuer control but removes Noble PoA, NMM and IBC layers; holding a crypto-backed stable asset may also reduce issuer freeze power. If a client specifically needs Cosmos-native settlement, Noble can be reviewed as a limited chain dependency after signer thresholds, validators, upgrade notice and exact asset routes are mapped. It cannot be approved merely because reputable issuers use it. Reopen requires a sourced chain grade and issuer-specific profile, not a larger chain balance.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Noble Docs — chain overview · primary · accessed 2026-08-19
  Supports: Cosmos SDK, CometBFT, Proof of Authority, asset issuance
• Noble Docs — Authority module · primary · accessed 2026-08-19
  Supports: NMM, arbitrary execution, software upgrades, IBC recovery
• Noble Docs — chain upgrades · primary · accessed 2026-08-19
  Supports: upgrade history, release process
• Noble GitHub — nobled · primary · accessed 2026-08-19
  Supports: chain code, modules, release history
• Circle Docs — CCTP Noble · primary · accessed 2026-08-19
  Supports: USDC issuance, CCTP transfer path, issuer dependency
• DefiLlama — Noble protocol data · secondary · accessed 2026-08-19
  Supports: protocol category, chain perimeter, current TVL

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.