dexX7

Current block: 748990
Activation target 1: 755000 ( 6010 blocks, ~41 days from now)
Activation target 2: 757500 ( 8510 blocks, ~59 days from now)
Activation target 3: 760000 (11010 blocks, ~76 days from now)
Emergency target: 765000 (16010 blocks, ~111 days from now)

UTXO

In the following example the transaction format of:

A Class C send-to-many transaction with seven receivers
A Class B send-to-many transaction with eight receivers
A Class B send-to-many transaction with 221 receivers

STM with 7 receivers

omni_gettransaction "7f37af450deb8fbaa3095736d56eac586401ea213e19ae268072ee972286ddb2"

Send-to-Many transactions

A new transaction structure allows to include multiple transfers in one transaction.

The payload of this new transaction type includes one token identifier, which defines the tokens to send. It also includes a list of receiver -> amount mappings to specify, which receiver receives how many tokens. Receivers are specified by actual Bitcoin transaction outputs, which are referenced in the payload. One or more receivers can be defined.

The new transaction type has 7 as identifier.

The payload structure may look like this:

Current block: 708290
Activation target: 711500 (~22 days from now)
Emergency target: 715500 (~50 days from now)

UTXO

{"txid":"379d513464362882ef321593c66691a433702347c17e6cca922c76ee9d1f48d9","vout":1,"scriptPubKey":"a914167e39ef2efa6612405c9175c5a37a2af1c8cef287","value":0.0005}
{"txid":"379d513464362882ef321593c66691a433702347c17e6cca922c76ee9d1f48d9","vout":2,"scriptPubKey":"a914167e39ef2efa6612405c9175c5a37a2af1c8cef287","value":0.0005}

Current block: 694159
Activation target: 698250 (~28 days from now)
Emergency target: 702250 (~56 days from now)

UTXO

{"txid":"3834588ade30f3fe340d1f79ce0ef22e441ab27bcd1a78facc3d483702abd04a","vout":0,"scriptPubKey":"a914167e39ef2efa6612405c9175c5a37a2af1c8cef287","value":0.00025000}
{"txid":"3834588ade30f3fe340d1f79ce0ef22e441ab27bcd1a78facc3d483702abd04a","vout":1,"scriptPubKey":"a914167e39ef2efa6612405c9175c5a37a2af1c8cef287","value":0.00025000}

  OLE: XXX
  Layer: Protocol
  Title: Delegated Issuance
  Author: dexx ([email protected])
  Comments-Summary: No comments yet.
  Comments-URI: https://github.com/OmniLayer/Documentation/blob/master/OLEs/ole-XXX.adoc
  Status: Draft
  Type: Informational
  Created: 2021-04-20

UTXO

{"txid":"379d513464362882ef321593c66691a433702347c17e6cca922c76ee9d1f48d9","vout":0,"scriptPubKey":"a914167e39ef2efa6612405c9175c5a37a2af1c8cef287","value":0.0005}
{"txid":"379d513464362882ef321593c66691a433702347c17e6cca922c76ee9d1f48d9","vout":1,"scriptPubKey":"a914167e39ef2efa6612405c9175c5a37a2af1c8cef287","value":0.0005}

Feature Id: 15 (fast signing)

Before updating to Omni Core v0.4.0, you can manually perform a database consistency check.

If any of the following commands fails to return transaction data or retuns a generic error output, there is a database inconsistency:

omnicore-cli omni_gettransaction b7c66175a99ca0e7b1691905d50a46165adb7a8012d9ec5e1ecf8239f859df6d
omnicore-cli omni_gettransaction a59ac18eda590dfe9f3671f99f3cec5679e95ea4d1478d5313e2b4706307537b
omnicore-cli omni_gettransaction ce56ee84abd20bd1386d66e5ab9e3661a9bfad45a7d46490cae2241bbebf91df
omnicore-cli omni_gettransaction bbdb911227c033697e92d6828d43b15f99bbc24c97147be0aed12dd98f362c28
omnicore-cli omni_gettransaction 69604c02f219136245d309b722816d6f4f77ccead60ded6976219f9a0becceff

	<!DOCTYPE html>
	<!-- Last Published: Tue Nov 14 2017 19:16:27 GMT+0000 (UTC) -->
	<html data-wf-page="59f91ec83b328600018322cf" data-wf-site="59eb25c5e8bbc50001a454b7">
	<head>
	<meta charset="utf-8">
	<title>Omni Layer: Download</title>
	<meta content="Download" property="og:title">
	<meta content="width=device-width, initial-scale=1" name="viewport">
	<link href="css/normalize.css" rel="stylesheet" type="text/css">
	<link href="css/components.css" rel="stylesheet" type="text/css">

	#!/usr/bin/env bash

	export LC_ALL=C

	# Get BUILDDIR
	CURDIR=$(cd $(dirname "$0") \|\| exit; pwd)
	# shellcheck source=/dev/null
	. "${CURDIR}/../config.ini"

	if [ -z "$BUILDDIR" ]; then