Have been speaking with Supabase and they have asked if this repo can be moved open-source both as a demo for the open-telem feature and for the feat/web3 branch.

Needs to be evaluated as to how much time it will take and if it will benefit us currently because our plan is to just throw this away in a few months

Redeploy GoTrue with the new updates. This will also need some logic changes on the frontend due to some API changes

Create GitHub action to:

• pull https://github.com/WalletConnect/gotrue
• switch to branch feat/web3
• build/push image to ECR

Launch list of issues.

Critical:

• https://github.com/WalletConnect/cloud-app/issues/141
• #31
• https://github.com/WalletConnect/cloud-app/issues/137
• https://github.com/WalletConnect/cloud-app/issues/140
• https://github.com/WalletConnect/cloud-app/issues/139
• #34
• Fix emails
• Final manual testing on different devices and wallets

Supabase shows "waiting for verification" for users that have logged in with SIWE.
Instead, this should show the last sign in date.

AC:

• (simple) test covering the basic functionality using the staging api
• must be possible to run against both the local/dev/staging endpoints
• must gate deployments from staging to prod

Background: We pay bandwidth for public container image downloads. We don't want someone to do a griefing attack on us and force us to pay a huge amount for egress fees.

Looks like the action's if checks aren't working, evaluate why this is.

Just skimming your PR over at supabase/auth#282 and since I have no comment ability there, I'd love to contribute a few comments here (since this is kind of the "nerve center" for the temporary self-hosted solution?).

I think that on a DB level, the PR creates a lot of unnecessary new tables (kind of rhyming with @hf feedback there. Would you consider using something like this to identify chains in the provider field?
https://chainagnostic.org/CAIPs/caip-2

It could then be prefixed with a web3: prefix as per @hf recommendation. e.g:
web3:eip155:1

Or you can just go raw and write:
eip155:1 (This seems cleaner and I don't see how it would be a problem, since it won't conceivably clash with any other provider in gotrue)

Then you eliminate all crypto specific identity tables and you can store the other information (such as address e.t.c) in the identity_data JSONB field.

As for the SIWE logic, it would be useful to already write SIWx (CAIP-122: https://chainagnostic.org/CAIPs/caip-122), since it's already a superset of EIP-4361 (SIWE) abstracted for chain agnostic use.

I'd be happy to contribute code directly (as well as a migration strategy for your existing stuff) since I'm working on a similar solution and would love to contribute to existing efforts vs. forking effort.

Review health checks so that container will be draind for any issues

From @arein's PR review

Currently repos are made all the time with no distinction of environment, they should be limited to the prod environment only when multiple environments/workspaces are made.

Currently using Cloudflare but would like to use Route53 Hosted Zones, so that CF credentials aren't required and login.walletconnect.com can be delegated to this project.

Current Plan

• Use Terraform Cloudflare Provider (from #4)
• Manage all DNS Records using cloudflare_record

Preferred Solution

• Use AWS Provider
• Create aws_route53_zone for login.walletconnect.com
• Manage DNS records using aws_route53_record

Formatting is weird, look at other repos to try and fix.

Example

Add default tags to the provider so that all resources are tagged to the CloudSIWE project

Look at, https://github.com/WalletConnect/ts-relay/pull/212 and https://github.com/WalletConnect/ts-relay/blob/master/.github/workflows/terraform_plan.yml

current delays are too close and doesn't give the ALB time to start up and route traffic towards the new containers

Possible Solution

Get each branch (feat/web3 and feat/opentelem) working individually and ensure working locally because some changes were made in the branch walletconnect-dev to get migrations etc working.

AC:

• export metrics somewhere (I remember @Harry saying that GoTrue is integrated w/Datadog)
• integrate with our Grafana instance
• define top-level metrics
• setup dashboards
• setup monitors

Review implementation with the SpruceID team

Create the ECS definitions for:

• Cluster
• Task
• Service