CKB Pulse

All lessons · Wallets and signing · Start here · Glossary

EVM owners may hold Omnilock lock args with auth flag 0x12, not only 0x01WorkingFrom one fix

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

When mapping an Ethereum address to the CKB lock scripts it controls, match Omnilock args 0x12 || addr20 || 0x00 (Ethereum displaying, used by CCC's EVM signer for new addresses) as well as 0x01 || addr20 || 0x00 and PW Lock args = addr20. Otherwise deposits held by CCC created EVM addresses are not recognised. The commit notes this is still pending confirmation in a wallet proof of concept.

Why it matters: Without the 0x12 form, an EVM signature from a user whose deposit sits under a CCC-created Omnilock address fails the owner-lock match and is rejected, so that deposit is never counted.

Pattern

Prefer
v.push(omni.with_args(omni_args(OMNILOCK_AUTH_ETHEREUM_DISPLAYING)));

Taken from the commit, shortened.

A test changed in the same commit

It sits next to the fix. We did not run it.

Concepts
Witnesses and signatures, Login and authorization
Evidence
From one fix: from one project, checked against its commit
First seen
2026-10-08
Last changed
2026-10-08
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)

More about Wallets and signing

All 23 in this topic

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

Cite this lesson
LusoCryptoLabs, "EVM owners may hold Omnilock lock args with auth flag 0x12, not only 0x01", CKB lessons, https://pulse.lusocryptolabs.com/learned/wallets/evm-owners-may-hold-omnilock-lock-args-with-auth-flag-0x12-n, CC BY 4.0, last changed 2026-10-08.

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.