Keys/Hashes Opcodes for Update
Motivation
The next opcode which is necessary in order to build Crown Platform registration infrastructure is an update opcode: OP_REG_UPDATE.
It can be used to update name, or/and data, or/and hash (if it’s not an address) of the registered entity. Verify/approve changes of the registered and verified entity.
Feature Definition
- Implementation of OP_REG_UPDATE opcode and ability to process it by Crown Core software
- JSON RPC commands to update existing entities
- REST API for update existing entities
Requirements
Opcode: <Owner Address(es)> OP_REG_UPDATE(hash/address, name, data)
Workflow Rules: 1 of OP_REG_NEW | OP_REG_VERIFY | OP_REG_UPDATE | OP_REG_DUP → OP_REG_UPDATE → 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
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information