Requirements on library and which factory to choose about clone-factory

[yarrumretep]

Hey @mrwillis - no worries, here is fine.

1. The contract should not be a solidity library - it should be an ordinary contract but likely with an initialization pattern such as the one in the example. Yes - the Thing that is deployed initially is the master contract - the code for which is run for each of the 'clones' but with the clones' storage.
2. The one without the numeric suffix is the easiest to start with. The numbered ones can be used to squeeze a few bytes of deployment cost out of the system by using a vanity contract address for the master. Not necessary in most cases. The numbers refer to the number of non-leading-zero bytes in the vanity address of the master contract.

Make sense?

Good luck and happy cloning!

Rock on,

pete

[yarrumretep]

Hi Julian, Yes, a separate mini-contract is deployed for each clone. The contract that is deployed for each clone contains only the bytecode which forwards all incoming calls to the master. It is literally the hex bytecode in the CloneFactory.sol file, but with the destination address replaced with your master contract destination address. The way the storage / events work the delegatecall will just "do the right thing" and the master-contract code will run as if it lives at the clone-contract's address (and, therefore, storage address space).

…

-pete

On Fri, Jul 6, 2018 at 9:59 AM Julian Wilson ***@***.***> wrote: Thanks Pete. Just so I have this clear, there *still* are contracts being deployed, it's just that these contracts simply delegatecalling everything to the master contract, is this right? As well, if you had to write the source of the clones (in solidity), what would it look like? Just the storage members, the event and static declarations, and a bunch of methods with one line forwarding the call to the master with delegatecall? Thanks again. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAsQuwW5T2pHkrfcmuAWAkWsLZgX7Brcks5uD21bgaJpZM4VEoos> .

-- -pete peter m. murray [email protected]

[nateawelch]

@mrwillis Just to elaborate on what pete said a little bit, there is no Solidity source for the cloned contracts. We wrote the assembly so it was as small as possible while still having complete return data and revert capabilities. If I were to write the equivalent of what it does in Solidity, it would just be a payable fallback function that takes the call data and calls the master contract with it, returns the result (including revert data), and does nothing else. If you wrote this in Solidity though, the bytecode would be a good amount larger.

[mrwillis]

Thanks all for the help. I managed to get it to work. I got my 500 line contract to be deployed with ~100k gas! Great improvement.

[mrwillis]

Thanks Pete.

Just so I have this clear, there still are contracts being deployed, it's just that these contracts simply delegatecalling everything to the master contract, is this right?

As well, if you had to write the source of the clones (in solidity), what would it look like? Just the storage members, the event and static declarations, and a bunch of methods with one line forwarding the call to the master with delegatecall?

Thanks again.

[yarrumretep]

Great stuff, @mrwillis - I'll close this issue for now, feel free to reopen or just comment on it if you have further questions.