BitcoinCash/chip-bcmr
1
Fork 0
Code Issues Pull Requests Releases Activity

add bitauth figure

Browse Source
This commit is contained in:
Jason Dreyzehner
2023-05-10 16:36:20 -04:00
parent bc1ae59202
commit 94430623af
2 changed files with 49 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
figures/bitauth-identities.svg
+46
View File
File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 92 KiB

readme.md
+3 -1
View File
@@ -6,7 +6,7 @@
Maintainer: Jason Dreyzehner Maintainer: Jason Dreyzehner
Status: Draft Status: Draft
Initial Publication Date: 2022-10-31 Initial Publication Date: 2022-10-31
Latest Revision Date: 2023-05-09 Latest Revision Date: 2023-05-10
Version: 2.0.0-draft Version: 2.0.0-draft
<details> <details>
@@ -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. 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 #### 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.) 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.)