rename smart contracts for whitepaper consistency/maximum generality

zerolawtech / ZAP-Tech

ZeroLaw Augmentation Protocol

GNU General Public License v3.0

27 stars 13 forks source link

rename smart contracts for whitepaper consistency/maximum generality #21

Closed lex-node closed 4 years ago

lex-node commented 5 years ago

Certain smart contracts or components should renamed for consistency with whitepaper and maximum generality for all organizations/use cases. Here is my (WIP) proposal for renaming; I will update this from time to time as I work on the whitepaper:

IssuingEntity --> OrgCode
KYCBase --> IDVerifierBase
- KYCIssuer --> OrgIDVerifier
- KYCRegistrar --> RegistarIDVerifier
TokenBase --> OrgShare
- NFToken --> CertShare
- SecurityToken --> BookShare
Investor --> Member

iamdefinitelyahuman commented 4 years ago

Places this will need to happen:

[x] contracts
[x] documentation
[x] test suite (optional: do https://github.com/iamdefinitelyahuman/ZAP-Tech/issues/13 at the same time)
[x] whitepaper

@lex-node please confirm you're happy with the proposed name changes above, edit the post if not... once it's good to go i will begin the process :+1: