Skip to content

Conversation

@klkvr
Copy link
Collaborator

@klkvr klkvr commented Jul 21, 2025

Blocked on revm release with bluealloy/revm#2711

@MatusKysel
Copy link
Collaborator

@klkvr revm has new release are you planing to finish this PR ?

@mattsse
Copy link
Collaborator

mattsse commented Jul 29, 2025

yep should require using reth main and latest alloy-evm release

@klkvr klkvr merged commit f93f2e9 into main Jul 29, 2025
8 checks passed
// basic check
if header1.number.to_be_bytes().len() > 32 || header2.number.to_be_bytes().len() > 32 {
return Err(BscPrecompileError::DoubleSignInvalidEvidence.into());
return revert()
Copy link
Contributor

@will-2012 will-2012 Jul 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hello @klkvr , does this fix break #44 ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what did the #44 change exactly? before this PR Reverted variant had same effect as DoubleSignInvalidEvidence

Copy link
Contributor

@will-2012 will-2012 Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

https://testnet.bscscan.com/tx/0x899592476081d65840828cc65b283c2835c15c6d9101c865dd5db07824bcd9bf#internal

staticcall_0_1 returns the InvalidEvidence.

I will check the specific impact of this during the next round of testnet resync.

@will-2012
Copy link
Contributor

Fixed #30.

will-2012 referenced this pull request in will-2012/reth-bsc Sep 3, 2025
chore: resolve conflicts with develop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants