The DNet owner manages the dnet's member list and the OVC resources subscription. Thus, the DNet owner needs to perform both read and write operations on the DNet records on DNetDB.
This is what's happening under the hood when running create ovc
command:
Input | Output | |
---|---|---|
TXID | Previous TXID Output Signature | 0.0001 OP_DNET_XXXX ScriptPubKey |
`OP_DNET_CREATE <ovc_id> <ovc_name>`
ĐNetDB Transaction always sends a fixed amount to self address with additional Opcodes. This becomes the base transaction for this private overlay network and all subsequent ĐNetDB CRUD operations on this ovc will use this base transaction’s UTXO as input.