You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the problem is the following, the PermissiveAccount uses libraries with the use A for B notation. So the libraries need to be deployed and linked to the contract.
using ECDSA for bytes32;
using BytesLib for bytes;
The problem is that forge deploys the libraries without create2 opcode so they are not deterministic and impact the address of the account so the factory.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (c49e5e1 2023-04-09T00:16:17.106319000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
I have the following deployment script
And the PermissiveFactory deploys the PermissiveAccount with the following
constructor(IEntryPoint _entryPoint, FeeManager feeManager, bytes32 salt) { accountImplementation = new PermissiveAccount{salt: salt}( address(_entryPoint), payable(address(feeManager)) ); }
But the problem is the following, the PermissiveAccount uses libraries with the
use A for B
notation. So the libraries need to be deployed and linked to the contract.using ECDSA for bytes32; using BytesLib for bytes;
The problem is that forge deploys the libraries without create2 opcode so they are not deterministic and impact the address of the account so the factory.
Example of what it looks like in the explorer
The text was updated successfully, but these errors were encountered: