Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current status of the project (April 2024) #435

Open
therealdannzor opened this issue Apr 15, 2024 · 1 comment
Open

Current status of the project (April 2024) #435

therealdannzor opened this issue Apr 15, 2024 · 1 comment

Comments

@therealdannzor
Copy link

Hello, first of all thanks for all the open-source work concerning the zk stack. Very useful and well documented.

To my question: is this project still working as expected after the Discord announcement on March 27? It would be super useful to have that confirmed as we're attempting to get automatic finalization of withdrawals on a pre-eip-4844 hyperchain.

cc @montekki, zkSync-Community-Hub/zksync-developers#457

Screenshot 2024-04-15 at 09 01 19

@montekki
Copy link
Contributor

Hi @therealdannzor , yes the project should still be functional for the general use-case, if it is not this is not expected and is a bug. What the above announcement actually means withing our setup, is that we are running the same existing code with the following option:

ONLY_L1_RECIPIENTS: "[\"0xA9232040BF0E0aEA2578a5B2243F2916DBfc0A69\"]"

Which basically means that within our own setup we only want to be finalising withdrawals that happen to our own fees address. However without such a whitelist things should work as before. LMK if this helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants