Skip to content
Fork
API checking
Base 8453Moonwell Core

The model proposes. The EVM proves.

Know the next protocol change before it hits the wallet.

Paste a Base address or use a demo wallet. Numbers appear only after the API reads the Comptroller. Fork then replays a supported change on a mainnet fork so solvency is decided by contracts, not the model.

Analyze a Base address
No dashboard numbers are shown until the API returns a real wallet snapshot.

Connecting a wallet is separate and does not prove ownership.

Demo wallets

  1. 01SnapshotRead the wallet from the live Moonwell Comptroller on Base.
  2. 02ReplayApply the supported destination effect on an Anvil mainnet fork.
  3. 03DecidePost-state invariants mark SAFE, AT_RISK, or SHORTFALL.

Comptroller-backed numbers

Positions and risk come from Base 8453 after the API returns a real snapshot. Nothing is invented in the UI.

Destination-effect replay

Proposal 176 is the supported Moonwell Core replay. The model can propose a plan. Only the EVM proves it.

User-signed execution

Rescue plans stay unsigned until the connected wallet approves. Fork never holds keys.