diff --git a/figures/bitauth-identities.svg b/figures/bitauth-identities.svg new file mode 100644 index 0000000..9b13a83 --- /dev/null +++ b/figures/bitauth-identities.svg @@ -0,0 +1,46 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/readme.md b/readme.md index 108d325..90ecded 100644 --- a/readme.md +++ b/readme.md @@ -6,7 +6,7 @@ Maintainer: Jason Dreyzehner Status: Draft Initial Publication Date: 2022-10-31 - Latest Revision Date: 2023-05-09 + Latest Revision Date: 2023-05-10 Version: 2.0.0-draft
@@ -133,6 +133,8 @@ A **zeroth-descendant transaction chain** – also known as an **authchain** The first transaction in an authchain is referred to as the **authbase transaction**; authbase transactions have no distinguishing features, and any valid transaction can serve as an authbase transaction. The final transaction in an authchain is referred to as the **authhead transaction**. By definition, the identity output of the authhead transaction is unspent. +![Bitauth Identities on Bitcoin Cash](./figures/bitauth-identities.svg) + #### Authchain Resolution To resolve an authchain (a [zeroth-descendant transaction chain](#zeroth-descendant-transaction-chains)), clients must recursively identify the transaction that spent the output at index `0` of the current transaction, beginning with the authbase transaction. (Note, this process can be [accelerated using data from `authchain` extensions](#authchain-extension) in registries.)