It takes time to invoke MetaMawk and load data. While it happens a user is in limbo. Unclear what is happening.

Links support EIP1271, but signing requests for eoa signers for EIP1271 needed additional flag

ceramicnetwork/js-3id-blockchain-utils@18ae58d

Make sure this change made into new library, and that opts can get passed through authprovider. Optionally see if anyway we can support without flag, especially with when using walletconnect

Same as 3id-connect, bundle, push to s3 at another path

Make explicit each case/flow that is supported, and split out clear paths in code base with descriptions

Lots of if x and y, but not z do this, etc and not clear how they map to end user flow or what condition they support.

This will make it easier for others to contribute after.

Pinned docker image to hash, since we were having problems with dependencies in CI. With the pinned version we may have other issues with upgrading the test dependencies the future.

good to do sooner than later, may change/break tests which took some time to get good mock data for, and best to do before more testing and everyone using with test app

we have different build configs for development and deployment, add an additional for prod vs dev. We already have dev pipeline, but should be configured to use dev-unstable (probably), and didv0 migration enabled.

Due to past bugs in 3box, there is a few instances where it is not easy to migrate the dids. As implemented the migration will just fail with error, and then reprompt user to create a new instead.

For known failures we can detect ahead of time, we could instead just default to creating a new did without any migration prompts. This is likley best.

Example of an account we cant easily migrate

DID owned by ADDRESS_ONE
https://ipfs.3box.io/did-doc?cid=bafyreihggvtidyvqw42hitvj3veki7wmhnchuok5mcjlosgu5532mrkcya

LINK DID -> ADDRESS_TWO
https://beta.3box.io/address-server/odbAddress/0x12396e8b57b1a64ed18aa6fc2f5fec75ba55de07

It is diffucult to make any default choices about migration (other than just create new), since the user may not want ADDRESS_TWO profile added to ADDRESS_ONE, this may have been linked by accident. And unfortunately when authenticating with ADDRESS_ONE no link will be found and a new did will be created anyways

the permission func is getting domain undefined on first request (not first req per domain, but first when creating local auth did data), so its not properly stored locally, then on second loading domain is passed, thinking it has no permissions, it asks again

As a 3Box Labs developer, I want the 3ID Connect application to be built using React instead of HTML templates so that I can add more rich functionality such as making IDX queries.

Spinner maybe.

Text in permission modal until we have actual permissions
Determine if we are ok with any kind of customization by app in modal
When create account, combine permission modal with account create/link or just remove (will remove at least one prompt)

Currently:
caip10 -> did
did -> seed

Not freindly for key rotations, auth data may not be necessarily either. Need to change implementation once key rotations are more widely supported and/or make additional network requests.

"background"/non-interactive auth where an app could check if it's allowed to connect directly or needs user consent (= showing user prompts), so the app's UX can be adapted accordingly.

Now it makes sense to replace 3id-blockchain-utils with linking utils from ceramic repo.

Reasons:

• 3id-blockchain-utils package is effectively deprecated AFAIK,
• new linking utils package is lighter, thus making the resulting 3id-connect lighter too.

Make explicit each case/flow that is supported, and split out clear paths in code base with descriptions

Lots of if x and y, but not z do this, etc and not clear how they map to end user flow or what condition they support.

This will make it easier for others to contribute after.

User story: As a developer, I want my users to enjoy a seamless and secure authentication experience so that I can increase trust with users and improve conversion in my onboarding/login flow.

Goals:

• Increase user trust by providing a more transparent and user-friendly experience
• Reduce developer objections (and rolling their own 3ID DID Provider interface solutions) by providing basic customization and a better user experience

Definition of done:

We will know this initiative is done by:

• All stories are agreed on and completed
• Sharing it with users and getting positive feedback
• Sharing it with developers and getting positive feedback
• Testing the implementation to ensure everything works smoothly

The tutorial hosted here states that the Filecoin or EOS blockchains are already supported for authentication, but 3id-connect package doesn't export any FilecoinAuthProvider or smth similar. Do you have any additional instructions or hints about how to add authentication using Ethereum, Filecoin, Cosmos or EOS?

provider, rpc methods and interface for UIs to implement

Sync with @zachferland on exactly what to do!

Mostly been used in desktop, no need to optimize mobile design yet, but confirm that it minimally works (visually) and that it works with major mobile wallets.

Most times this is instant, but the case of account already exist in network, not in local storage and first time using app will take some time and needs visual feedback

Feedback already exist for create and migrate modals, just not the permissions modal.

• allow configuration by url and network (ie mainnet -> app.3idconnect.org, clay-testnet -> app-dev.3idconnect.org)
• allow ceramic api url be passed for prod build as well
• have pipeline deploy dev with testnet, master with mainnet

Add a "Stay connected" option in the prompt so that 3ID Connect would persist the last time this consent prompt showed up and only ask for consent again at a certain frequency (every 2 weeks for example).

Make explicit each case/flow that is supported, and split out clear paths in code base with descriptions

Lots of if x and y, but not z do this, etc and not clear how they map to end user flow or what condition they support.

This will make it easier for others to contribute after.

Just confirm configs aligned for management app and 3id-connect, and add option to config for mainnet (consider if any other parts of deployment, ie infra will have to change as well)

