Skip to content

docs(spark): clarify Spark signature cost per operation #754

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cylon56 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(spark): clarify Spark signature cost per operation #754

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions features/networks/spark.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,16 @@ Turnkey supports every Spark wallet operation. For a runnable walkthrough of eac
| Static deposit | Bitcoin L1 → Spark (reusable address) | `CREATE_WALLET_ACCOUNTS`, `EXPORT_WALLET_ACCOUNT`, `SIGN_TRANSACTION` |
| Token transfer | Spark token operations (mint, transfer) | `SIGN_RAW_PAYLOAD` |

<Note>
Unlike most networks, one Spark action needs more than one wallet signature.
The enclave does not call the Spark Operators. Your client sends each FROST
step. Thus a send needs 2 signatures. A claim or a withdrawal needs 3. A leaf
split adds more signatures. A read also needs a signature, because Turnkey
signs with your identity key to get the data from the Operators. Calculate the
cost for each operation, not for each transfer. To control your costs, do not
read balances on a timer.
</Note>

## Security model

### Pre-signed exit transactions must be secured
Expand Down