Skip to content

Frozen (did:ad:frozen blake3 hash) resources #1208

Open

Description

@joepio

Relevant: #1139

We recently added a bunch of did:ad types:

  • did:ad:{genesis} the most common type, uses genesis commit to identity initial signature.
  • did:ad:blob a blake3 hash that identifies a binary blob (e.g. file)
  • did:ad:agent an ed25519 public key, identifies an agent

I think we should add a new one: did:ad:frozen, which refers to a static version of some json-ad resource.

This is useful for:

  • Pointing to a specific version of some thing
  • Cheaper verification: no need to check signatures / commits
  • Cheaper creation: creating resources WITHOUT any agent (no sighnature)
  • In the schema context these advantages are important Schema creation in-code #1207

But a big question is: how do we resolve these? Of course any AtomicServer's /did endpoint will be able to resolve them if they're on the server. But what if a server doesn't have that specific resource? See #1146

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions