Kaan Uzdoğan

Was there a particular reason we were replacing '@openzeppelin' with '_openzeppelin' when saving in our repo, like the fs does not allow names with '@'? @ligi @chriseth Also discussed in...

Thanks for the suggestion. We can maybe have a `chainId` of `0` to indicate the `CREATE2` addresses. As far as I understood from the EIP, the `init_code` is the contract...

Thanks for the detailed description and the contract example! It is much clearer One thing we need to make sure is to ensure we have the correct contract creation code...

Also fails for the Celo Mainnet contract 0xFCC5A03BF803213E478ccbE6517857faa3136978 https://gist.github.com/lastperson/4ffc43310d5aa8f35b35b3cc5c22c7a4

Yes if the explorer is not server-side rendered then we can't immediately scrape if as the scraper directly fetches the HTML and does not spin up a browser. For the...

Good point @wmitsuda But given any change to the IPFS repo will change the root hash, I can't immediately see how this could be worked around. It is not an...

I looked into this a bit and there's actually a service for these purposes [ipfs cluster](https://cluster.ipfs.io/). I am just trying to better understand the permissions of clusters. [CRDT](https://cluster.ipfs.io/documentation/guides/consensus/) consensus seems...

I see in the test-new-chain CI job the normal verification fail but immutables pass. Could you check if the provided contract is the correct one or maybe deploy a new...

Failing again and indeed I see the creation bytecodes are different: Expected (`./sources/shared/1_Storage.json`): ``` 0x608060405234801561001057600080fd5b50610150806100206000396000f3fe608060405234801561001057600080fd5b50600436106100365760003560e01c80632e64cec11461003b5780636057361d14610059575b600080fd5b610043610075565b60405161005091906100d9565b60405180910390f35b610073600480360381019061006e919061009d565b61007e565b005b60008054905090565b8060008190555050565b60008135905061009781610103565b92915050565b6000602082840312156100b3576100b26100fe565b5b60006100c184828501610088565b91505092915050565b6100d3816100f4565b82525050565b60006020820190506100ee60008301846100ca565b92915050565b6000819050919050565b600080fd5b61010c816100f4565b811461011757600080fd5b5056fea2646970667358221220404e37f487a89a932dca5e77faaf6ca2de3b991f93d230604b1b8daaef64766264736f6c63430008070033 ``` Found (in [blockexplorer](https://blockscout.mandala.acala.network/address/0x28F5550315182D8446e9BFa5eD24a7796ee6e2a1/contracts)): ``` 0x608060405234801561001057600080fd5b5060c78061001f6000396000f3fe6080604052348015600f57600080fd5b506004361060325760003560e01c80632e64cec11460375780636057361d146053575b600080fd5b603d607e565b6040518082815260200191505060405180910390f35b607c60048036036020811015606757600080fd5b81019080803590602001909291905050506087565b005b60008054905090565b806000819055505056fea2646970667358221220147f3cf30018f8f81e5d18392cb5863560a8fed3540f92860706834fa72bb1a664736f6c63430007040033 ``` How are you deploying the contract? Are you...

Closing due to inactivity