ConsenSysMesh / ConsenSysMesh/web3studio-dONT
(DOnT) Off-chain Non-Transferability
- Dominant language
- Haskell
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
## Overview
As an (part)owner of a digital asset, I want to ensure that my asset can't be accessed by an unauthorized user, so that the value of the asset stays high.
### Reference
- [Media Chain](http://www.mediachain.io/)
### Questions
- How do we enforce unauthorized users?
- Do we use cryptography?
- Stenography
- User puts up collateral (private key, or eth in escrow)
- Can we use streaming somehow?
- Are there other things out there that we can use?
- mediachain.io
- What experiments could we run?
- What can we build to show our DRM pattern off?
- What options exist both on and off chain?
### Assumptions
- We need some kind of DRM to maintain value of the bootleg token
- Our DRM pattern should not be tightly coupled to #5 the ERC, but it should inform it
- Time permitting, given interest and result of the research, we should build something.
### Acceptance
- Documentation for pattern implementation
- Architecture diagrams and descriptions
- POC - working implementation of encryption, decryption, and secret sharing
- Encryptor lib, decryptor lib, a smart contract
- Works with #5 (Runs inside the simulation/example)
- ~Run at: Medium article explaining how we might do DRM with blockchain~
## Stories Draft
- [ ] Research what already exists for DRM in the blockchain space
- [ ] Write up an article
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points; start by reviewing the linked Media Chain reference and researching existing blockchain DRM approaches. Done means documenting a DRM pattern with architecture diagrams and descriptions, plus a working encryption, decryption, secret-sharing, and smart-contract proof of concept that runs in the simulation/example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain, cryptography, documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100