docs(spark): clarify Spark signature cost per operation - #754
Open
cylon56 wants to merge 1 commit into
Open
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
MasterHW
approved these changes
Aug 5, 2026
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.
Spark actions require multiple wallet signatures because the enclave does not talk to the Spark Operators directly. Each FROST round is relayed by the client, so a send needs 2 signatures, and a claim or withdrawal needs 3. Reads also incur a signature, since Turnkey signs with the identity key to fetch data from the Operators.\n\nThis note sits under
## Supported operationsinfeatures/networks/spark.mdxand sets cost expectations up front so integrators size activity budgets per operation rather than per transfer, and avoid polling balances on a timer.\n\nStems from customer billing surprises surfaced by Block (a Breeze partner).