Release / v2.107.0 and v2.107.1 - #2600
Open
superKalo wants to merge 71 commits into
Open
Conversation
…med-payload Trending tokens/ remove duplicate properties
…lized and normalization tests
…excluding the Safe
…alization Refactor/ Domain names normalization
Feature / Trending tokens
…/import-safe-by-owner
Feature / NFC cards integration on mobile
Feature: import safes by owner
…nt-flow Refactoring / Create new account flow
…ction-trailing-dot
…-trailing-dot Fix / Dapp phishing protection - Trailing-dot hostnames bypassed the checks
…/paymaster-sponsorship-improvemens-allow-upgrade
…ing an userOp pass bug
…p-improvemens-allow-upgrade Allow ERC-7677 sponsorship retry after bundler estimation
The fee speed preference was a single value shared by every chain and was
written to storage the moment the user picked a speed, even if the
transaction was then rejected. The fee token preference already worked
per-network and was only committed on a successful broadcast, so the two
behaved in opposite ways.
- signAccountOpFeeSpeedPreference is now a { [chainId]: FeeSpeed } map
- values stored before this change were a bare FeeSpeed string and cannot
be mapped to a chain, so they are dropped on load and fall back to Fast
- update() takes pendingFeeSpeedPreference instead of shouldPersistSpeed;
the staged speed is discarded when a different speed is selected and is
written to storage next to the fee token one, on broadcast
- feeSpeedPreference and pendingFeeSpeedPreference are exposed to the UI
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Per-network default fee speed + NFC multi-tx signing (for v2.107)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See: