Troubleshooting

No wallet appears, or connection fails

Check that your Midnight wallet is installed, unlocked, and enabled for this browser and site. Use the wallet picker’s rescan option after it loads. The app only discovers connector 4.x wallets. Discovery does not confirm transaction compatibility. See wallet testing and compatibility; do not use real funds to test it.

If you declined the connection, reconnect only when ready. If the wallet does not respond, check its pending requests before trying again.

Wrong network

The app verifies the wallet’s network after connection. Switch the wallet to the network shown in the app and reconnect. Tokens and addresses from another network cannot be substituted. A Cardano wallet connection does not supply Midnight NIGHT.

Balance is unavailable

An unavailable balance is not a zero balance. Let the wallet synchronize and check its connection and indexer status. The form blocks sending when the relevant balance cannot be read. Do not assume that a delayed update means a transaction failed.

Invalid amount or recipient

Enter a positive decimal amount using plain digits and a decimal point, with at most six decimal places, within your available balance. Do not use commas or scientific notation. The SDK limits amounts to 1 through 2⁶⁴ − 1 smallest units.

For wrapping to another address, use a complete shielded Midnight address on the selected network. For unwrapping, use an unshielded Midnight address on that network. The zero address is rejected. If My wallet cannot supply an unwrap address, choose Another address and verify a valid destination.

Wrapping is disabled

Read the app’s reason. It may have no configured pool, an unsupported indexer, an unreadable maintenance authority, or a changeable contract. Restore working services or wait for a supported deployment; do not bypass the immutability protection. The SDK allows an unwrap attempt without this wrapping guard, subject to the other requirements.

Proving or wallet approval fails

Check the wallet’s pending requests, ledger support, DUST, and proving configuration. An error before submission can have a different meaning from a lost response after submission. Check the displayed outcome rather than assuming all errors are safe to retry.

Submitted, timed out, or unknown outcome

Do not send again until you have checked balances and transaction history. The transaction may still confirm. If a transaction identifier is available, inspect it on the correct network’s explorer, alongside your wallet’s history and balances.

The SDK distinguishes a known failure from an unknown outcome. It treats partial network application as unknown because some effects occurred. The app remembers unresolved requests across reloads; closing or refreshing the tab does not recall a transaction already handed to the wallet. Follow the app’s balance-review prompts before retrying.

Reporting an issue

For SDK problems, review existing SDK issues. The app repository is not publicly accessible at the latest source-access check; do not assume its issue tracker is available. Include the network, action, error text, and wallet/software version. Never share a seed phrase, private key, or coin secret key. Public issue reports can expose any addresses, amounts, or transaction identifiers you include.

Implementation references are listed in Sources and verification.