A place for talking about the Ethereum Virtual Machine on Farcaster.

Worked on a multi-chain contract factory at ETH NY this weekend. All deployments and admin actions originate from a single Safe on a single chain, passing bytecode and calldata over a bridge. No more nonce issues or one-Safe-per-chain setups.

Would love feedback :)

Worked on a multi-chain contract factory at ETH NY this weekend. All deployments and admin actions originate from a single Safe on a single chain, passing bytecode and calldata over a bridge. No more nonce issues or one-Safe-per-chain setups.

Would love feedback :)

https://github.com/jaydenwindle/safe-create2

Perpetually learning. Building primitives: /tokenbound /perma fp.inc

Good hack! 

have thought about this a decent bit, so sharing my 2 cents, probably not the best idea to use a bridge to do this

deployer can just sign over the bytecode and relayers can send the bytecode across-chains

bridge adds new trust to the system as well as is expensive

I say this as a bridge builder myself.

Thanks! This is a neat idea, but how would it work with a Safe as the deployer (since the Safe only exists on one chain)? Agreed on trust, this is essentially trusting that a bridge can handle cross-chain actions in a more secure/decentralized way than you can manage a deployer private key.