LEMONCHAIN_ENG
WhitePaper
  • LEMONCHAIN Introduction
  • LEMONCHAIN Feature
  • HBN (Healthcare Blockchain Network)
  • 📖WhitePaper
    • 1. Abstract
    • 2. Introduction
      • 2.1 Current status of Smart Healthcare Ecosystem
      • 2.2 Importance of Smart Healthcare Ecosystem
      • 2.3 Role of Healthcare Data
      • 2.4 Mission of LEMONCHAIN team
    • 3. LEMONCHAIN, New Healthcare Data Ecosystem
      • 3.1 High level of Authority of Data User
      • 3.2 Rigorous Management Standards for Services Participating in Ecosystem
      • 3.3 Disclosure of transparent data management standards
      • 3.4 Decentralized Blockchain Ecosystem Structure
      • 3.5 Incentives for wellness
      • 3.6 Healthcare Big data statistics & search service
      • 3.7 HBN (HealthCare Blockchain Network)
    • 4. Technical details of LEMONCHAIN
      • 4.1 1st layer: Data accumulation
      • 4.2 2nd layer: Data inquiry
      • 4.3 3rd layer: Data utilization
    • 5. LEMONCHAIN, business flow
      • 5.1 Provision of complete decentralized healthcare service
      • 5.2 Data upload
      • 5.3 Settlement of account
      • 5.4 Making payment
      • 5.5 Data marketplace
      • 5.6 Guarantee for quantity of healthcare services that can be provided according to staking
      • 5.7 Mediation of disputes
      • 5.8 Fees
      • 5.9 Additional business operator
        • 5.9.1 Information business operator
        • 5.9.2 Settlement of account business operator
        • 5.9.3 Insurance business operator
    • 6. Future of LEMONCHAIN ecosystem
      • 6.1 Employment of LECO format for the ‘Healthcare data & service’
      • 6.2 Application of DeFi system
        • 6.2.1 Automated Market Maker (AMM)
        • 6.2.2 Lending protocols: Healthcare data-based loan-deposit margin model
        • 6.2.3 Synthetic assets: Issuance of token that follows price of specific asset
        • 6.2.4 Service for trading of divided ownership of healthcare data NFT
    • 7. Token model
      • 7.1 Overview of LEMC token
      • 7.2 LEMC token Pool
      • 7.3 Token Allocation
    • 8. Road Map
    • 9. Timeline
    • 10. Miscellaneous (legal issues to be notified, etc.)
Powered by GitBook
On this page
  1. WhitePaper
  2. 5. LEMONCHAIN, business flow

5.6 Guarantee for quantity of healthcare services that can be provided according to staking

Previous5.5 Data marketplaceNext5.7 Mediation of disputes

Last updated 2 years ago

Service participant needs to stake LEMC token to guarantee the execution of his/her services. In order to enable collaboration-based healthcare service, it is essential for the associated participants to faithfully execute their respective duties and be responsible for the costs incurred when they failed to fulfill their roles or if problems occur. For this purpose, the participants will stake prescribed quantity of tokens as guaranty deposit in the LEMONCHAIN ecosystem for use as means of compensation in the event of occurrence of problems.

Token staked by each participant contains the significance of guarantee for the services provided and, in order to be granted with larger quantity of service contracts under the LEMONCHAIN ecosystem, token that corresponds to such quantity must be staked. Quantity of tokens that can be staked is computed based on the existing history of the participant and reasons for sincere execution of contact is provided through this.

If the participant wants to provide services in excess of the token staked, it is possible to provide guarantee for the contract through the use of insurance business operator.

📖