Hadrien Croubois

this is still relevant

I've tried using the code in #152, and I couldn't make it work When calling a function that throws a custom error, I'm getting ``` Error: Unrecognized revert error string...

see https://github.com/OpenZeppelin/openzeppelin-contracts/issues/5002

For the time being I made a fork of some proxy with 0.6.0 in my solidity tooling repo: https://github.com/iExecBlockchainComputing/iexec-solidity/tree/master/contracts This is a repo I use in addition of openzeppelin contracts....

Hello @CypherBee The latest changes that you can see in the master branch were indeed not released yet. In the Changelog, these are marked as "Unreleased"

Hello @joe-p If you want to use a custom encoding, you should probably use the [`SimpleMerkleTree`](https://github.com/OpenZeppelin/merkle-tree?tab=readme-ov-file#simple-merkle-trees) that lets you pass already leaves that are already hashed. This is not realeased...

> There is the problem that information about the encoding is lost in `dump` Yes that is defintielly a downside

Currently, the StandardMerkleTree takes a "leafEncoding" that is a `string[]`, and assumes the leafs are built by doing ```solidity keccak256(bytes.concat(keccak256(abi.encode(...values)))) ``` or ```javascript keccak256(keccak256(defaultAbiCoder.encode(types, values))) ``` If we wanted to...

@habdelra, an EOA (wallet with a private key) cannot use `create2`. `create2` power can only be used by a smart contract. This is why you need a factory. You first...

Hello @pcpLiu I believe that, until the bug is resolved, you have limited options. Upgrading a proxy involves 3 steps: - checking the storage compatibility of the new implementation -...