Midnight sprint: debugging error 170 and deploying a sealed-bid auction smart contract

Short summary

A self-taught builder recounts deploying a sealed-bid auction smart contract to Midnight Preprod, battling a persistent error 170 (InvalidDustSpendProof). The root cause was resubmitting the same proven transaction on retry instead of rebuilding it fresh. The author also contributed a PR improving the error-code documentation in the Midnight Expert repo, turning a painful debugging session into a genuine community contribution.

• •Error 170 (InvalidDustSpendProof) fixed by rebuilding transactions fresh on each retry rather than resubmitting
• •Sealed-bid auction with domain-separated nullifier deployed to Midnight Preprod with live on-chain interaction
• •PR submitted to midnight-expert repo improving error 170 documentation based on lived experience

Generated with AI, which can make mistakes.