Transaction Builder derives wrong multisig address and cannot see confirmed UTxO

[nicholestan1984]

Hi Mesh team, I'm evaluating Mesh Multisig for a community treasury and found what appears to be an address derivation mismatch in the Transaction Builder.

The 2-of-3 wallet created by Mesh has this address:

addr1wx8m0ykl983j099ulp93z6q2tm5v4uwu63h209vfujjr4mc4cu408

I funded it with 5 ADA. Cardanoscan and Koios both confirm the funds, and Koios reports the current UTxO:

90b9b8e7871dfe28353a91a37e31a1859ee2320c08c9b641d138ebee7fe4c909#0

Value: 5,000,000 lovelace

However, Mesh Overview shows 0 ADA and Transaction Builder reports No UTxOs available.

Using Chrome DevTools, I found that Transaction Builder is querying Blockfrost for a different address:

addr1wx52d4la4rxwy9wttklaksnlu65uea55yjhwt527knsk9qc7vukx3

Request:

GET https://cardano-mainnet.blockfrost.io/api/v0/addresses/addr1wx52d4la4rxwy9wttklaksnlu65uea55yjhwt527knsk9qc7vukx3/utxos?page=1

Response: 404 Not Found

The Build UI also displays addr1wx52d...7vukx3 as Self (Multisig), while the actual created wallet is addr1wx8m0...4cu408.

I initially had two local Mesh records for the same wallet, possibly because I clicked Create twice while the first request appeared unresponsive. I archived the duplicate, but the address mismatch remains.

I also tried the built-in bug reporter, but POST /api/github/create-issue returns 500 Internal Server Error.

Could you advise why Transaction Builder is deriving addr1wx52d... rather than the actual wallet address, and whether there is a safe way to repair/rebuild this wallet record?

No production assets have been moved. This was discovered during a 5 ADA test before using the wallet for production.