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
Since starting this build, SE-2 has released a major upgrade migrating from using the v1 versions of viem and wagmi to using the v2 versions instead.
Upgrading versions would allow for parsing of the event logs of the transaction receipts for swaps, joins, and exits. Viem v1 lacked support for this so I ended up setting up an event listener that points at the deployed contract which causes a lag between when the tx executes and when the frontend updates.
Since the migration from v1 to v2 versions is fairly intensive and involves many changes to a lot of the custom hooks and components, the best strategy may be to transplant the content of the current scaff bal frontend into the latest version of a fresh SE-2 frontend.
The backend packages/foundry folder will remain unchanged
The text was updated successfully, but these errors were encountered:
Looks like this upgrade will be needed in order to take advantage of the SDK's buildCallWithPermit2 because it relies on viem v2 Client which is different from viem v1 Client
EDIT: I misunderstood the SDK. Permit2Helper is only for internal testing. buildCallWithPermit2 is now being used for this project
Overview
Since starting this build, SE-2 has released a major upgrade migrating from using the v1 versions of viem and wagmi to using the v2 versions instead.
Upgrading versions would allow for parsing of the event logs of the transaction receipts for swaps, joins, and exits. Viem v1 lacked support for this so I ended up setting up an event listener that points at the deployed contract which causes a lag between when the tx executes and when the frontend updates.
Since the migration from v1 to v2 versions is fairly intensive and involves many changes to a lot of the custom hooks and components, the best strategy may be to transplant the content of the current scaff bal frontend into the latest version of a fresh SE-2 frontend.
The backend
packages/foundry
folder will remain unchangedThe text was updated successfully, but these errors were encountered: