Baseledger
Search…
Baseledger
Welcome (tl;dr)
Baseledger Introduction
Abstract
Baseledger Setups
The Baseline Protocol
Problems tackled
The Right Mainnet
Service Quality
Data Privacy
Integration
Lack of a Unified Architecture for Multi-Chain Coordination
Baseledger Core
Architecture of Architectures (Multi-Chain)
Integration
Identity Management
Consensus Model
Data Privacy
Performance
Transaction Costs
Example Use-Case
Energy Consumption & Sustainability
Governance
Governance
Token Model (UBT)
Requirements
Token Model and UBT
HowTos
How to explore the Baseledger testnets
How to find information on UBT (Unibright Token)
Related Websites
Baseledger.net
Unibright.io
Unibright Token (UBT)
Provide.Services
Baseline Protocol
Appendix
Disclaimer & Imprint
Powered By GitBook
Service Quality
The Service Measurement Index (“SMI”) was designed based on International Organization for Standardization (ISO) standards. It consists of a set of business-relevant Key Performance Indicators (KPIs) that provide a standardized method for measuring and comparing business services.
The SMI framework provides a holistic view of Quality of Service (QoS) needed by customers for selecting business services (including blockchain services) to evaluate the feasibility of an enterprise solution based on:
  • Costs: Is the service cost-effective (per transaction, data storage, integration,…)?
  • Performance: Are there predictable projections for usage of service in terms of performance metrics?
  • Accountability: Are there concepts in place to serve demands around governance, support and service level agreements?
  • Agility: Is the service elastic, portable, adaptable and flexible?
  • Assurance: Will the service perform as expected (reliability, resiliency and service stability)?
  • Usability: Is it easy to integrate the services into the existing landscape (Accessibility, Installability, Learnability, Operability)?
  • Sustainability: Can it be assured that the different technical components of an enterprise solution can be maintained, enhanced or (if needed) exchanged without affecting the overall availability of the solution?
Previous
The Right Mainnet
Next
Data Privacy
Last modified 3mo ago
Copy link