Date
1 - 4 of 4
create a fabric supporting thin peers
|
qs meng <qsmeng@...>
Hi, I want to make some modification to the fabric such that the peer only save blockheaders, not the transactions, not the meta data. A peer with the code is called a thin peer which needs less storage. But I still want a thin peer can check the correctness of transactions. Now I want you some help. 1. is the idea feasible? 2. what codes should be modified? what I find is " common/ledger/blkstorage/fsblkstorage/blockfile_mgr.go". is there any other codes? Thank you. best regards, qsmeng
|
|
|
|
Gari Singh <garis@...>
What exactly is your use case here?
In order to validate transactions, a peer will need access to the state database (which is of course populated by processing validating and committing blocks/transactions). Technically, the peer does not need access to the entire file ledger. ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain IBM Middleware 550 King St Littleton, MA 01460 Cell: 978-846-7499 garis@... ----------------------------------------- -----fabric@... wrote: ----- To: "fabric@..." <fabric@...> From: "qs meng" Sent by: fabric@... Date: 03/08/2020 09:55PM Subject: [EXTERNAL] [Hyperledger Fabric] create a fabric supporting thin peers Hi, I want to make some modification to the fabric such that the peer only save blockheaders, not the transactions, not the meta data. A peer with the code is called a thin peer which needs less storage. But I still want a thin peer can check the correctness of transactions. Now I want you some help. 1. is the idea feasible? 2. what codes should be modified? what I find is " common/ledger/blkstorage/fsblkstorage/blockfile_mgr.go". is there any other codes? Thank you. best regards, qsmeng |
|
|
|
qs meng <qsmeng@...>
Hello Gari, Thank you for your letter.
In a real application, storage is always a heavy burden because every
orderer, peer each has a complete blockchain. To relievee the storage
requirement, a peer can only store world states, not the transactions
themselves. The peer can validate the block by checking the related
blockheaders and the transactions just like a committing peer.
I dont know if the idea is feasible because something important is not
considered. and want to know how to modify codes or what codes should be
modified. Thank you again. Best regards, meng
|
|
|
|
ravinayag .
Hi, If I rightly understand question, It make sense for thin peer within the org structure. For example. If an org has normal 3 peers such as ledger storage, statedb, anchor/endorsement roles. The 4th can have a thin peer just to do endorsement role or a query role which no need to maintain ledger or Statedb. Hi MENG, excuse and correct if misunderstood. Thanks On Mon, 9 Mar 2020, 15:33 Gari Singh, <garis@...> wrote: What exactly is your use case here? |
|
|