RitzyDevBox

You need to have a USD/WETH pool in order to get pricing information. If you added a new chain make sure to add a value to the USDC Map in...

Yeah I have Node LTS installed 18. The project works fine when using a linux distro, but from windows it gets Polyfill errors

I don't use that version, but you should add a key for that in the .env On Mon, Mar 11, 2024, 4:17 AM fcor111 ***@***.***> wrote: > following your answer,...

The issue is that the optional chains runs the default validations, to fix this for now just modify the code to include the regular chains with the defaults, IMO this...

You can update the walletconnectv2 connector to include all chains const [mainnet] = Object.keys(MAINNET_CHAINS).map(Number) const [...optionalChains] = Object.keys(MAINNET_CHAINS).map(Number) const projectId = process.env.walletConnectProjectId; export const [walletConnectV2, hooks] = initializeConnector( (actions) =>...

Yeah the UI will break, because they use the proposalCount, to enumerate the previous proposals. In all fairness, the uniswap code there is kinda hacky, but I didn't feel like...

I ignored proposals coming through the 4 parameter, which may be a bug. I was debating on just using a closure around the propose function to store the original count...

> That would not be compatible though, because the `proposalId` given by the events is the hash one. > > So when you have a proposalId, depending on if it...

I see your point, To be honest a separate base altogether may make sense. The only downfalls there would be. 1. More maintenance managing multiple contracts 2. Updating the wizard...

I can fix this bug for you guys. https://github.com/OpenZeppelin/openzeppelin-contracts/issues/3997 I've already put most of the code there On Wed, Jan 25, 2023, 8:47 AM Hadrien Croubois ***@***.***> wrote: > Also...