Building a DAO using RGB

[pxr64]

I want to get started on building a DAO using the blockchain network, would RGB be a suitable tool for getting something like that to production?

Also :

1. What are the challenges in storing data using the lightning network In terms of cost, performance and accessibility?
2. How should I approach implementing NFT’s or DAO system to lightning ( using RGB, TARO, or TAPSCRIPT)?
3. Would it be challenging to scale a system such as a DAO on the lightning network?

[dr-orlovsky]

Hi! I think we are still quite early: no toolchain suitable for external devs is there; it will take few more months to get it done. The protocol is there, but it is pretty low level.

[pxr64]

Having the client software store date is a good idea, it's a bit unclear how we make sure that the data is tamper-proof unless it's embedded on a chain in some way.

I figured that we need to store some key information on the chain so that this info becomes the single source of truth. For example, when a member votes, they embed their intent in an on-chain transaction, later, after the voting ceremony ends, the outcome can be determined by looking at these transactions.

However, maybe I'm thinking about this the wrong way because initially, I was envisioning the whole system as a special wallet application that would have the classic btc wallet features plus some features that would allow users to use interact with each other similar to how they would do if they were part of a DAO.

These features essentially boil down to what you described earlier (that events are uniquely identifiable and immutable). This leads me to the idea that the wallet needs to be able to embed information on the chain and be able to access it later.

[dr-orlovsky]

I think you need to check how RGB and client-side validation is working - your question is about the exact problem they solve.

Please check https://www.youtube.com/watch?v=gGPLYfWOb_8

There is no point making DAO on RGB without using its advantages over on-chain storage.

[dr-orlovsky]

I think you need to check how RGB and client-side validation is working - your question is about the exact problem they solve.

Please check https://www.youtube.com/watch?v=gGPLYfWOb_8

There is no point making DAO on RGB without using its advantages over on-chain storage.

[cryptoquick]

@brinzi You might benefit from the solutions we're developing at diba.io to geographically distribute, periodically verify integrity, and checkpoint data hashes on the blockchain that we're developing to support RGB21 contracts, code, and content using Carbonado. This allows keeping the RGB23 DAO log data in a safe, verifiable, distributed, and scalable place off-chain, which also expands what metadata and capabilities can be validated using RGB consensus checking.

[pxr64]

@cryptoquick Amazing. Thanks for the reference, let me digest it a bit and I will leave some feedback.
Also @dr-orlovsky, I really enjoyed your presentation, it gave me a lot of valuable insight, thank you. 🙏