Echo Server -> Push Server v2

[HarryET]

This issue is tracking all the steps of updating Echo Server to Push Server v2 as well as all issues that are handled during the changeover period.

Push Server v2

• [ ] Write Specification
  • [ ] Mapping of Device Token to Client ID is 1-1
  • [ ] Use DID-JWTs for Webhooks 2.0
  • [ ] Document Security "better"
• [ ] Scope work
  • [ ] Single-tenant Endpoints
  • [ ] Multi-tenant support
  • [ ] Analytics
  • [ ] User-agent for endpoints called by SDK
  • [ ] Testing

Migration

• [ ] Ensure no regression of features
• [ ] Write migration doc for moving tenants from Echo Server to Push Server v2
• [ ] Write doc for Wallets to migrate
• [ ] Migrate SaaS product
  • [ ] Decide on subdomain for Push Server, should it be push.walletconnect.com or echo.walletconnect.com?
• [ ] Take a snapshot of "Echo Server v1" and place it on legacy branch replacing main with Push Server 2.0
• [ ] Rename the Repo
• [ ] Speak to Wallets Self-Hosting and help with migration

[jdorman16]

This issue is tracking all the steps of updating Echo Server to Push Server v2 as well as all issues that are handled during the changeover period.

Push Server v2

• [x ] Write Specification

  • [ x] Mapping of Device Token to Client ID is 1-1
  • [ x] Use DID-JWTs for Webhooks 2.0
  • [ x] Document Security "better"

• [ x] Scope work

  • [ x] Single-tenant Endpoints

  • [ x] Multi-tenant support

  • [ x] Analytics

  • [ x] User-agent for endpoints called by SDK

  • [ x] Testing

Migration

• [ x] Ensure no regression of features
• [x ] Write migration doc for moving tenants from Echo Server to Push Server v2
• [x ] Write doc for Wallets to migrate

• [x ] Migrate SaaS product

  • [ x] Decide on subdomain for Push Server, should it be push.walletconnect.com or echo.walletconnect.com?
• [x] Take a snapshot of "Echo Server v1" and place it on legacy branch replacing main with Push Server 2.0
• [x] Rename the Repo
• [x] Speak to Wallets Self-Hosting and help with migration

[jdorman16]

Go