truffleor a system alike.
updateof the contract
simple_price_oracle v0.2.7with address 0xea9419fa3cf9c66ef250e474db596575986cad48 on network
@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.
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.
When deploying a contract written in Zinc using
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)?
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
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?
rinkebyand interacts with its zkSync node (sends transactions and executing contract methods). The release you are using now (0.2.3) is half a year old demo, so the contract storage (except balances) is kept in PostgreSQL, but the balances are stored in zkSync.
0xprefix from the private key.
Thanks for the help! Can't wait for the next release. The private key change worked. I was also able to deploy & call my contract on rinkeby using
Tried the API endpoints but so far to no avail (gives 404). Is the root url I got from https://github.com/matter-labs/zinc/blob/main/zargo/src/network.rs#L23 correct (
I tried with
curl -v -X PUT "https://rinkeby3-zandbox.zksync.dev/api/v1/query?address=0x6f5c9eaa40f5ca1b5fb0913d59a85beb4aa721d9&method=get_fee"