Non-Transferability Technical Design/Document - Githubissues

ConsenSysMesh / web3studio-bootleg

The Shared Royalty Non-Fungible Token (a.k.a Bootleg) is an open source project started by the ConsenSys Web3Studio team. The purpose of the Shared Royalty Non-Fungible Token (SRNFT) is to make any royalty business model, from the oil and gas industry to entertainment, easy to manage with the Ethereum blockchain .

https://consensys.net/web3studio/bootleg/

Apache License 2.0

91 stars 30 forks source link

Non-Transferability Technical Design/Document #42

Closed hadasz closed 5 years ago

hadasz commented 5 years ago

Overview

As a non-transferable asset implementer, I want to have a design and architecture, so I have a clear picture and understanding of what to build.

Reference

Questions

What is the best way to implement this?
What should be left out? What should be included?

Assumptions

There is a way to implement something in the timeline we have

Acceptance

A descriptive technical document that will serve as a map.
Diagrams explaining the architecture

Tasks

Figure out what can be implemented
Figure out overview of how to implement iti
write it down

brian-lc commented 5 years ago

I'll help out with this and we'll work together to close this out today.

brian-lc commented 5 years ago

Document is attached and included below in the LucidCharts diagrams for bootleg (team members should all have full access)

https://www.lucidchart.com/invitations/accept/ba1933c9-82e4-4c23-ae0e-557f986cfa7d Bootleg - Encryption Diagram.png