<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Private Digital Identity on Blockchain</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Tom</forename><surname>Hamer</surname></persName>
							<email>tomhamer@live.com</email>
							<affiliation key="aff0">
								<orgName type="department">College of Engineering and Computer Science</orgName>
								<orgName type="institution">The Australian National University</orgName>
								<address>
									<postCode>ACT 0200</postCode>
									<settlement>Canberra</settlement>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Kerry</forename><surname>Taylor</surname></persName>
							<email>kerry.taylor@anu.edu.au</email>
							<affiliation key="aff0">
								<orgName type="department">College of Engineering and Computer Science</orgName>
								<orgName type="institution">The Australian National University</orgName>
								<address>
									<postCode>ACT 0200</postCode>
									<settlement>Canberra</settlement>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Kee</forename><forename type="middle">Siong</forename><surname>Ng</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">College of Engineering and Computer Science</orgName>
								<orgName type="institution">The Australian National University</orgName>
								<address>
									<postCode>ACT 0200</postCode>
									<settlement>Canberra</settlement>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Alwen</forename><surname>Tiu</surname></persName>
							<email>alwen.tiu@anu.edu.au</email>
							<affiliation key="aff0">
								<orgName type="department">College of Engineering and Computer Science</orgName>
								<orgName type="institution">The Australian National University</orgName>
								<address>
									<postCode>ACT 0200</postCode>
									<settlement>Canberra</settlement>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Private Digital Identity on Blockchain</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">381FD4900819E5727EDC4DE699F414F7</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T09:04+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Verifiable Claims</term>
					<term>Blockchain</term>
					<term>Cancelable Biometrics</term>
					<term>Homomorphic Signature</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>For many identification systems, including those in government, finance and healthcare, it is critical that at most one identity exists for each human individual within a given system. Many existing approaches identify individuals through an exchange of verifiable documents attesting to basic identification information. However, the same basic information is collected for identification in almost every system, meaning that persons are linkable across different identity systems and are not in control of how their identity is used. We propose Unique Self-Sovereign Identity, (USI), combining Cancelable Biometrics [6] and W3C Verifiable Claims [8] to achieve privacy preserving and non-linkable identification, with guarantees against double enrolment with any system. Because our protocol is based on biometrics, it permits individuals to enrol without official identification documents. Our protocol can be used in a wide range of situations, offering data security for large organisations, access to basic services for over one billion people who lack official identifying documents, and personal identity control for all individuals.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.1">Motivation</head><p>One fundamental aspect of many human identification systems is that for each individual, no more than one identity exists <ref type="bibr" target="#b0">[1]</ref>. This is often due to an unfair advantage that can be gained by a malicious individual having two identities, for example, they may be able to fraudulently access additional credit at a bank <ref type="bibr" target="#b1">[2]</ref>. However, preventing malicious double enrolment is difficult. Many existing approaches uniquely identify individuals through an exchange of verifiable documents and basic identification information <ref type="bibr" target="#b2">[3]</ref>. However, these traditional identification methods have a number of fundamental drawbacks:</p><p>1. Through organisations storing basic identity attributes such as name, birthdate and address, individuals can be linked across multiple independent uses of their identity, without consent.</p><p>2. When organisations requiring identity verification store a large amount of information about each individual for identification purposes, it makes the system vulnerable to attacks, as it is easy for a hacker who obtains access to the internal records to learn many details about each individual. Worse still, basic attributes such as address cannot easily be cancelled or changed and so a fresh identity is very hard to establish.</p><p>3. Over 1 billion individuals worldwide lack a form of officially recognised identity such as a passport <ref type="bibr" target="#b3">[4]</ref>, which makes it very difficult to enrol with service providers-such as banks, which need to uniquely identify individuals.</p><p>We propose a decentralised, privacy-preserving identity system which can identify individuals through a bijective mapping from individuals to identifiers used in a specific organisational context. It is designed to give individuals control over their own identity and shared information but to give organisations a guarantee of uniqueness. To our knowledge, such a privacy preserving biometric identification system does not exist in the literature.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.2">Related Work</head><p>Biometrics are a useful tool in identification of individuals because biometric signatures, such as fingerprints, are unique to each human <ref type="bibr" target="#b4">[5]</ref>. Further, they do not depend on an individual needing to hold official identity documents. Cancelable biometrics have been created as a method to protect biometric signatures; rather than storing the full biometric in identification databases, biometrics are non-invertibly transformed to obfuscate the original biometric signature <ref type="bibr" target="#b5">[6]</ref>, and only the obfuscated version is stored. However, one problem with current cancelable biometric protocols is that the individual must trust the organisation receiving their biometric signature to correctly transform and securely manage the biometric signatures.</p><p>Homomorphic signatures allow a verifier to prove that a calculation has been done correctly without having to access the underlying data <ref type="bibr" target="#b6">[7]</ref>. We propose utilising homomorphic signatures as a proof mechanism to allow the individual to obfuscate their own biometric signature on their personal device through applying a specific non-invertable transformation that is requested by the organisation wanting to identify the individual. The authors are unaware of previous research proposing the use of homomorphic signatures to prove the validity of cancelable biometrics. For the first time, we propose that the combination of these techniques enables self-sovereign identity.</p><p>The W3C, an international standards organization, has introduced Distributed Identifiers (DIDs) and Verifiable Claims. DIDs are linked to DID documents, which store mechanisms used to authenticate the DID, service endpoints, and other claims <ref type="bibr" target="#b7">[8]</ref>. Using DIDs, the W3C aims to create a standard for individuals and organizations to control their own identity. W3C Verifiable Claims are a mechanism to express credentials on the Web in way that is cryptographically secure, privacy respecting, and machine-verifiable <ref type="bibr" target="#b8">[9]</ref>. The Sovrin foundation has used DID and Verifiable claims to create a Blockchain based Identity System <ref type="bibr" target="#b9">[10]</ref>, which enables distributed management of public keys and revocation of verifiable claims. Similarly, we propose to facilitate transfer of obfuscated biometrics using Blockchain-based verifiable claims.</p><p>Self-sovereign identity can be defined as "the concept of individuals or organizations having sole ownership of their digital and analogue identities, and control over how their personal data is shared and used" <ref type="bibr" target="#b10">[11]</ref>. A number of organisations including The Sovrin Foundation <ref type="bibr" target="#b9">[10]</ref>, Civic Ledger <ref type="bibr" target="#b12">[13]</ref> and uPort <ref type="bibr" target="#b13">[14]</ref> have recently launched of self-sovereign identity protocols. The Sovrin Foundation has been involved in the development of ID2020 which aims to create an open and human-centric approach to identity <ref type="bibr" target="#b11">[12]</ref>. They suggest benefits including no physical papers and the convenience of biometric authentication. Other attempts, such as Civic ledger's solution, depend on the individual holding official identity documents such as passports to enrol with their system, which is problematic for displaced persons and others.</p><p>No self-sovereign identity schemes are currently available which offer nonlinkability of individually-controlled identities. Where existing protocols offer the capacity to use biometric signatures, they do not allow individuals to noninvertably transform their biometric signature before it is sent, and therefore do not protect the privacy of personal biometrics.</p><p>We propose the concept of Unique Self-Sovereign Identity, or USI. USI means that an individual can have at most one identity in a particular context, but identities cannot be linked between contexts without permission from the individual. Therefore, individuals can be uniquely identified but still have control over their personal identifying data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Solution Sketch</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Our USI protocol</head><p>We define three key roles: Individual: a human who wants to be identified by a Service Provider. Service Provider: an organisation requiring its individual users to complete identity verification for access to services. The service provider commits to requiring a specific variety of biometric for all of its users. Trusted Organisation: an organisation within the trust network of both a service provider and an individual. Service providers trust these organisations to ensure that the biometric signatures are accurate and individuals trust these organisations to destroy their biometric signature immediately after use. Trusted organisations maintain public keys for each variety of biometric signature they sign, meaning that service providers are able to verify that the biometric signature is of the variety they require.</p><p>In our protocol, each individual is identified for each service provider by a cancelable (non-invertibly transformed) version of their biometric signature. To achieve this non-invertibility, we use a Partial Discrete Fourier Transform for non-linkable biometrics <ref type="bibr" target="#b5">[6]</ref>. We extend existing cancelable biometric schemes so that the service provider never has access to the complete biometric signature of each individual. To enable this, we use fully homomorphic signatures <ref type="bibr" target="#b6">[7]</ref> to prove the validity and correctness of a biometric signature which is already Fig. <ref type="figure">1</ref>: Our USI Protocol showing the interactions between an Individual represented by a User Device, a Trusted Organisation, and several Service Providers non-invertibly transformed by the individual before it is sent. Finally, the solution uses a Blockchain W3C standard Verifiable claims system <ref type="bibr" target="#b9">[10]</ref>, where our homomorphic signature acts as the proof mechanism, meaning that individual biometric signatures can be revoked when needed, and requiring that the public key of the Trusted Organisation is publicly available. Our protocol does not address authentication, that can employ conventional means such as username and password. Our protocol is as follows (see figure <ref type="figure">1</ref>).</p><p>1. The individual enrols for an identity with a trusted organisation C of their choice (see Algorithm 1). C collects finger print and vein scans, ensuring that the biometrics are collected accurately and are truly the biometrics of the individual. The assurance process will be determined by C's own policy, but will probably include human supervision. The individual stores the biometrics together with a corresponding signature which is provided by C. C must not store the biometrics-and is trusted not to by the individual. C has its public key available on the Blockchain Verifiable Claims system. C adds required randomly generated public parameters for homomorphic signature verification to the ledger, and adds the signature for the biometric to a public revocation register, attesting to the validity of the biometric.</p><p>2. The individual wants to enrol with a service provider B i and B i requires proof that they have not enrolled previously with B i . To check, B i requests an P-DFT transform <ref type="bibr" target="#b5">[6]</ref> with the trusted organisation's specific parameters, from the individual. These parameters are derived using the public key of B i and are therefore not used by any other organisation requiring identity verification.</p><p>The individual computes the result of the transformation and sends it to B i , with a fully homomorphic signature under that P-DFT, along with the name of trusted organisation C for lookup in the Blockchain Verifiable Claims Public Key register. Verifying that the calculation was done correctly does not require the individual to send the initial signature from C or the individual's raw biometric.</p><p>3. Service provider B i looks up trusted organisation C's public key on-chain and verifies the homomorphic signature against the transformed biometrics sent by the individual, the public parameters, and the public key of C (see <ref type="bibr">Algorithm 2)</ref>. If it holds as valid, and the proof of non-revocation holds, then B i checks all current biometric vectors in its database for any vectors within a thresholded similarity of the provided biometric. If it finds no matches, then B i has verified that the individual has not previously enrolled.</p><p>Algorithm 1 Trusted Organisation Creates Verifiable Claim for Individual to Store 1: procedure VCgen(pk,device) 2:</p><p>bV ec ← retrieve(device) //retrieve processed biometric vector for individual from trusted organisation's external device 3:</p><p>l ← length of bVec 4:</p><p>V ← randomly generate l public parameters 5:</p><p>x ← Sign sk (bVec)//trusted organisation homomorphically signs the biometric vector using its secret key 6:</p><p>writeToChain(V) //write the public parameters V onto the Blockchain 7:</p><p>claim ← generate a verifiable claim from trusted organisation's metadata [9] 8:</p><p>claim.proof ← generate a proof property from signature x 9:</p><p>addToNonRevocationRegister(claim) //add the claim to a public nonrevocation register 10: cleanup() //critically, trusted organisation must delete bVec, the user's raw biometric vector 11: return claim</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Features of our USI System</head><p>Self-sovereignty: The identity holder has complete control over storage and use of their identity. This is provided through the use of verifiable claims, and the homomorphic proof mechanism, which allows individuals to reliably store their own biometric signature <ref type="bibr" target="#b8">[9]</ref>, <ref type="bibr" target="#b6">[7]</ref>.</p><p>Privacy and Non-linkability: The verifier, who receives a non-invertibly transformed version of the biometric is unable to reverse the transformation and discover the individual's actual biometric signature. Provided that the transformations have different parameters, cross matching of biometrics is impossible. These privacy and non-linkability features are provided by definition through cancelable biometrics <ref type="bibr" target="#b4">[5]</ref>. Further work is required on the non-linkability of the proof mechanism as it is in some cases possible for proofs to be linked via the Algorithm 2 Service Provider Enrols Individual 1: procedure AddNewUser(pi, biometricVariety, similarityThreshold ) //pi is unique to each service provider 2:</p><p>claimP res ← request verifiable claim for P-DFT biometric transform from user with parameters pi 3:</p><p>sig ← claimP res.proof.proof V alue // extract the transformed biometric from the claim presentation <ref type="bibr" target="#b8">[9]</ref> 4:</p><p>transbV ec ← claimP res.credentialSubject.transf ormedBiometric // extract the proof from the verifiable claim presentation <ref type="bibr" target="#b8">[9]</ref> 5:</p><p>V, pk ← retrieve(biometricVariety) //get public parameters V and trusted organisation's public key for the biometric typepk from Blockchain 6:</p><p>if not valid pk (V, sig, transbV ec) or isRevoked(claimPres) then 7:</p><p>//if the homomorphic signature does not hold, or the claim has been revoked 8:</p><p>return false 9:</p><p>for transformedBiometric in database do 10:</p><p>if transbV ec.isSimilar, similarityThreshold(transf ormedBiometric) then 11:</p><p>return false //if a similar biometric exists already then reject. 12: addNewUserToDb(transbVec) //save transformed biometric 13:</p><p>return true //success public parameters. This issue may be rectified either through Gorbunov's multidata signing scheme <ref type="bibr" target="#b6">[7]</ref> or by having the trusted organisation issue a number of public parameters to each individual, and each one could be used to establish an unlinkable identity. Unique Identification: An individual can create as many signed biometrics or identities as they like and enrol with any trusted organisation. The transformation will always map them back to the same identifier, with an error rate that is dependant on the quality of the matching algorithm and the number of individuals in the system. This is irrespective of the trusted organisation and is a result of biometric classification algorithms. The error rate arises from the imprecise nature of biometric feature extraction. Note that each Service Provider must require the same variety of biometric from all of their clients, or unique identification is impossible. <ref type="bibr" target="#b4">[5]</ref>. Decentralisation: The trusted organisations do not have to communicate or be in consensus for the Unique Identification property to hold. This is enabled through Blockchain technology, which allows public keys and parameters to be stored without a central authority <ref type="bibr" target="#b9">[10]</ref>.</p><p>Biometrically Derived: Biometrics are used, meaning that the system does not depend on individuals holding previous identity documents in order to enrol.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Conclusion</head><p>We describe a USI identity system which is capable of addressing number of significant current challenges in identity management. A key area for further work is improving the performance of biometric identification. The error rate could prove to be an obstacle due to the compounding of errors in biometric identification systems <ref type="bibr" target="#b14">[15]</ref>. The need to trust the trusted organisation's management of biometric data is a potential drawback of our protocol that could be addressed by legal or social mechanisms. Personal enrolment with the trusted organisation potentially exposes information about identity that could be exploited. However, we believe that this system could be feasible for distributed and privacy preserving identification at large scale. Future work includes a reference implementation and security analysis.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="4,169.35,115.84,276.67,200.48" type="bitmap" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><surname>Unhcr</surname></persName>
		</author>
		<title level="m">UNHCR Resettlement Handbook</title>
				<meeting><address><addrLine>Geneva</addrLine></address></meeting>
		<imprint>
			<publisher>UNHCR -the UN Refugee Agency</publisher>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Counteracting Identity Fraud in the Information Age: The Identity Theft and Assumption Deterrence Act</title>
		<author>
			<persName><forename type="first">K</forename><surname>Saunders</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Zucker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Review of Law, Computers &amp; Technology</title>
				<imprint>
			<publisher>Routledge</publisher>
			<date type="published" when="1999">1999. 1999</date>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="183" to="192" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">KYC Optimization Using Distributed Ledger Technology</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">P</forename><surname>Moyano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Ross</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Business &amp; Information Systems Engineering</title>
		<imprint>
			<biblScope unit="volume">59</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="411" to="423" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">G</forename><surname>Kour</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Saabne</surname></persName>
		</author>
		<ptr target="http://id4d.worldbank.org/global-dataset/visualization" />
		<title level="m">Global Identification Challenge by the Numbers</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Can Cancelable Biometrics Preserve Privacy? Biometric Technology Today</title>
		<author>
			<persName><forename type="first">P</forename><surname>Punithavathi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Subbiah</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017. 2017</date>
			<biblScope unit="page" from="8" to="11" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">A fingerprint and finger-vein based cancelable multi-biometric system</title>
		<author>
			<persName><forename type="first">W</forename><surname>Yang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Pattern Recognition</title>
		<imprint>
			<biblScope unit="volume">78</biblScope>
			<biblScope unit="page" from="242" to="251" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Leveled Fully Homomorphic Signatures from Standard Lattices</title>
		<author>
			<persName><forename type="first">S</forename><surname>Gorbunov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vaikuntanathan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Wichs</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">STOC&apos;15 Proceedings of the forty-seventh annual ACM symposium on Theory of Computing</title>
				<meeting><address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="469" to="477" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<author>
			<persName><forename type="first">D</forename><surname>Reed</surname></persName>
		</author>
		<ptr target="https://w3c-ccg.github.io/did-spec/" />
		<title level="m">DID Spec</title>
				<imprint>
			<date type="published" when="2019-07-30">2019. 30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Sporny</surname></persName>
		</author>
		<ptr target="https://www.w3.org/TR/vc-data-model/" />
		<title level="m">Verifiable Credentials Data Model</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><surname>Sovrin</surname></persName>
		</author>
		<ptr target="https://sovrin.org/wp-content/uploads/Sovrin-Protocol-and-Token-White-Paper.pdf" />
		<title level="m">Sovrin Protocol and Token White Paper</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><surname>Metadium</surname></persName>
		</author>
		<ptr target="https://medium.com/metadium/introduction-to-self-sovereign-identity-and-its-10-guiding-principles-97c1ba603872" />
		<title level="m">Introduction to Self-Sovereign Identity and Its 10 Guiding Principles</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><surname>Leong</surname></persName>
		</author>
		<ptr target="https://www.accenture.com/us-en/insight-blockchain-id2020" />
		<title level="m">ID2020: Digital Identity</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<ptr target="https://tokensale.civic.com/CivicTokenSaleWhitePaper.pdf" />
		<title level="m">Civic Whitepaper</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
		<respStmt>
			<orgName>Civic Technologies</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<author>
			<persName><forename type="first">P</forename><surname>Dunphy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Petitcolas</surname></persName>
		</author>
		<ptr target="https://arxiv.org/pdf/1801.03294.pdf" />
		<title level="m">A First Look at Identity Management Schemes on the Blockchain</title>
				<imprint>
			<date type="published" when="2019-07-30">30 July 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">N</forename><surname>Pato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">I</forename><surname>Millett</surname></persName>
		</author>
		<title level="m">Biometric Recognition: Challenges and Opportunities</title>
				<meeting><address><addrLine>Washington, DC</addrLine></address></meeting>
		<imprint>
			<publisher>The National Academies Press</publisher>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
