Lit Protocol vs Turnkey

Confirmed in SDK source

The reviewed TypeScript verify() checks signatures and proof linkage, but does not check expected enclave measurements or a trusted manifest. Its own warning says another AWS account’s enclave can pass. verifyWithQosPolicy() adds measurement and manifest allowlists. An integration using only the basic helper has a narrower guarantee; this is not evidence that Turnkey’s production signing authorization can be bypassed.[12]

Published configuration + architectural inference

The published 2026.9.0 signer manifest specifies 2-of-11 manifest approvers and 3-of-10 secret-share holders. These are separate controls, not a single wallet-signing quorum. Key forwarding validates release approvals and an attested destination instead of collecting fresh operator shares. Consequently, assess compromise of the release-approval threshold together with access to the permitted AWS environment; counting secret shares alone overstates the upgrade barrier.[5][13]

Documented failure condition

QuorumOS explicitly records a rotation hazard: an old enclave still trusting compromised manifest approvers can provision another enclave they approve. Forwarding also enforces namespace, version, attestation, and AWS-role checks. The missing guarantee is automatic fleet-wide revocation: containment depends on retiring old instances. We have not established that this condition exists in Turnkey’s live deployment.[10][13]

Unresolved production parameter

The whitepaper describes timestamped notarizations and Merkle proofs to reject stale organization data. It does not specify the production freshness window there. To establish revocation speed, request that bound and evidence that previously valid state cannot authorize a request after a credential or policy change. The published design alone does not establish immediate revocation or prove an exploitable rollback.[14]

Integration responsibility

An App Proof attests to a typed claim from measured code. The consuming application must check its meaning: the intended organization, request, state, and result. It must also choose trusted measurements independently. A valid proof is not proof that every operation was disclosed, that the code is correct, or that an operator-approved upgrade was acceptable to the customer.[15]

Documented dependency

Turnkey documents replicated data and offline backups for its service secrets. Its export design involves the Signer enclave. Those are useful mechanisms, but the cited recovery page does not establish a customer-operated exit during a prolonged provider outage. Confirm an independently usable recovery arrangement if provider-independent availability is required.[16][14]