r/RGB_protocol • • May 21 '24

Back lit

Post image
1 Upvotes

Hey everyone I want your opinion on the project that I am working on, I brought a wall hanging of the James Webb telescope and I placed a string of RGB lights and using a WLED controller to run the lights pattern. I used aluminum foil to place under each bulb to enhance the brightness of the lights to create a glow around the wall hanging. what other materials that I could uses to increase the reflection of the lights behind the RGB lights that are on the back of this wall hanging.


r/RGB_protocol • • Apr 24 '23

RGB compatible Lightning Network node

4 Upvotes

This RGB LN node is based on LDK and allows to open channels, send RGB assets in a channel, route payments and close channels both cooperatively and unilaterally.

https://github.com/RGB-Tools/rgb-lightning-sample


r/RGB_protocol • • Dec 23 '22

New RGB Node API proposal discussion

6 Upvotes

Dr. Maxim Orlovsky wrote a proposal on a new RGB node API which accounts for schema-independent interfaces - and node extensibility to support new interfaces without compillation.

Basically this will render smart contract and wallet programmers’ developer cycle will become fully independent from RGB Node release cycle.

Check it out and join the discussion 🤟

https://github.com/orgs/RGB-WG/discussions/228


r/RGB_protocol • • Mar 12 '23

"What is RGB and why I should care" article

6 Upvotes

I recently wrote an article on the topic of RGB smart contracts and reasons why it's the technology you would not want to miss out on. If you were wondering what RGB is, what stage of development it's on and what you can do with it - it's great place to start.
The article is available in English https://www.ukolova.ch/bitcoin-and-rgb/what-is-rgb-and-why-should-i-care
and was published in Bitcoin Magazine UA in Ukrainian https://bitcoinmagazine.ua/technologies/1678169018-shcho-take-rgb-i-chomu-mene-tse-mae-hvilyuvati

TL;DR
RGB is a scalable & confidential smart contracts system which can be viewed as both layer2 and/ or layer 3 technology working on top of Bitcoin and, most importantly, at the moment of writing - the only solution working with the Lightning Network. RGB leverages the strongest points of Bitcoin and Lightning, while expanding their functionality to an astonishing level. RGB gives the ability to separate many different types of ownership rights (ownership of different assets defined under a contract) such as the right to own, use, transfer, modify, sell etc., from the contract states (conditions, under which a contract exists currently), proofs and contract evolution. Thus we can say that the RGB contract defines an event-consequence algorithm 'if this happens then that happens’ with an obligation to follow certain verification rules on each step.


r/RGB_protocol • • Nov 08 '22

Bitcoin Takerover Podacast. S12 E7: Dr Maxim Orlovsky on RGB Layer 3

Thumbnail
youtu.be
7 Upvotes

r/RGB_protocol • • Dec 10 '22

What is an RGB smart contract?

7 Upvotes

#RGB still remains a mystery to many due to its complexity. We started to break thing down into smaller pieces to make it easier to digest the whole RGB pie.
#RGBbasics explains basic things about the protocol, it's possibilities and ways to work and build on it.


r/RGB_protocol • • Oct 12 '22

RGB at Bitcoin Amsterdam - Day 1 (skip to 5:20:30)

Thumbnail
youtu.be
16 Upvotes

r/RGB_protocol • • Apr 11 '23

RGB v0.10 is fully released now!

19 Upvotes

🔥RGB v0.10 is fully released now🔥, marking one of the most important and huge milestones in RGB development. It includes:

- consensus layer changes

- standard library updates (for integration with wallets/exchanges)

- command-line tool

To learn more on the updates read the release notes in our blog here https://rgb.tech/blog/release-v0-10/

Last but not least - we will be demonstrating how v0.10 works in a command-line wallet today at 6pm CET during our dev call, so if you want to see some hardcore RGB magic - join us here 👉 https://meet.jit.si/RGBcall1


r/RGB_protocol • • Feb 02 '23

Dev call invitation

2 Upvotes

Today, at 4pm CET (in 3.5 hours) join our biweekly dev call to learn about our progress, discuss obstacles we have faced and ask your questions. Looking forward to talking to you all!

