Blockchain Configuration Data Distribution via Hashed Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large computing networks, updating configuration data across multiple devices is inefficient due to the need for extensive verification and authentication of numerous intermediate nodes, which can be time-consuming and impractical, especially in networks with limited resources and redundancy.
Innovation Solution
The use of a blockchain for propagating and updating configuration data, where each configuration transaction is hashed and digitally signed, allowing for faster validation and distribution, reducing the need for repeated verification across intermediate nodes by maintaining a ledger of all transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is propagated through multiple intermediate computing devices in a large computing network, then the data distribution can reach distant nodes, but the verification and authentication time increases significantly
Solution Approach 1:
The patent applies preliminary action by pre-establishing a blockchain ledger that contains cryptographic hashes and digital signatures of configuration data before distribution. Intermediate nodes can verify data authenticity by checking these pre-computed cryptographic elements, eliminating the need for time-consuming real-time verification of each intermediate node's permissions and data integrity.
Solution Approach 2:
The patent introduces a blockchain-based intermediary mechanism that mediates between the data source and intermediate nodes. The blockchain acts as a trusted mediator containing verifiable configuration data and permissions, allowing intermediate nodes to validate data without directly trusting or verifying each other's authentication, thus reducing verification overhead.
2Loss of time
If the number of direct connections to the source is increased to reduce verification time, then verification efficiency improves, but network complexity and vulnerability to failures increase
Solution Approach 1:
The blockchain serves as an intermediary that simplifies network topology by providing a single source of truth. Instead of requiring multiple direct connections to the source for verification, nodes can verify data against the blockchain ledger, reducing the need for complex direct connection requirements while maintaining verification efficiency.
Solution Approach 2:
The blockchain ledger performs multiple functions simultaneously: it stores configuration data, maintains permission information, provides verification mechanisms, and enables data propagation. This multi-functionality reduces the need for separate verification infrastructures and complex network topologies, simplifying the overall system while improving verification efficiency.
3Reliability
If more intermediate computing devices are used for data propagation, then network redundancy improves, but the number of verification operations increases
Solution Approach 1:
The blockchain intermediary enables intermediate nodes to verify data independently using cryptographic proofs stored in the ledger. This eliminates the need for repeated verification operations across intermediate nodes, allowing the network to maintain high redundancy with multiple intermediate devices without proportionally increasing verification overhead, thus improving both reliability and productivity.
Solution Approach 2:
The patent uses cryptographic copying by distributing hashes and signatures of configuration data across the blockchain ledger. Intermediate nodes can verify data by comparing against these cryptographic copies rather than performing full verification operations, enabling efficient data propagation through multiple intermediate devices while maintaining verification efficiency.
Data Source
AI summary
A method for propagating configuration data using a blockchain includes: storing a blockchain comprised of a plurality of blocks, each being comprised of a block header having a timestamp and one or more configuration transactions; receiving one or more configuration data items; generating a new configuration transaction for each configuration data item; hashing a most recent block identified based on the timestamp included in the respective block header to generate a previous block hash value; hashing a combination of the new configuration transactions and/or data associated therewith to generate a current block hash value; generating a new block header, the new block header including a current timestamp, the previous block hash value, the current block hash value, and a digital signature; generating a new block comprised of the new block header and each new configuration transaction; and updating the blockchain by appending the new block.