nlordell / deadbeef Goto Github PK

Hey @nlordell, this project is awesome and I just had a quick question.

I am trying to update to Safe v1.4.0 - I did all the necessary updates for the PROXY_FACTORY, SINGLETON, and FALLBACK_HANDLER based on these Safe deployment addresses.

But I don't see how you calculated thePROXY_INIT_CODE_DIGEST here:

I've tried calling:

cast call 0xa6B71E26C5e0845f74c812102Ca7114b6a896AB2 "proxyCreationCode()"

where 0xa6B71E26C5e0845f74c812102Ca7114b6a896AB2 is the v1.3.0 address, and running Keccak256 on that result, and it does not seem to match.

Would love to get some guidance on how I can get the new PROXY_INIT_CODE_DIGEST for v1.4.0. I'll make a PR here to update once that's done.

This issue captures the work to build deadbeef in WASM and provide a JS wrapper for running it in the browser.

Ideally, it could spawn multiple web Workers to leverage multiple CPUs. It can read the number of CPUs from: navigator.hardwareConcurrency.

In particular, not all chains share the same proxy factory contract, and hence PROXY_INIT_CODE value. As such, in order to support more varied configurations, constants such as PROXY_INIT_CODE should be configurable on the command line.

For example, the value of PROXY_INIT_CODE needed for Arbitrum is caf2dc2f91b804b2fcf1ed3a965a1ff4404b840b80c124277b00a43b4634b2ce.

I've been trying to generate multiple vanity Safe addresses. In particular finding a case sensitive match word (0xca1f vs 0xCA1F). For this it's good to run the script multiple times, until you find the right vanity Safe address. Doing this manually is tedious.

Perhaps it could be mentioned in the README.MD file you could run the script multiple times and write the output to a (text) file. E.g. using this bash one liner.

for i in {1..200}; do ./deadbeef --owner 0x0000000000000000000000000000000000000000 --owner 0x0000000000000000000000000000000000000000 --threshold 1 --prefix 0xCa1f00 >> deadbeef-output.txt; done

This will run deadbeef 200 times and write the output to the same directory in file deadbeef-output.txt. You then can manually case-sensitive search the output file for the desired Safe address.

On my machine it happened to run the tasks in parallel (utilizing all CPUs, also a moment to appreciate https://github.com/aristocratos/btop :) ).

Hi - trying to use this generator, but I don't understand where the saltNonce is coming from?

Shouldn't there be one more output after callData?