The privacy paradox in blockchain: best procedures for knowledge management in crypto


Blockchains are touted as next technology databases that promise to facilitate safe and effective transactions amongst unknown functions. Having said that, one of the principal pillars of a blockchain’s security is the actuality that folks with entry to the blockchain can see the overall historical past of transactions executed on the blockchain – the outcome currently being that every single celebration has an equal opportunity to verify the precision of data stored. But if all the info saved on the blockchain can be seen by any person with accessibility to the blockchain, what takes place when that info qualifies as “personal information” underneath Canadian privateness laws? Businesses that collect use or disclose “personal information” are subject matter to a selection of compliance obligations, which as we established out below, can be tricky to reconcile with particular blockchain fundamentals.

What is personalized information?

In Gordon v Canada, the Federal Court described that particular data is facts that can be utilized to establish an individual if the information “permits” or “leads” to the attainable identification of the unique, whether on the basis of that data by itself, or when the info is put together with other facts from other accessible sources.1 Accordingly, a enterprise that basically “de-identifies” or “pseudonymizes” details may well still be matter to Canadian privateness legislation demands for the reason that there is a risk that such information can be “re-identified”. This poses a special obstacle to the builders of blockchain infrastructure, and the enterprises that work atop blockchain infrastructure, when the metadata that is necessarily ingrained in blockchain transactions might be re-identifiable. These types of metadata may possibly represent personal facts when it reveals the place transactions are despatched from, who they are sent to (not essentially the name of the recipient, but the handle of the recipient), how a great deal funds was despatched, and at what time.

Choose decentralized applications (DApps) for case in point, which are constructed from software program deployed on the blockchain (e.g., intelligent contracts) that are commonly created to execute enterprise functions for providers.2 The functions of the sensible contracts that proficiently aid the functionality of the DApps are typically made publicly available to each individual node in the blockchain community as “bytecode”, which can be reverse engineered to reveal the exact same transactional data as metadata in peer-to-peer transactions.

So, what does it suggest if this sort of data, stored and processed on community blockchain networks, qualifies as personalized facts? The consequence is relatively of a paradox.

The blockchain – privacy paradox

Information released to a blockchain are not able to be deleted, but most modern privateness legislation grant folks a “right to be forgotten”. How can an unique or facts matter work out their right to be neglected when the facts recorded on a blockchain’s ledger is long-lasting?

The really foundation of have faith in in decentralized networks outcomes from the transparency of the ledger. All members in community blockchain networks belief in the sanctity of the information and facts simply because they can all see and evaluate that info equally and in authentic time. But if all the information and facts is transparent, it gets available to any person and might, theoretically, be utilised by unknown actors for not known functions. Accordingly, how can an entity that leverages blockchain engineering to execute transactions and/or retail store info give the appropriate protections for information topics about how their info may possibly be employed or disclosed?

General public blockchains are intentionally decentralized so that there is not just one accountable entity. Moreover, the networks composed via community blockchains often span jurisdictions, and may perhaps consist of hundreds, thousands, or millions of people today who all technically have the means to notify updates to the blockchain (an capability akin to managerial choice creating). Beneath these circumstances, how can a regulator enforce actions against the supporters of a general public blockchain, when duties around maintenance, management, and ongoing progress are spread throughout a community of unassociated people today?

Best practices for managing personalized details in the blockchain context

No formal tips or interpretations of how to process personalized details on general public or private blockchains have been published in Canada. Even so, a wide interpretation of individual information and facts, which is customary less than Canadian legislation, could deter blockchain stakeholders from processing personalized info on community blockchains, because information on a blockchain is accessible by anybody with obtain to that blockchain, and distributed/saved among all nodes in the general public blockchain community.

In the private blockchain context, management of person rights about particular information is attainable because there are designated and accountable entities that control the quantity of stakeholders with entry to the blockchain. Less than this sort of conditions, stakeholders could need compliance with privacy regulations as a usually means of accessing the personal blockchain and its involved application(s). Stakeholders might also be removed from the network for failures to comply, and a adequately centralized non-public blockchain may well be overwritten by individuals through collaboration to react to particular privateness infringing incidents.

The stakeholders powering DApps in both public or private blockchain contexts also have the ability to proactively mitigate privateness regulation pitfalls by designing acceptable privacy procedures and implementing best tactics that require:

  • Combining on-chain and off-chain info

The blockchain application really should keep away from storing individual data as a payload on the blockchain (i.e., which include pinpointing data in the concept accompanying the payment itself), and in its place have blockchain transactions serve as mere tips or an entry regulate mechanism to much more quickly managed storage answers off-chain.

  • Making use of privateness centric technologies and cryptographic strategies

Encryption techniques at the moment remaining used by privateness-centric chains consist of ZK-SNARKS, Ring Confidential Transactions, and mixing procedures, all of which are intended to mask the id of the sender or recipient and/or allow individuals to affirm transactional legitimacy by cryptographically proving that they know one thing with no revealing the mother nature and identification of the details.

  • Conducting facts transformations

Other privacy enhancing encryption and destruction methods could be made use of to shield an individual’s privacy rights, these types of as hashing information or implementing other details transformation strategies to particular data, and revocation of entry legal rights to a blockchain software (or entire blockchain in a private blockchain network). Nevertheless, Canadian regulators have not addressed no matter whether these kinds of actions are enough to satisfy the needs of Canadian privacy legislation.

Companies leveraging blockchain technology to accumulate, use or disclose private data will have to consider care to stay knowledgeable and compliant to needs less than Canadian privateness legislation.

Share this post

Leave a Reply


%d bloggers like this: