Registered Security Token Contract

Target release
Epic
Document status
DRAFT
Document owner
Designer
Developers
QA

Goals

  • Growth, Reduce Risk

Background and strategic fit

There are thousands of tokens in the market, and persons are investing in these tokens without any kind of regulation.  With RChain, if we offer a token contract example that contains within it the requirements for SEC registration, we will move the entire landscape forward, by clarifying and standardizing the process to obtain registration.  


Assumptions

  • Will have to work with KYC and Identity.
  • Will have to define how the tokens can be distributed.
  • Work with regulators and have them tell us what parts won't work and why not.

Requirements

#TitleUser StoryImportanceNotes
1NameWe should brand this token name.
2
   

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome
What are the SEC Requirements?
What are the KYC requirements?  Would there be a specific set of Identity services that would be 'trusted'?

Not Doing