Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Akira Taniguchi
    @Akira-Taniguchi

    The "zargo build" command gives an error with this source.

    1.command can't resolve "String".
    https://github.com/dev-protocol/zk-sync-protocol/blob/main/dev_protocol/src/main.zn#L8
    What should I do if I want to use a string in a zinc contract?

    2.command can't use "contract" as a reserved word.
    https://github.com/dev-protocol/zk-sync-protocol/blob/main/dev_protocol/src/main.zn#L6

    [ERROR znc]
    error: expected one of type, struct, enum, fn, mod, use, impl, const, found ``
    --> ./src/main.zn:7:1
    |
    7 | contract AddressRegistry {
    | ^
    help: only constants, types, functions, and type implementations may be declared at the module root

    [ERROR zargo] the subprocess failed with status exit code: 1

    3.command can only compile main.zn.
    First, I created a file named address_registry.zn and tried to compile it.
    However, I got an error message "main.zn does not exist.
    When I create a project that handles multiple contracts, what kind of file structure should I use?

    Please, help me.

    tshabs
    @tshabs
    @Akira-Taniguchi 1. you can only use String in a require or debug statement (https://zinc.zksync.io/03-variables-and-types/02-types/06-strings.html)
    for 2 this is strange, which version of zargo & znc are you running?
    Akira Taniguchi
    @Akira-Taniguchi
    1. you can only use String in a require or debug statement (https://zinc.zksync.io/03-variables-and-types/02-types/06-strings.html)
      ok, thanks
    for 2 this is strange, which version of zargo & znc are you running?
    I will search it, please, just moment
    AmitBRD
    @AmitBRD
    Hello, I try to deploy the basic zinc example to rinkeyb but I keep getting:
    [ERROR zargo] contract unlocking request: HTTP error (500 Internal Server Error) ZkSync: RpcError(Failure { jsonrpc: Some(V2), error: Error { code: ServerError(104), message: "Transaction fee is too low", data: None }, id: Str("1") })
    1 reply
    Alex Z
    @hedgar2017
    @AmitBRD hi.
    There have been a lot of zkSync updates since the Zinc 0.2.* release.
    We do not support that Zinc version anymore, so I would recommend waiting for the upcoming release of the Turing-complete Zinc 0.3.
    AmitBRD
    @AmitBRD
    @hedgar2017 thank you for your feedback. I will await 0.3 release , cheers
    Austin Liu
    @yaliu14
    @hedgar2017 I'm getting the following errors: E0277, E0308.
    when trying to compile zinc 0.2.3 with rustc 1.53.0, is there a different compiler version I should be using?
    AmitBRD
    @AmitBRD
    @yaliu14 I would say to wait for zinc 0.3.* as well (I am waiting for that release as 0.2 is no longer supported)
    Alex Z
    @hedgar2017
    @yaliu14 hi!
    Please, show the full error messages.
    Weird, there should be no breaking changes up to Rust 1.53. I think the last time we compiled Zinc 0.2.3 with Rust 1.49 or so.
    Alan.Li
    @lialan
    Hello, apologize if this is not the right place to ask... I am curious about the progress of zkEVM's LLVM backend. I am wondering if any one is working on that?
    Alex Z
    @hedgar2017
    @lialan hello.
    Working on it every day.
    All tests now pass, but we need to optimize bitwise operations a little bit.
    Next week we’ll start making it more public :)
    mattt21
    @mattt21
    Hi @shamatar, could you expand on what other solidity features such as keccak will be left out of 2.0, and what their possible replacements are?
    Alan.Li
    @lialan
    @hedgar2017 Awesome! I am interested in how you are going to do the stack allocation.
    Alexander
    @shamatar
    Keccak/sha256 will be introduced as “precompiles” or builtins in the first expansion. Before this point all the hashes are transformed into collision resistant algebraic hash (e.g. for storage slot derivation)
    Alex Z
    @hedgar2017
    @lialan you will be able to check it out having compiled your first contract :)
    The compiler produces both a text assembly file for reading and a binary file for deployment.
    Alex Z
    @hedgar2017
    @/all by the way, the Yul-to-LLVM front-end has been open-sourced.
    jagdeep sidhu
    @sidhujag
    @hedgar2017 nice so yul to llvm works? that mean it can leverage solc to yul now?
    also zkevm which is based on llvm compiler is also testable?
    Affax
    @affaxltd
    Hello! Just asking, I know that Zinc v0.2 is outdated and all, but I'd still want to experiment with it onchain. My problem is, that I get the error: contract unlocking request: HTTP error (500 Internal Server Error) ZkSync: RpcError(Failure { jsonrpc: Some(V2), error: Error { code: ServerError(104), message: "Transaction fee is too low", data: None }, id: Str("1") }).
    Is there any way to temporarily bypass/fix this? I'd be interested in at least getting something ready in Zinc v0.2 so that when v0.3 drops, I can upgrade to that while still having something done!
    Alex Z
    @hedgar2017
    @sidhujag only the Yul front-end codebase is public. The compiler toolchain binaries will be released later.
    @affaxltd hi!
    Zinc 0.2 and 0.3 are too different for porting something between them. Please, wait for the release.
    Affax
    @affaxltd
    @hedgar2017 Alright, sounds good! Is there any ETA for that happening?
    I'm pretty eager to get started haha
    Peterpaul Klein Haneveld
    @peterpaul
    @hedgar2017 I'm working on a project that uses zinc 0.1.5, but we've ran into the "using witness as array index is not yet supported" error already a couple of times. I've found the commit that solves this for 0.2.0 (ae1849699da7ba9d4a6d8e884f548b71a0b313b4), however that commit also contains some other changes. I've fixed it up to the point that "zargo run" works as expected, however now "zargo setup" fails with "[ERROR zvm] synthesis error: an assignment for a variable could not be computed
    at ./src/main.zn:6:5 (at index_fn)". Do you have any pointers about what was the problem behind the "witness as array index" error?
    Peterpaul Klein Haneveld
    @peterpaul
    Could that error be related to ConstraintSystem changes? I did not yet apply those...
    Peterpaul Klein Haneveld
    @peterpaul
    The circuit I'm testing is:
    fn main(array: [u8; 10], index: i8) -> u8 {
        array[index]
    }
    Alex Z
    @hedgar2017
    @peterpaul hi!
    The witness array indexing was never supported, since we discontinued Zinc 0.1.x almost a year and a half ago.
    In Zinc 0.2.x, we simply disabled most of the constraints in preparation of Turing-incomplete smart contracts release without proofs.
    Unfortunately, we do not plan to support Zinc 0.1.x and 0.2.x, as we are completely focused on our testnet launch and Turing-complete smart contracts on Solidity, Zinc, and Vyper.
    Peterpaul Klein Haneveld
    @peterpaul
    @hedgar2017 Thank you for clearing that up. I thought that I could 'backport' the fixes, but if there are no fixes there's nothing to backport ;). For my immediate problem I've found an alternative implementation.
    Affax
    @affaxltd
    @hedgar2017 any news on Zinc v0.3?
    tshabs
    @tshabs
    @affaxltd im guessing everyone from the ML team is busy trying to get this thing shipped :) so ill put this here: https://medium.com/matter-labs/zksync-2-0-developer-update-d25417f16446
    FeichiDe
    @FeichiDe
    辛苦了!团队
    Alex Z
    @hedgar2017
    @tshabs thanks!
    JuliaJiang7
    @JuliaJiang7
    image.png
    Hi,after I run this command " zargo publish --network rinkeby --instance default", I get this error. what should I do? thanks~
    W. Liu
    @singularTnT
    @hedgar2017 Hi AZ, could you provide some demo of common ERC20/ERC721 token in ZINC doc, I think this can be helpful for a newer to migrate project to zkSync. Thx!
    Alex Z
    @hedgar2017
    @JuliaJiang7 hi!
    The currently available version of Zinc is not supported anymore.
    Please, wait for the upcoming release.
    2 replies
    @singularTnT hi!
    We are currently integrating the Solidity ERC20 contract.
    Perhaps, we'll also have a Zinc implementation later.
    1 reply
    W. Liu
    @singularTnT
    @hedgar2017 Looking forward to update! Thanks for your efforts!
    Johnny Bergström
    @balboah
    just reading about Zinc. I see there are no activity in the repo for 6 months or so. is this thing still scheduled to be integrated in main net this year?
    Celestine Kariuki
    @kcelestinomaria
    Hello there
    I'm still confused on how to set up zinc
    I downloaded the release link but I'm lost at how to enable it, or is there a simpler & straightforward way of setting it up ?
    Would appreciate some help so I can go ahead and use it
    @hedgar2017 , is the current zinc version dead ? I see in one message you state that it's not supported anymore
    JuliaJiang7
    @JuliaJiang7
    @hedgar2017 Hi, when I build my smart contract, I got this error. How can I fix this? thx~
    Michał Wrzosek
    @michal.wrzosek:matrix.org
    [m]

    Hi! I'm trying to deploy a new contract zargo publish --network rinkeby --instance default and I'm getting

    [ERROR zargo] contract uploading request: HTTP error (413 Payload Too Large) <html>
    <head><title>413 Request Entity Too Large</title></head>
    <body>
    <center><h1>413 Request Entity Too Large</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>

    Did you know what could be the problem?

    Michał Wrzosek
    @michal.wrzosek:matrix.org
    [m]
    That's the contract code I wanted to publish on test network: https://github.com/michal-wrzosek/zksync-messages/blob/master/messages/src/main.zn
    Michał Wrzosek
    @michal.wrzosek:matrix.org
    [m]
    My ./target/debug/main.znb is compiled into 11MB file - maybe that's too much for that nginx server. Also, this is my first attempt to write something in zinc so could be that I'm just doing something very wrong here 😬
    Michał Wrzosek
    @michal.wrzosek:matrix.org
    [m]

    :point_up: Edit: Hi! I'm trying to deploy a new contract zargo publish --network rinkeby --instance default and I'm getting

    [ERROR zargo] contract uploading request: HTTP error (413 Payload Too Large) <html>
    <head><title>413 Request Entity Too Large</title></head>
    <body>
    <center><h1>413 Request Entity Too Large</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>

    Do you know what could be the problem?