top of page

Measurable Metrics for Orchestration and Chain Abstraction Layers

Chain Abstraction and Orchestration significantly advance blockchain infrastructure, emphasizing an enhanced developer and user experience. This approach transcends the limitations of proof-of-concept applications on a single blockchain, enabling more sophisticated and robust applications to be developed. By abstracting the complexities inherent in different blockchain networks, developers can focus on innovation without being hindered by technical details.

A Layered Approach to Chain Abstraction

We can conceptualize a layered framework called the Cake Framework to effectively abstract the fragmented blockchain ecosystem. This framework comprises the following layers:

  1. Blockchain Layer: This foundational layer ensures seamless asset assertions and transactions between various blockchains. It is crucial in maintaining smooth transaction operations and data transfer across different networks.

  2. Account Layer: Utilizing advanced cryptographic techniques, this layer abstracts chain accounts into unified user accounts. It enhances transaction security and data integrity while safeguarding against potential vulnerabilities.

  3. Application Layer: This layer decouples application logic from specific blockchain technologies, allowing developers to build applications operable across multiple blockchains. This eliminates the need for developers to understand each blockchain in detail.

  4. User Experience Layer: This layer creates user-friendly interfaces and enhances the end-user experience.

Metrics for Measuring Success

To evaluate the effectiveness of chain abstraction layers, we propose several key metrics across different layers of the framework:

Blockchain Layer Metrics

  • Number of Cross-Chain Asset Assertions: Tracks the number of zero-knowledge proof (ZKP) assertions that facilitate cross-chain transactions.

  • Number of Bridge Transactions for Liquidity Aggregation: Ideally, this metric should decrease as cross-chain asset assertions become more reliable and prevalent.

Account Layer Metrics

  • Supported Blockchains: The count of blockchains supported by the framework, indicating its interoperability capabilities.

  • Number of Users: Reflects the number of user wallets created, showcasing adoption and trust in the layer.

  • Security Audit Reports: Regular security audits and their outcomes provide insights into the framework's ongoing security health.

  • Account Hacks: Tracks the number of hacks or wallet-draining incidents, crucial for assessing security robustness.

Application Layer Metrics

  • Number of SDK Developers: Indicates the number of developers using the API framework. High engagement levels suggest ease of use and effectiveness.

  • Number of Active Blocs / Intent Solvers: Tracks developer activity and contributions.

  • Developer Activity: Monitored through GitHub activity, reflecting the community's engagement and framework improvements.

  • Number and Volume of Transactions: Measures the frequency and volume of transactions facilitated by the abstraction layer, indicating usability and service demand.

  • Transaction Speed: Assesses the time required to complete transactions, affecting user experience and operational efficiency.

  • Cross-Chain Transactions: The number of successful transactions between blockchains demonstrates the layer’s interoperability efficiency.

User Experience Layer Metrics

  • Batched / Single Click Transactions: Tracks the adoption of simplified transaction methods that enhance user experience.

  • Gasless Transactions: Monitors the implementation of gasless transactions, contributing to a more user-friendly and cost-effective experience.


By focusing on these metrics, we can better understand and improve the success of chain abstraction and orchestration layers. These metrics serve as a foundation for community feedback and further refinement, ensuring the development of a robust and user-centric blockchain infrastructure. We invite comments from the community to make this framework more robust and comprehensive.


Commenting has been turned off.
bottom of page