Learn how Abstract differs from Ethereum’s EVM opcodes.
Aspect | Ethereum | Abstract |
---|---|---|
Fee Composition | Entirely onchain, consisting of base fee and priority fee. | Split between offchain (fixed) and onchain (variable) components. |
Pricing Model | Dynamic, congestion-based model for base fee. | Fixed offchain component with a variable onchain part influenced by Ethereum gas prices. |
Data Efficiency | Publishes full transaction data. | Publishes only state deltas, significantly reducing onchain data and costs. |
Resource Allocation | Each transaction independently consumes gas. | Transactions share batch overhead, potentially leading to cost optimizations. |
Opcode Pricing | Each opcode has a specific gas cost. | Most opcodes have similar gas costs, simplifying estimation. |
Refund Handling | Limited refund capabilities. | Smarter refund system for unused resources and overpayments. |
block.baseFee
context variable;
and have no way to know the exact fee to pay for a transaction.
Instead, the following steps occur to refund accounts for any excess funds spent on a transaction:
Block overhead fee deduction
Gas price calculation
Gas price calculation
tx.maxFeePerGas * tx.gasLimit
. The transaction is then executed (see transaction
flow).Gas refund
gas_per_pubdata_limit
value
to configure the maximum gas price that can be charged per byte of pubdata (data posted to Ethereum in the form of blobs).
The default value for this parameter is 50000
.
O(tx) = max(SO, MO(tx), EAO(tx))