CKB Pulse

All lessons · CCC (TypeScript SDK) · Start here · Glossary

Building a remote CCC signer by extending SignerCkbPublicKeyWorkingFrom one fix

From one fix · Check: partly right · Checked 2026-11-19

To expose a remote secp256k1 key as a CCC signer, extend ccc.SignerCkbPublicKey(client, publicKey) and override signOnlyTransaction and signMessageRaw to call the backend. The address and lock come from the public key, and signMessageRaw must sign in the "Nervos Message:" format so signMessage and verifyMessage keep working. SignerCkbPublicKey also reports anyone-can-pay addresses of the key, whose cells a backend that only signs the secp256k1 lock cannot spend, so override getAddressObjs to return only the lock you can sign (ckb-keyway had to do this later).

Why it matters: If signMessageRaw signs in any other format, signatures from the remote signer fail CCC's verifyMessage even though the key is correct.

Concepts
Witnesses and signatures
Evidence
From one fix: from one project, checked against its commit
First seen
2026-10-12
Last changed
2026-10-12
Last checked
2026-11-19
Check against the commit
partly right: a true core, with a part that is loose or too wide

Sources (1)

More about CCC (TypeScript SDK)

All 33 in this topic

Do you maintain a project this lesson came from? Confirm or correct it

Cite this lesson
LusoCryptoLabs, "Building a remote CCC signer by extending SignerCkbPublicKey", CKB lessons, https://pulse.lusocryptolabs.com/learned/ccc/building-a-remote-ccc-signer-by-extending-signerckbpublickey, CC BY 4.0, last changed 2026-10-12.

Drawn from public commits and checked against the commit each one came from and the project's code today. Read the source before you rely on one. Text under CC BY 4.0: credit LusoCryptoLabs, CKB lessons, with a link to the lesson. Want a lesson changed or removed? Open an issue.