You call balanceUnboundTransaction . It throws — or worse, it succeeds silently with wrong token balances, and the transaction fails somewhere downstream with a message that has nothing to do with sync. You check the obvious things. Funds are in the wallet. The contract compiled. The proof server is running. Nothing looks wrong. The problem is that your wallet hasn't finished scanning the chain, and balanceUnboundTransaction built a transaction from an incomplete local database. This is probably the most common early failure in Midnight development. It's almost always invisible until you've seen it once. The mental model shift Most developers approach a crypto wallet like a stateless lookup tool — you call it, it queries the network, you get a live answer. Midnight's wallet doesn't work that way. The Midnight wallet is a local database.…