All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Bump
@metamask/delegation-corefrom^2.0.0to^2.2.1(#8823) - Bump
@metamask/delegation-deploymentsfrom^1.3.0to^1.4.0(#8823) - Bump
@metamask/keyring-controllerfrom^25.5.0to^26.0.0(#8912) - Bump
@metamask/delegation-controllerfrom^3.0.0to^3.0.1(#8912)
- Bump
@metamask/authenticated-user-storagefrom^1.0.1to^2.0.0(#8802)
- Bump
@metamask/network-controllerfrom^31.1.0to^32.0.0(#8774)
- Add remaining steps in money account upgrade process (#8621)
- BREAKING: The controller messenger now requires access to six additional allowed actions:
AuthenticatedUserStorageService:listDelegations,AuthenticatedUserStorageService:createDelegation,ChompApiService:verifyDelegation,ChompApiService:getIntentsByAddress,ChompApiService:createIntents, andDelegationController:signDelegation. Delegation signing is now delegated to@metamask/delegation-controllerrather than callingKeyringController:signTypedMessagedirectly; consumers must instantiateDelegationControllerand update their messenger configuration accordingly. (#8621) - BREAKING:
init()now takes a{ chainId, boringVaultAddress }object instead of anInitConfig. The EIP-7702 delegator implementation and caveat enforcer addresses are resolved from@metamask/delegation-deploymentsfor the target chain;init()throws if the chain is not supported by Delegation Framework 1.3.0. TheInitConfigtype is no longer exported. (#8621) - Add
@metamask/authenticated-user-storage,@metamask/delegation-controller,@metamask/delegation-core, and@metamask/delegation-deploymentsas dependencies. (#8621) - Bump
@metamask/network-controllerfrom^31.0.0to^31.1.0(#8765) - Bump
@metamask/chomp-api-servicefrom^3.0.1to^3.1.0(#8769)
- Build-delegation step no longer emits a redundant duplicate
ValueLteEnforcercaveat; the Delegation Framework treats both as equivalent, but the duplicate was inadvertently inherited from@metamask/smart-accounts-kit'serc20TransferAmountscope helper. (#8621) - EIP-7702 authorization step now treats a 409 response from
POST /v1/account-upgradeasalready-doneinstead of a fatal error, making the step retry-safe when a prior submission was accepted by CHOMP but has not yet been observed on-chain. (#8621)
- Bump
@metamask/keyring-controllerfrom^25.4.0to^25.5.0(#8722) - Bump
@metamask/chomp-api-servicefrom^3.0.0to^3.0.1(#8755) - Bump
@metamask/network-controllerfrom^30.1.0to^31.0.0(#8755)
- Bump
@metamask/keyring-controllerfrom^25.3.0to^25.4.0(#8665)
- Fix the ChompApiService:createUpgrade call in the EIP-7702 auth step, pasing correct arguments (#8657)
- Bump
@metamask/chomp-api-servicefrom^2.0.0to^3.0.0(#8651) - Bump
@metamask/messengerfrom^1.1.1to^1.2.0(#8632) - Bump
@metamask/keyring-controllerfrom^25.2.0to^25.3.0(#8634) - Bump
@metamask/network-controllerfrom^30.0.1to^30.1.0(#8636)
- Fix the associate-address step to detect the already-associated case via
status: 'active'. (#8635)
- Bump
@metamask/chomp-api-servicefrom^1.0.0to^2.0.0(#8618)
- Send the CHOMP authentication timestamp as a number instead of a string in the associate-address step. (#8610)
- Add EIP-7702 authorization step to the upgrade sequence. (#8565)
- Add
MoneyAccountUpgradeControllerwithupgradeAccountmethod (#8426)