You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current work on SP1 prover binary is a part of a PR in our fork of the cdk-validium-node. However, most of our future Polygon integration work will likely be done through kurtosis-cdk and here the cdk-validium-node seems to be deprecated and split up into different components. Thus, this issue aims at moving this work from the deprecated cdk-validium-node and into our zkrollup-integration repository to be aligned with the approach of kurtosis-cdk.
Context: It is currently unclear exactly how the Aggregator is setup to communicate with the prover (in the context of the kurtosis-cdk). Mainly because the code of the image responsible for running the Aggregator in the kurtosis-cdk is not public yet. However, we can still do the initial work of introducing a Rust binary in the zkrollup-integration repository and introduce the necessary logic when more information is available.
The text was updated successfully, but these errors were encountered:
Current work on SP1 prover binary is a part of a PR in our fork of the cdk-validium-node. However, most of our future Polygon integration work will likely be done through kurtosis-cdk and here the cdk-validium-node seems to be deprecated and split up into different components. Thus, this issue aims at moving this work from the deprecated cdk-validium-node and into our zkrollup-integration repository to be aligned with the approach of kurtosis-cdk.
Context: It is currently unclear exactly how the Aggregator is setup to communicate with the prover (in the context of the kurtosis-cdk). Mainly because the code of the image responsible for running the Aggregator in the kurtosis-cdk is not public yet. However, we can still do the initial work of introducing a Rust binary in the zkrollup-integration repository and introduce the necessary logic when more information is available.
The text was updated successfully, but these errors were encountered: