Clément Renaud comments

Results 229 comments of


                                            Clément Renaud

Using https://gnosisscan.io/

remains - [ ] previous versions of public lock and unlock - [ ] hooks

ok, verified these hooks - https://gnosisscan.io/address/0xd10DF26AEaE179521D6195Cf6f3b2701B5089Fb6 - https://gnosisscan.io/address/0x4F44e968961f5ff818b788E626564BBAF2c96bAC except the erc721 one [0xE4c2f9281ec03a1956c3756C66E73f22233323D3](https://blockscout.com/xdai/mainnet/address/0xE4c2f9281ec03a1956c3756C66E73f22233323D3/contracts#address-tabs) - didnt work so far BUT not much nft on gnosis anyway

The next versions (0.2.33 and 0.2.34) are not available on npm registry

same here, just made a `npm update` and get the same message

Renew keys shortly before expiry

Hello @haseebrabbani , thanks for the feedback ! Currently our contract will flag a key as "renewable" if it has reached 90% of its total expiration time (see the lines...

Do not publish `localhost` network in npm package

Yes that's legacy before we had a dedicated parser for networks. I'll remove it

Protocol governance monitoring

Maybe better to start with that once we have a clean `governance` folder with the relevant scripts in the monorepo (see #12707)

Protocol governance monitoring

also need to make sure that `swapPurchaser` is deployed #12806 - as well as `SwapBurner`

Protocol governance monitoring

one easy way to create reporting will be to send a post on Discord https://github.com/marketplace/actions/actions-for-discord

fix(deps): update dependency ethers to v6.13.1

After merging https://github.com/unlock-protocol/unlock/commit/4cd5a233263e66834554a3518eb86e170bbdff7d only v5 > v6 is left here

fix(deps): update dependency ethers to v6.13.1

> Unfortunately removing the peerDependency breaks things when building `unlock-app`: > > ``` > ../packages/unlock-js/dist/index.mjs:24439:1 > Module not found: Can't resolve 'net' > 24437 | > 24438 | // node_modules/ethers/lib.esm/providers/provider-ipcsocket.js...