Skip to content

Abstractionkit v0.3.7

Choose a tag to compare

View all tags
@Sednaoui Sednaoui released this 06 May 07:54
· 101 commits to dev since this release
v0.3.7
9b3337f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fixes

  • Safe multi-chain single-operation signing now hashes the correct payload. Single-op SafeMultiChainSigAccountV1 flows previously hashed through the Merkle wrapper and were rejected on-chain with AA24, since Safe4337MultiChainSignatureModule verifies against keccak256(SafeOp) directly when merkleTreeDepth == 0. The per-op SafeOp digest is now reachable via SafeMultiChainSigAccountV1.getUserOperationEip712Hash / getUserOperationEip712Data, which default safe4337ModuleAddress to the multi-chain module so the digest matches the on-chain verifier without manual override.
  • Safe multi-chain WebAuthn / EIP-1271 signatures keep contract-signer formatting. signUserOperationsWithSigners now preserves the "contract" signer type when formatting multi-operation signatures, so dynamic Safe contract-signature segments are emitted correctly.

API changes

  • getMultiChainSingleSignatureUserOperationsEip712Hash / ...Eip712Data are wrapper-only and throw for length < 2. They now do one thing: hash the Merkle-wrapped multi-op payload. Single-op callers must use SafeMultiChainSigAccountV1.getUserOperationEip712Hash / getUserOperationEip712Data (which default safe4337ModuleAddress to the multi-chain module). If you call the parent SafeAccount helpers directly, pass safe4337ModuleAddress explicitly. Their default points at the standard 4337 module, not the multi-chain one.

Maintenance

  • Added signer API documentation, type-level signer tests, signer unit-test coverage, and CI checks for linting, type tests, build, and signer tests.

Full Changelog: v0.3.5...v0.3.7

Assets 2
Loading