You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm leaning towards a local array of arbitrary, user-defined strings with DIDs as keys as an object in local memory
1.) portability/sync between different credible form factors may be required later so we may need to pick a type of object/array that works across contexts.
2.) eventually we might need to align this with: https://identity.foundation/faq/#what-exactly-is-a-connection-is-it-a-transport-is-it-ephemeral
and/or https://w3c-ccg.github.io/universal-wallet-interop-spec/#connection
passive interop might be fine-- if our data model connection doesn't align perfectly with the Aries one, it's fine, as long as it's relatively feasible to translate between the two on im/export.
The text was updated successfully, but these errors were encountered:
I'm leaning towards a local array of arbitrary, user-defined strings with DIDs as keys as an object in local memory
1.) portability/sync between different credible form factors may be required later so we may need to pick a type of object/array that works across contexts.
2.) eventually we might need to align this with:
https://identity.foundation/faq/#what-exactly-is-a-connection-is-it-a-transport-is-it-ephemeral
and/or
https://w3c-ccg.github.io/universal-wallet-interop-spec/#connection
passive interop might be fine-- if our data model connection doesn't align perfectly with the Aries one, it's fine, as long as it's relatively feasible to translate between the two on im/export.
The text was updated successfully, but these errors were encountered: