ZKV presents... Privacy on Polkadot - Presenting Patract, Lipeng Yue

Transcript

[Music] thank you uh let me introduce patrick labs first we are taking a that provides solutions for the watson contract ecosystem we hope to accelerate the transition of the smart contract industry to the washington technology and technology stack as a member of samantha consoles we provide infrastructure level support of tools and services to the community and the zika is an important part of it patrick will issue our own tokens or

launch our own parachutes but as the technology provider helping the parishes of the entire community to integrate the watson contract model developed by parity and helping the entire community to develop a wasting contract more smoothly therefore we organized the patriarch's open platform about the term parishes and four debts by now some of them are focusing on privacy and leaking before introducing how we support zika support for pogba advanced contract we need to first understand the architecture of zika in ethereum

in 2017 ethereum added three pre-compiled contracts of ads mouse and pairing of the bn256 curve they are based on the zika zcash library and run on the native layer of ethereum so developers can continue to use solidity to write the verification logic of the circuit and the application logic which run on the vm virtual machine layer and continue to develop some often programs for generating some proofs at present most of the zika related projects are chosen to develop on

ethereum because of the three pre-compound contracts integrity almost four years ago and the other two was all developed by the community in the last four years so therefore we should first supply provided with such basic library supports the partitions in pocatello ecosystem are all based on the substrate framework with one more layer than the ethereum contract which is a runtime layer based on the vast virtual mission the community can develop different types of contract models including

evm compatible frontier parity is russian contract on the or libra as a move contract so above contract is about the wrong time is the contract layer also uh also we only focus on supporting the watson contract but the support of native and runtime layers can be shared with other contract models if a parachum project doesn't integrate the contract module after slot after auctioneer slot they can only develop a small number of zika applications by themselves and if they integrate a contract function

and provide the z key capability of runtime to the upper level contract developers they can add they can support large scale z key applications and become a platform that's false leaking so compared with e0 which only supports an old bn2 uh 56 the curve uh ziki mega hoped to also support another more efficient bls 12 curve from the beginning but later uh alistair from webster foundation recommended the bs 12 377 and bw6 761 curves by using the artworks

library instead of z cash so as mentioned above we definitely hope to integrate the add mu and a pairing of these four curves directly on the native layer and then provide them to the contract to call through a runtime interface and the chain extension step by step then merge our changes in the native layer upstream into subsidy ripple later alistair thought that there will be a lot of curves that can be integrated so if each curve has three runtime interfaces

the number would be a very large and the entire polka dots would also need to hard focus to support the new curves because the hot upgrade powered by the governance can only update the runtime layer running invasive therefore it is better to decompose the lower level shared algorithms of these curves and then integrate them in the native layer or the samsung primitive layer so in this way the interface will be relatively fixed and the community can add the upper level curves at any time but the detailed design remains to be

researched therefore even if we develop as a native version something won't allow us to merge uh if native layer cannot be changed we can also add a palace in the runtime but the speed will be much slower so we did the same work twice uh in the native layer and long-time layer adjust the native version cannot be used in the production level production environment but only used as a benchmark comparison with our long time version so now the ink can cause its curves so we also encapsulated

an ink contract library including a high level group 16 verification function and three other small two functions making it more easier to develop upper level applications these are the commonly used functions of existing dke ethereum which were previously written by the expensive solid kit but now we use more efficient version or in contract right maybe one times faster than evm uh by benchmarking the basic units of these four curves the runtime version is at least five times a slower than the

nikki version it's a big gap about still acceptable but benchmarking the high level group 16 verification function the gap between the runtime version and the native version reduced to only two times due to the mixing of additional calculations in ink and the actual consumer time is about 16 to 170 milliseconds which is still far less than the one second central second of the block configuration time so it's still all is also practical in the future we need to work together with web3

and the community to study how to design the runtime interface or substrate primitive to improve the executing efficiency of this basic libraries above work is our 0.1 so in 0.2 we added the support for option hooks we migrated the females equities so that it can support ink contract and music mega we named this project as zoo patrick which has also been released through the perfect developers can easily do operations such as compile setup compute witness generate proof and

export verifier just like the equities our plan for 0.3 was to develop a sample of the quest transfer application based on the key mega and zero project but don't have time yet so uh for anything else helpful for zika uh watson contract we will we are happy to embrace it here are some links about our design and source code and the report we will share it in our groups so and if you go to our website you can find more products related with waxing contract development

so uh it's also very useful for zika development thank you