RGB FAQ
  • Welcome to RGB!
  • 💡What is RGB?
  • 📚RGB Resources
  • ⚙️RGB design principles
  • 🎓RGB paradigms
    • Single-use seals
    • Cryptographic commitments
    • Client-side validation
    • Strict encoding
  • 🔖RGB Smart contracts
    • What is a smart contract?
    • What is contract schema?
    • How does one program RGB smart contracts?
    • Do you define the validity of a state transition with Schema?
  • ☣️RGB & ₿itcoin
    • Will RGB require a fork of Bitcoin or Lightning?
    • RGB testnet & mainnet
    • Taproot, Schnorr signatures and RGB
    • Does anything need to happen in Lightning or Bitcoin to enable Lightning on RGB?
    • Is there a plan to work on channel factories?
  • 🎨RGB NFT
    • RGB NFT vs other NFT
    • What's the difference between RGB design of NFTs and common NFT approach?
  • ❓FAQ
    • What is RGB?
    • What does 'RGB' stand for?
    • Is RGB a new blockchain?
    • What can I do with RGB?
    • Is it possible to create a DAO with RGB?
    • RGB vs alternatives
    • Is RGB Turing-complete?
    • Does RGB require Taproot?
    • What RGB is compatible with?
    • Will Simplicity be used in RGB?
    • Why there is no RGB MVP with updates rolling out after?
    • How is confidentiality reached in RGB?
    • How is safety reached in RGB?
    • What is client-side validation?
    • How scalable is RGB?
    • Is there an RGB "Hello World" guide?
  • 📖Glossary
    • Contracts
      • ContractId
      • NodeId
      • Node
      • State
      • State assignment
      • State transition
      • Assignment
      • Assignment variant
      • State data
      • State type
      • Metadata fields
      • Metadata
      • Data type
      • Genesis
    • AluVM
    • Bifrost
    • Client-side validation
    • Contractum
    • Deterministic Bitcoin commitments
      • Container construction/deconstruction
      • Container
      • Commitment
      • Commitment embedding
      • LockScript
      • Proof
      • Protocol-specific entropy
      • Supplement
    • Right
    • Schema & Scripts
      • Schema
      • Field type
      • Assignment type
      • Bit dimensions
      • ABI
      • Script library
      • Occurence boundaries
      • Script extensibility
      • Transition type
    • Single-use seals
      • Witness
      • Seal definition
      • Seal blinding
      • Multimessage commitments
      • Seal closing over message
    • Stash
      • Stash
      • Consignment
      • Disclosure
      • Anchor
      • Forget procedure
      • Merge procedure
      • Validate procedure
      • Conceal procedure
      • Consign procedure
    • Encodings
      • Merklization commitment encoding
      • Storage encoding
      • Strict encoding
      • Pedersen commitments
      • Blinding factors
      • Buletproofs
      • Conceal
      • Commitment encoding
  • 🙋Community
    • Developer calls
    • Presentation slides
    • YouTube
    • Getting familiar with RGB
    • Articles & interviews on RGB
Powered by GitBook
On this page

Was this helpful?

  1. RGB NFT

What's the difference between RGB design of NFTs and common NFT approach?

PreviousRGB NFT vs other NFTNextFAQ

Last updated 3 years ago

Was this helpful?

In general, the way (Digital Rights management) system works today is very far from individual/author/owner-centric, leading to appearance of huge industry of distributors and labels and impossibility to buy into ownership of some certain content. So the assumption is, that removing the ability to prevent copyright technically (current DRM) and use instead economical incentives is much more sustainable and will lead to the healthier ecosystem. That is what can be expected from the RGB NTF design.

So, the change with RGB (in legal terms) is:

  • when content creator sells his content, he (1) does that directly to the buyer and (2) he sells the right to copy (i.e. "copyright”) with it (which is the actual ownership over a piece of content) - and he can do that multiple times. RGB provides distribution channel (LN+Bifrost), decentralized storage (Bifrost+Storm), payment (BTC, lBTC or RGB stablecoins like USDT) and protection of the content from being accessed by non-buyers (client-side-validation with encryption and confidentiality) for that.

  • when content owner sells content, he has two options: (1) sell access to the content, for smaller money than when the content is sold, so he sells “usage rights”, and the new content user will be able to use the content/copy multiple times, but will have a challenge of selling it (still being able to distribute it for free) and (2) pass the ownership rights further, the same way the content creator did.

This indeed does not provide copy protection at technical level. But what it does, it provides free public access protection at technical level (until one of the content users will publish it for free).

That is weaker publisher guarantees comparing to DRM, but stronger comparing to any other NFT or alternative out there (and the same strong guarantees as with software licenses back in old days).

At the end of the day, arguably, there is a probability that if we take game theory & economy into account (and not only technical means) that will still give more profit to the content producers because we remove intermediaries (lables/distributors) taking 90% of profitability from the equation + provide economic incentives to pay to owners, and not cheating content users.

🎨
DRM