Compact Smart Contract Testing & Debugging FAQs

Question 1

How do I test Compact contracts using TypeScript?

Accepted Answer

The skill provides templates for using @midnight-ntwrk/compact-testing to create a TestContext, allowing you to call contract functions and verify results within a standard Mocha or Jest environment.

Question 2

What causes a 'circuit constraint failed' error?

Accepted Answer

This is a runtime assertion failure within the circuit. It typically means an 'assert' condition was not met or the provided inputs violate the contract's logic. This skill provides a decision tree to isolate the specific failure point.

Question 3

Can I mock witness functions for unit tests?

Accepted Answer

Yes, the skill includes patterns for defining mock witness objects to simulate private user data or external inputs, enabling you to test contract logic without a full network deployment.

Question 4

Why does my proof generation fail even if the contract compiles?

Accepted Answer

Proof generation failures are often caused by invalid witness values, arithmetic overflows, or division by zero. The skill helps you audit your code for these edge cases and implement proper bounds checking.

Question 5

What is a 'potential witness-value disclosure' error?

Accepted Answer

This error occurs when a private value (witness) flows into a public output without explicit authorization. The skill helps you resolve this by correctly applying the disclose() function or using commitments.

Compact Smart Contract Testing & Debugging

Compact Smart Contract Testing & Debugging

Key Features

Use Cases

Key Features

Use Cases