I am using Lace Testnet wallet and the faucet doesn’t send tDUST to it. The transaction ID of the “successful” faucet withdrawal isn’t even found on the midnight testnet explorer when searched. I am now figuring out the CLI method but can’t seem to get it either.
3 Likes
Lace testnet wallet didn’t receive tDUST.
CLI wallet address also not receiving tDUST from faucet. Address: mn_shield-addr_test1drt53prvnfr5vn77swvpgwvuyxtx254qz3mxzexzzjvkvkwqqvgqxqzpzpnlu3rc7twxgvtr7ddnvp8sm57rmxs6w5d533fy7qnw9p6qzsv6sv5x - can someone manually send or check faucet status?
2 Likes
that is the situation most of us are in.
2 Likes
man.. isn’t midnight going live very soon? 
2 Likes
me too for week or so,
3 Likes
@Spy The issue likely stems from a synchronization delay between the faucet, the network mempool, and the Midnight Testnet Explorer indexer, which can cause “successful” transactions to temporarily appear as non-existent. To resolve this, first verify your Lace Wallet address directly on the explorer rather than searching by Transaction ID, and ensure your wallet is correctly pointed to the Midnight Testnet in the settings. If transitioning to the CLI method, double-check your environment variables and public key exports, as tDUST (the unshielded gas token) requires precise pathing to settle correctly in your balance compared to the governance-focused tNIGHT.
1 Like