From 532ff11003eb8cb0c1b2f67e23adf7de851baf74 Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Thu, 17 Feb 2022 23:28:29 +0100 Subject: [PATCH] comment on donation Signed-off-by: Pascal Marco Caversaccio --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 36ac36d..705b8c1 100644 --- a/README.md +++ b/README.md @@ -194,3 +194,6 @@ Using the `CREATE2` EVM opcode always allows to redeploy a new smart contract to ### A Note on the Contract Creation Transaction It is important to note that the `msg.sender` of the contract creation transaction is the helper smart contract [`Create2Deployer`](https://github.com/pcaversaccio/create2deployer) with address `0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2`. If you are relying on common smart contract libraries such as [OpenZeppelin](https://github.com/OpenZeppelin/openzeppelin-contracts) for your smart contract, which set certain constructor arguments to `msg.sender` (e.g. `owner`), you will need to change these arguments to `tx.origin` so that they are set to your deployer's EOA address. > **Caveat:** Please familiarise yourself with the security considerations concerning `tx.origin`. You can find more information about it, e.g. [here](https://docs.soliditylang.org/en/v0.8.11/security-considerations.html?highlight=tx.origin#tx-origin). + +## Donation +I am a strong advocate of the open-source and free software paradigm. However, if you feel my work deserves a donation, you can send it to this address: [`0x07bF3CDA34aA78d92949bbDce31520714AB5b228`](https://etherscan.io/address/0x07bF3CDA34aA78d92949bbDce31520714AB5b228). I can pledge that I will use this money to help fix more existing challenges in the Ethereum ecosystem 🤝.