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

start network #20

Closed
tony-armstrong opened this issue Nov 6, 2023 · 5 comments
Closed

start network #20

tony-armstrong opened this issue Nov 6, 2023 · 5 comments
Assignees

Comments

@tony-armstrong
Copy link
Collaborator

  1. adjust b2-zkevm-node conf(contract, ip, port, etc.) to adapt to b2-node
  2. adjust b2-zkevm-node genesis(contract, ip, port, etc.) to adapt to b2-node
@tony-armstrong tony-armstrong self-assigned this Nov 6, 2023
tony-armstrong pushed a commit to b2network/b2-zkevm-node that referenced this issue Nov 6, 2023
tony-armstrong pushed a commit to b2network/b2-zkevm-node that referenced this issue Nov 7, 2023
@tony-armstrong
Copy link
Collaborator Author

The Full Prover require 96-core CPU, Mininum 768GB RAM Deploying Your Own Full zkEVM | Polygon Wiki

tony-armstrong pushed a commit to b2network/b2-zkevm-node that referenced this issue Nov 7, 2023
tony-armstrong pushed a commit to b2network/b2-zkevm-prover that referenced this issue Nov 7, 2023
tony-armstrong pushed a commit to b2network/b2-zkevm-node that referenced this issue Nov 8, 2023
refactor: made small changes to genesis.json
tony-armstrong pushed a commit to b2network/b2-zkevm-node that referenced this issue Nov 8, 2023
tony-armstrong pushed a commit to b2network/b2-zkevm-contracts that referenced this issue Nov 8, 2023
@tony-armstrong
Copy link
Collaborator Author

  1. the local dev/test (mock prover) network can be started
  2. should deployment-related code/doc be moved to repo b2network/b2-deployment? b2network/b2-deployment#1 @0x677261706562616261

@0x677261706562616261
Copy link

  1. the local dev/test (mock prover) network can be started
  2. should deployment-related code/doc be moved to repo b2network/b2-deployment? Init b2 network devnet scripts b2-deployment#1 @0x677261706562616261

If not so many deps exist, i think it is better to moving. what's your opinion? Maybe we could have a call tomorrow.

@tony-armstrong
Copy link
Collaborator Author

  1. some e2e test actions rely on these codes
    intel-10400f .github gigit remote get-url origin 
    git@github.com:b2network/b2-zkevm-node.git
    intel-10400f .github git:(develop) grep -wrnE 'make|test' workflows/test-*
    workflows/test-e2e.yml:14:  test-e2e:
    workflows/test-e2e.yml:34:      run: make build-docker
    workflows/test-e2e.yml:37:      run: make compile-scs
    workflows/test-e2e.yml:38:      working-directory: test
    workflows/test-e2e.yml:41:      run: make test-e2e-group-${{ matrix.e2e-group }}
    workflows/test-e2e.yml:42:      working-directory: test
    workflows/test-from-prover.yml:15:  test-from-prover:
    workflows/test-from-prover.yml:44:      run: make build-docker
    workflows/test-from-prover.yml:47:      run: make compile-scs
    workflows/test-from-prover.yml:48:      working-directory: test
    workflows/test-from-prover.yml:51:      run: make test-full-non-e2e
    workflows/test-from-prover.yml:52:      working-directory: test
    workflows/test-full-non-e2e.yml:14:  test-full-non-e2e:
    workflows/test-full-non-e2e.yml:32:      run: make compile-scs
    workflows/test-full-non-e2e.yml:33:      working-directory: test
    workflows/test-full-non-e2e.yml:38:      run: make test-full-non-e2e
    workflows/test-full-non-e2e.yml:39:      working-directory: test
  2. I think even if this part is moved to another repo, there is still a way to be used by action
  3. or maybe wo can leave it alone and let the bullets fly for a while 😄

how about we not move this code yet? @0x677261706562616261 @Stonepapa

tony-armstrong pushed a commit to b2network/b2-zkevm-node that referenced this issue Nov 10, 2023
@tony-armstrong
Copy link
Collaborator Author

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

No branches or pull requests

2 participants