RGB system libraries represent non-applied level of RGB technology.
All RGB system libraries can be classified into the following categories:
- Consensus libraries
- Standard library
- Node-related libraries
- Schema-specific libraries
- Toolchain
The dependencies between these groups are strongly abstracted into four layers, such that underlying group doesn’t know anything about the libraries from the layer above.
Node-related and schema-scpecific libraries reside on the same level and must not depend on each other.
These libraries are a part of RGB ossified client-side-validation consensus and must not be modified except of bugfixing. Usually, consensus-level libraries are named with “Core“ or “Foundation” as a part of their name.
- Client-side-validation foudation library
- Bitcoin common libraries: implementation of parsing bitcoin data related to bitcoin consensus layer. Currently, there are split in two groups:
- Rust bitcoin ecosystem, maintained by Rust bitcoin community (mostly Blockstream members and Andrew Poelstra)
- BP Foundation Libraries, maintained by LNP/BP Standards Association, Bitcoin Protocol Working Group. Contain re-implmenetaiton or improvements of the rust-bitcoin libraries
- Bitcoin client-side-validation, also called “BP Core Lib”. It provides primitives such as deterministic bitcoin commitments (“TapRet”, ”OpRet”) and single-use-seals.
Standard library (called RGB Std Lib) provides high-level convenience API for working with RGB data, but does not performes any consensus-level tasks. Any validation and RGB operations must perform without standard library, which enables use of RGB smart contract on embedded devices.
| GitHub Org | Controlled by | Main maintainers |
|---|---|---|
| bitcoin-core | Bitcoin Core | Peter Wuille |
| rust-bitcoin | Blockstream | Andrew Poelstra |
| rust-amplify | Pandora Prime | Maxim Orlovsky |
| Strict-Encoding | LNP/BP Association [^1] | Maxim Orlovsky |
| AluVM | LNP/BP Association [^1] | Maxim Orlovsky |
| LNP-BP | LNP/BP Association | Maxim Orlovsky |
| BP-WG | LNP/BP Association | Maxim Orlovsky |
| RGB-WG | LNP/BP Association | Maxim Orlovsky |
[^1]: It can be that these GitHub ogranisations will be moved to a different non-profit or a for-profit controlling body outside of the scope of LNP/BP Standards Association.
| Repo (crate) | GitHub Org | Maintained by | Description |
|---|---|---|---|
| rust-secp256k1 (secp256k1) | bitcoin-core | Bitcoin Core | |
| rust-lnpbp (lnpbp_secp256k1) | LNP-BP | LNP/BP Association | Fork of Grin re-implementation of rust-secp256k1-zkp; used for bulletproofs only |
| bitcoin_hashes | rust-bitcoin | Blockstream | |
| rust-bitcoin (bitcoin) | rust-bitcoin | Blockstream | |
| rust-amplify (amplify) | rust-amplify | Pandora Prime | |
| rust-stens (stens) | Strict-Encoding | LNP/BP Association [^1] | Data encoding used in RGB |
| rust-aluvm (aluvm) | AluVM | LNP/BP Association [^1] | Virtual machine used in RGB |
| client_side_validation | LNP-BP | LNP/BP Association | Abstract client-side-validation |
| bp-foundation | BP-WG | LNP/BP Association | Bitcoin primitives (alternative to rust-bitcoin) |
| bp-core | BP-WG | LNP/BP Association | Client-side-validation for bitcoin protocol |
| rgb-core | RGB-WG | LNP/BP Association | RGB consensus library |