---
# System prepended metadata

title: ID Hub Syncing

---

# ID Hub Syncing

No implementation should be forced. All decisions made by S&C WG should be 
for a spec on how syncing should work, not implementation specifics.

Syncing is *not* important for Workday right now. No other implementations of idhubs exist so who would we sync with.

Workday should build a hub with syncing in mind, but not worry about an implementation of sync until the community comes to an agreement about how syncing should work.

Commits seem to be a good hook for sync capability. Provide replayability for the hub as well as audit history.

We don't care as much about commits right now. Latest commit is the version we use. When commits do matter, we can use the object as is as the "base commit".

Bjorn needs to weigh in on how involved Workday should be in the WG.
- Do we want to Open Source our id-hub implementation?
- What are we expecting from the Working Group?
    - Interoperability
    - need somebody else with skin in the game
    - 2 scenarios: 
        - DID from another network but a did that points to workday idhub
            - did:work (user's identity), did:ion idhub
            - disassociate the DID from the hub location
        - did:work and did:ion idhubs. How do they coexist? (syncing)
            - syning two hubs from different ledger networks
Push for an interoperability between two distinct implementations of the idhub spec.

We need to do things like fully uptake JWE and other internal implementation choices to reflect the direction that Workday wants to take idhubs.

1-2 years from open source
- Ratified standard is a prerequisite

Stephen - "In 6 months what do members of the group expect? Is Workday going to be the only idhub by then?"

Protocols to investigate: (eventually)
 - SWIM
 - Scuttlebutt
 - Dat

