
$GRAM believer / TON on-chain investigator / degen trader / flipper / influencer in TG https://nitter.cf/t.co/cpuS2Y0MH7
Serbia
Joined January 2025
- Tweets692
- Following43
- Followers267
- Likes2K
TON is retiring a protocol from its original whitepaper đź‘€
RLDP was TON’s own way of reliably sending large messages between nodes, like when one node asks another for data and the reply is too big to fit in a single packet
TON built RLDP before QUIC became an internet standard
QUIC is the transport behind HTTP/3. It lets one connection carry several independent streams, so the other streams can keep moving while lost data in one stream gets resent
we checked TON’s mainnet config and found QUIC already enabled for consensus on the masterchain and shardchains
TON deprecated RLDP2 in October and removed it from the testnet branch on nov 16 as part of the gradual switch to QUIC
the mainnet node update is scheduled for nov 23, with a separate configuration vote on nov 25
is Wintermute behind this TON wallet?
from nov 1 to 14 the wallet UQDQ…MICS sent 2.48M GRAM to KuCoin and Gate across 85 transfers
1.39M GRAM went to KuCoin
1.09M GRAM went to Gate
Wintermute is one of crypto’s biggest market makers
it provides liquidity across 60+ exchanges and reports over $10B in average daily trading volume
we started with Arkham, a blockchain analytics platform that links wallet addresses to firms like Wintermute
in 2024 an Ethereum wallet Arkham labels as Wintermute burned 1.134M wrapped TONCOIN to bridge funds back to TON
the bridge recipient later sent 155,604 GRAM to UQAo…YPp9
that wallet also sent GRAM directly to UQDQ…MICS
then we compared where those two wallets sent their GRAM
at each of Bybit, KuCoin and Gate both wallets used the same deposit address and the same memo
the memo tells the exchange which account to credit
in the Tonviewer screenshot both wallets used KuCoin memo 1867793293 more than two years apart
that’s the strongest clue linking the newer wallet to Wintermute
who controls it and what happened to the GRAM after deposit are still open questions
wallets we traced
tonviewer.com/UQDQp9s8gsduff…
tonviewer.com/UQAoF4hojDwh3g…
3
19
1,795
your next Telegram gift sale could start in your profile and end in your Gram Wallet
the new macOS beta adds an On Blockchain filter for NFT gifts listed directly through @telegram
Fragment listings still show up under From Fragment
my read is that you’ll be able to move a gift onchain into your Gram Wallet and list it for GRAM right from your profile
the GRAM could go straight to your wallet once it sells
that’s the part i still want to verify with a completed sale
i’d list my Resistance Dog #671 there so more people browsing gifts in Telegram could find it
would you sell your onchain gifts this way?
Fragment buying and selling are moving into @telegram
we checked macOS beta 13.2.0
the new “From Fragment” filter brings Fragment listings into the gift marketplace, with purchases handled through Gram Wallet
you can also open a gift from your profile or wallet and choose “List on Fragment”
the gift must already be on the blockchain
set your price and confirm the listing through your wallet
sale proceeds go directly to your wallet
currently being tested on the test server
wallet connected but tapping pay does nothing?
we checked the TON Connect fix
after you reopened a mini app the SDK could use the name gramwallet to route your payment request to a different wallet
the fix keeps the original route while it’s still listed
merged on nov 13 with the npm release still pending when we checked
ever had this happen in @telegram ?
1
16
849
could @telegram get its own Polymarket?
BetBot surfaced alongside a demo of the GRAM coin flip we covered last week
the mini app showed a market on whether TON would trade above $5 on dec 31 2026
yes and no buttons
60% chance on screen
trading volume in GRAM
on nov 12 we traced the transfer of the collectible username @telemarkets from marat.ton to 424242.ton
we previously linked the receiving wallet to @durov
an earlier screenshot of the TeleMarkets bot said “Trade the future with TeleMarkets directly in Telegram”
Marat showed a Gram Wallet concept back in 2019
seven years later Telegram started rolling out its native wallet
our theory is that prediction markets could be next
would you actually trade on a prediction market inside Telegram?
3
23
2,013
we’ve been following the TON upgrades and digging through Telegram’s code for months @durov
the network is getting better at moving data between nodes and now people can pay right inside a bot message
that’s what makes us so bullish on everyday use of the-open-network:native
1M+ self-custodial Gram wallets activated on Telegram in just 48 hours.
$GRAM is up 10% in 24h, the #1 gainer in the CMC top 100.
TON node operators
CVE-2026-98432 can allow remote code execution on vulnerable Linux servers
install the official Ubuntu or Debian kernel update and reboot to load the patched kernel
update validators one at a time and wait for each to sync and resume validation
1
18
751
we’ve spent the last few months digging through TON contracts and Telegram’s code
the amount of work happening across both is seriously bullish
TON Core is improving network transport and stability
global balance verification adds another check on the blockchain’s accounting
work on further scaling keeps moving
Telegram is building the product layer alongside it
interactive messages
wallet interactions
payments inside the conversation
more tools for developers to turn useful ideas into things people can actually use
Omniston adds another piece by connecting TON with liquidity on other networks
what makes this powerful is how these pieces can reinforce each other
better infrastructure supports better apps
better apps give people more reasons to use the ecosystem
Telegram gives those apps a direct route to users
for GRAM the opportunity is to become part of that everyday activity
payments
commerce
games
services built into the place where people already talk
that is a massive long term thesis
the infrastructure and the user experience are being built together
that’s how you build an ecosystem capable of earning a top 3 position 🚀
IN TON WE TRUST
thank you @durov 🤝
how Omniston from @ston_fi completes a swap between TON and another blockchain
imagine swapping USDT on TON for USDT on Arbitrum
you and a liquidity provider lock funds in contracts on the two networks
a shared secret allows both sides to complete the exchange
we traced that secret through Omniston’s official demo code
1 → the app generates 32 random bytes with crypto.getRandomValues
2 → it hashes the secret using the algorithm specified in the quote
the TON order builder receives the hashes through secretMode provided
3 → orderTrack streams execution updates from Omniston’s API
the app checks that both inputPositionPhase and outputPositionPhase are ready for completion
4 → once both checks pass it calls orderDiscloseHtlcSecret with the quote ID and execution index
that is the completion trigger in this example
the app releases the secret based on readiness reported through the API
reviewed official React example at commit ae756abd35e2
Fragment buying and selling are moving into @telegram
we checked macOS beta 13.2.0
the new “From Fragment” filter brings Fragment listings into the gift marketplace, with purchases handled through Gram Wallet
you can also open a gift from your profile or wallet and choose “List on Fragment”
the gift must already be on the blockchain
set your price and confirm the listing through your wallet
sale proceeds go directly to your wallet
currently being tested on the test server
a bot message in @telegram could become a checkout
we checked Telegram Desktop 7.4.0 and found the Gram Wallet flow for HTML widgets
tap a button in the message and Telegram opens its own wallet confirmation over the chat
after you approve, the bot gets a message hash it can verify on TON or a signature if it requested one
the desktop code is already in 7.4.0
Telegram’s widget docs still list the wallet server API as pending
a the-open-network:native coin flip could be coming to @telegram gift marketplace
on Nov 4 sl4sh.ton deployed a heads or tails contract on TON
the next day one wallet sent sl4sh.ton three transfers marked “tgmarket test deposit”
that same sender played the game and received a 2Ă— payout
we also traced seven bets of 2.72 GRAM each to 424242.ton, a wallet linked to @durov
two bets paid out 5.44 GRAM each with the memo “You won: tails”
the game already pays out onchain
the deposit memos are the clue pointing to a possible Market integration
KYC is back on Fragment for @telegram monetization withdrawals
earlier this week Fragment removed identity checks
now verification has returned for withdrawing GRAM earned through channels bots and groups
other features currently remain available without KYC
purchases and earnings withdrawals now have different identity requirements
buying Stars or Premium remains available without verification
withdrawing monetization income requires it
we checked Fragment’s public JavaScript
the withdrawal handler opens a verification window when the server returns need_verify
the same conditional checks remain in the Stars and Premium purchase handlers
the verification system remains part of Fragment
its server determines which operations require it
TON Nov 3 vote is about checking that every GRAM adds up
we decoded the proposal
Config 8 would move from global version 16 to 17
the code enables an independent recount of GRAM across accounts and message queues plus validator fees still held by the network
money travelling between shards gets counted too
the total must equal the previous balance plus newly created coins minus burned coins
if the numbers disagree the candidate block is rejected
this helps catch accounting bugs that accidentally create or erase the-open-network:native
at 08:08 UTC on Nov 3 mainnet was still on version 16
the proposal was pending
t.me/tonstatus/255
TON validators have a mainnet configuration vote scheduled for Nov 3 from 03:30 UTC
participation is mandatory for mainnet validators according to TON Status
the broader technical direction is already clear
TON Core plans to use the bandwidth freed by the October updates to increase shardchain throughput
shardchains are the parts of TON that process user transactions
the goal is to let each one handle more transfers and smart contract operations as activity grows
a configuration vote can approve changes to the network settings that govern this processing
the exact Nov 3 changes remain to be published
the proposal will show whether this vote advances that scaling plan or changes other network settings
TON validators have a mainnet configuration vote scheduled for Nov 3 from 03:30 UTC
participation is mandatory for mainnet validators according to TON Status
the broader technical direction is already clear
TON Core plans to use the bandwidth freed by the October updates to increase shardchain throughput
shardchains are the parts of TON that process user transactions
the goal is to let each one handle more transfers and smart contract operations as activity grows
a configuration vote can approve changes to the network settings that govern this processing
the exact Nov 3 changes remain to be published
the proposal will show whether this vote advances that scaling plan or changes other network settings
TON is making room for more transactionsЫ
the public node in @anatoly_makosov chart went from 27.9 to 10.6 Mbit/s of combined incoming and outgoing traffic after the October rollout
we calculated a ~62% drop in bandwidth usage
nodes use their network connections to exchange block data. reducing the traffic needed to distribute blocks leaves more room for additional transaction load
TON plans to use that headroom to increase shardchain throughput. the goal is to handle more transfers and smart contract operations with the available network capacity
the chart measures bandwidth savings on one node. the actual increase in transactions per second will need separate measurements
TON is making room for more transactionsЫ
the public node in @anatoly_makosov chart went from 27.9 to 10.6 Mbit/s of combined incoming and outgoing traffic after the October rollout
we calculated a ~62% drop in bandwidth usage
nodes use their network connections to exchange block data. reducing the traffic needed to distribute blocks leaves more room for additional transaction load
TON plans to use that headroom to increase shardchain throughput. the goal is to handle more transfers and smart contract operations with the available network capacity
the chart measures bandwidth savings on one node. the actual increase in transactions per second will need separate measurements
three wallets hold ~43% of the GRAM in @telegram Money
we checked Gram explorer’s Nov 1 snapshot: ~854k created wallets, ~93k holding GRAM, and ~1.29M GRAM in total
we separately verified the three largest balances through TON API. together, these WalletTg addresses hold 548,906 the-open-network:native
the creation counter includes wallets with zero on-chain transactions. funded wallets and repeat usage are the next adoption metrics to watch
gram.org/telegram-wallets
5
42
2,970
TON’s validator issues are showing up in rewards.
TON Status reports ~2.5% lower masterchain block production since Oct 19 and 1.45% less total validator rewards per round. seven masterchain validators were flagged for persistent underperformance.
we compared the warnings. a separate workchain validator, D19D…41E3, was urged to update on Oct 22. today, Oct 31, it is listed as still outdated.
TON Status says user experience remains unaffected.
t.me/tonstatus/253
t.me/tonstatus/251
TON’s new public block broadcasts are now active
we covered the validator vote on October 21. today, TON Status confirmed that the transition to new public-overlay broadcasts is complete
in simple terms, this changes how nodes in TON’s public network pass blocks to each other
the Plumtree rollout is intended to improve delivery reliability, including when some peers fail to forward traffic
we also checked the live on-chain configuration: Config 30 now contains protocol version 2 for both the masterchain and shardchains, matching the setting proposed in the vote we covered
for node operators, TON Status gives two requirements:
→ node software updated to 2026.10
→ a working QUIC port
according to the announcement, nodes meeting both conditions should now experience more stable connectivity. nodes that haven’t upgraded will lose synchronisation
this is the next milestone in our October update coverage: the public-overlay transition has moved from voting to confirmed completion
announcement:
t.me/tonstatus/252
technical background:
t.me/toncore/131
17
998
importing your Telegram Money wallet into another app keeps the same contract, including its automatic upgrades
we checked TON’s documentation. WalletTg loads its shared wallet logic from network configuration parameter -123. validator-approved changes apply to every WalletTg account. owners cannot opt out
upgrades require more than 75% of total validator weight. @telegram cannot push them through alone
the distinction matters: holding your signing key gives you control over signing transactions. future wallet logic remains governed by validator voting
changing apps preserves that arrangement. choosing a different contract, such as V5, means creating a separate wallet and transferring assets to its address
your recovery phrase lets you change the app. the contract determines which upgrade rules follow you
we checked Affluent’s Oct 26 upgrade. nine hours later, the vault credited unbacked shares again
after @replysd investigation, we reviewed 516 transactions across the two lending vaults, traced the payouts and compared archived contract states
the timeline extends beyond Sept 30, Oct 12 and Oct 16
we found 18 share credits following error 1002. fifteen occurred between Oct 19 and Oct 27. in the reviewed traces, shares were credited without a matching deposit of the underlying token
the later operations include tiny credits. the identities of those operators and the purpose of their transactions remain unverified
the September and October activity is also connected. the wallet redeeming shares on Oct 12 was using the balance left from its Sept 30 credit
the early redemptions we verified paid out approximately 781,605.877 GRAM and 13,824.935 USDT. gas additions and subsequent bridge transfers are excluded from those totals
then comes the upgrade
Advanced Market’s code changed on Oct 26 at 11:48:33 UTC. we recovered the previous bytecode from an archival block and confirmed the code change
tonviewer.com/transaction/86…
at 21:00:14 UTC that same day, the pool returned error 1002 and the USDT vault credited shares again. TON Center independently confirms the updated code was already running
tonviewer.com/transaction/04…
that transaction also explains the apparent trillion USDT in the vault’s internal cash field. adjacent archived blocks show the accounting increase without the corresponding tokens arriving
we also traced a separate route involving the newly credited shares
some were deposited into Vault Market as collateral. on Oct 22, one later share recipient received 13 borrow payouts totalling 10,691 GRAM and 19 USDT
one of the payouts:
tonviewer.com/transaction/27…
these are confirmed loan disbursements. the eventual loss depends on repayment and collateral recovery
we reconstructed 13 accounts for the two vaults across eight pools. our book value model gives roughly 113,903 GRAM and 18,384 USDT, including direct token balances. borrower debts are valued at face value, so these figures cannot be treated as immediately withdrawable reserves
the recovery calculation needs to reconcile the extra shares, their transfers, collateral positions and recoverable debts before assigning losses to legitimate depositors
our findings cover historical transactions and snapshots through Oct 28. the Oct 26 upgrade was insufficient for the share credit path observed that evening
@AffluentOrg affected users need a public breakdown of what changed in the contracts, how the extra shares and collateral will be handled, the shortfall per vault, and the funds and timetable for reimbursement
Affluent (@AffluentOrg) suffered exploits on Sept 30, Oct 12 and Oct 16, with reported losses of ~$1.1M. On Oct 19, community members shared their findings with the team. There is still no public incident report or clear plan to reimburse affected users. Full investigation:
23
214


































