From 92d3b24f5a31a1cab8b398ff729b6528dd36e9f2 Mon Sep 17 00:00:00 2001 From: Michael Lewellen Date: Tue, 4 Aug 2026 16:11:21 -0400 Subject: [PATCH] docs(spark): note multiple signatures per action and read signing cost --- features/networks/spark.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/features/networks/spark.mdx b/features/networks/spark.mdx index 3c528fe7..2c6678a9 100644 --- a/features/networks/spark.mdx +++ b/features/networks/spark.mdx @@ -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` | + + 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. + + ## Security model ### Pre-signed exit transactions must be secured