All lessons · Wallets and signing · Start here · Glossary
JoyID sub-key signing needs the COTA aggregator and CSP allowancesWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
If you strip external hosts from a CCC bundle or restrict CSP connect-src, keep CCC's COTA aggregator host (cota.nervina.dev) and allow it, because the JoyID signer calls it before signing for sub-key wallets. Also allow the RPC websocket hosts your CCC client uses, such as wss://testnet.ckb.dev.
Why it matters: With the aggregator host stripped or blocked, JoyID sub-key wallets cannot sign transactions in the app.
Low confidence: inferred from the commit message only. The diff showed just a rebuilt bundle.
- Concepts
- Witnesses and signatures, Network and RPC reliability
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-16
- Last changed
- 2026-11-16
- Last checked
- 2026-11-19
- Check against the commit
- right: the lesson follows from its commit and still holds in the code today
Sources (1)
- 2026-11-16 · psawyerberlin/ckb-revocable-timelock · more from this project
More about Wallets and signing
- JoyID sub key membership is checked through the CoTA aggregator
- JoyID sub key signatures depend on the live CoTA cell dep holding the sub key root
- Devnet tests need a real secp256k1 lock to exercise signing
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "JoyID sub-key signing needs the COTA aggregator and CSP allowances", CKB lessons, https://pulse.lusocryptolabs.com/learned/wallets/joyid-sub-key-signing-needs-the-cota-aggregator-and-csp-allo, CC BY 4.0, last changed 2026-11-16.