Smart Contract Security via High Granularity Metrics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain security approaches fail to effectively protect smart contracts from malicious behavior and security breaches, as they do not adequately serve as security gatekeepers for the blockchain platform or its operations, leading to vulnerabilities that can result in hacks and fund thefts.

Innovation Solution

Implementing a system-level High Granularity Metrics (HGM) detection mechanism within a kernel execution framework for smart contracts, which involves function boundary detection, monitoring function calls, and applying HGM-based control rules to block potentially malicious behavior by comparing detected metrics against permitted or prohibited sets, thereby ensuring secure execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional blockchain security approaches (Proof of Work, consensus protocols, private keys) are used, then basic blockchain integrity is maintained, but smart contracts remain vulnerable to security breaches and malicious behavior

Engineering Contradiction:
Improvesmart contract securityVSAvoidsecurity framework complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a security gateway as an intermediary component between the blockchain execution environment and smart contracts. This gateway monitors function calls, enforces access control policies, and detects malicious behavior patterns without requiring changes to the underlying blockchain consensus mechanisms or smart contract code, thus improving security while maintaining relative simplicity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary security checks and function call validations before smart contract execution proceeds. By pre-defining allowed function calls, access control policies, and malicious behavior patterns, the security gateway can prevent attacks before they execute, rather than reacting after breaches occur

Inventive Principle:
Principle #10Preliminary action

2Reliability

If security gatekeepers are added to protect smart contracts, then security improves, but execution speed and transaction throughput may decrease

Engineering Contradiction:
Improvesmart contract securityVSAvoidtransaction throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The security gateway applies partial monitoring and validation only to critical function calls and high-risk operations within smart contracts. Rather than scrutinizing every single operation, the system focuses security resources on the most vulnerable points, maintaining security effectiveness while minimizing impact on overall transaction throughput

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If detailed monitoring of function calls is implemented, then detection precision improves, but system complexity and computational overhead increase

Engineering Contradiction:
Improvemalicious behavior detection precisionVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The security gateway segments the monitoring function into distinct modules: function call interception, pattern matching engine, policy enforcement, and logging. This segmentation allows each component to specialize in a specific aspect of security monitoring, improving detection precision while making the overall system more manageable and less complex

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240113861A1Adaptive security for smart contracts using high granularity metrics
Publication Date: 2024.04.04 EBAY INC
  • US20240113861A1 patent drawing
  • US20240113861A1 patent drawing
  • US20240113861A1 patent drawing

AI summary

Technologies are shown for high granularity metric (HGM)-based control for smart contract execution. In accordance with some aspects, a function call associated with one or more methods of a smart contract on a blockchain is detected by identifying an entrance or exit of the function call in a kernel for smart contract execution on the blockchain. The function call is added to a function call stack, and one or more detected HGMs are identified in the function call stack. A comparison of the detected HGMs in the function call stack against one or more control rules is performed. Execution or completion of the function call is blocked based on the comparison.