ComBoox - White Paper
  • πŸ‘‹Welcome to ComBoox!
  • πŸ›οΈSystem Overview
    • ⌨️Overview
      • βš οΈβ€œPain Points” of Corporate Governance
      • πŸ’‘Blockchain Solution
      • πŸ’°Tokenization and Company Evaluation
      • ✨Features and Advantages
    • πŸ–₯️Computational Control Model
    • πŸ—οΈSystem Architecture
    • 🚷Identification and Access Control
    • πŸ“Templates and Version Control
    • πŸ’°CBP and Economic Model
    • πŸ’ΈFinancial Records
    • ☝️Key Legal Issues
    • πŸ₯‡Software License
  • πŸ•ΉοΈOperation Guide
    • πŸ›£οΈGet Start !
    • βœ’οΈDraft SHA
    • πŸ—³οΈPut Director On Board
    • πŸ—žοΈInvest And Trade Shares
  • πŸ“šTechnical Brochure
    • 🌻Key Objects
      • πŸ—žοΈShare and SharesRepo
      • πŸ‘¨β€πŸ‘¨β€πŸ‘§β€πŸ‘§Member and MembersRepo
      • πŸ’ΊPosition and OfficersRepo
      • πŸ—³οΈMotion and MotionsRepo
        • ✍️DelegateMap
        • πŸ—³οΈBallot and BallotsBox
      • πŸ›οΈDeal and DealsRepo
        • πŸ”„Swap and SwapsRepo
      • πŸ“ˆOrder and OrdersRepo
      • πŸ“‘Pledge and PledgesRepo
      • βš–οΈOption and OptionsRepo
      • πŸ“Rule and RulesParser
      • 🍡Anti-Dilution
      • πŸ”Lock Up
      • 🚜Drag / Tag Along
      • πŸ›ΈPut / Call Options
    • πŸ› οΈStructure and Components
      • ⏱️Checkpoints
      • 🏁TopChain
      • πŸ₯‡GoldChain
      • πŸ”€EnumerableSet
      • πŸ”„Condition and ConsRepo
      • πŸ”HashLock and LockersRepo
      • πŸ–‹οΈSignature and Sigpage
      • πŸ“‚File and FilesRepo
      • πŸ—„οΈDoc and DocsRepo
    • πŸ‘¨β€πŸš€Identity and Verification
      • 😜Role and RolesRepo
      • 🚷Access Control Contract
      • 🦸User and UsersRepo
    • πŸ„β€β™€οΈBehaviors and Process
      • 🀝Share Transaction
Powered by GitBook
On this page
  1. Technical Brochure

Identity and Verification

PreviousDoc and DocsRepoNextRole and RolesRepo

Last updated 1 year ago

The smooth operation of the system and the realization of functions, depend on the authority control and the routing control of the writing instructions. In other words, for the calling instructions ("writing instructions") which can change the state of each smart contract, it is necessary to review and verify the identity and authority of the account that issued the instructions, and at the same time, it is necessary to strict control the target contract address and API referred by the writing instructions. When the writing instructions are strictly controls from the "receiving” and β€œsending" direction, the information of the whole system can be updated as the established commercial and legal logic.

The writing instructions in the system can be divided into three categories:

  1. System Configuration: the drafting and system configuration actions triggered by external accounts, and will not directly lead to legal consequences;

  2. Legal Behavior: the share transactions and corporate governance activities triggered by external accounts, and will not lead to direct legal consequences; and

  3. Algorithmic Control: the actions triggered by the first two types of writing instructions, in which the bookkeeper contract may issue the writing instructions in orderly manner to change the Register Contract, shareholders agreement, investment agreement, and other smart contracts.

For the above three types of writing instructions, the system adopts three verification methods to control the access varying from the behaviors and scope of influence.

πŸ“š
πŸ‘¨β€πŸš€
😜Role and RolesRepo
🚷Access Control Contract
🦸User and UsersRepo