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
The 3ID Account Module should be a package in the js-ceramic repo. The result of this story should be a spec for the api of this package. The module should be able to use both a ceramic-core instance and a ceramic-http-client instance to interact with ceramic.
Rough API:
new ThreeIDAccount (did: string, ceramic: Ceramic)
setDIDProvider(provider: any)
DID: string
didDocument: DIDDocument (class for interacting with 3ID doctype)
Should be backwards compatible. Can we use js-ipfs-did-document? (might need some changes to ceramic 3id doctype)
accountLinks: AccountLinks (class for interacting with account links tile)
sources: Sources (class for interacting with sources tile)
services: Services (class for interacting with services tile)
keychain: Keychain (class for interacting with keychain tile)
profile: Profile (class for interacting with profile tile)
Maybe needs an async method for constructing?
The api above describes the high level interface. For this sprint we should focus on building out the way to interact with the DID Document and AccountLinks primarily (and account tile in the background). All of the classes for the different tiles needs their own api.
Make sure to coordinate with @zachferland on the functionality that the IdentityWallet provides though the 3idProvider interface.
The text was updated successfully, but these errors were encountered:
The 3ID Account Module should be a package in the js-ceramic repo. The result of this story should be a spec for the api of this package. The module should be able to use both a
ceramic-core
instance and aceramic-http-client
instance to interact with ceramic.Rough API:
Maybe needs an async method for constructing?
The api above describes the high level interface. For this sprint we should focus on building out the way to interact with the DID Document and AccountLinks primarily (and account tile in the background). All of the classes for the different tiles needs their own api.
Make sure to coordinate with @zachferland on the functionality that the IdentityWallet provides though the 3idProvider interface.
The text was updated successfully, but these errors were encountered: