Hey folks!
Telegram recently started providing an asymmetric signature for initData using a Telegram-custodied key. Telegram’s docs state that this new signature is suitable for proving user sign-in to third parties without revealing the bot token and that third party can rely on the public key published by Telegram for verification.
Are there any plans to add support for this as a sign-in method in Web3Auth, so that we can sign users in without doing the hash → JWT step outlined in Web3Auth’s current Telegram mini-app guide?