I'd propose using our current view of physical reality to own a subset of the UIID + version field if new physics is discovered.

10-20 bits: version/epoch

10-20 bits: cosmic region

40 bits: galaxy ID

40 bits: stellar/planetary address

64 bits: local timestamp

This avoids the potentially pathological long chain of provenance, and also encodes coordinates into it.

Every billion years or so it probably makes sense to re-partion.

▲ skvmb 25 minutes ago | parent | next [-]

offset length

  00     04:    Version + Flags
  04     08:    Timestamp (uint64)
  12     16:    Node/Agent Hash
  28     16:    Namespace Hash
  44     32:    Random Entropy
  76     20:    Extra / Extension
  96     32:    Integrity Hash

Total: 128bytes

▲ rbanffy 4 hours ago | parent | prev [-]

As for coordinates, don’t forget galaxies are clouds of stars flowing around and interacting with each other.

▲

dylan604 3 hours ago | parent [-]

That's the problem with address type of systems is that they expect the object at that location to always be at that location. How do you encode the orbital speed, radius of orbit for not just the object, but also the object it is orbiting will need the same info as it is also in motion, then that object's parent galaxy's motion. Ugh, now I need a nap to calm down a bit.

	▲	rbanffy 3 hours ago \| parent [-]
		You could estimate when the object was labelled by the coordinates used. But where is the Greenwich meridian for the Milky Way?