docs: note the privacy boundary of remote / delegated proving - #370
Open
kutluhaneth46 wants to merge 1 commit into
Open
docs: note the privacy boundary of remote / delegated proving#370kutluhaneth46 wants to merge 1 commit into
kutluhaneth46 wants to merge 1 commit into
Conversation
Remote provers receive transaction witness data (serialized inputs), not just a digest. Call that out on the web-client setup/transactions pages, the network tools overview, and the delegated-proving FAQ answer.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remote / delegated proving is documented mainly as a performance option today. These pages now also state the trust trade-off: the prover receives the transaction witness (serialized transaction inputs), which can include private account / note / advice data.
Updated:
docs/builder/tools/clients/web-client/setup.mddocs/builder/tools/clients/web-client/transactions.mddocs/builder/tools/network.mddocs/builder/faq.mdFixes #360
Test plan
RemoteTransactionProver/TransactionInputsbehavior described in the issue