Bridge Server for Multi-Shard Blockchain Asset Transfers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems fail to efficiently manage and transfer ownership rights of in-game digital assets across multiple shards of blockchains in online gaming platforms, leading to inefficiencies in transaction processing and ownership updates.

Innovation Solution

A bridge server system is implemented to support multiple shards of blockchains, facilitating the transfer of ownership rights by interacting with decentralized ledger servers to update records on different shards, ensuring seamless and efficient transfer of digital assets between users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single blockchain is used to record ownership rights of all digital assets, then ownership records are complete and centralized, but transaction processing efficiency decreases and communication overhead increases

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidblockchain structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The blockchain is divided into multiple shards, with each shard maintaining a subset of ownership records. This segmentation allows parallel transaction processing across shards, improving throughput and efficiency while reducing the communication overhead associated with a single centralized chain.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple shards are used to increase transaction capacity, then processing efficiency improves, but coordination and communication overhead between shards increases

Engineering Contradiction:
Improvetransaction capacityVSAvoidcommunication overhead
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

A bridge server is introduced as an intermediary component that coordinates transactions spanning multiple shards. The bridge server manages cross-shard communication, retrieves necessary data from relevant shards, and facilitates atomic transfers, thereby reducing direct communication overhead between shards and improving coordination efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If digital assets are distributed across multiple shards, then transaction parallelism increases, but asset transfer complexity between shards increases

Engineering Contradiction:
Improvetransaction parallelismVSAvoidasset transfer complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The bridge server acts as a mediator for cross-shard asset transfers, abstracting the complexity of multi-shard coordination from users and applications. It handles the retrieval of assets from source shards, validation of transfer conditions, and deposition of assets to destination shards, thereby simplifying the transfer process while maintaining parallelism.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-fetching asset data from source shards and preparing transfer conditions before finalizing cross-shard transactions. This allows the bridge server to validate and prepare transfers in advance, reducing the complexity and time required for actual asset movement between shards.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11748724B2Systems and methods for operating a bridge server to support multiple shards of a blockchain
Publication Date: 2023.09.05 MYTHICAL INC
  • US11748724B2 patent drawing
  • US11748724B2 patent drawing
  • US11748724B2 patent drawing

AI summary

Systems and methods for operating a bridge server to support multiple shards of blockchains are disclosed. The multiple shards may be used to record ownership rights of in-game digital assets. The in-game digital assets may be usable in an online gaming platform. Exemplary implementations may: execute an instance of a game; maintain user accounts for the users of a blockchain on a first and a second decentralized ledger server; record sets of rights pertaining to sets of digital assets; receive an exchange request for a first digital asset; receive transferal information for the first digital asset; transfer sets of instructions to the first and second decentralized ledger servers such that the first decentralized ledger server removes the first digital asset from the first set of digital assets and the second decentralized ledger server adds the first digital asset to the second set of digital assets.