All lessons · Wallets and signing · Start here · Glossary
Do not detect DER signatures by a leading 0x30 byteWorkingFrom one fix
From one fix · Check: true, but the check found it more general than CKB · Checked 2026-11-19
When converting secp256k1 signatures to DER for a CKB contract (here the Perun channel script, which uses k256 and expects low-S), a 64 or 65 byte compact R||S(||V) signature can begin with 0x30 because R is arbitrary. Dispatch on the fixed lengths first, and parse anything else with a full asn1.Unmarshal that has no trailing bytes, followed by a check that R and S lie in [1, n).
Why it matters: A compact signature whose R happens to start with 0x30 (about 1 in 256) was passed through untouched as if it were DER. That produced a malformed signature in the channel witness, which the contract cannot verify.
Pattern
if len(sig) > 0 && sig[0] == 0x30 {Taken from the commit, shortened.
A test changed in the same commit
It sits next to the fix. We did not run it.
- perun-network/perun-ckb-backend:
encoding/signature_test.go
- Concepts
- Witnesses and signatures, Data encoding (molecule, hex, bigints)
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-10
- Last changed
- 2026-11-10
- Last checked
- 2026-11-19
- Check against the commit
- true, but the check found it more general than CKB
Sources (1)
- 2026-11-10 · perun-network/perun-ckb-backend · more from this project
More about Wallets and signing
- Omnilock owner signing needs an 85 byte zeroed witness lock placeholder
- Verifying Neuron style signed messages against a secp256k1_blake160 lock
- JoyID sub key membership is checked through the CoTA aggregator
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Do not detect DER signatures by a leading 0x30 byte", CKB lessons, https://pulse.lusocryptolabs.com/learned/wallets/do-not-detect-der-signatures-by-a-leading-0x30-byte, CC BY 4.0, last changed 2026-11-10.