compact-core:compact-ledger

Design on-chain ledger state in Compact by selecting appropriate ledger types like Counter, Map, Set, List, MerkleTree, or HistoricMerkleTree based on your contract's data requirements, then initializing them in the constructor with disclosed values and default() patterns.

Compact ledger state privacy rules govern on-chain visibility, allowing non-sensitive data to remain transparent while enforcing private state handling through disclosure rules, MerkleTree patterns, and zswap private membership proofs for sensitive information.

Initialize Compact constructors with sealed fields by applying constructor initialization patterns, leveraging helper circuits, and structuring nested ADTs to ensure correct visibility rules and safe defaults for on-chain state.

Use a MerkleTree for standard private membership proofs in on-chain state, whereas a HistoricMerkleTree is suited for scenarios requiring historical state tracking alongside privacy and disclosure patterns in Compact contracts.

Yes, Compact supports managing private state with transparent on-chain behavior by applying design patterns that separate sensitive data using privacy rules and zswap patterns while maintaining disclosure for non-sensitive ledger data.