Integrate Ceramic Network

[META-DREAMER]

Create a "hello world" integration of Ceramic / IDX into our repo (e.g. adding 3ID connect to login flow and setting / getting a field from the user profile)

https://twitter.com/ceramicnetwork/status/1354448316512284675?s=20

[dysbulic]

For reference, there is a profile record associated with an IDX, but it is currently empty. So, the first time a user logs in with IDX, maybe the system should copy their 3Box profile into IDX?

You can experiment in the web playground which instantiates the ceramic, idx, & did objects for manipulation using the development console.

Setting and retrieving the profile looks like:

• await idx.set('basicProfile', { name: 'Δυς' })
• await idx.get('basicProfile', did.id)

[dysbulic]

I checked with 3Box support and 3ID Connect will eventually handle migrating the user profile the first time a user uses IDX "closer to the mainnet release".

I created a tracking issue on the 3ID Connect repository.

[dysbulic]

The system which verifies accounts (Discord, Github, Twitter) and associates them with an IDX DID is identitylink-services. It is possible to run the services ourselves, but there will be a hosted version that is released closer to mainnet.

To support out current coverage, there would also need to be support for Discourse as well.

Github verification requires creating a Gist; Twitter tweeting. To verify on Discourse, a user could have to post a reply with their DID to a special thread dedicated to these verifications. It looks like there's an API for reading posts in a particular topic.

[dysbulic]

I forked identitylink-services to the MetaFam repo to look into adding Discourse support while still garnering my precious XP.

[dysbulic]

Another aspect of the IDX integration is using it as the basis for determining a Player's accounts for XP distribution.

I'm working on IDX as a SourceCred source of truth for ETHDenver.

[dysbulic]

The ETHDenver work is complete. I summarized the outstanding issues on SourceCred's Github. I'll copy that here for ease of access:

The current state of the work to use IDX to generate SourceCred aliases has been submitted to ETHDenver.

The development of IDX is not quite to the point that it is fully possible to complete this work.

• In Ceramic, the aka default document type alias for holding social account links doesn't exist yet. (basicProfile & cryptoAccounts are all that's defined.)
• There will be a hosted version of the IdentityLink system.
• There will be a UI for completing account verifications and a profile.

Additionally there are a few known issues with the current system:

• The attestation for the Verifiable Credential for an account link is not verified.
• If the verification process fails repeatedly, you can get an Invalid Challenge Token message. I assume from Redis returning a stale entry.
• The aliases are not serialized back out. Support was added this morning, but time didn't permit.
• Discourse is not a linkable account type.

Until the IDX support for linked accounts is a little better, I'm going to move this back to the Icebox.

[oed]

Thanks for the rundown @dysbulic!

In Ceramic, the aka default document type alias for holding social account links doesn't exist yet. (basicProfile & cryptoAccounts are all that's defined.)

This will be fixed within the next week or so.

There will be a hosted version of the IdentityLink system.

We will have this up and running within the next week as well (at least for twitter + github)

The attestation for the Verifiable Credential for an account link is not verified.

What do you mean by this? Not sure I follow.

If the verification process fails repeatedly, you can get an Invalid Challenge Token message. I assume from Redis returning a stale entry.

Interesting point. We will look into this. Tracking here: ceramicstudio/identitylink-services#15

[dysbulic]

The attestation for the Verifiable Credential for an account link is not verified.

What do you mean by this? Not sure I follow.

This is a limitation of the software I wrote. I'm not calling verifyJWS and checking the attestation author. I'm just creating aliases for any account links that exist, and that's not secure.