Skip to content

Instantly share code, notes, and snippets.

View dexX7's full-sized avatar

dexX7

View GitHub Profile
@dexX7
dexX7 / send-to-many.md
Last active October 2, 2022 17:19
New Omni Layer transaction: Send-to-Many

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:

@dexX7
dexX7 / activations_0.12.0.md
Created August 11, 2022 14:36
Activation of Send-to-Many and NFT-Send-All
  • 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

@dexX7
dexX7 / stm_examples.md
Last active April 20, 2022 08:01
Send to many transaction examples

In the following example the transaction format of:

  1. A Class C send-to-many transaction with seven receivers
  2. A Class B send-to-many transaction with eight receivers
  3. A Class B send-to-many transaction with 221 receivers

STM with 7 receivers

omni_gettransaction "7f37af450deb8fbaa3095736d56eac586401ea213e19ae268072ee972286ddb2"
@dexX7
dexX7 / leveldb_dump.py
Created November 2, 2014 23:46
Python LevelDB debug dumper
#!/usr/bin/env python
import binascii
import sys
import leveldb
def b2x(b):
"""Convert bytes to a hex string"""
if sys.version > '3':
return binascii.hexlify(b).decode('utf8')
@dexX7
dexX7 / nft_activation_0.11.0.md
Last active November 5, 2021 08:35
Activation of NFTs
  • 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}
@dexX7
dexX7 / delegation_activation_0.11.0.md
Last active August 4, 2021 12:14
Activation of delegated issuance
  • 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}
@dexX7
dexX7 / delegatedissuance.adoc
Last active April 20, 2021 13:44
OLE XXX: Delegated Issuance
  OLE: XXX
  Layer: Protocol
  Title: Delegated Issuance
  Author: dexx (dexx@bitwatch.co)
  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
<!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">
@dexX7
dexX7 / gist:b46f0fea46b9ea881142
Last active June 24, 2020 07:19
Master Core: Gitian build instructions for Windows
@dexX7
dexX7 / many-to-many.md
Last active May 28, 2020 07:46
Omni Lite

Multi-command transactions

A new transaction structure allows to include multiple commands into one transaction. This is done by including a list of commands in the transaction payload. Each command is executed one by one and may be invalid without invalidating the other commands.

The payload structure may look like this:

[transaction marker] [number of commands] [command 1] ( [command 2] [...] )