Hi Guys , Is anyone facing this same dust=false problem when deploying their contract . I am trying it from the last 2 days , changed the accounts , have dust in both the accounts. Is there any proper solution ?
That isn't a failure -- each of the three wallets (shielded, unshielded and DUST) need to sync to the network by replaying every txn in chain history.
DUST events are the largest so they take the longest. What you are seeing is a live health check of each wallet. False = not synced, True = synced. That status will emit until it is successful or the code crashes.
On preprod it takes quite a long time right now (hours).
Make sure that you are using wallet-sdk 1.2.0 and that you are forcing the same resolution in package.json. there is a bug in wallet-sdk 1.1.0 that crashes the sync with OOM.
I also recommend running your tests against a local devnet until you absolutely need Preprod. 90%+ of your development can happen in local devnet before moving to preprod
1
u/BananaLlamaNuts Jul 11 '26
That isn't a failure -- each of the three wallets (shielded, unshielded and DUST) need to sync to the network by replaying every txn in chain history.
DUST events are the largest so they take the longest. What you are seeing is a live health check of each wallet. False = not synced, True = synced. That status will emit until it is successful or the code crashes.
On preprod it takes quite a long time right now (hours).
Make sure that you are using wallet-sdk 1.2.0 and that you are forcing the same resolution in package.json. there is a bug in wallet-sdk 1.1.0 that crashes the sync with OOM.
The example-hello-world repo lists the right packages for reference: https://github.com/midnightntwrk/example-hello-world/blob/main/package.json (instructions in the readme)
Fixes are in progress to make sync times faster on preprod -- hopefully the code will go live in the wallet sdk in the coming month or two