---
# System prepended metadata

title: dPIDs

---

# Current DOI problmes
*  **resolving operation of the given PID is not transparent**
* The **entry point** of the resolver is provided only by the **core authority** itself, so it should be considered one and the only, despite the existence of proxies and balancers.
*  reverse lookup for the given PID  is not possible
*  singular point of failure
*  Accessibility: reproducibility of the PID itself increases complexity on the client side
* **PID production and resolving algorithms are closed and/or declared proprietary**
* PID prefix/affix is a subject of decision made by the provider


Ways to avoid the described problems
- At least the most significant part of the **PID could be reproducible from the data on the client side via an open algorithm.**
- If the PID database used as the main reference of the given PID subset is distributed, verifiable incremental updates and local resolution are possible.
- The access control and requesting models should be defined using the individual cryptographic keys of the data producers and clients, but not the PID providers.


 # PIDs aim
 - uniform, reliable, convenient, self-contained way to produce, verify, resolve or convert PIDs.
 
 - **Decentralization**. The infrastructure should not depend on any kind of central authority or organisation that can mangle, censor or intercept the resolving/conversion of PIDs.
- **Reliability**. The infrastructure must be resilient to failures, attacks, and changes in underlying networks or infrastructures.
- **Transparency**. The infrastructure must be open and public in all aspects, including specifications, working policies and source code so that any node on the network can check the history and current state of PID registration, conversion and resolution.
- **Safety**. The infrastructure should prevent unauthorized or abusive addition, modification, or deletion of PIDs, and provide ratification mechanisms to authorize these operations in a convenient and transparent way.
- **Flexibility**. The infrastructure must allow PIDs within the node-owned subsets to be added, changed or deleted by the agreement of all decentralized network nodes that have the right to publish them, without the need to change code or system parameters.
- **FAIR-compliance.** The infrastructure should implement all the described features with a maximal level of compliance with FAIR Data Management Principles, inclueding all kinds of underlying access control and provenance.


- **IPNS** - Interplanatory Name System

- The **InterPlanetary File System (IPFS)** is a protocol, hypermedia and file sharing peer-to-peer network for storing and sharing data in a distributed file system. By using content-addressing, IPFS uniquely identifies each file in a gloA content identifier, or CIDbal namespace that connects IPFS hosts, creating a resilient system of file storage and sharing.


**A content identifier, or CID**, is a label used to point to material in IPFS
- CIDs are based on the content’s cryptographic hash. 


- A single DOI could unfold into an entire file system with individual PIDs for machine-actionable digital objects and resolve deterministically to their mapped resource.
- Decentralized Identifiers. Decentralized Identifiers (DIDs) enable verifiable, decentralized digital identity. A DID can refer to any target (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the DID. The design enables the controller of a DID to prove control over it without requiring permission from any other party, allowing trustable interactions.
