fix(evm): validate jump destination high bits

[ZR74]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains CI/CD configuration changes
• Contains documentation changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

6. Release note

None

[Copilot]

Pull request overview

This PR adds validation to ensure that EVM jump destinations do not have any high bits (bits 64-255) set in their uint256 values. This is a security fix that prevents jumps to addresses outside the valid 64-bit address space.

Changes:

• Modified the interpreter to return max uint64_t when high bits are set, triggering existing validation
• Added compile-time checks in the MIR compiler to validate jump destinations at both constant and runtime
• Ensured consistent validation across both JUMP and JUMPI opcodes

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/evm/interpreter.cpp	Modified Uint256ToUint64 lambda to check high bits and return max uint64_t if set, added <limits> include
src/compiler/evm_frontend/evm_mir_compiler.cpp	Added high-bit validation for constant and non-constant jump destinations in both handleJump and handleJumpI functions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.