midnight-compact-app-builder

Start by designing the Compact contract with separated public and private data, then generate the TypeScript bindings and integrate them via compact-runtime and midnight.js. Connect a wallet through the Wallet SDK or Wallet API, configure a proof server endpoint, and verify with contract and integration tests before deploying to testnet.

Use local for the fastest iteration on circuits and integration flows, testnet for team validation and demo preparation close to real conditions, and devnet when verifying experimental features. The choice depends on whether you prioritize development speed, shared testing, or specific feature verification.

Proof generation failures usually come from an incorrect proof server URL, a network ID mismatch, stale generated TypeScript after contract changes, or input values violating circuit constraints. Check these four causes in order before investigating deeper issues.

Use the Wallet API methods such as balanceAndProveTransaction, proveTransaction, and submitTransaction, separating prove and submit steps so failures can be isolated. Inject network ID and endpoint configuration through environment variables and record transaction IDs for traceability.

Write tests before implementation covering both accepted and rejected inputs, state transition consistency, repeated execution, and out-of-order calls. Stabilize one circuit at a time, treat type errors as design mismatch signals, and update related tests whenever the specification changes.