OVC Record

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:

  1. Initialize - A network wide-unique <ovc_id> is generated from base58-encoded SHA256 hash value of a previous transaction ID.
  2. Pseudo Token Transaction - A Pseudo Token Transaction is created to enable the ĐNetDB Transaction.
TXIDPrevious TXID Output Signature0.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.

  1. Broadcast to whole network - the pseudo transaction is broadcast to all nodes as usual .
  2. Generate block - through mining and consensus algorithm, the record is added to the block.
  3. Creation finish - once the block becomes mature in about 2 minutes, the ovc is created and the <ovc_id> becomes available.

Edit this page on GitHub