Skip to content
Melvin Carvalho edited this page Jul 20, 2021 · 3 revisions
  BIP: 100021
  Layer: Applications
  Title: URI Scheme
  Author: Melvin Carvalho 
  Comments-Summary: No comments yet.
  Status: Draft
  Type: Informal
  Created: 2021-07-20

Abstract

This BIP proposes a URI scheme for transaction outputs

Motivation

The purpose of this URI scheme is to enable users and machines to easily identify a transaction output.

Specification

General rules for handling

General Format

txo URIs follow the general format for URIs as set forth in RFC 3986. The path component consists of a transaction hash, a delimiter, and an output, the query component is not yet specified.

Elements of the query component may contain characters outside the valid range. These must first be encoded according to UTF-8, and then each octet of the corresponding UTF-8 sequence must be percent-encoded as described in RFC 3986.

ABNF grammar

 txourn     = "txo:" txhash ":" txoutput [ "?" txoparams ]
 txhash     = *hex (64 long)
 txoutput   = *hex (up to 4 long)
 txoparams  = txoparam [ "&" txoparams ]
 txoparam   = not yet specified

The scheme component ("txo:") is case-insensitive, and implementations must accept any combination of uppercase and lowercase letters. The rest of the URI is case-sensitive, including the query parameter keys.

The chain is not currently specified, but is likely to be assumed from the context. At some point in future the chain may be specified. Supported chains are fair coins and derivatives e.g. bitcoin, litecoin, bitmark, liquid plus testnets

Forward compatibility

Backward compatibility

Appendix

Examples

Just the tx:

txo:86d7106f3a3de59ce8e4d6bcee112ebed0f78ff5318b56bd8123fe6cc4612fbe

Tx with output 0:

txo:86d7106f3a3de59ce8e4d6bcee112ebed0f78ff5318b56bd8123fe6cc4612fbe:0

Characters must be URI encoded properly.

Reference Implementations

Libraries