From bbadae7e07216f47b455e2d59d5d2d9fca310a83 Mon Sep 17 00:00:00 2001 From: xjd Date: Fri, 26 Apr 2024 12:21:00 +0800 Subject: [PATCH] Improve description to owner lock --- rfcs/0042-omnilock/0042-omnilock.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/rfcs/0042-omnilock/0042-omnilock.md b/rfcs/0042-omnilock/0042-omnilock.md index 50c5e6fb..b1075e3c 100644 --- a/rfcs/0042-omnilock/0042-omnilock.md +++ b/rfcs/0042-omnilock/0042-omnilock.md @@ -114,9 +114,14 @@ Depending on the value of the flag, the auth content has the following interpret MultiSig](https://github.com/nervosnetwork/ckb-system-scripts/blob/master/c/secp256k1_blake160_multisig_all.c) with a little modification. When a message is calculated for signing, there is a step to clear witness. In omnilock, it clears the whole field `lock` in `witness`. But in CKB MultiSig script, it only clears part of `lock` in `witness`. This part is used as `signatures` followed by `multisig_script`. -* 0xFC: The auth content that represents the blake160 hash of a lock script. The lock script will check if the current - transaction contains an input cell with a matching lock script. Otherwise, it would return with an error. It's similar - to [P2SH in BTC](https://en.bitcoin.it/wiki/Pay_to_script_hash). +* 0xFC: The auth content represents the blake160 hash of a lock script. The + omnilock checks if the current transaction contains an input cell with a lock + script hash matching the auth content. If it is present, the validation + succeeds. In such a transaction, there should be at least 2 cells on input: + one locked by omnilock and another locked by the owner script. The owner + script's blake160 hash is the same as the auth content. In other words, the + Omnilock delegates its validation to the owner script. It's similar to [P2SH + in BTC](https://en.bitcoin.it/wiki/Pay_to_script_hash). * 0xFD: The auth content that represents the blake160 hash of a preimage. The preimage contains [exec](https://github.com/nervosnetwork/rfcs/blob/master/rfcs/0034-vm-syscalls-2/0034-vm-syscalls-2.md#exec) information that is used to delegate signature verification to