💎 Durov is quietly building the wallet layer
🔝 What changed
⚫️ TON now has a public tg-wallet-contract repository
⚫️ The contract is called WalletTg
⚫️ Its bytecode is designed to stay in TON config
⚫️ Updates go through validator voting and apply to Telegram wallets at once
⚫️ Telegram creates the wallet first, but the user can later switch to self-custody
⚫️ The contract supports signing key rotation
⚫️ A recent revision added tgUserId, meaning Telegram ID can be stored inside the wallet logic
🔝 Why it matters
⚫️ This looks like the missing contract layer for native Gram Wallet
⚫️ Telegram does not need every user to understand seed phrases on day one
⚫️ It can create a wallet first, then let advanced users take full control later
⚫️ Validator voting makes the wallet code part of TON infrastructure, not just a client feature
⚫️ Storing tgUserId inside the wallet logic connects Telegram identity and TON accounts much more directly
⚫️ The current vote to add Telegram Wallet code into blockchain config is the kind of step you take before a serious rollout
Everyone is watching the Gram Wallet button inside Telegram. But the real story may be lower: Telegram is preparing a shared wallet contract that validators can approve, update and push across the ecosystem. That is not a cosmetic integration. That is wallet infrastructure.
🤑 TON Insider 🤑
A new repository appeared under TON: tg-wallet-contract. This is not just another wallet app. It is the on-chain contract layer for Telegram Wallet, where the wallet logic can live directly in blockchain config and be updated through validator voting.
🔝 What changed
⚫️ TON now has a public tg-wallet-contract repository
⚫️ The contract is called WalletTg
⚫️ Its bytecode is designed to stay in TON config
⚫️ Updates go through validator voting and apply to Telegram wallets at once
⚫️ Telegram creates the wallet first, but the user can later switch to self-custody
⚫️ The contract supports signing key rotation
⚫️ A recent revision added tgUserId, meaning Telegram ID can be stored inside the wallet logic
🔝 Why it matters
⚫️ This looks like the missing contract layer for native Gram Wallet
⚫️ Telegram does not need every user to understand seed phrases on day one
⚫️ It can create a wallet first, then let advanced users take full control later
⚫️ Validator voting makes the wallet code part of TON infrastructure, not just a client feature
⚫️ Storing tgUserId inside the wallet logic connects Telegram identity and TON accounts much more directly
⚫️ The current vote to add Telegram Wallet code into blockchain config is the kind of step you take before a serious rollout
Everyone is watching the Gram Wallet button inside Telegram. But the real story may be lower: Telegram is preparing a shared wallet contract that validators can approve, update and push across the ecosystem. That is not a cosmetic integration. That is wallet infrastructure.
🤑 TON Insider 🤑