update EIPs

Author: isabellewei

src/content/docs/en/technology/chain/differences.mdx

@@ -32,19 +32,9 @@ The remaining precompiled contracts have the same behavior as Ethereum. However,
 
 ## EIPs
 
-Our sequencer was developed based on the London fork initially. We disabled some EIPs in the London fork and introduced a few EIPs from the Shanghai fork to improve the compatibility.
-
-Disabled EIPs until the London fork:
-
-- [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559): Fee market change and EIP-1559 transaction type
-- [EIP-2930](https://eips.ethereum.org/EIPS/eip-2930): Optional access lists
-
-EIPs imported from the Shanghai fork:
-
-- [EIP-3651](https://eips.ethereum.org/EIPS/eip-3651): Warm `COINBASE`
-- [EIP-3855](https://eips.ethereum.org/EIPS/eip-3855): `PUSH0` instruction
-- [EIP-3860](https://eips.ethereum.org/EIPS/eip-3860): Limit and meter initcode
+Our sequencer was developed based on the London fork initially. Since then we have adopted most features from London, Shanghai, and Cancun.
 
+Our EIP-1559 fee market behaves differently: the sequencer sets the L2 base fee (based on the L1 base fee), and we don't burn ETH.
 
 <Aside type="caution" title="">
 Opcodes related to EIP-4844, like `BLOBHASH` and `BLOBBASEFEE`, are not yet available on Scroll. Additionally, [EIP-4788](https://eips.ethereum.org/EIPS/eip-4788) for accessing the Beacon Chain block root is not supported.