Summary
custom_fee_limits set on the transaction are not propagated to max_custom_fees in the transaction body.
Expected Behavior
When custom_fee_limits are provided, they should be correctly mapped to max_custom_fees in the transaction body so fee limits are enforced as intended.
Actual Behavior
custom_fee_limits are ignored and not used to populate max_custom_fees, resulting in missing fee limit enforcement.
Impact
- Breaks permissionless revenue-generating topic behavior introduced by the relevant HIP-991
- Prevents correct fee limiting for custom fees
- Leads to unexpected or incorrect transaction fee handling