LNP-BP / LNP-BP/presentations

What is the approach of RGB architecture?

Open
#12 0 comments 0 reactions 1 assignee View on GitHub

@UkolovaOlga is already working on this.

Since May 12, 2020.

documentation FAQ
Dominant language
No language data
Stars
62
Forks
9
PR merge metrics
No merged PRs in 30d

Description

### RGB uses paradigm-based approach:
* Layer isolation via abstraction
* Layer interaction via strictly-defined interfaces
* No future hardforks, just a single release

### Common development/coding architecture paradigms used for RGB:
* Strict encoding: LNPBP-6
* Single-use seals: LNPBP-7
* Cryptographic commitments: LNPBP-8
* Client-side verification: LNPBP-9
Paradigms descriptions can be found in 
GitHub [here](https://github.com/LNP-BP/rust-lnpbp/tree/refactor-structure/src/paradigms)

### RGB applies these general paradigms to Bitcoin transaction graph
* Single-use seals: transaction output-based seals (LNPBP-10; lnpbp::bp::txo_seals)
* Strict encoding: RGB consensus encoding (LNPBP-11; lnpbp::rgb::*)
* Cryptographic commitments:
- deterministic bitcoin commitments (LNPBP-1, -2, -3; lnpbp::bp::dbc)
- multi-contract commitments (LNPBP-4; lnpbp::lnpbps::lnpbp4)
* Client-side verification:
- RGB schema (LNPBP-12; lnpbp::rgb::schema)
- RGB contracts 
(LNPBP-13; lnpbp::rgb::{transition, stash, ancor, consignment})

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.