Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alex Z
    @hedgar2017
    @james-ray Zandbox is only a demo. Our production design is different :)
    gazellefi
    @gazelle75113415_twitter
    How to get the time parameter in Zine? If you cannot get the block time, can you get the system time?
    gazellefi
    @gazelle75113415_twitter
    Can't you set global variables in the Zine language?
    gazellefi
    @gazelle75113415_twitter
    Can the key in Maps be written in letters? Similar to "byte" or" string" in the solidity language?
    Husen Wang
    @wanghs09
    global variables are not available now
    Husen Wang
    @wanghs09
    if the layer2 vm is similar to EVM, would openzeppelin/truffle test be compatible in Zinc contract test? the interactive test in https://zinc.zksync.io/07-smart-contracts/02-minimal-example.html is quite inefficient.
    Alex Z
    @hedgar2017
    @gazelle75113415_twitter to all three questions: not available yet :)
    We'll implement the system and block in one of the next versions.
    Global mutable variables will probably never be implemented due to the safety concerns.
    Byte strings will be also implemented with the byte array behavior.
    @wanghs09 we are planning the integration with truffle or a system alike.
    gazellefi
    @gazelle75113415_twitter
    Can the LP in curve be transferred in the wallet?
    CURVE in the demo version is incomplete and there is no LP.
    Alex Z
    @hedgar2017
    @gazelle75113415_twitter yeap, no LP for now.
    We are going to add it after the Turing-complete release.
    @z330789559 hi. Could you please try the Contract::fetch function?
    z330789559
    @z330789559
    @hedgar2017 I'm very happy to hear the news, I'll give it a try
    z330789559
    @z330789559
    @hedgar2017 query is ok but call has error
    libaozhongdeMacBook-Pro:simple_price_oracle libaozhong$ zargo call --address 0xea9419fa3cf9c66ef250e474db596575986cad48 --method update --network rinkeby
    Calling method update of the contract simple_price_oracle v0.2.7 with address 0xea9419fa3cf9c66ef250e474db596575986cad48 on network rinkeby
    [ERROR zargo] signing error: Signing failed: Transfer is incorrect, check amounts
    {
    "address": "0xea9419fa3cf9c66ef250e474db596575986cad48",
    "balances": [
    {
    "key": "0x0",
    "value": "64400000000000"
    }
    ],
    "x": "0"
    }
    @hedgar2017
    I have never understood how to use my eth private key to generate private_key
    z330789559
    @z330789559
    @hedgar2017 call has normally work ,but if msg.recipient is 0x0000000000000000000000000000000000000000 ,it will case error signing error: Signing failed: Transfer is incorrect, check amounts
    JamesRay
    @james-ray
    @hedgar2017 For the same circuit, if we execute setup() many times, the vk should be the same, right?
    Can I say anyone can verify a certain vk is related to some logic or relation to prove? This fact can be verified by anyone?
    Alex Z
    @hedgar2017
    @z330789559 thanks. We have already taken care of that counter-intuitive error.
    @james-ray we are currently focused on the smart contracts release and temporarily suspended circuits support.
    I believe we'll get back to that functionality after the mainnet release.
    Dennis Gearon
    @kwince
    @hedgar2017
    @hedgar2017 (1) do you know an effective way to search on gitter to find previous post? (2) the only link I found for a source for token pricing from within a zinc contract is a dead link on your website now. Can you give me some sort of documentation or example of the current source of token pricing from within a zinc contract? (3) This is pretty exciting stuff 😀
    Alex Z
    @hedgar2017
    @kwince
    1) No, it doesn’t seem like it’s possible)
    2) Our old examples shouldn’t be relied on at the moment. In the Turing-complete version contracts will be slightly different. Also, if something is not in the Zinc book, it does not exist in Zinc yet :)
    3) thanks :heart_eyes_cat:
    Dennis Gearon
    @kwince
    Thx @hedgar2017
    JamesRay
    @james-ray
    Can you shed some light on how L1 can verify the post-state of some Zinc contract, whether Turing-complete or not complete.
    You said production design will be different, how does the verification work? @hedgar2017
    Lasse Herskind
    @LHerskind
    Hi, is the solidity transpiler up somewhere, cannot find it? If not, will it be available with the testnet or do we have to wait for main? :)
    Dennis Gearon
    @kwince
    @hedgar2017 Is the next version of zinc going to be 1.0? Or will it be less? Also is there going to be a pragma or some other mechanism that tells the validator running the contract which version of zinc it is set for? And how long will the versions pre 1.0 continue to run on the validator networks? Is there any point in making anything production level before like 1.0 or 1.01?
    Alex Z
    @hedgar2017
    @james-ray hi. This information will be available in our docs, when we are close to the release.
    @LHerskind hi. Actually, we suspended the Solidity-to-Zinc transpiler support, as we are going to support Solidity directly. You’ll need only to make some minor changes to compile a contract into our VM bytecode.
    Alex Z
    @hedgar2017

    @kwince the testnet Turing-complete release is likely to be 0.3. Perhaps, the mainnet one will be 1.0 - not decided yet.

    Concerning pragmas, Zinc is only a language with its compiler.
    There are several abstraction layers between the compiler and VM, like LLVM IR and the bytecode (or assembly text).
    Thus, pragma will be needed only for the package manager like zargo to check whether there is the correct version of the Zinc compiler in PATH.

    Dennis Gearon
    @kwince
    Thx Alex @hedgar2017
    hanakomodo
    @hanakomodo
    turing complete zinc and testnet are both targeting may right? excited to try developing for zksync but seems like the correct thing to do is wait for that?
    Alex Z
    @hedgar2017
    @hanakomodo yeah, exactly :)
    85
    @eightyfive
    👋 there. How much cheaper is running some SC on zkSync L2? Is there some
    *docs someone could point to?
    Alex Z
    @hedgar2017
    @eightyfive hi!
    There were some talks about orders of magnitude, but there zkSync guys should give more precise info :)
    https://gitter.im/matter-labs/zksync
    85
    @eightyfive
    🙏
    Is there some public vyper-to-zinc transpiler ? I guess the team did not translate all the Curve vyper contracts by hand, or did you?
    Alex Z
    @hedgar2017
    @eightyfive nope, just rewrote this part by hand.
    https://github.com/matter-labs/curve-zinc
    85
    @eightyfive
    Ok. Why not 🙂
    JamesRay
    @james-ray
    I am trying to use CLion to debug the server and the prover, however the sever started and soon panicked:
    thread 'main' panicked at 'Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.'
    24: 0x562d3a2c60ba - zksync_api::fee_ticker::ticker_api::coingecko::CoinGeckoAPI::new::hb7540c35664399f4
    at /home/james/workspace/zksync/core/bin/zksync_api/src/fee_ticker/ticker_api/coingecko.rs:27:26
    25: 0x562d3a3c1127 - zksync_api::fee_ticker::run_ticker_task::h47c3c743da9dc809
    at /home/james/workspace/zksync/core/bin/zksync_api/src/fee_ticker/mod.rs:282:17
    26: 0x562d3a6efd54 - zksync_api::run_api::h550531807cbf1995
    at /home/james/workspace/zksync/core/bin/zksync_api/src/lib.rs:25:23
    I found it tries to connect http://127.0.0.1:9876/api/v3/coins/list, I open the url in internet explorer, the url is fine.
    Alex Z
    @hedgar2017
    @james-ray please, address zkSync issues to the zkSync chat :)
    Dennis Gearon
    @kwince
    @hedgar2017 Do you know how to get the private_key needed for transactions? Is it a ZKSYNC private key derived from an Ethereum wallet private key, or is it just he Ethereum private key. I am doing the 'minimal example' here. https://zinc.zksync.io/07-smart-contracts/02-minimal-example.html
    Madis Nõmme
    @madis

    Hello. First of all, amazing technology. I'm happy to be a pioneer and bringing it to the masses. Sorry for my n00b questions in case this is something obvious to the more knowledgeable people here.

    1. When deploying a contract written in Zinc using zargo to rinkeby, do the rinkeby EVM nodes execute it? Or where and how does the L2 come into play (e.g. when and where is the actual zkSync storage kept)?

    2. To call the Zinc contract methods, should I use the same web3 workflow (e.g. new web3.eth.Contract(...) etc.)? Or something else is needed? (the tutorial on Contract Workflow suggests zargo call ...). If it's the latter, what options there are (e.g. to do it using JavaScript)?

    Madis Nõmme
    @madis

    Another question. I followed the minimal-example to the dot (https://zinc.zksync.io/07-smart-contracts/02-minimal-example.html), added private_key but during deployment I get the following error.

    ❯ zargo publish --network rinkeby --instance default
       Compiling vorsti_hind v0.1.0
        Finished release [optimized] target
      Setting up key pair `./data/proving_key` and `./data/verifying_key`
       Uploading the instance `default` of `vorsti_hind v0.1.0` to network `rinkeby`
         Address 0xa87b7674c7e7f1e46e880542b15d4c6857893bfc
    [ERROR zargo] Invalid character 'x' at position 1

    Any hints what could be causing the [ERROR zargo] Invalid character 'x' at position 1?