# Blockchain Architecture for Lightweight Storage
## 1 Introduction  
The blockchain concept was first proposed by [PERSON] and [PERSON] and is considered one of the most promising technologies [1]. Subsequently, [PERSON] introduced Bitcoin [2], which propelled the blockchain trend to its peak. The core technology of blockchain is designed to facilitate peer-to-peer electronic transactions and data storage, enabling multiple participants to share ledger contents and synchronize them through community verification [3]. This technology has been extensively utilized in finance, transportation, education, healthcare, cybersecurity [4], and management science due to its decentralization, high reliability, data integrity, and traceability [5]. Nodes in the blockchain jointly maintain a distributed ledger that globally records events, utilizes asymmetric encryption algorithms to secure user transactions, and employs consensus algorithms to ensure orderly transaction execution [6]. As a distributed ledger, blockchain not only possesses inherent advantages in data processing [7], but its decentralized feature also addresses the limitations of traditional transactions, where confirmation and recording entirely rely on trusted institutions, thereby enhancing trust and improving transaction transparency [8]. As information technology advances, blockchain is evolving across multiple dimensions. Regarding consensus, [PERSON] introduced a novel multi-chain method, MC-RHotStuff [9], which screens nodes based on performance and dynamically adjusts node numbers to enhance system throughput. [PERSON] proposed the adaptive PBFT protocol, APBFT [10], whichminimizes communication overhead and response delay. [PERSON] introduced Helix [11] to ensure fair transaction ordering among nodes in distributed networks, while [PERSON] introduced DPNPBFT [12], aiming to balance complexity, efficiency, and security. In storage, some scholars achieve lightweight solutions by restructuring blockchain, as seen in LDAGB [13] and LDV [14]. Additionally, researchers reduce blockchain storage redundancy through techniques like corrective deletion codes [15], sharding [16], data compression [17], and offloading [18]. In the era of big data, blockchain must enhance its processing and analytical capabilities for data querying. [PERSON] introduced a blockchain-based lightweight searchable data-sharing scheme, BLDSS [19], which combines public key encryption with equivalence testing and agent re-encryption features to facilitate efficient data matching and sharing. [PERSON] monitors the execution of transactions without disrupting the operation of the smart contract by establishing a recording replay mechanism in the contract container [20]. [PERSON] introduces MSMLI [21], which constructs a composite index through a weight matrix and slices the blockchain according to the maintain structure, thereby enhancing query efficiency while minimizing storage overhead. Although blockchain technology has great potential and many advantages, there are still numerous aspects requiring optimization and enhancement [22]. Over time, due to its immutable nature, data accumulates on the blockchain, and the performance of the blockchain network is hindered by the uncontrolled growth of the blockchain ledger [23], which is essentially a performance bottleneck due to the lack of blockchain scalability [24]. The network also suffers from poorly motivated nodes, node failures, or malicious nodes tampering with the data, thereby compromising data consistency. To address the above issues, this paper proposes a lightweight sender-based blockchain architecture (LSB) to optimize the storage structure and consensus mechanism of the blockchain. The contributions of this paper to the existing literature are outlined as follows:  
* Enhanced efficiency of transaction queries. The hash in the block is linked to the transaction sender, and the newly generated block will point to the block with the same wallet address, allowing for rapid transaction queries via the node wallet. * Lightweight storage implemented.