Key/Hashes Opcode for Verification
Motivation
The next opcodes are necessary in order to build Crown Platform registration infrastructure are verification opcodes: OP_REG_VERIFY, OP_REG_DUP.
OP_REG_VERIFY: Verify/approve (by signing a new registry entry). Need to sign the registered entity by its owners. OP_REG_UPDATE also can be used to verify the entity, but the data will be duplicated in this case.
OP_REG_DUP: Can be used to duplicate previous OP_REG output in case if OP_REG tx output needs to be spent but keep the registered entity without any changes. OP_REG_UPDATE also can be used to verify the entity, but the data will be duplicated in this case.
Feature Definition
- Implementation of OP_REG_VERIFY, OP_REG_DUP opcodes and ability to process it by Crown Core software
- JSON RPC commands to verify new entities
- REST API for verifying new entities
Requirements
Opcode: <Owner Address(es)> OP_REG_VERIFY (hash/address, hash(name, data)) Workflow Rules: Inputs: 1 OP_REG_NEW on this hash → Output: OP_REG_VERIFY → Next Output: OP_REG_UPDATE | OP_REG_DUP | Unregister Entity
Opcode: <Owner Address(es)> OP_REG_DUP (hash/address, hash(name, data)) Workflow Rules: Inputs: 1 of OP_REG_NEW | OP_REG_VERIFY | OP_REG_UPDATE | OP_REG_DUP on this hash → Output: OP_REG_DUP → Next Output: OP_REG_UPDATE | OP_REG_DUP | Unregister Entity
Links/references
More details are available in the specification: https://docs.google.com/document/d/1WE9ikiSieQvyiM0iSY7hJh1h6HXIdQZJFD9jkJPW6dc/edit#bookmark=kix.jsqt9cncqfmr