Axel has been upgraded to version 2.17.10, but SSL is still reporting an error Initializing download: https://universal-setup.ams3.digitaloceanspaces.com/setup_2%5E20.key SSL error: certificate verify failed (null) Error: Child process exited with code 1

Hi, I'm trying to check out a gitcoin grants donation via zksync, but I'm getting Network error.

It looks like the reason is CORS errors showing up in my terminal:

Access to XMLHttpRequest at 'https://api.zksync.io/jsrpc' from origin 'https://checkout.zksync.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Getting an invalid tx error after the transfer signature request.

wallet: Authereum via WalletConnect network: rinkeby account (contract-based-account): 0xe0DBe2703FB3fC9Cd36fb5717437e738F4002681 message (hex): 0x5472616e7366657220302e30303031204554480a546f3a203078346363613566326630313734366231633133636137613364616230343632643232353739356433610a4e6f6e63653a2033350a4665653a20302e3030303031333338204554480a4163636f756e742049643a203334 message (utf8):

Transfer 0.0001 ETH
To: 0x4cca5f2f01746b1c13ca7a3dab0462d225795d3a
Nonce: 35
Fee: 0.00001338 ETH
Account Id: 34

signature: 0x1a1997812a419ae57e68d8f4d3f375e0b7b2a036f0a58e838bbd5ec931dfddd80d0875b60940248b043e41c1239e5fc06a6e940b610c13431130fd9a082f2e7d1c

The isValidSignature on-chain check appears to be valid:

request:

{"id":2,"jsonrpc":"2.0","params":[{"data":"0x20c13b0b000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000006f5472616e7366657220302e30303031204554480a546f3a203078346363613566326630313734366231633133636137613364616230343632643232353739356433610a4e6f6e63653a2033350a4665653a20302e3030303031333338204554480a4163636f756e742049643a203334000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000411a1997812a419ae57e68d8f4d3f375e0b7b2a036f0a58e838bbd5ec931dfddd80d0875b60940248b043e41c1239e5fc06a6e940b610c13431130fd9a082f2e7d1c00000000000000000000000000000000000000000000000000000000000000","to":"0xe0dbe2703fb3fc9cd36fb5717437e738f4002681"},"latest"],"method":"eth_call"}

response:

{"jsonrpc":"2.0","id":2,"result":"0x20c13b0b00000000000000000000000000000000000000000000000000000000"}

Thanks in advance for any help

Here is my code :

const walletPrivateKey = new ethers.Wallet(PrivateKey) ;
const ethWallet = await walletPrivateKey.connect(ethersProvider);
const syncWallet = await zksync.Wallet.fromEthSigner(ethWallet, syncProvider);

if (! await syncWallet.isSigningKeySet()) {
    const onchainAuthTransaction = await syncWallet.onchainAuthSigningKey();
    // Wait till transaction is committed on ethereum.
    await onchainAuthTransaction.wait();

    const changePubkey= await syncWallet.setSigningKey({
        feeToken: "ETH",
        fee: ethers.utils.parseEther("0.001")
    });
    // Wait till transaction is committed 
    const receipt = await changePubkey.awaitReceipt();
}

Error for the same code on mainnet network :

