Record reference

Records are encrypted state objects. Their ciphertexts and commitments appear on chain. An authorized holder uses view material to decrypt their contents.

​

PositionNFT

Mint creates the record. Increase, decrease, and collect return a replacement for the same token ID. Rebalance consumes the old record and returns a new record with a new token ID and range. Burn consumes a record without replacement. PositionNFT is a Leo record, not an ARC-721 token.

​

SwapComplianceRecord

Single-hop swap creates this investigator-owned record. It contains owner, swap_id, token_in, token_out, the full SwapRequest, caller, signer, and blinded_address.

​

MultiHopSwapComplianceRecord

Multi-hop swap creates this investigator-owned record. It contains owner, swap_id, the full SwapMultiHopRequest, caller, signer, and blinded_address.

​

MintComplianceRecord

Mint and rebalance create this investigator-owned record. A rebalance record describes the replacement position.

​

Dynamic token records

The AMM accepts and returns dyn record values. The selected token program defines the concrete record schema. Plain ARC-20, wrapped credits, and wrapped ARC-22 assets can therefore use different source programs and amount types at the router boundary. Use the deployment contract registry to resolve the AMM token program, underlying record program, token field ID, decimals, and record amount type for each asset.