toggle quoted messageShow quoted text
Thank you for this information, including the two JIRAs.
FAB-5097 would definitely help satisfy the ISO requirement that I
I'm not sure that I understand the other JIRA (FAB-18461). If
data is only deleted on an individual peer, would it continue to
live on other collection member ledgers? Would the deleted
transaction get re-copied over to the original peer or would the
collection members need to maintain divergent copies of the
I agree with you on channel-wide purge being more important (from
my perspective on compliance).
On 5/4/21 7:12 AM, David Enyeart wrote:
Note that deletePrivateData only deletes from private state.
The private data remains in the private data store (committed
data) and transient store (uncommitted data) for other peers
that may be running behind to pull. There are a couple stories
being considered to deal with this other data in future versions
GDPR for private data - On demand delete of private data prior
to block-to-live policy based on a delete transaction. Option
for transaction resulting from DelPrivateData() chaincode API to
purge key from peer's private data store and transient store on
all peers, in addition to deleting from private state database
on all peers.
FAB-18461 GDPR for private data - On demand delete of private
data prior to block-to-live policy on an individual peer. API to
purge a private data key from private state, private data store,
and transient store on an individual peer (could be done before
or after or instead of DelPrivateData() chaincode API).
Basically, channel-wide versus peer-scoped purge, while keeping
the hash on the chain. I assume the former would be more
important, but would like to hear thoughts from people familiar
with the ISO and GDPR requirements.
Also, let us know if anybody could assist to expedite an
implementation, as many people have asked for such a feature.
via lists.hyperledger.org" ---05/03/2021 07:21:54 PM--- Hey
Simeon, - You can purge using the deletePrivateData
Leonardi via lists.hyperledger.org"
<fabric@...>, Simeon MacMillen
Re: [Hyperledger Fabric] Purge Private Data - by individual
transaction - on trigger
Sent by: fabric@...
Hey Simeon, - You can purge using
the deletePrivateData function. https://hyperledger.github.io/fabric-chaincode-node/release-1.4/api/fabric-shim.ChaincodeStub.html#deletePrivateData__anchor - You can't purge a transaction on a
block, you purge ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your
- You can purge using the
- You can't purge a transaction on a
block, you purge the data that you inserted into the database
segunda-feira, 3 de maio de 2021 16:41:45 BRT, Simeon MacMillen
the documentation, Private Data can be purged after a
number of blocks, based on a Collection 'blockToLive' value.
- Is there
any other way of purging private data when the purge
quantity is not known in advance (e.g. schedule a purge after
- Is there
any way to purge only a single transaction in a channel?
I am looking
for how to "dispose" of data as needed based on customer or
regulations (e.g. ISO 9001:2015 184.108.40.206 d)).