Mithril snapshot fails with DNS resolution error in Whonix/Tor environment (even on Sync from genesis)

[StevenTCramer]

Description

Daedalus 8.0.x crashes during startup with a DNS resolution error when trying to reach the Mithril aggregator, even when choosing "Sync from genesis".

This happens inside Whonix (Tor-only environment).

Environment

• Daedalus version: 8.0.x (installed via official .bin from daedaluswallet.io)
• OS: Whonix Workstation (Debian-based, forced through Tor)
• Network: Tor only (no clearnet)

Steps to reproduce

1. Fresh install of Daedalus 8.0.x on Whonix.
2. During first run, Mithril fast sync fails with DNS error.
3. Choose "Wipe chain & retry" -> same error.
4. Choose "Sync from genesis" -> still crashes with the same DNS error before syncing starts.

Error

Error: Can not get the list of artifacts while retrieving the latest cardano db hash
Caused by:
  0: Failed to list latest Cardano database v2 snapshots
  1: Remote server unreachable
  2: error sending request for url (https://aggregator.release-mainnet.api.mithril.network/...)
  3: client error (Connect)
  4: dns error
  5: failed to lookup address information: Name does not resolve

Additional info

• nslookup aggregator.release-mainnet.api.mithril.network works fine from the terminal inside Whonix.
• Multiple full wipes of chain/, state/, Secrets/, tls/, wallets/, and lockfiles were performed.
• The crash happens consistently even with no chain data present.
• This appears to be a failure of the Mithril client inside Daedalus to resolve the aggregator hostname through Whonix's Tor DNS setup, and it does not fall back gracefully to genesis sync.

Expected behavior

Daedalus should either successfully use Mithril when possible, or fall back cleanly to "Sync from genesis" without crashing when the Mithril endpoint cannot be resolved.

Logs

(Attach or paste relevant parts from ~/.local/share/Daedalus/mainnet/Logs/mithril-bootstrap.log and recent cardano-node logs)

[StevenTCramer]

Additional log findings

After reviewing the logs from ~/.local/share/Daedalus/mainnet/Logs, there appear to be two relevant failure paths.

1. The Mithril DNS failure repeats consistently in mithril-bootstrap.log.

mithril-client-cli is 0.13.9, and the same aggregator lookup failure appears multiple times:

{"mithril_client_cli_version":"0.13.9"}
Error: Failed to list latest Cardano database v2 snapshots

Caused by:
    0: Remote server unreachable
    1: error sending request for url (https://aggregator.release-mainnet.api.mithril.network/aggregator/artifact/cardano-database)
    2: client error (Connect)
    3: dns error
    4: failed to lookup address information: Name does not resolve

The higher-level failure also repeats:

Error: Can not get the list of artifacts while retrieving the latest cardano db hash

Caused by:
    0: Failed to list latest Cardano database v2 snapshots
    1: Remote server unreachable
    2: error sending request for url (https://aggregator.release-mainnet.api.mithril.network/aggregator/artifact/cardano-database)
    3: client error (Connect)
    4: dns error
    5: failed to lookup address information: Name does not resolve

2. When genesis sync is attempted, cardano-node appears to start from genesis but then exits with an io_uring permission error.

From node.log, repeated startup attempts show:

No valid last location was found. Starting from Genesis.
Opened imm db with immutable tip at genesis (origin) and chunk 0
Opened empty Volatile DB
Started opening Ledger DB

cardano-node: setupURing: permission denied (Operation not permitted)

This repeats many times. cardano-wallet.log then shows the wallet backend repeatedly starting, failing to connect to the node socket, and shutting down:

Wallet backend server listening on https://127.0.0.1:<port>/
Node Tip node client: Couldn't connect to node (x2). Retrying in a bit...
Delegation Rewards node client: Couldn't connect to node (x2). Retrying in a bit...
Chain Sync node client: Couldn't connect to node (x2). Retrying in a bit...
Starting clean shutdown...

cardano-wallet.log also repeatedly logs DNS resolution failures for NTP:

ntp client experienced io error Network.Socket.getAddrInfo (... host name: "0.de.pool.ntp.org" ...): does not exist (Name does not resolve)

Interpretation

The Mithril DNS failure is still the first visible failure. However, the logs suggest that selecting "Sync from genesis" may get past the Mithril path and then hit a separate cardano-node startup failure in Whonix:

cardano-node: setupURing: permission denied (Operation not permitted)

This may indicate that the packaged cardano-node is trying to use io_uring, but Whonix or its sandbox/kernel/security profile denies that operation. If so, Daedalus cannot recover because the node process exits repeatedly, causing cardano-wallet to lose its node socket connection and shut down.

Could the Daedalus/cardano-node team confirm whether the bundled node requires io_uring, and whether there is a supported way to disable it or fall back to a non-io_uring backend in restricted Linux environments such as Whonix?