Product Development and Privacy Roadmap

Product Development Roadmap

HP Feature	Attribute	Phase 1	Phase 2
PoH Issuance Process	Supported VC	Unique human	Unique human identity
	VC Type	Boolean (Yes = human, No = non-human)	Customized
	Human Recognition	Palm Signature v1 (Visible Lights)	Palm Signature v2 (Visible + Infra-Red Lights)
	Identity Validation	N/A	Via zkKYC Solution
PoH Verification Process	Verification	Humanity zkProofers	Humanity zkProofers + Identity Validators
	Supported Methods	Direct VC sharing	Direct VC sharing + Customized ZK proof (VP) + API queries
VC Management	Private key storage	Key-share network	Key-Share Network
Interoperability	DApps on HP	Yes	Yes
	DApps on other L1/L2/L3 + Web 2.0/Physical world	No	Yes
Degree of Decentralization	Issuance	Centralized	Centralized + Decentralized
	VC Database	Centralized	(non-PII VCs), Decentralized (PII VCs), Partially decentralized, with sharding
	Humanity zkProofers	Decentralized	Decentralized

Phase 1 Privacy Table (“Who Can See What”)

HP Network Player	Encrypted Palm Signature	Private Key for Encrypted Palm Signature	{Address, Palm Signature} Combo	{Address, Unique-human VC} Combo
User (Local Device)	No	No	Yes to User’s own data	Yes to User’s own data
User (Decentralized Key-Share Network)	No	Yes, atomized and spread across storage nodes	No	No
Decentralized Storage (IPFS)	Yes	No	No	No
HP Core Platform (Issuer, Oracles, Credential Store)	Yes	No	Yes	Yes
Humanity zkProofers	No	No	No	Yes, in the form of ZK-proof during verification
Sequencer (for ZK-EVM rollup)	No	No	No	Yes, if granted access by User
Other L1/L2/L3 EDApps	No	No	No	Yes, if granted access by User
HP Blockchain/ General Public	No	No	No	Yes, if granted access by User

Phase 2 Privacy Table (“Who Can See What”)

HP Network Player	Physical Identity/ PII	Encrypted VC Metadata (PII + Non-PII)	Private Key for Encrypted VC Metadata (PII + Non-PII)	{Address, PII VC Metadata} Combo	{Address, Non-PII VC Metadata} Combo	{Address, Non-PII VC} Combo	{Address, PII VC} Combo
User (Local Device)	Yes	No	No	Yes to User’s own data	Yes to User’s own data	Yes to User’s own data	Yes to User’s own data
User (Decentralized Key-Share Network)	No	No	Yes, atomized and spread across storage nodes	No	No	No	No
Decentralized Storage (IPFS)	No	Yes	No	No	No	No	No
HP Core Platform (Oracles + Credential Store)	Yes, with sharding	Yes, with sharding	No	Yes, with sharding	Yes, with sharding	Yes, with sharding	Yes, with sharding
HP Smart Contract	No	Yes for non-PII VC, and only in the form of ZK Merkle Trees	No	No	Yes, in the form of ZK Merkle Trees	Yes, in the form of ZK Merkle Trees	No
Identity Validators (Issuer Nodes)	Yes, but only for Users with VC issued by the node	Yes, but only for Users with VC issued by the nodes	No	Yes, but only for Users with VC issued by the nodes during issuance	Yes, but only for Users with VC issued by the nodes during issuance	(Users with VC issued by the nodes) Yes (Other Users) Yes, if granted access by User	(Users with VC issued by the nodes) Yes (Other Users) Yes, if granted access by User
Humanity zkProofers	No	No	No	No	No	Yes, in the form of ZK-proof during verification	Yes, in the form of ZK-proof during verification
Sequencer (for ZK-EVM rollup)	No	No	No	No	No	Yes, if granted access by User	Yes, if granted access by User
Other L2/L3 Enterprise Applications	No	No	No	No	No	Yes, if granted access by User	Yes, if granted access by User
HP Blockchain/ General Public	No	No	No	No	No	Yes, if granted access by User	Yes, if granted access by User