You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Appendix A: Notable differences between FEVM and EVM for smart contract developers](#appendix-a-notable-differences-between-fevm-and-evm-for-smart-contract-developers)
71
66
-[Appendix B: Upgrades](#appendix-b-upgrades)
@@ -129,7 +124,7 @@ EVM storage (u256 => u256 map) is backed by a specialized data structure based o
129
124
130
125
Contrary to traditional EVM storage, the KAMT is an enumerable data structure. However, no operations are provided for smart contracts to enumerate keys, at least not at this stage. This property merely facilitates external observability and debuggability.
131
126
132
-
TODO: specify these optimizations, or the KAMT.
127
+
TODO: specify the KAMT.
133
128
134
129
### Actor interface (methods)
135
130
@@ -474,7 +469,7 @@ _Errors_
474
469
475
470
### Other considerations
476
471
477
-
####Historical support
472
+
####Historical support
478
473
479
474
EVM opcode and precompile support is restricted to the Ethereum Paris fork. Historical Ethereum behaviors are not supported.
0 commit comments