| description |
|---|
Terminology used in RGB sorted in alphabetical order |
Set of client-side data that proves the inclusion of a unique commitment inside a transaction. In RGB protocol it is constituted by:
- The Bitcoin transaction ID of the witness transaction.
- The Multi Protocol Commitment - MPC.
- The Deterministic Bitcoin Commitment - DBC.
- The ETP in the case of Tapret commitment scheme.
Acronym of Algorithmic logic unit Virtual Machine, it is a register-based virtual machine for smart contract validation and distributed computing, used but not limited to RGB contract validation.
The RGB-equivalent of a transaction output modifying, updating or creating some properties of the state of a contract. It is formed by:
The set of operations and rules contained in a contract Schema which allows for the rightful update of the contract state.
The operation which allows the verification of some data exchanged between parties according to some defined protocol rules. In RGB protocol these data are in form of consignment; the above data can be exchanged privately between the parties involved as, unlike Bitcoin protocol, they don't need to be registered on a public medium (e.g. the blockchain).
A defined mathematical object
-
Commit operation, which takes as inputs a public message
$$m$$ and a random value$$r$$ , and by applying to them the chosen cryptographic algorithm returns a value$$C = \text{commit}(m, r)$$ . -
Verify operation, which takes the value returned by the commit algorithm
$$C$$ , the public message$$m$$ and the secret value$$r$$ and returns True/False.$$\text{verify}(m, r, com) \rightarrow (\text{True} / \text{False})$$ .
The commitment is required to possess two fundamental security properties:
-
Binding: requires that there cannot be two valid messages of the same commitment
$$C$$ . That is, it is computationally unfeasible to produce different$$m' : | : m' \neq m$$ and$$r' : | : r' \neq r$$ such that:$$\text{verify}(m,r,C)=\text{verify}(m',r',C) \rightarrow \text{True}$$ -
Hiding: requires that the message
$$m$$ cannot be easily discovered by commitment attempts, i.e., that$$r$$ be uniformly sampled in a set$$R$$ such that it is statistically independent of$$m$$ .
The data transferred between parties that are subject to client-side validation. In RGB there are 2 types of consignment:
- Contract Consignment: provided by the contract issuer including the information about the contract setup, such as the Schema, the Genesis, the Interface, and the Interface Implementation.
- Transfer Consignment: provided by the payer user party and containing all the state transition history up to the terminal consignment.
A set of rights established and executed digitally between certain parties through RGB protocol. A contract possesses an active state and business logic, expressed in terms of ownership rights and executive rights. The contract state, rights and conditions of valid operations are defined using RGB schema. Only state and operations which allowed by the schema declarations and validation scripts are allowed to happen within the contract scope.
An update to the contract state performed according to the rules defined in the contract schema.
Contract operations include:
An actor who participates in contract operations. Contract parties are classified into the following categories:
- Contract issuer: an actor creating contract Genesis.
- Contract party: all actors who have some ownership rights over RGB contract state which have been provided through an Assignment.
- Public party: an actor who is able to construct State Extensions. Can exist only in contracts providing Valencies to be redeemed by State Extension.
RGB contract parties have different rights as a part of the contract conditions defined through RGB Schema. The rights under RGB contracts can be classified into the following categories:
- Ownership rights: the rights associated with the ownership of some UTXO referenced by a Seal Definition.
- Executive rights: the ability to construct the contract state in a final form, i.e. to construct a valid state transition satisfying schema validation rules.
- Public rights: a right under some Schema to use a contract Valency and construct a valid State Extension.
The set of up-to-date, private, and public information that manifests the condition of a contract at a certain point in history. In RGB, the contract state is constituted by:
The set of rules which allows for the registration of a provably single commitment in a Bitcoin transaction. Specifically, RGB protocol embeds 2 forms of DBC:
A directed graph that does not contain any directed cycle thus allowing topological ordering. A Blockchain or an RGB Contract Shard are examples of DAG.
An optional data string that past owners of a contract can register in the contract history. It is implemented in the RGB21 interface.
The part of the Anchor that embeds the additional data necessary for the validation of Tapret commitment contained in a taproot transaction, such as the internal PubKey and the Script Path Spend.
The set of data, regulated by a contract schema, which represents the starting state of every contract of RGB. It's the equivalent of Bitcoin Genesis Block at the client-side level.
The set of code instructions that allow for the parsing of the compiled binary data contained in Schema, Contract Operation, and States in user and wallet-readable information.
The set of code declarations that bind an Interface to a Schema and make possible the semantic translation operated by the Interface itself.
A base58 URL-encoded string embedding the necessary data in order to allow a payer counterpart to construct a State Transition.
The set of public properties included in the state of a contract, defined in Genesis and optionally updatable according to the rule defined therein, which are not owned by any party.
A decentralized network of bidirectional payment (state) channels constituted by 2-of-2 mutisig wallet constructing and updating off-chain transactions. It represents a popular Bitcoin Layer 2 scaling solution.
The Merkle Tree structure used in RGB to include in a single Bitcoin Blockchain commitment the multiple Transition Bundles of different contracts.
Part of the state of a contract enclosed into an Assignment that contains the definition of the digital property being subjected to someone's ownership.
The control and thus the possibility to spend a UTXO to which some client-side property isthat assigned.
A transaction which lacks some element of its signature and which can be completed/finalized with some additional elements later in time.
A particular type of cryptographic commitment characterized by the homomorphic property with respect to the addition operation. This means that given a certain
So it is possible to verify the total sum without revealing the individual values. This operation, for example, becomes useful to conceal the amounts of tokens transacted.
A construct present in State Extension which references a previously-declared Valency.
A declarative piece of code that contains the set of variables, rules, and business logic according to which an RGB contract works.
The reference part of an Assignment which binds the commitment to a UTXO belonging to the new owner.
A branch of the DAG chain of the RGB State Transitions.
A promise to commit to a yet unknown message in the future, once and only once, such that commitment fact will be provably known to all members of a certain audience.
The set of client-side data related to one or more contracts that undergo validation and are stored by the users.
A contract operation that allows for the redeeming of some Valencies. It needs to be closed by a State Transition in order to put in effect the changes to the contract expressed by the Valencies.
The most important contract operation that makes possible the transition of an RGB State to a New State, changing state data and/or ownership.
The Bitcoin's Segwit v1 transaction format detailed in BIP341 and BIP342.
A transfer consignment that includes the last state of a contract embedding the State Transition constructed from a payee counterparty invoice.
A set of RGB State Transitions that belong to the same contract and that are committed in the same witness transaction.
A Bitcoin Unspent Transaction Output. It is defined by a transaction hash and a vout index which, collectively, constitute an outpoint.
A public right having no state but which can be referenced and redeemed through a state extension.
The transaction that provides the Seal closing operation around a message that contains a Multi Protocol Commitment an MPC Tree.