Error: insufficient funds for intrinsic transaction cost (error={"reason":"processing response error","code":"SERVER_ERROR","body":"{"jsonrpc":"2.0","id":46,"error":{"code":-32000,"message":"insufficient funds for gas * price + value"}}","error":{"code":-32000},"requestBody":"{"method":"eth_sendRawTransaction","params": ......

syncWallet.onchainAuthSigningKey(); this function perfectly works on ropsten but not on mainnet! is this issue arising from my code or library somehow has an issue ? thanks for your help in advance.

I am reading the source code of matter-lab/zksync to understand it better and then join you guys to build this project.

But I have some questions.

I want to know which branch is more suitable for reading and learning, master branch or dev branch, can you tell me the difference between them?

Can you explain this to me?

And another issue, there is a few information about zksync source code, so I think the solution is to encourage more people write articles to explain how exactly zksync works

@popzxc @StanislavBreadless

Hello, I'm interested in the Instant Confirmation Mechanism, and want to know more details about it. Where can I get the doc or the code? Waiting for your reply, thank you!

https://github.com/matter-labs/zksync/blob/59e6def837099021169c35b7db7d7641f1a03b3b/core/bin/data_restore/src/events_state.rs#L364-L374

when self.verified_events.len() > self.committed_events.len() self.committed_events[0..count_to_get].to_vec() will overflow.

I meet this condition when restore databae.

I will give a bug fix.

I'm trying to transfer eth and getting this error

`async function asyncCall() { const syncWallet = zksync.Wallet.fromEthSigner(ethWallet, syncProvider); const object = await syncWallet; console.log(object.address());

const deposit = await object.depositToSyncFromEthereum({ depositTo: object.address(), token: 'ETH', amount: ethers.utils.parseEther('0.1') }); }`

UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'mainContract' of undefined at Wallet. (/Users/aequalis/Documents/zksync/node_modules/zksync/build/wallet.js:429:92) at Generator.next () at fulfilled (/Users/aequalis/Documents/zksync/node_modules/zksync/build/wallet.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:97:5)

Prize Title

Cheap blanc checks / payment links dapp built with zkSync.

Prize Bounty

500 DAI.

Challenge Description

Introduction

There is an open-source coder Alice. She earns her living via donations. She receives payments on Ethereum, but to make the process of donating simple, Alice wants to put on her project's GitHub page a donation payment link instead of her address. This way, the users can jump straight into donating by clicking the link.

Alice does not want to pay high fees and does not want her users to pay them either, so she uses zkSync as the Ethereum scaling solution of her choice. But how can she generate such a payment link?

The challenge

Your task is to create a website that can generate zkSync payment links. Your website should be able to do the following:

Given an Ethereum address and maybe some additional information, your website should generate a payment link, which encodes the address of the transaction's recipient (and possibly some additional information). Whenever someone opens the link, the user will go through the zkSync checkout process and will donate to the provided zkSync account.

The library that you must use to start the checkout process is described here.

Submission Requirements

• The solution must use the zkSync checkout library. Here is the link to the docs.
• It must be secure, i.e. no exposure of private keys, etc.
• A link to the demo of your service must be included in the submission. You might also attach the link to the GitHub repo of your solution.
• You must include the link to the GitHub page with the source code, containing README.md with the description of your solution in English.

Judging Criteria

• UI quality.
• The UX should be smooth and delightful.
• Usability, i.e., it should be easy for both senders and recipients to use your service.
• Universality, i.e. there should be many use-cases for your service. Donations is only one example. There might also be shops, that would want to use your website. The bigger the target audience is, the better!

I often use the zksync network for transfers and mint nft, but I found that in the past few months, the system will require me to activate my account multiple times to use the transfer function. This is different from the advertised account that only needs to be activated once. I hope to check out what caused this error My address is 0x6eCe332E1324FB0C080a6364e84171EEc1571f5f thank you very much

Hi, when I run zk init, in the last step this happens:

[100%] Built target wasm-opt
wasm2js(38848,0x114345e00) malloc: *** error for object 0x7fd9b7820000: pointer being freed was not allocated
wasm2js(38848,0x114345e00) malloc: *** set a breakpoint in malloc_error_break to debug
./build.sh: line 24: 38848 Abort trap: 6           ../binaryen/bin/wasm2js ./dist/zksync-crypto-bundler_bg.wasm -o $ASM

Another prove I did:

within the sdk/binaryen folder, run:

python3 check.py

[ checking wasm-opt -o notation... ]

executing:  /Users/julian/workspace/rskj-projects/zk/zksync/sdk/binaryen/bin/wasm-opt /Users/julian/workspace/rskj-projects/zk/zksync/sdk/binaryen/test/hello_world.wat -o a.wat -S
warning: no passes specified, not doing any work
wasm-opt(39600,0x1062f5e00) malloc: *** error for object 0x7f92b1c0ab60: pointer being freed was not allocated
wasm-opt(39600,0x1062f5e00) malloc: *** set a breakpoint in malloc_error_break to debug
Traceback (most recent call last):

Here my clang version:

clang --version
Apple clang version 12.0.5 (clang-1205.0.22.11)
Target: x86_64-apple-darwin20.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 12.0.5 (clang-1205.0.22.11)
Target: x86_64-apple-darwin20.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

The OS is MacOS Big Sur 11.5.1

(lldb) target create "bin/wasm-opt"
Current executable set to '/Users/julian/workspace/rskj-projects/zk/zksync/sdk/binaryen/bin/wasm-opt' (x86_64).
(lldb) b malloc_error_break
Breakpoint 1: where = libsystem_malloc.dylib`malloc_error_break, address = 0x00007fff2014f9ab
(lldb) run test/hello_world.wat -o a.wat -S
Process 5197 launched: '/Users/julian/workspace/rskj-projects/zk/zksync/sdk/binaryen/bin/wasm-opt' (x86_64)
warning: no passes specified, not doing any work
wasm-opt(5197,0x100920e00) malloc: *** error for object 0x107015e00: pointer being freed was not allocated
wasm-opt(5197,0x100920e00) malloc: *** set a breakpoint in malloc_error_break to debug
Process 5197 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x00007fff2034b9ab libsystem_malloc.dylib`malloc_error_break
libsystem_malloc.dylib`malloc_error_break:
->  0x7fff2034b9ab <+0>: pushq  %rbp
    0x7fff2034b9ac <+1>: movq   %rsp, %rbp
    0x7fff2034b9af <+4>: nop
    0x7fff2034b9b0 <+5>: nopl   (%rax)
Target 0: (wasm-opt) stopped.

This PR adds comments to the code to improve its readability and understandability. In open source projects, it is important to have well-documented code so that other contributors can easily understand the intent and purpose of the code. By adding comments, we can help ensure that the code is maintainable and can be easily modified and extended by others in the future.

The following error occurs when I run zk init Finished release [optimized] target(s) in 0.08s [WARN]: :-) origin crate has no README [INFO]: License key is set in Cargo.toml but no LICENSE file(s) were found; Please add the LICENSE file(s) to your project directory [INFO]: Installing wasm-bindgen... [INFO]: Optimizing wasm binaries withwasm-opt`... [INFO]: Optional field missing from Cargo.toml: 'description'. This is not necessary, but recommended [INFO]: :-) Done in 2.40s [INFO]: :-) Your wasm pkg is ready to publish at /home/march/桌面/code/zksync-master/sdk/zksync-crypto/node-dist. [WARN]: :-) There's a newer version of wasm-pack available, the new version is: 0.10.3, you are using: 0.10.1. To update, navigate to: https://rustwasm.github.io/wasm-pack/installer/ CMake Warning: Ignoring extra path from command line:

