ZK Rollups as Parachains

OliverTY · April 5, 2023, 11:27am

There is an ongoing effort to have host functions for ZK integration here from @achim

github.com/paritytech/substrate

arkworks integration

paritytech:master ← paritytech:achimcc/arkworks-integration

opened 06:29PM - 29 Dec 22 UTC

achimcc

+1279 -40

- What does it do? [Arkworks](http://arkworks.rs/) integration into Substrate…. We provide Elliptic curves (bls12_381, bls12_377, ed_on_bls12_381, ed_on_bls12_77, bw6_761), were we replace the compute intense operations by host function calls in Substrate. We add those host function calls to `sp_io::elliptic_curves` and refer to the `arkworks` crate. The curves live in https://github.com/paritytech/ark-substrate) and call into the host functions. To avoid point preparation of the elliptic curves in the runtime, we also partially fork the models `bls12` and `bw6` in [ark-substrate](https://github.com/paritytech/ark-substrate). - What important points should reviewers know? This is using the https://github.com/paritytech/ark-substrate repo which contains the curve and model code. ~~We cover tests in the `arkworks-curves` crate by usage of the arwkorks algebra test-templates.~~ Tests are now covered by pulling in https://github.com/paritytech/ark-substrate where we implement the arkworks curves which receive the sp-io host function implementations by dependency injection. We can re-use the arkworks-rs algebra [test-templates](https://github.com/arkworks-rs/algebra/tree/master/test-templates) for testing. An overview and comparison of benchmark results can be found [here](https://github.com/achimcc/substrate-arkworks-examples/blob/main/benchmarks-comparison.md). - Is there something left for follow-up PRs? It might be possible to avoid forking the models. Adding more curves and replacing more operations by host function calls would be further possible optimisations. - [x] **Labels:** You labeled the PR appropriately if you have permissions to do so: - [x] `A*` for PR status (**one required**) - [x] `B*` for changelog (**one required**) - [x] `C*` for release notes (**exactly one required**) - [x] `D*` for various implications/requirements - [x] Github project assignment - [x] **Related Issues:** You mentioned a related issue if this PR is related to it, e.g. `Fixes #228` or `Related #1337`. - [x] **2 Reviewers:** You asked at least two reviewers to review. If you aren't sure, start with GH suggestions. - [ ] **Style Guide:** Your PR adheres to [the style guide](https://github.com/paritytech/substrate/blob/master/docs/STYLE_GUIDE.md) - In particular, mind the maximal line length of 100 (120 in exceptional circumstances). - There is no commented code checked in unless necessary. - Any panickers in the runtime have a proof or were removed. - [x] **Runtime Version:** You bumped the runtime version if there are breaking changes in the **runtime**. - [ ] **Docs:** You updated any rustdocs which may need to change. - [ ] **Polkadot Companion:** Has the PR altered the external API or interfaces used by Polkadot? - [ ] If so, do you have the corresponding Polkadot PR ready? - [ ] Optionally: Do you have a corresponding Cumulus PR?

I dont know how it will be used though.

Topic		Replies	Views
Data Availability as a Service Tech Talk	6	1368	April 20, 2023
Rollup vs Parachain Tech Talk	7	2571	December 31, 2023
Scaling a Polkadot EVM parachain Tech Talk evm	6	995	October 30, 2023
JAM Services and related system chains Tech Talk	9	362	September 28, 2024
Elastic Scaling Tech Talk	14	855	April 13, 2024

ZK Rollups as Parachains

Related topics