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
Currently, users must manually enter an RPC endpoint when creating a wallet, requiring them to copy it from external sources (e.g., TG bot). This disrupts the UX and makes the onboarding process harder.
We need a new approach where users don’t have to manually input an RPC endpoint, but instead get automatically assigned one. This requires a new flow, potentially involving a “Connect with X” button that assigns an endpoint based on the user’s credentials (e.g., username)
Acceptance Criteria:
Implement an automated method for assigning RPC endpoints
Ensure the flow is user-friendly and does not introduce complexity
Sync with Design and Product teams to finalize UX changes
Technical Notes:
We have a backend which already manages a set of RPC endpoints for TG bot interactions, evaluate integrating a similar mechanism in the extension
Consider a “Connect with X” button approach to assign endpoints dynamically
The text was updated successfully, but these errors were encountered:
0xAleksaOpacic
changed the title
Improve RPC Endpoint Selection Flow During Wallet Creation
Optimize RPC Endpoint Selection & Speed Up Wallet Creation
Feb 7, 2025
0xAleksaOpacic
changed the title
Optimize RPC Endpoint Selection & Speed Up Wallet Creation
Optimize RPC Endpoint Selection & Speed Up Smart Account Creation
Feb 7, 2025
Description:
Currently, users must manually enter an RPC endpoint when creating a wallet, requiring them to copy it from external sources (e.g., TG bot). This disrupts the UX and makes the onboarding process harder.
We need a new approach where users don’t have to manually input an RPC endpoint, but instead get automatically assigned one. This requires a new flow, potentially involving a “Connect with X” button that assigns an endpoint based on the user’s credentials (e.g., username)
Acceptance Criteria:
Technical Notes:
The text was updated successfully, but these errors were encountered: