Skip to content

Commit

Permalink
developer glossary
Browse files Browse the repository at this point in the history
  • Loading branch information
dr-orlovsky committed Sep 2, 2024
1 parent bc92117 commit 0ce6bdf
Show file tree
Hide file tree
Showing 3 changed files with 47 additions and 6 deletions.
43 changes: 43 additions & 0 deletions content/glossary/dev.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
+++
description = "Glossary of developer terms used in RGB smart contracts"
layout = "contents"
permalink = "/glossary/dev"
+++

Terms not listed in user section:

- Transition bundle
- Asset tag
- Blinding factor
- Allocation
- Blind UTXO
- Secret seal
- Opid

- Owned state
- Public state
- Data types
- Metadata
- Valency
- Redeem

- Blank transition
- Rights split transition
- Consensus ordering

- Fascia
- Batch

- Type library
- Script library
- Contractum
- RGB assembly

---

RGB evolution

- LNP/BP standards
- RGB proposals
- Push-packs
- Fast-forwards
3 changes: 1 addition & 2 deletions content/glossary/user/assignment.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
+++
description = "Combination of state (data) with single-use seal definition"
layout = "page"
permalink = "/glossary/user/assignment"
+++

Expand Down Expand Up @@ -47,7 +46,7 @@ act as operation outputs -- similar to the role of bitcoin transaction outputs.
use the term <em>assigned</em> instead.</p>
</aside>

You won't meet assignments directly when working with RGB: they are hidden deep inside [RGB Core library](rgb-core-library).
You won't meet assignments directly when working with RGB: they are hidden deep inside [RGB Core library](rgb-libs#core).
The only place where RGB user can face them is terminologically: when someone talks about client-side validation,
the right way to say is that some data or a state is _assigned_ by a user (i.e. _client_) to a public single-use seal
definitions and validated in that way.
7 changes: 3 additions & 4 deletions content/glossary/user/consignment.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
+++
description = "Consignment is data package exchanged between users of RGB smart contracts"
layout = "page"
permalink = "/glossary/user/consignment"
+++

Expand Down Expand Up @@ -41,9 +40,9 @@ There are two main types of consignments: _contract_ and _transfer_.
some specific RGB contract. They are usually distributed by the contract issuers, but may also be downloaded from asset
or contract registries and explorers (like <https://rgbex.io>), or sent peer-to-peer, from a user to a user.

<a name="transfer"><dfn>Transfer consignments</dfn></a> are used by contract clients for [state transfers](state-transfer)
from one user to another. For instance, when a payment is made, the sender of the payment must provide the beneficiary
with a transfer consignment.
<a name="transfer"><dfn>Transfer consignments</dfn></a> are used by contract clients for
[state transfers](rgb-payment#state-transfer) from one user to another. For instance, when a payment is made, the sender
of the payment must provide the beneficiary with a transfer consignment.


## How do consignments look like?
Expand Down

0 comments on commit 0ce6bdf

Please sign in to comment.