Bundle Requirements
Transaction Requirements for Solver Operations
Gas Parameters for
userOpHash
GenerationLegacy Transactions:
gasPrice
: Must match the opportunity-creating transaction.
Type 2 (EIP-1559) Transactions:
maxFeePerGas
andmaxPriorityFeePerGas
: Must match the opportunity-creating transaction.
Implementation:
Ensure meta transactions (EIP-712) use gas parameters identical to the opportunity-creating transaction to accurately generate
userOpHash
.
userOpHash
GenerationPurpose: Identifies the opportunity transaction in the PFL-Auction context
Procedure:
Call the
PFL-Auction
dAppControl
contract with the matched gas parameters.The transaction type influences the gas parameters used but does not need separate handling.
Solver Operation Handling
Behavior:
Does not differentiate between legacy and Type 2 transactions.
Relies solely on the correctly generated
userOpHash
for processing.
Implications:
No adjustments needed within the solver for different transaction types.
Please follow Bundle Format guide for more detailed guide for Solver Operation
Note: In Atlas, the transaction hash alone is not sufficient. Instead, we incorporate additional Atlas-specific parameters and configuration details, combining them with the original transaction hash to create a new, unique identifier. This rehashing process ensures that each transaction reflects Atlas-specific context and configurations accurately.
The Example below show how to obtain the correct userOpHash
to be passed as reference ot the targeted opportunity transaction.
Last updated