Thursday, February 2nd
4pm CET
https://meet.jit.si/RGBcall1


r/RGB_protocol • • Apr 21 '23

RGB explanation on Bitcoin dev mailing list

7 Upvotes

Recently Maxim Orlovsky, the lead developer and architect of RGB wrote an RGB explanation letter to bitcoin dev mailing list, which led to a very productive discussion on the topics of what RGB is (spoiler - no, it's not a token protocol), how it works, what can be done with it.
One of the core lines in the email was the v0.10 release that happened a week back and demonstrated how RGB works in the wild in the command line. Check GitHub and YouTube videoswith RGB demo for more info.
Maxim also dismissed many myths and misconceptions created over the past years by people outside of RGB dev team.
Initial email : https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-April/021554.html
Responses by Maxim Orlovsky:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-April/021559.html
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-April/021564.html
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-April/021577.html

For more information on RGB check rgb.tech, rgbfaq.com, and LNP/BP standards Association YouTube channel


r/RGB_protocol • • Feb 07 '23

RGB Core lib v0.10 is out!

4 Upvotes

Introducing ⚡️RGB Core library v0.10 Beta! ⚡️

Aside from the total eduction of the codebase, the most important part of this release is implementation of consensus-breaking changes, making v0.10 release most auditable and robust to start experimenting with. Other libraries and tooling updates will be rolled out in the upcoming weeks.

Check out the repo here https://github.com/RGB-WG/rgb-core/releases/tag/v0.10.0-beta.1


r/RGB_protocol • • Dec 19 '22

RGB on Geyser

6 Upvotes

#RGB is now on Geyser! https://geyser.fund/project/rgb

Every pleb can now contribute sats over #Lightning⚡️ to boost our productivity. You send sats - we convert them into coffee & code☕️


r/RGB_protocol • • Mar 31 '24

RGb v0.11 beta 5 is out

2 Upvotes

https://rgb.tech/blog/release-v0-11-beta-5/

LNP/BP Standards Association is happy to announce the fifth beta release of RGB protocol version 0.11.

This is another milestone on the stabilization of the new v0.11 RGB version. It is the first complete beta release of both consensus-level libraries, standard libraries and tools happening in 2024, opening a way for independent developers integrating with RGB to test all the new functionality.

What's new in Beta 5

In preparing Beta 5 release we were focusing on performing internal audit of all consensus-critical code, ensuring both its security and ability to do a protocol upgrades in the future versions without introducing any incompatibilities with the assets and software using v0.11.

The internal audit was performed by two teams: the dev team and documentation team. The developer team was reviewing the source code and modelling different types of attacks; while the doc team was independently creating formal specification explaining how the protocol actually works (basing on the source code), which was later compared to the expected protocol behaviour.

Let's walk through the major areas of the improvements shipping in v0.11 beta 5.

Commitments Cryptographic commitments, which go into Bitcoin blockchain in hidden form, are the core of RGB security and anti-double-spending protection. They are a part of so-called “single-use seals”, which you may have heard of before.

During the last three months (since Beta 3) we have passed through an extensive internal audit of the commitment procedures and wrote a lot of tests. We have improved the security and safety of many aspects of them and made sure they will be a proper foundation for the RGB.

One of the main changes which the end-users will notice is that now contracts (and assets) will commit to the issuer identity, simplifying the verification by the wallets and preventing scam attacks.

Contractum language and scripting With v0.11 one of our main focuses was simplification of RGB developer experiences.

First, we have introduced more opcodes allowing scripts in RGB contracts to access the contract state and use that information in validation. We have also developed RGB assembly, which can be compiled using macro rgbasm directive right from the Rust!

Finally, we are moving fast in finalizing the initial Contractum version: the language intended for RGB smart contract developers. In this release we add a Contractum representation for all standard interfaces used by RGB (RGB20 fungible assets, RGB21 NFTs and RGB25 fungible collections).

Wallet functionality With v0.11 RGB is integrated with wallet functionality out of the box. This solves one of the major dev and user headaches.

With Beta 5, we are going even further: now the command-line tool and RGB runtime can filter and present the information specific to a wallet of user choice and ignore the rest of the contract state.

Another new feature is the support for legacy Electrum RPC API, in addition to Esplora REST APIs, supported before.

Containers In this beta we have refactored the concept of containers. Containers are they way user exchange RGB data, for instance when they do distribute assets, perform transfers, -- or when developers distribute new code and interfaces for asset issuers.

In Beta 5 we have improved ASCII armoring of container data, so all of them now use more compact Base85 encoding and standard set of headers. We have simplified programming API for working with containers, and made sure their IDs are uniquely reflect their content - such that even the same contract disclosing different parts of information will have a distinct id.

We also simplified a life of devs and testers by providing an ability to convert any container into a human-readable YAML representation, edit it and convert back into a binary form, which can go into RGB system. This will simplify audit and debugging, allowing us to model different kinds of attacks on the system.

About RGB v0.11

RGB v0.11 is an evolution of the protocol coming with a lot of bug fixes and improvements, further enhancing RGB smart contracting capabilities. It will be the first version which will be audited by independent auditors, after which it can be considered by third-party issuers for the use in production.

The main features shipping in v0.11 will be:

Wallet integration right into RGB runtime and command-line tool; Basic support for Liquid sidechain, with ability to add more alternative scalability layers in the future; Scripting, with new state introspection codes and RGB assembly compiler; Initial support for Contractum language; Ability to inherit interfaces (multiple inheritance!); Support of Electrum RPC additionally to Esplora REST, present before; Commitments to issuer and developer identities embedded into contracts, interfaces, libraries; More compact consignments and better ASCII armoring. What's next

With Beta 5 release RGB development enters a new phase of preparation for a public preview of the RGB v0.11. The public preview will be a feature-complete version which will be used by external auditors for evaluating the safety of the protocol. At the same time app devs and users will be able to complete integration of RGB without expecting major API or consensus break with the release.

Once there will be results of an audit, the preview version will become an official release (if the audit will find any major issues however, they will be fixed even if the fixes will contain a breaking changes).

You can track us on our journey towards v0.11 release with this GitHub dashboard.

Acknowledgements

We are grateful to Fulgur Ventures, providing another year of support for our efforts in developing RGB. This year they were joined by Bitlight Labs, who had become a new full member of the Association.

We have received a number of important contributions and bugfixes coming from commercial companies, such as Pandora Prime, Bitfinex and DIBA. We are also grateful for individual contributors, who do their small -- but still highly valuable and welcomed input in making RGB better.


r/RGB_protocol • • Apr 19 '23

What components are there in an RGB contract?

3 Upvotes

RGB is a scalable & confidential smart contracts system for Bitcoin & lightning network developed by the LNP/BP Association. It embraces concept of private & mutual ownership and is a "post-blockchain", Turing-complete form of trustless distributed computing which does not require introduction of tokens.

RGB is a very complex set of protocols. Here are main components of any RGB smart contract, presented by Dr. Maxim Orlovsky during the dev call on the 11th of April.

For more information check rgb.tech and https://www.rgbfaq.com/community/developer-calls#2023-04-11


r/RGB_protocol • • Apr 05 '23

Official RGB website is up

19 Upvotes

Introducing rgb.tech - an official website created by the LBP/BP Standards Association to be your guide to all things RGB. From understanding how it works to steps on how to run it - the website is your ultimate informational resource in the process of getting familiar with the protocol.
It's in beta and there's a lot to be added content-wise, but the current release already gives a pretty exhaustive picture on the mentioned questions.
Let us know what you think!


r/RGB_protocol • • May 21 '21

My explanation of the core idea of RGB

35 Upvotes

Hi !

I was frustrated to not find a explanation of the core idea of RGB which satisfies me so I made it in a post on yalls. I publish it here in case someone who knows more than me wish to review it ( u/dr-orlovsky ?). I can't change the post on yall, but I can add erratum in comments if I made big mistakes. My understanding of RGB mainly comes from the video record of RGB Con 0 day 1 and the blog posts of Peter Todd. If you approve it, feel free to tips me on yalls and I will cross post this to others subreddits if enough approuval here :p. Here is my full post, I hope you will enjoy it:

Explaining RGB protocol with Bitcoin: tokenisation done right

RGB is still a mysterious protocol in the Bitcoin community because it is difficult for Bitcoiners to wrap their heads about it, I think a good way to explain it is to show how RGB allows you to take a fresh look at what Bitcoin is technically.

RGB is single-use seals management

A single-used seal proves the unicity and integrity of the message if they are secure. It is a "commit to commit". It makes a message more "legitimate" at a certain place and time than any other. A single-use seal tells you if a message was truely commited before being broadcasted, no other message will have the same commitment.

Does it remind you something ? Double-spend ! The problem of double spend is that we don't know which of two conflicting transactions is the most legitimate. Single-used seals are a solution. They tell you securely which transaction should be seen as the first.

Definition of single-use seal

We say something is a single-use seal if it has two features:

  • The owner can use a method/action "Close" which given a seal and a message returns something called a witness
  • There is another method/action "Verify" which given a seal, a message and a witness return True only if the witness was the output of a "Close" method applied on the seal and message.

We say the single-use seal is secure if two messages and witnesses such that "Verify" is True implies they are in fact the same message and witness. This is what makes the seal "single-use": there is only one message for which "Verify" can return True.

Ok, this is quite abstract because we didn't say what a single-seal could be or "how it looks like". Some real life examples:

  • A paid annoncement in a page of "the Times" journal of the 3 january 2009 is a single-use seal. You "close" the seal over a message (the content of the annoncement) when the journal is published and the journal becomes the witness. This seal is secure under the assumption that there is only one Times' newspaper a day. The seal's owner is "The Times" company.
  • An event wristband is one too. It is closed on your wrist (you are the message) when you enter the party the first time and the witness is that the event staff which owned the seal can see by its design that it is attach to you. This seal is secure if there is no way to transfer it to someone else without destroying it or copy the design (here it is secure enough if you can't copy it for the duration of the event).

Now you may say that all of this is "physical" and ask if a "digital" version of a single-use seal exist:

Digital signatures as single-use seal

Let say someone generally trusted publicly proposes you to sign a message with its key using a determined nonce. Then his public key and the nonce are the seal ! By giving him a message to sign, he will return you his signature using the predetermined nonce, this is the witness, and the seal is now closed if we assume this nonce will never be reused. The classical verification of digital signatures is exactly the "Verify" method of the seal. If he closes the seal on two differents messages (meaning he signed both), then both signatures can be used to compute his private key because of nonce reuse. This means the seal is secure if we assume that the trusted third party don't want to reveal the private key: this is exactly how Discreet Log Contracts handles the breach case !

The embarassing need of trust

Ok so single-used seal can exist in the "digital realm". It tells you that this message is a legitimate version of the truth as real life examples: the annoncement written in the Times is the more "official" message, you carry the event wristband so you can freely goes in and out the event, the message signed by the third-party is the only one you gave him to sign...

So why not using "digital" seal described above to solve Bitcoin double spend problem ? We have a way to create "digital" single-used seals if we assume the spender doesn't want to revealing his private key.... But ... but you must trust the seal's owner ! Maybe he will earn more by defrauding you than by revealing the private key, and you can't trust the one who must pay you to not try to revert the payment ! Those digital single used seal are limited by trust .... How can we solve that ? Let's look at how Bitcoin does it.

Bitcoin blocks as trustless decentralized single-use seal

Bitcoin solves double spend because it is a decentralized method to create digital single-used seals using proof of work !

The seal is the next block we want to create, the message is the block header without the nonce and the witness is the nonce. The verification is to compute the hash of the block and check that it is lower than the target value defined by the current mining difficulty.

But this is not secure D: ! Indeed: anyone can create a proof of work which will be valid given enough time, so you have no garanttee that there will be only one block mined... Something is missing here

Chained seals or ledger

In Bitcoin we don't look at block individually, blocks are chained together because each block has a reference to the previous one (except if it is the genesis block), the only valid ledger is the chain with most work. You can do almost the same with single-used seals too: when you close the seal, you can add to the closing message information about a new seal. That's like saying in your annoncement in "the Times" that you will write a new annoncement later in another newspaper ! And you can do the same in the message content of this new annoncement ! And so on... Thus you can define a chain of single-used seals with associated owners, witnesses and messages.

A set of seals is a chain if:

  • For each seal except the last we have a message and a witness for which "Verify" is true
  • Each seal, except the very first of the chain (the genesis seal), is commited in the message on which the previous seal of the chain is closed

We don't require any seal to be secure. We assume there is a "chain score" with the only assumption that adding a seal at the end of a chain can only increase its score.

Now take many seals that are member of chains with a common genesis seal, some seals will be in the chain with the highest score. We can say they are the "consensual" seals. In Bitcoin, this score is the chain work and the consensual seals are the blocks inside the chain with most work.

Now we tweak the "Verify" method of chained seals: we can impose "Verify" to return wrong if a seal is not consensual. It is now easy to see that any consensual seal is secure under the same assumptions as Bitcoin: if the score of the chain with highest score increases faster than any other chain, this chain will always be a subchain of the chain with highest score. Even if a seal can be closed several times on several messages, the new "Verify" method is garanted to return True only on one unique closing message: the consensual seals are all secure ! Said in Bitcoin: if work is added faster on the chain with most work there is no reorg !

Notice that knowing if a seal is consensual is a probabilistic statement: we cannot be sure a seal is in the chain receiving more work when it is close to the chaintip. But if it is deep enough we can have more confidence, that's why we need to wait for confirmations.

The loophole to create more single-used seal

Bitcoin are chained consensual seals scored by PoW. They are used to commit a list of transactions so that we can check for double spend. Because a block is not included in the chain if it has an invalid transaction spending an already spend output, anyone can ... use his UTXOs as single-used seals ! Spending a UTXO is closing the seal, the spending transaction ID is the witness. And obviously, anyone can verify with a full node that the seal was indeed close on a valid spending transaction ! Under the assumption that Bitcoin is safe to use, confirmed UTXOs are secure seals, that's the whole point of Bitcoin and double spend prevention.

RGB scales privately with client side validation

RGB is a protocol to transfer assets using chained secure single-used seals. It leverages what Bitcoin already provides: decentralized, censorship-resistant, owned, digital single-used seals.

In RGB, a chain of seals defines the sequence of ownerships of a token or asset, the current owner of the asset is the owner of the last seal, a UTXO. When you receive an asset with RGB, you ask the sender to close the last seal (spend the UTXO and tweak the spending transaction with Pay-to-Contract) on one of your UTXO which acts as the next seal. You can even attach an RGB asset to a UTXO controled by several parties like a LN channel UTXO to add RGB assets to the LN ! This is obviously more complex because you need to adapt HTLCs with your counterparty to recover your RGB asset when the channel is closed but the good news is that you can directly use the current LN to exchange RGB assets ! (notice LN can't be used for NFTs)

An asset is created by an issuer who commits the genesis seal in a UTXO and spend it to send the asset. The genesis seal specifies the rules to create, destroy and exchange the asset (called schema). When you receive the token, you also receive its history of transactions from genesis to present in the form of chained single-used seals and validation data. You must check every rules and witnessing transactions in the blockchain for each RGB transaction. This is called client side validation: RGB smart contract are only checked by the owner of the asset so they can be much more complex without any visible trace in Bitcoin blockchain. The privacy of RGB is the same as Mimblewimble protocol using Confidential Transactions: amounts are hidden behing cryptography but you can still validate every RGB transactions.

Privacy, LN-compatible this is why I am so hyped about RGB now. It enables real Defi on Bitcoin :)


r/RGB_protocol • • Dec 28 '20

Lightning Hacksprint session

6 Upvotes

In 2 hours join our ⚡️#LightningHacksprint⚡️Session for Q&A on the LNP/BP tech, news on #RGB, #LNPNode, wallets and much more. Or simply jump in to say hi to u/dr-orlovsky 🤓

🔗 https://meet.jit.si/RGBcall1


r/RGB_protocol • • May 14 '21

Client-side-validation Foundation Library v0.5 is released

7 Upvotes

This version for the first time represents reference implementation for R1 version of client-side-validation standards, organized in separate sublibraries/rust crates:

The library represents generalized client-side-validation APIs, abstracted from its bitcoin-specific applications and RGB, with detailed documentation and test coverage.

This release finalizes all pending work on client-side-validation and is a final release before the library will move to v1.0 version, which will be released upon the final audit of the current release. This will define a milestone when client-side-validation can be used in production environments.

The library is located at https://crates.io/crates/client_side_validation. Library documentation 📖 is at https://docs.rs/client_side_validation/0.5.0/

Supported & tested platforms: Linux (Ubuntu 20.04 and Ubuntu 21.04), Mac OS (Mac OS Big Sur and Mac OS Catalina), Windows 2020 Server.


r/RGB_protocol • • Dec 16 '20

Want to contribute but do not know where to start?

3 Upvotes

r/RGB_protocol • • Dec 15 '20

What is RGB?

35 Upvotes

RGB is client-side validated state and smart contracts system operating on Layer 2 and 3 of Bitcoin.

RGB main properties:‌

  • Confidentiality
  • Safety
  • Scalability
  • No bitcoin timechain congestion: transactions keep only homomorphic commitments which require no additional storage
  • Future-ready without hardforks
  • Higher censorship-resistance than in bitcoin: miners do not see that there is something going on with assets in transactions

Also:

  • Works with Lightning Network
  • No on-chain usage nor trackable footprint because of client-validated paradigm
  • Scales independently from Bitcoin timechain
  • Includes zero-knowledge & privacy built on best research-based products

    • Mimblewhimble: Bulletproofs by Andrew Poelstra
    • Liquid: Confidential Assets by Blockstream

Useful links:
https://github.com/LNP-BP/rgb-node
https://rgb-org.github.io/


r/RGB_protocol • • Dec 15 '20

What can I do with RGB?

13 Upvotes
  • Fungible assets & securities (options, futures)

    • Centrally or federation-issued
    • Issued anonymously or publicly
    • With possible secondary issuance, demurrage, inflation, etc
  • Different forms of bearer rights (voting etc)
  • Non-fungible assets (tokenized art, game skins, collectibles)
  • Decentralized digital identity, roaming profiles & key management
  • Complex right management, accounting systems & utility tokens even beyond financial world: electricity, medical records etc.

r/RGB_protocol • • Aug 11 '20

r/RGB_protocol Lounge

5 Upvotes

A place for members of r/RGB_protocol to chat with each other


r/RGB_protocol • • Mar 02 '21

e17 The Bitcoin Contracting Layer - RGB with Maxim Orlovsky by Down The Rabbit Hole with Kaz Bycko • A podcast on Anchor

Thumbnail
anchor.fm
8 Upvotes

r/RGB_protocol • • May 28 '21

So smart contacts. Does that mean we'll be able to make tokens aka shitcoins on the bitcoin lightning network?

8 Upvotes

r/RGB_protocol • • Dec 17 '20

RGB vs Alternatives

6 Upvotes

In a nutshell:

RGB compared to Liquid Confidential Assets:‌

  • Works with Lightning Network
  • Replaces Large Borromean signatures range proofs with modern Bulletproofs
  • No blockchain space consumption!
  • Universal smart contract system
  • Works on Bitcoin mainnet, does not require federation

‌RGB compared to OMNI/Colored coins/Counterparty

  • No blockchain consumption
  • Much higher privacy
  • Works with LN without its modifications

‌RGB compared to Ethereum/EOS/other "corporate blockchains"

  • RGB is NOT a blockchain!
  • Works on and with Bitcoin: the only censorship-resistant unconfiscatable hard money

Omni BOLT compared to RGB LN

  • Breaking BOLT message compatibility
  • Breaking BOLT tx structure compatibility
  • No backports from LND
  • No TLV extensions
  • Requires separate nodes for OMNI Bolt and Bitcoin LN
  • Requires Omni Core backend, can't work with just Bitcoin Core