Console Guides

Wallets

Register non-custodial addresses for monitoring, manage wallet-scoped webhooks, browse supported chains, and estimate or broadcast a transaction, all without Mudbase ever holding a private key.

Find it

Wallets is in the sidebar under the Engage group (marked NEW). Everything here is public-address monitoring and already-signed transaction relaying; Mudbase never signs anything on your behalf.

Monitored addresses

Wallets page with a stats row (monitored addresses, wallet webhooks, supported currencies, fee oracle entries) and a Monitored addresses table with three rows across Ethereum, Polygon, and Bitcoin, two active and one inactive
Three registered addresses: two active and being synced, one deactivated with an Activate action
  1. Opens a form for a public address, chain, optional derivation path, and label. Registration is a client-side-only operation; no keys are ever sent or stored.
  2. Counts across this project: registered addresses, wallet webhooks, chains/currencies Mudbase supports, and fee-oracle entries currently cached.
  3. Every registered address with its chain, label, last sync/transaction time, and status. Deactivate offers a soft delete (stop monitoring, keep the record) or a permanent delete; an inactive row shows Activate instead.

Wallet webhooks, currencies, fees

Wallet webhooks table showing one active webhook with delivery stats, a collapsed Supported currencies & chains card, a Fee oracle snapshot card showing 13 cached entries, and the start of an Estimate network fee form
One active webhook at 16/18 successful deliveries, alongside real fee-oracle data
  1. Webhooks scoped to wallet events (balance updates, transaction confirmed/failed/ detected/broadcast), separate from the project's general-purpose Webhooks page. Click a row to open its full edit/test/delivery-log page.
  2. Opens a form for URL, one or more events, an optional HMAC secret, and optional address/chain filters.
  3. A collapsible list of every chain and currency Mudbase supports for wallet monitoring (18 entries as of this build); expand to browse.
  4. How many chain fee entries are currently cached and when they were last refreshed. This populates from real network traffic, not from anything you configure.

Estimate fee, broadcast transaction

Estimate network fee form with currency and amount fields and a Calculate fee button, and a Broadcast a signed transaction form with chain, signed transaction textarea, optional from address, and a Broadcast button
The two lowest-level tools on this page: fee estimation and raw transaction relaying
  1. Network-fee-only estimate (no Mudbase platform fee added) for a currency and amount; USDT additionally requires picking a network since it settles on several.
  2. Relays an already-signed raw transaction to the network: paste the hex or raw blob from your own signing step. An optional From address links the broadcast to a registered wallet for tracking; it's never used to sign anything.
Note
Block-scanner metrics behind wallet monitoring are in-memory only (services/wallet/scannerMetrics.js) and need a live, continuously-running chain-scanner process; they reset on every backend restart and can't be seeded into a database. Everything shown on this page (addresses, webhooks, currencies, and the fee oracle) is otherwise real, persisted data.
Chat with us