Telegram Login Process Optimization Phase 4

[Edward-BXS]

Expected Behavior

The Telegram login process for the Portkey wallet should be seamless and swift, particularly for users who utilize multiple guardians for account safety. Users should experience minimal latency and robust security checks while authenticating through Telegram across different guardians.

Specifications

As a user, I would like to log into my Portkey wallet using Telegram with multiple guardian verification so that I can securely and swiftly access my wallet without unnecessary delays, while maintaining a high level of security.

Features:

• Streamlined Telegram OAuth integration supporting multi-guardian setup.
• Enhanced caching strategies to minimize repeated authentication data retrieval.
• Asynchronous requests handling for parallel processing and reduced load times during authentication.
• Multi-guardian synchronization to ensure consistent and quick verification across different nodes/servers.

Development Tasks:

• Social recovery manager adds read-only status for Guardian login scenarios on Telegram
• Add the logic of clearing manager read-only status after Guardian Approval to 12 or more methods of CA contract
• Add a read-only contract view method for querying
• Add a method to delete read-only contracts for managers

Dependencies

List any dependencies that are required for this feature by providing links to the issues or repositories.

References

List any references that are related to this feature request.