compact-core:compact-witness-ts

To implement Compact witnesses in TypeScript, you must enforce WitnessContext as the first parameter and return a [PrivateState, ReturnValue] tuple. This ensures your implementation type-checks against compiler-generated managed contract APIs.

Compact type mapping translates Compact primitives and ADTs into TypeScript equivalents while enforcing runtime bounds and length checks. This ensures your TypeScript witness functions remain compatible with generated ledger and contract type declarations.

The WitnessContext pattern for private state requires passing WitnessContext as the first parameter to your TypeScript witness function. It enables contract-address keyed state scoping and allows witnesses to read or mutate private state during DApp integration.

To verify TypeScript witness implementations against compiled Compact contracts, bind your witness functions to the generated Contract class and run mechanical verification. This validates compatibility with pureCircuits, impureCircuits, and ledger type declarations before deployment.

Writing a private state factory for a Compact witness involves returning a [PrivateState, ReturnValue] tuple from your TypeScript function. You can implement patterns like a local_secret_key witness that reads a 32-byte Uint8Array secret from private state.

Use pureCircuits versus impureCircuits in Compact testing based on side-effect requirements when invoking generated contract APIs. The Skill provides guidance on distinguishing these circuits to ensure proper ledger parsing and runtime verification during DApp integration.