It fails on setDIDProvider. The 3idconnect version is alpha 11 but it was also failing with alpha 6.
If you need more details you can see the code here: https://github.com/DistributedTown/distributed-town-skill-wallet/tree/skill-wallet-ref

const [ceramic, provider] = await Promise.all([ceramicPromise, getProvider()])
  console.log('1');
  await ceramic.setDIDProvider(provider)
  console.log('2');
  const idx = createIDX(ceramic)

I spoke to @michaelsena on Discord and they said that when a user first authenticates using 3ID Connect eventually it will automatically migrate their 3Box profile to IDX.

I'm just creating this issue to track the progress of that since MyMeta already has everyone using 3Box, and until that information can be migrated we're blocked on the migration to IDX.

After authenticating with Authereum, I'm getting '{"error":"Invalid proof for signed commit"}' after the POST to https://ceramic-clay.3boxlabs.com/api/v0/commits. This happens right after my code calls this: 'await ceramic.setDIDProvider(provider)'.

Code:

const ethProvider = await web3Modal.connect()
const addresses = await ethProvider.enable()
const authProvider = new EthereumAuthProvider(ethProvider, addresses[0])
threeIdConnect = new ThreeIdConnect()
await threeIdConnect.connect(authProvider)
const didProvider = await threeIdConnect.getDidProvider()

Steps to reproduce:

1. At web3Modal.connect(), browser opens second windows with Authereum login.
2. Login with Authereum login (on Mainnet).
3. In popup window, a new page is loaded with prompt to 'Sign Message': "Create a new account link to your identity. did:3:xxx Timestamp: 1611281995". Click 'Sign'
4. After clicking Sign, window closes. Popup (like a toast) pops up inside of first browser (where code is executing) with message: Signed Message "Create a new account link to your identity. did:3:xxx, Timestamp: xx" 6:20pm. I close it.
5. Another message inside first browser window pops and says 'Signed message: Add this account as a Ceramic authentication message." I close this.
6. In browser console, an error throws with: I'm getting '{"error":"Invalid proof for signed commit"}' after the POST to https://ceramic-clay.3boxlabs.com/api/v0/commits.

Package versions:

+-- [email protected]
+-- [email protected]
+-- @ceramicnetwork/[email protected]
+-- @ceramicnetwork/[email protected]
+-- @ceramicstudio/[email protected]
+-- @portis/[email protected]
+-- @stablelib/[email protected]
+-- @testing-library/[email protected]
+-- @testing-library/[email protected]
+-- @testing-library/[email protected]
+-- @walletconnect/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- UNMET PEER DEPENDENCY [email protected] - 3
+-- [email protected]
+-- UNMET PEER DEPENDENCY popper.js@^1.16.1
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

Describe the bug
Error: Unable to connect on ceramic popup

To Reproduce
Steps to reproduce the behavior:

1. Using package '@3id/connect'
2. Connecting with 3id with the following code

import { ThreeIdConnect, EthereumAuthProvider } from '@3id/connect'
const threeIdConnect = new ThreeIdConnect()
let authProvider = new EthereumAuthProvider(window.ethereum, address)
yield threeIdConnect.connect(authProvider)
const didProvider = yield threeIdConnect.getDidProvider()
const CERAMIC_URL = "https://ceramic-clay.3boxlabs.com";
const ceramic = new Ceramic(CERAMIC_URL)
yield ceramic.setDIDProvider(didProvider)

Screenshots
Pic 1 - These APIs are getting called only, after which i get the error in Pic 2

Pic 2

Pic 3 and Pic 4 - Getting error on this API only for now but still other APIs are getting called which further gives the error on popup.

Ceramic versions
"@3id/connect": "^0.1.3",
"@ceramicnetwork/http-client": "^0.9.3",
"@ceramicstudio/idx": "^0.7.0",

Machine, OS, browser information (please complete the following information):
Linux,testing on Chrome and Brave only for right now.

Describe the problem
3id-connect currently only works with the Clay Testnet. As a developer, I would like to be able to get a fully isolated dev set up working.

steps to reproduce

1. run ceramic daemon --network=inmemory
2. run CERAMIC_API=http://localhost:7007 npm run start in 3id-connect
3. set https://github.com/ceramicstudio/web-playground to use local node + local 3id-connect
4. timeout errors

On "Connect to existing" vs "Create new" panel.

It does load management page, and appears to load fine
seems to only be visual issue
need to make sure we can force overlay the management app in most all context

Describe the bug
Receiving a failure when trying to connect an existing 3ID in 0.1.3

To Reproduce
Steps to reproduce the behavior:

1. Via the web playground connect a wallet that has an existing 3ID
2. Select "Continue" when prompted "The site wants to access your personal data"
3. Select "Continue" when prompted "Your 3Box DID <> will be migrated"
4. Sign two messages in wallet
5. Receive error "Unable to connect"

Expected behavior
No error is expected.

Versions
Produced using the web playground using @3id/[email protected]

Screenshots

Additional context

• Same error was received using the same 3id-connect version in a different app
• I'm not sure if the 3ID I'm attempting with had an old 3Box profile, or a not-so-old 3ID from Ceramic < 1.0

It is now unclear if I can click on the button or not.

Related to #60

As a 3Box Labs developer, I want the IDX SDK integrated into 3ID Connect so that I can use it to display a DID's profile information.

https://playwright.dev/docs/test-intro
Might be a good alternative to using Jest with Playwright, it could simplify the setup.