LogoLogo
  • 🔮DeSci Codex
    • 🕊️Overview
    • 🏁Design goals
  • Data layer definition
    • 🌳Introduction to Sidetree
    • 👾Entities
      • 🧑‍🔬Profiles
      • 📗Research object
      • 📄Research component
      • 🏅Claim
      • 📯Attestation
      • 💬Annotation
      • 🔁Relational information
        • 💫Research field
        • 🤝Contributor
        • 👉Reference
    • 🏷️Metadata
  • Protocol operation
    • 🎣Deterministic resolution
    • 🧑‍🤝‍🧑Participation
      • 📚Network operators
      • 🔮Gateway providers
      • 📦Data services
      • 🧲Advanced indexing
      • 🗺️dPID resolvers
      • 🛂Identity verifiers
      • 🏷️Legacy PID mapping
  • Implementation
    • 🌊Ceramic & ComposeDB
    • 🛠️Reference implementation
    • ⚠️Current limitations
      • 🤞Mutability quirks
      • 🧐Invalid data
      • ⌛Timestamps
      • 🎟️Delegation of permissions
  • Future work
    • 🧩Feature wishlist
    • 🛣️Roadmap
Powered by GitBook
On this page
  1. Protocol operation
  2. Participation

dPID resolvers

Short, persistent identifiers for the protocol

Last updated 1 year ago

While the protocol already has unique and persistent identifiers for nodes (including versioning), they are quite verbose, being dependent on hashing. The separate system allows claiming a short identifier. This is done in a smart contract, which permanently maps the PID to a node in the protocol graph. This contract is open for anyone to interact with, the protocol data is open, and the resolver service will be released as free, open source software.

Going from dPID URL to content is where the resolver comes in: first finding the correct protocol node from the mapping in the smart contract, then following the steps in Deterministic resolution to point to the target content.

is one such operational resolver, but for resilience there is a need for more of them. If one resolver is down because of technical issues, the company running it no longer exists, or similar reasons, one just needs to use a different resolver to fetch the same dPID.

The dPID registry is currently operating according to the previous version of the protocol, and a planned future upgrade is required for supporting identifiers of the protocol implementation. When this is done, a resolver application ready for deployment will be released with a free license.

🧑‍🤝‍🧑
🗺️
dPID
dpid.org