"."

CMake Error: The source directory "/home/march/桌面/code/zksync-master/sdk/binaryen" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. ./build.sh:行29: ../binaryen/bin/wasm2js: 没有那个文件或目录error Command failed with exit code 127. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed. Exit code: 127 Command: /usr/bin/node Arguments: /usr/lib/node_modules/yarn/lib/cli.js build Directory: /home/march/桌面/code/zksync-master/sdk/zksync-crypto Output:

info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command. error Command failed with exit code 127. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 127. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Error: Child process exited with code 127 `

I'm sure the dependency package version is correct.

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• core/bin/add_seq_no/Cargo.toml (cargo)
• core/bin/block_revert/Cargo.toml (cargo)
• core/bin/data_restore/Cargo.toml (cargo)
• core/bin/key_generator/Cargo.toml (cargo)
• core/bin/parse_pub_data/Cargo.toml (cargo)
• core/bin/prover/Cargo.toml (cargo)
• core/bin/remove_proofs/Cargo.toml (cargo)
• core/bin/server/Cargo.toml (cargo)
• core/bin/tree_cache_updater/Cargo.toml (cargo)
• core/bin/zksync_api/Cargo.toml (cargo)
• core/bin/zksync_core/Cargo.toml (cargo)
• core/bin/zksync_eth_sender/Cargo.toml (cargo)
• core/bin/zksync_event_listener/Cargo.toml (cargo)
• core/bin/zksync_forced_exit_requests/Cargo.toml (cargo)
• core/bin/zksync_witness_generator/Cargo.toml (cargo)
• core/lib/api_client/Cargo.toml (cargo)
• core/lib/api_types/Cargo.toml (cargo)
• core/lib/balancer/Cargo.toml (cargo)
• core/lib/basic_types/Cargo.toml (cargo)
• core/lib/circuit/Cargo.toml (cargo)
• core/lib/config/Cargo.toml (cargo)
• core/lib/contracts/Cargo.toml (cargo)
• core/lib/crypto/Cargo.toml (cargo)
• core/lib/eth_client/Cargo.toml (cargo)
• core/lib/eth_signer/Cargo.toml (cargo)
• core/lib/gateway_watcher/Cargo.toml (cargo)
• core/lib/mempool/Cargo.toml (cargo)
• core/lib/notifier/Cargo.toml (cargo)
• core/lib/prometheus_exporter/Cargo.toml (cargo)
• core/lib/prover_utils/Cargo.toml (cargo)
• core/lib/state/Cargo.toml (cargo)
• core/lib/storage/Cargo.toml (cargo)
• core/lib/storage/db_test_macro/Cargo.toml (cargo)
• core/lib/token_db_cache/Cargo.toml (cargo)
• core/lib/types/Cargo.toml (cargo)
• core/lib/utils/Cargo.toml (cargo)
• core/lib/vlog/Cargo.toml (cargo)
• sdk/zksync-crypto/Cargo.toml (cargo)
• sdk/zksync-rs/Cargo.toml (cargo)
• docker-compose-runner.yml (docker-compose)
• docker-compose.yml (docker-compose)
• infrastructure/exit-tool/docker-compose.yml (docker-compose)
• docker/data-restore/Dockerfile (dockerfile)
• docker/dev-liquidity-token-watcher/Dockerfile (dockerfile)
• docker/dev-ticker/Dockerfile (dockerfile)
• docker/event-listener/Dockerfile (dockerfile)
• docker/exit-tool/Dockerfile (dockerfile)
• docker/geth/Dockerfile (dockerfile)
• docker/keybase-secrets/Dockerfile (dockerfile)
• docker/prover/Dockerfile (dockerfile)
• docker/runner/Dockerfile (dockerfile)
• docker/server/Dockerfile (dockerfile)
• docker/zk-environment/Dockerfile (dockerfile)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/deploy.chat.yml (github-actions)
• .github/workflows/deploy.rinkeby-beta.yml (github-actions)
• .github/workflows/deploy.yml (github-actions)
• .github/workflows/loadtest.yml (github-actions)
• .github/workflows/npm.publish-packages.yml (github-actions)
• .github/workflows/server.update-config-dispatch.yml (github-actions)
• .github/workflows/server.update-config.yml (github-actions)
• .github/workflows/setup.runtime.yml (github-actions)
• .github/workflows/zk-environment.publish.yml (github-actions)
• contracts/package.json (npm)
• infrastructure/api-docs/package.json (npm)
• infrastructure/exit-tool/perform_exodus/package.json (npm)
• infrastructure/reading-tool/package.json (npm)
• infrastructure/token-lists-manager/package.json (npm)
• infrastructure/zk/package.json (npm)
• package.json (npm)
• sdk/zksync-crypto/package.json (npm)
• sdk/zksync.js/package.json (npm)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

What to Expect

With your current configuration, Renovate will create 94 Pull Requests:

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate. View repository job log here.

For producing environment,I think that it is necessary of zksync to support for distributed framework.

Considering the following situations:

• Single point problem.(It couldn't service at all when the only one server is down.)
• The main components of zksync communicate with each other by threads' channel.Distributed services will use rpc to interact with others instead.
• Transaction per second of zksync will also be limited by single one framework.(e.g Application like the perpetual contract that will reach more than thousand query per second.)But how to keep the zksync state of all server being consistent is another tricky problem.
• It couldn't service when need publish or restart.(e.g fixing bugs or publishing new features)

May be it is time to develop distributed mode for zksync in sometime with its widely used as a leading open source zk framework.

Thanks.