Releases: trailofbits/maat
Releases · trailofbits/maat
Version 0.6.9
What's Changed
- Various EVM fixes by @Boyan-MILANOV in #148
- Use
MemMapManager
to detect free space in memory instead of page permissions by @Boyan-MILANOV in #149
Version 0.6.8
What's Changed
- Expose more functionalities in python bindings by @Boyan-MILANOV in #146
Version 0.6.7
What's Changed
- Support KECCAK hash of empty string (0-length data) by @Boyan-MILANOV in #139
- Expose
ULE
andULT
to bindings by @Boyan-MILANOV in #140
Version 0.6.6
What's Changed
- Add support for EVM LOG* instructions by @Boyan-MILANOV in #138
Version 0.6.5
What's Changed
- Various improvements to
EVM
support by @Boyan-MILANOV in #137 - Various fixes for running a Smart Contract by @Boyan-MILANOV in #135
Version 0.6.4
What's Changed
- Allow to deep copy transaction objects in bindings by @Boyan-MILANOV in #133
Version 0.6.3
What's Changed
- Allow to skip the data parameter in python event callbacks by @Boyan-MILANOV in #132
Version 0.6.2
Patch
- Update lief to 0.12.1 by @ekilmer in #110
- Fix processing IR stores with big addresses by @Boyan-MILANOV in #131
Full Changelog: v0.6.1...v0.6.2
Version 0.6.1
This release is basically identical to 0.6.0
but is necessary for cibuildwheel
to generate proper release python packages to PyPI.
Version 0.6
Version 0.6 release with basic support for symbolically execute EVM bytecode:
- ghidra/sleigh specification for EVM bytecode as described by the 2022 ethereum yellow paper
- callother implementation for all exotic EVM operations
- simulation of a deployed smart-contract frame, with its own memory and stack. Sharing code and storage between contracts is supported
- special simplifications for EVM AST patterns
- basic support for modelling symbolic transaction data that has a fixed length
- engine "duplication" capabilities
Current limitations include:
- solving symbolic KECCAK hashes