Skip to content
This repository was archived by the owner on Feb 17, 2025. It is now read-only.

WIP 15 docs Endpoint page #121

Draft
wants to merge 3 commits into
base: 00-gitbook-docs
Choose a base branch
from
Draft

Conversation

alexandra-mara
Copy link

@alexandra-mara alexandra-mara commented Oct 26, 2023

@alexandra-mara alexandra-mara self-assigned this Oct 26, 2023
@alexandra-mara alexandra-mara force-pushed the verifier-docs branch 2 times, most recently from 863f282 to 027a019 Compare October 26, 2023 14:16
part of NilFoundation/devrel#15
Base automatically changed from verifier-docs to 00-gitbook-docs October 30, 2023 07:19
It enables several crucial operations:
* Requesting zkProofs: EVM applications can directly request zero-knowledge proofs for specific computations.
* Payment Facilitation: Payment for proof producers can be facilitated directly through Ethereum, streamlining the payment process.
* Proof Verification: The Ethereum Endpoint acts as an additional verifier in the proof generation pipeline, ensuring the validity of incoming proofs.
Copy link
Contributor

@NickVolynkin NickVolynkin Oct 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may be the Ethereum endpoint for us because we only have one. But for the Eth devs, so many things are Eth endpoints.

Why is it an additional verifier? I can't imagine someone doing the in-EVM verification twice because it's expensive.

I think so much capitalization is unnecessary. But we can discuss it. :)

Suggested change
* Proof Verification: The Ethereum Endpoint acts as an additional verifier in the proof generation pipeline, ensuring the validity of incoming proofs.
* Proof verification: the Proof Market Endpoint acts as an additional verifier in the proof generation pipeline, ensuring the validity of incoming proofs.

The Ethereum Endpoint acts as a gateway interface facilitating communication between EVM applications and Proof Market.
It enables several crucial operations:
* Requesting zkProofs: EVM applications can directly request zero-knowledge proofs for specific computations.
* Payment Facilitation: Payment for proof producers can be facilitated directly through Ethereum, streamlining the payment process.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should use a different word for the proof producer rewards. Asked folks in Slack.

Comment on lines +11 to +14
It's important to note that the Ethereum Endpoint only stores verification keys for the statements that require proof.
Due to Ethereum's limitations in storing large data chunks, this approach proves to be more economically advantageous.
Application developers should note that they need a one-time setup to upload their circuit to the original Proof Market.
Currently, Proof Market works with the Placeholder Proof System, but support for other proof systems can be requested.
Copy link
Contributor

@NickVolynkin NickVolynkin Oct 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is a verification key? What's a statement? These terms were not introduced.

Only verification keys and not what? The proofs themselves?

this approach proves to be more economically advantageous — as “proof” is a very specific term in this context, I would avoid using it in other meanings.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants