Forwarded from kek🛢
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from Telegram Crawler
Private key of self-custodial @wallet (TON Space)
Backup process:
1. Random recovery key generated using AES-GCM, length 256
2. All spaces between words removed from the mnemonic phrase
3. Mnemonic string encrypted using recover key (same AES-GCM)
4. Encrypted string split by 2 parts 50/50. Shard 1 and Shard 2
5. Shard 1 sent and stored in the SCW service
6. Shard 2 sent and stored in Telegram Cloud Storage
7. The recovery key sent and stored in @wallet service
The recovery process is the reverse of the backup process.
TLDR: your encrypted private key is stored 50% on Telegram and 50% on SCW service. To decrypt it you should get a recovery key from @wallet service.
Do you have ownership of your private key? I suggest exporting the mnemonic phrase and backup manually.
Research by @ilya_marshal and @teispam with support of @tgcrawl
Backup process:
1. Random recovery key generated using AES-GCM, length 256
2. All spaces between words removed from the mnemonic phrase
3. Mnemonic string encrypted using recover key (same AES-GCM)
4. Encrypted string split by 2 parts 50/50. Shard 1 and Shard 2
5. Shard 1 sent and stored in the SCW service
6. Shard 2 sent and stored in Telegram Cloud Storage
7. The recovery key sent and stored in @wallet service
The recovery process is the reverse of the backup process.
TLDR: your encrypted private key is stored 50% on Telegram and 50% on SCW service. To decrypt it you should get a recovery key from @wallet service.
Do you have ownership of your private key? I suggest exporting the mnemonic phrase and backup manually.
Research by @ilya_marshal and @teispam with support of @tgcrawl
Forwarded from Mifuru 🎌
это да только надо же чтобы арун и АльБабах скинули инфу в каналы что у дурова юзерка
Forwarded from M. D.
Please open Telegram to view this post
VIEW IN TELEGRAM