note deploy fails with "timed out waiting for VoucherGenerated event" on brand-new wallet after shellnet reset (v0.0.12)

[sgktas]

Running dexdo note deploy (v0.0.12) with a brand-new multisig wallet (freshly created via the dex.do site, funded with 1,000,000 SHELL/NACKL/USDC, confirmed "Active" on-chain via dexdo note balance) consistently fails with:

Error: deploy PrivateNote from wallet

: halo2 deposit voucher: wait for deposit VoucherGenerated from persisted wallet submit: timed out waiting for VoucherGenerated event with skUCommit= within 480s (N ext-out events scanned); refusing to submit a second wallet spend for recovery

Reproduced 3 times in a row (different skUCommit hashes each time, ~113-122 ext-out events scanned each time), always timing out at the same 480s window.

The wallet itself checks out fine via dexdo note balance (status: Active, correct SHELL balance). dexdo doctor reports PASS for general network health.

This looks specific to this particular wallet's deposit voucher flow post-reset — possibly the wallet is missing some post-reset initialization step, or there's an indexing lag specific to brand-new wallets created after the shellnet reset.

[sgktas]

Still failing after upgrading to v0.0.13 (confirmed via binary change — note deploy now shows the "fetching Hermez KZG SRS once" line that wasn't present in v0.0.12). Same wallet, same symptoms, but the recovery JSON now shows "event": null — the VoucherGenerated event is never captured at all, suggesting the wallet spend itself may not be landing on-chain.
Sanitized recovery JSON:
json{
"version": 1,
"endpoint": "https://shellnet.ackinacki.org",
"nominal": "N10000",
"token_type": 1,
"raw_value": 10000000000000,
"ecc_shell_deposit": 100000000000,
"funding_multisig_address": "0:7d7aeea78870f52c0a985751e9f1965fa565be41f4eed072aead45151cac58d1",
"owner_public_key_hex": "fce33cfb2344f08eb2514d7b2495ec415a39198dcaa7620d9da415dc0c67f413",
"pn_address": null,
"deposit_identifier_hash": null,
"deployed_at_unix": null,
"deposit_voucher": {
"sk_u_commit_hex": "cf57ced50d500e78b41f1411679af3797ab5b2cfde9318153a0051e808369623",
"recipient_ephemeral_pubkey_hex": "fce33cfb2344f08eb2514d7b2495ec415a39198dcaa7620d9da415dc0c67f413",
"token_type": 1,
"raw_value": 10000000000000,
"is_fee": false,
"submit_maybe_sent": true,
"event": null
},
"shell_voucher": null,
"shell_funded": false,
"sanity_checked": false
}

[sgktas]

Wallet code_hash: 3a7a53248ff39fde936a4274eab143b5fac94feac0d8e2e2748aac5e74538d5f
dexdo note balance returns status: Active and correct balances, but getDetails fails with "returned no output message" — suggesting this address is the multisig wallet contract itself, not a PrivateNote. This wallet was created via the dex.do site as a single-owner wallet (no multi-signer setup was done). Custodian count and reqConfirms are whatever the dex.do site sets by default for a new wallet.

[sgktas]

Full stderr from one failing run (v0.0.13, same wallet):
note deploy: in-process gosh.ackinacki -- wallet 0:7d7aeea78870f52c0a985751e9f1965fa565be41f4eed072aead45151cac58d1 funds a N10000 NACKL PrivateNote on https://shellnet.ackinacki.org ...
note deploy recovery: owner key persisted to /root/dexdo-cli/notes_n10000_newmultisig_1.json.recovery.json (0600) before wallet spend.
note deploy recovery: no on-chain PrivateNote recorded yet; continuing deploy with the persisted owner key.
note deploy recovery: recorded deposit voucher checkpoint before wallet spend.
note deploy recovery: marked deposit voucher wallet submit as uncertain; reruns will not submit a second wallet spend.
note deploy: funding wallet looks busy/out-of-sync; retrying attempt 2 after 10s
note deploy recovery: no on-chain PrivateNote recorded yet; continuing deploy with the persisted owner key.
note deploy recovery: resuming deposit voucher; waiting/proving the existing skUCommit without submitting another wallet spend.
Error: deploy PrivateNote from wallet 0:7d7aeea78870f52c0a985751e9f1965fa565be41f4eed072aead45151cac58d1: halo2 deposit voucher: wait for deposit VoucherGenerated from persisted wallet submit: timed out waiting for VoucherGenerated event with skUCommit=0x887b3078acd29d2f88bc49413e8a407483065fa6ab88f176f957b759a8eb4d1d within 480s (102 ext-out events scanned); refusing to submit a second wallet spend for recovery
No sendTransaction, generateVoucher, COMPUTE_*, or exit-code lines appear — the log goes directly from "retrying attempt 2" to "resuming deposit voucher" to the final timeout. 102 ext-out events scanned, none matching the skUCommit.

[sgktas]

Thanks for the thorough investigation and for catching your own errors so quickly — really appreciate the transparency. One question while you're looking into it: is this specific to my wallet/setup, or are other dex.do-site wallet users hitting the same submit_maybe_sent=true / event=null timeout? Wondering if it's widespread or isolated to something particular about my configuration.

[sgktas]

This problem seems to be unique to me, unfortunately, because everyone except me is currently accumulating points since I'm ranked first. It's quite a coincidence that my wallet is broken while the 2nd and 3rd place winners aren't. It's also strange that the problem hasn't been solved yet. The real question is, how will my loss be compensated? Regards.