Skip to content

fix: timelock policy create proposal using erc4337 with no-op calldata#36

Merged
leekt merged 46 commits intodev/0.2.0from
fix/tob-kernel-1
Apr 7, 2026
Merged

fix: timelock policy create proposal using erc4337 with no-op calldata#36
leekt merged 46 commits intodev/0.2.0from
fix/tob-kernel-1

Conversation

@leekt
Copy link
Copy Markdown
Contributor

@leekt leekt commented Feb 2, 2026

Also fixes tob-kernel-2 on #37 and tob-kernel-20 on #42

@leekt leekt changed the title fix: Create proposal with no-op fix: create proposal using erc4337 with no-op calldata Feb 2, 2026
@leekt leekt changed the title fix: create proposal using erc4337 with no-op calldata fix: timepolicy create proposal using erc4337 with no-op calldata Feb 2, 2026
@leekt leekt changed the title fix: timepolicy create proposal using erc4337 with no-op calldata fix: timelock policy create proposal using erc4337 with no-op calldata Feb 3, 2026
leekt added 17 commits February 6, 2026 14:21
fix: timelock policy to clear state when reinstalled
fix: TimelockPolicy to not accept erc1271
fix(TimelockPolicy): correct ERC-7579 no-op detection encoding
fix(TimelockPolicy): add upper bounds for delay and expirationPeriod
fix(TimelockPolicy): add grace period to prevent cancellation race condition
leekt added 21 commits February 11, 2026 14:48
fix(TimelockPolicy): use Guardian for cancellation, proper no-op decoding
fix: add install-time input validation (TOB-KERNEL-5)
fix: add zero-owner/signer guard in validation functions (TOB-KERNEL-13)
chore: replace string literal requires/reverts with custom errors
docs: add security assumption NatSpec comments
@leekt leekt merged commit 250cee4 into dev/0.2.0 Apr 7, 2026
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.

1 participant