Transaction building

The frontend uses Lucid Evolution and the generated contracts blueprint.

Rules

• Use the current contract version for new listings.
• Validate every datum field, redeemer and address.
• Preserve output order where validators use offsets.
• Pay listing/delist fees through the tagged fee path.
• Keep one unique payment tag per escrow input.
• Reject unexpected assets and duplicate inputs.
• Use only pure ADA UTxOs for automatic wallet fees and collateral.

Batch limits

Batch size must be measured with complete() or a dry-run. Never assume a fixed limit without measuring the current transaction.