![LeterTW's tweet photo. Two nights ago, my #CCTP cross-chain call caused a mistake I still deeply regret. Everyone knows #Circle has now opened native cross-chain services for $USDC on six chains. However, they only provide contracts for invocation and API endpoints for mint confirmation. Therefore, ordinary users cannot mint through an official web frontend. Having used CCTP multiple times before, I didn't perform thorough checks this time and successfully completed the contract call. Unbeknownst to me, this was just the start of a nightmare. Circle, whom I deeply trusted, simply said they couldn't handle the issue, without giving a convincing reason.
1. Incorrect Contract Call
According to the official documentation [https://t.co/VCy8PtOn5R], a typical cross-chain initialization transaction should include the following four variables: The 'mintRecipient' is the recipient's address on the target chain, using a 64-bit Bytes32 format. However, during the call, I did not perform the StringtoBytes32 format conversion.
Since every ETH address is 40 characters long, the shortfall of 24 zeros was added to the end, not the beginning. This resulted in the USDC being transferred to an empty address with 24 extra zeros at the end. [https://t.co/wcfN1qmHbH]
2. Confirmation Transaction Due to the issue in step 1, the target recipient address changed, and ultimately 100,000 USDC were transferred to this address on ARB: 0x8e662632c1c8eee5000000000000000000000000. [https://t.co/2l8cvKIJxI]
3. Attempting to Recover Upon discovering the problem, I immediately tried to contact PeckShield and SlowMist to help reach out to Circle, but the next day the consistent response was that I needed to contact Circle myself. Meanwhile, I sought help in Circle's CCTP developer channel and tried to submit a support ticket on Circle's official website. However, possibly due to the Christmas season, they did not respond immediately, and I still haven't received any auto-reply acknowledging my support case. The Discord community and a friend suggested I directly request help via Circle's customer support email.
I'm very grateful for the community Mod vcarl's help. I understand the delay in Circle's support due to the holiday season. However, it's puzzling that I couldn't find any email or online communication channel for help on Circle's entire official website. The only option was a ticket submission page, which like a black hole, never responds, and even limits the text length to less than a typical tweet.
4. Shattered Hope
With the help of friends and community staff, I started contacting the help email they provided. Unlike the official website's ticket submission page, Circle viewed and replied to my email within minutes, asking for specific event information, which I immediately provided.
I must admit Circle's support email was very efficient. After receiving my detailed information, they wrote their first effective reply: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time.' Circle's eloquent response subtly informed me they couldn't retrieve the funds because it was just a simple USDC transfer to the wrong address.
I initially thought Circle's internal team might not be well-trained or informed about the CCTP protocol, so I replied again with all the technical details of the event. The second effective reply I received today was identical: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time. For your reference, please refer to our User Agreement: [https://t.co/525KAf7mmU]' The same reply text, telling me they couldn't help retrieve the assets. Two years ago, in the USDC 2.1 version update, Circle stated they could help users retrieve USDC funds mistakenly transferred to a contract: [https://t.co/YAjcjjox8o] This contradiction is confusing and hard to understand. Indeed, it was my mistake that led to the USDC being transferred to the wrong address. However, I believe I have clearly proven the actual target of the transfer, and the Ethereum address with 24 extra zeros at the end cannot be used by anyone. It's puzzling and disrespectful how Circle's official response was dismissive and showed a lack of respect for their users.
Therefore, I request everyone's help in spreading the word and seeking viable solutions for fund recovery. To whoever provides decisive help in recovering the funds, I will give 40% of the recovered funds as a reward, and 10% will go to the friends who offered help or for charitable purposes.
Thank you for reading this far, and I hope everyone checks contracts carefully before invocation to avoid similar situations.](https://pbs.twimg.com/media/GCXd9DmbgAEKJB0.jpg)
![LeterTW's tweet photo. Two nights ago, my #CCTP cross-chain call caused a mistake I still deeply regret. Everyone knows #Circle has now opened native cross-chain services for $USDC on six chains. However, they only provide contracts for invocation and API endpoints for mint confirmation. Therefore, ordinary users cannot mint through an official web frontend. Having used CCTP multiple times before, I didn't perform thorough checks this time and successfully completed the contract call. Unbeknownst to me, this was just the start of a nightmare. Circle, whom I deeply trusted, simply said they couldn't handle the issue, without giving a convincing reason.
1. Incorrect Contract Call
According to the official documentation [https://t.co/VCy8PtOn5R], a typical cross-chain initialization transaction should include the following four variables: The 'mintRecipient' is the recipient's address on the target chain, using a 64-bit Bytes32 format. However, during the call, I did not perform the StringtoBytes32 format conversion.
Since every ETH address is 40 characters long, the shortfall of 24 zeros was added to the end, not the beginning. This resulted in the USDC being transferred to an empty address with 24 extra zeros at the end. [https://t.co/wcfN1qmHbH]
2. Confirmation Transaction Due to the issue in step 1, the target recipient address changed, and ultimately 100,000 USDC were transferred to this address on ARB: 0x8e662632c1c8eee5000000000000000000000000. [https://t.co/2l8cvKIJxI]
3. Attempting to Recover Upon discovering the problem, I immediately tried to contact PeckShield and SlowMist to help reach out to Circle, but the next day the consistent response was that I needed to contact Circle myself. Meanwhile, I sought help in Circle's CCTP developer channel and tried to submit a support ticket on Circle's official website. However, possibly due to the Christmas season, they did not respond immediately, and I still haven't received any auto-reply acknowledging my support case. The Discord community and a friend suggested I directly request help via Circle's customer support email.
I'm very grateful for the community Mod vcarl's help. I understand the delay in Circle's support due to the holiday season. However, it's puzzling that I couldn't find any email or online communication channel for help on Circle's entire official website. The only option was a ticket submission page, which like a black hole, never responds, and even limits the text length to less than a typical tweet.
4. Shattered Hope
With the help of friends and community staff, I started contacting the help email they provided. Unlike the official website's ticket submission page, Circle viewed and replied to my email within minutes, asking for specific event information, which I immediately provided.
I must admit Circle's support email was very efficient. After receiving my detailed information, they wrote their first effective reply: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time.' Circle's eloquent response subtly informed me they couldn't retrieve the funds because it was just a simple USDC transfer to the wrong address.
I initially thought Circle's internal team might not be well-trained or informed about the CCTP protocol, so I replied again with all the technical details of the event. The second effective reply I received today was identical: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time. For your reference, please refer to our User Agreement: [https://t.co/525KAf7mmU]' The same reply text, telling me they couldn't help retrieve the assets. Two years ago, in the USDC 2.1 version update, Circle stated they could help users retrieve USDC funds mistakenly transferred to a contract: [https://t.co/YAjcjjox8o] This contradiction is confusing and hard to understand. Indeed, it was my mistake that led to the USDC being transferred to the wrong address. However, I believe I have clearly proven the actual target of the transfer, and the Ethereum address with 24 extra zeros at the end cannot be used by anyone. It's puzzling and disrespectful how Circle's official response was dismissive and showed a lack of respect for their users.
Therefore, I request everyone's help in spreading the word and seeking viable solutions for fund recovery. To whoever provides decisive help in recovering the funds, I will give 40% of the recovered funds as a reward, and 10% will go to the friends who offered help or for charitable purposes.
Thank you for reading this far, and I hope everyone checks contracts carefully before invocation to avoid similar situations.](https://pbs.twimg.com/media/GCXd37fb0AAzQpj.jpg)
![LeterTW's tweet photo. Two nights ago, my #CCTP cross-chain call caused a mistake I still deeply regret. Everyone knows #Circle has now opened native cross-chain services for $USDC on six chains. However, they only provide contracts for invocation and API endpoints for mint confirmation. Therefore, ordinary users cannot mint through an official web frontend. Having used CCTP multiple times before, I didn't perform thorough checks this time and successfully completed the contract call. Unbeknownst to me, this was just the start of a nightmare. Circle, whom I deeply trusted, simply said they couldn't handle the issue, without giving a convincing reason.
1. Incorrect Contract Call
According to the official documentation [https://t.co/VCy8PtOn5R], a typical cross-chain initialization transaction should include the following four variables: The 'mintRecipient' is the recipient's address on the target chain, using a 64-bit Bytes32 format. However, during the call, I did not perform the StringtoBytes32 format conversion.
Since every ETH address is 40 characters long, the shortfall of 24 zeros was added to the end, not the beginning. This resulted in the USDC being transferred to an empty address with 24 extra zeros at the end. [https://t.co/wcfN1qmHbH]
2. Confirmation Transaction Due to the issue in step 1, the target recipient address changed, and ultimately 100,000 USDC were transferred to this address on ARB: 0x8e662632c1c8eee5000000000000000000000000. [https://t.co/2l8cvKIJxI]
3. Attempting to Recover Upon discovering the problem, I immediately tried to contact PeckShield and SlowMist to help reach out to Circle, but the next day the consistent response was that I needed to contact Circle myself. Meanwhile, I sought help in Circle's CCTP developer channel and tried to submit a support ticket on Circle's official website. However, possibly due to the Christmas season, they did not respond immediately, and I still haven't received any auto-reply acknowledging my support case. The Discord community and a friend suggested I directly request help via Circle's customer support email.
I'm very grateful for the community Mod vcarl's help. I understand the delay in Circle's support due to the holiday season. However, it's puzzling that I couldn't find any email or online communication channel for help on Circle's entire official website. The only option was a ticket submission page, which like a black hole, never responds, and even limits the text length to less than a typical tweet.
4. Shattered Hope
With the help of friends and community staff, I started contacting the help email they provided. Unlike the official website's ticket submission page, Circle viewed and replied to my email within minutes, asking for specific event information, which I immediately provided.
I must admit Circle's support email was very efficient. After receiving my detailed information, they wrote their first effective reply: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time.' Circle's eloquent response subtly informed me they couldn't retrieve the funds because it was just a simple USDC transfer to the wrong address.
I initially thought Circle's internal team might not be well-trained or informed about the CCTP protocol, so I replied again with all the technical details of the event. The second effective reply I received today was identical: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time. For your reference, please refer to our User Agreement: [https://t.co/525KAf7mmU]' The same reply text, telling me they couldn't help retrieve the assets. Two years ago, in the USDC 2.1 version update, Circle stated they could help users retrieve USDC funds mistakenly transferred to a contract: [https://t.co/YAjcjjox8o] This contradiction is confusing and hard to understand. Indeed, it was my mistake that led to the USDC being transferred to the wrong address. However, I believe I have clearly proven the actual target of the transfer, and the Ethereum address with 24 extra zeros at the end cannot be used by anyone. It's puzzling and disrespectful how Circle's official response was dismissive and showed a lack of respect for their users.
Therefore, I request everyone's help in spreading the word and seeking viable solutions for fund recovery. To whoever provides decisive help in recovering the funds, I will give 40% of the recovered funds as a reward, and 10% will go to the friends who offered help or for charitable purposes.
Thank you for reading this far, and I hope everyone checks contracts carefully before invocation to avoid similar situations.](https://pbs.twimg.com/media/GCXduYUbYAAGyvr.jpg)
Olivia
Online
Etherscan turns 10! 🥳
Our 10th Anniversary Campaign + Etherscan Points (Beta) are LIVE
To our OG supporters, your rewards are waiting:
🎖️ 10th Anniversary Badge
🌟 OG Points Reward
#10YearsofEtherscan
Read on ⬇️
https://t.co/CsGyn14ynY
🎉 I just claimed my free 10th-Anniversary collectible NFT from https://t.co/XCqdU8fs1L 🔷 Celebrating a decade of open, decentralized innovation. Join me 👉 https://t.co/sWOPihsrpH #Ethereum10
@cursor_ai you should nofity users via email instead of just a post here🤷♂️
为啥没涨？原因很多。
我觉得好的，都会拿到他涨。🤣
my raycast journey of 2024
Thank you Emmy for showering me with 1,600 Diamonds and getting me to shamelessly tweet this out. If you've collected Ethereum NFTs, all the way back to 2017, head to https://t.co/h8JtRV2NiQ to claim your taste of Diamonds on the best cross-chain rewards program.
With a limited supply and the claim window only open for 7 days, make sure you secure your Pass today, by downloading the required wallets, securing some Signet Bitcoin (sBTC) and staking any amount on the Babylon testnet platform at https://t.co/21LAlUqAoz
The Pioneer Pass is a symbol of your commitment to Babylon and the next evolution of Bitcoin.
Every Pass will be uniquely inscribed (not literally) with your user number to represent how early you were to staking Bitcoin and to the Babylon community.
How it works? 🔽
#StakingBitcoin https://t.co/apZFPq66Rb
AND. WE’RE. LIVE 🥳
It's time to join the Bitcoin Staking Revolution🔶🔒
Babylon Testnet, the first ever Trustless Native Bitcoin Staking protocol, is now officially live!
Get involved, stake Signet #BTC and claim your free Pioneer Pass now.
https://t.co/kdBgiu12Fq
👇🧵
AND. WE’RE. LIVE 🥳
It's time to join the Bitcoin Staking Revolution🔶🔒
Babylon Testnet, the first ever Trustless Native Bitcoin Staking protocol, is now officially live!
Get involved, stake Signet #BTC and claim your free Pioneer Pass now.
https://t.co/kdBgiu12Fq
👇🧵
🚀 Milestone Alert! 🌟
🛡️A total of 60 validators have joined Babylon's Bitcoin Staking Protocol Testnet - propelling towards a more resilient, secure, and decentralized economy!
🎯 Our mission is to enable a Bitcoin-secured Proof-of-Stake economy, tapping into Bitcoin's vast $1 trillion idle capital to secure PoS systems and generate yield.
#StakingBitcoin #BitcoinDeFi #Babylon
#StakingBitcoin https://t.co/tsZ6Hzze6m
🚀 Countdown to Babylon's Bitcoin Staking Protocol Testnet Public Launch Begins!
🔒 Trustless Staking
⚡ Fast Unbonding
🧩 Modular Design
📈 Scalable Restaking (coming soon)
Read more: https://t.co/l39wONLYIN
👀 Ready to witness a new era in Bitcoin staking?
#StakingBitcoin #BitcoinDeFi #Babylon
🚀 Countdown to Babylon's Bitcoin Staking Protocol Testnet Public Launch Begins!
🔒 Trustless Staking
⚡ Fast Unbonding
🧩 Modular Design
📈 Scalable Restaking (coming soon)
Read more: https://t.co/l39wONLYIN
👀 Ready to witness a new era in Bitcoin staking?
#StakingBitcoin #BitcoinDeFi #Babylon
It's time to join the Bitcoin Staking Revolution! 🔶
The Babylon Testnet goes live next week giving everyone a chance to experience Trustless Native Bitcoin Staking for the first time ever 🥳
Here's everything you need to know to secure your Bitcoin Staking Pioneer Pass NFT👇🧵
https://t.co/GX6WHZKEwG
Wormhole x @AMD
I’m gonna give 10 random people that repost this and follow me $25,000 for fun (the $250,000 my X video made)
I’ll pick the winners in 72 hours
Two nights ago, my #CCTP cross-chain call caused a mistake I still deeply regret. Everyone knows #Circle has now opened native cross-chain services for $USDC on six chains. However, they only provide contracts for invocation and API endpoints for mint confirmation. Therefore, ordinary users cannot mint through an official web frontend. Having used CCTP multiple times before, I didn't perform thorough checks this time and successfully completed the contract call. Unbeknownst to me, this was just the start of a nightmare. Circle, whom I deeply trusted, simply said they couldn't handle the issue, without giving a convincing reason.
1. Incorrect Contract Call
According to the official documentation [https://t.co/VCy8PtOn5R], a typical cross-chain initialization transaction should include the following four variables: The 'mintRecipient' is the recipient's address on the target chain, using a 64-bit Bytes32 format. However, during the call, I did not perform the StringtoBytes32 format conversion.
Since every ETH address is 40 characters long, the shortfall of 24 zeros was added to the end, not the beginning. This resulted in the USDC being transferred to an empty address with 24 extra zeros at the end. [https://t.co/wcfN1qmHbH]
2. Confirmation Transaction Due to the issue in step 1, the target recipient address changed, and ultimately 100,000 USDC were transferred to this address on ARB: 0x8e662632c1c8eee5000000000000000000000000. [https://t.co/2l8cvKIJxI]
3. Attempting to Recover Upon discovering the problem, I immediately tried to contact PeckShield and SlowMist to help reach out to Circle, but the next day the consistent response was that I needed to contact Circle myself. Meanwhile, I sought help in Circle's CCTP developer channel and tried to submit a support ticket on Circle's official website. However, possibly due to the Christmas season, they did not respond immediately, and I still haven't received any auto-reply acknowledging my support case. The Discord community and a friend suggested I directly request help via Circle's customer support email.
I'm very grateful for the community Mod vcarl's help. I understand the delay in Circle's support due to the holiday season. However, it's puzzling that I couldn't find any email or online communication channel for help on Circle's entire official website. The only option was a ticket submission page, which like a black hole, never responds, and even limits the text length to less than a typical tweet.
4. Shattered Hope
With the help of friends and community staff, I started contacting the help email they provided. Unlike the official website's ticket submission page, Circle viewed and replied to my email within minutes, asking for specific event information, which I immediately provided.
I must admit Circle's support email was very efficient. After receiving my detailed information, they wrote their first effective reply: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time.' Circle's eloquent response subtly informed me they couldn't retrieve the funds because it was just a simple USDC transfer to the wrong address.
I initially thought Circle's internal team might not be well-trained or informed about the CCTP protocol, so I replied again with all the technical details of the event. The second effective reply I received today was identical: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time. For your reference, please refer to our User Agreement: [https://t.co/525KAf7mmU]' The same reply text, telling me they couldn't help retrieve the assets. Two years ago, in the USDC 2.1 version update, Circle stated they could help users retrieve USDC funds mistakenly transferred to a contract: [https://t.co/YAjcjjox8o] This contradiction is confusing and hard to understand. Indeed, it was my mistake that led to the USDC being transferred to the wrong address. However, I believe I have clearly proven the actual target of the transfer, and the Ethereum address with 24 extra zeros at the end cannot be used by anyone. It's puzzling and disrespectful how Circle's official response was dismissive and showed a lack of respect for their users.
Therefore, I request everyone's help in spreading the word and seeking viable solutions for fund recovery. To whoever provides decisive help in recovering the funds, I will give 40% of the recovered funds as a reward, and 10% will go to the friends who offered help or for charitable purposes.
Thank you for reading this far, and I hope everyone checks contracts carefully before invocation to avoid similar situations.
![LeterTW's tweet photo. Two nights ago, my #CCTP cross-chain call caused a mistake I still deeply regret. Everyone knows #Circle has now opened native cross-chain services for $USDC on six chains. However, they only provide contracts for invocation and API endpoints for mint confirmation. Therefore, ordinary users cannot mint through an official web frontend. Having used CCTP multiple times before, I didn't perform thorough checks this time and successfully completed the contract call. Unbeknownst to me, this was just the start of a nightmare. Circle, whom I deeply trusted, simply said they couldn't handle the issue, without giving a convincing reason.
1. Incorrect Contract Call
According to the official documentation [https://t.co/VCy8PtOn5R], a typical cross-chain initialization transaction should include the following four variables: The 'mintRecipient' is the recipient's address on the target chain, using a 64-bit Bytes32 format. However, during the call, I did not perform the StringtoBytes32 format conversion.
Since every ETH address is 40 characters long, the shortfall of 24 zeros was added to the end, not the beginning. This resulted in the USDC being transferred to an empty address with 24 extra zeros at the end. [https://t.co/wcfN1qmHbH]
2. Confirmation Transaction Due to the issue in step 1, the target recipient address changed, and ultimately 100,000 USDC were transferred to this address on ARB: 0x8e662632c1c8eee5000000000000000000000000. [https://t.co/2l8cvKIJxI]
3. Attempting to Recover Upon discovering the problem, I immediately tried to contact PeckShield and SlowMist to help reach out to Circle, but the next day the consistent response was that I needed to contact Circle myself. Meanwhile, I sought help in Circle's CCTP developer channel and tried to submit a support ticket on Circle's official website. However, possibly due to the Christmas season, they did not respond immediately, and I still haven't received any auto-reply acknowledging my support case. The Discord community and a friend suggested I directly request help via Circle's customer support email.
I'm very grateful for the community Mod vcarl's help. I understand the delay in Circle's support due to the holiday season. However, it's puzzling that I couldn't find any email or online communication channel for help on Circle's entire official website. The only option was a ticket submission page, which like a black hole, never responds, and even limits the text length to less than a typical tweet.
4. Shattered Hope
With the help of friends and community staff, I started contacting the help email they provided. Unlike the official website's ticket submission page, Circle viewed and replied to my email within minutes, asking for specific event information, which I immediately provided.
I must admit Circle's support email was very efficient. After receiving my detailed information, they wrote their first effective reply: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time.' Circle's eloquent response subtly informed me they couldn't retrieve the funds because it was just a simple USDC transfer to the wrong address.
I initially thought Circle's internal team might not be well-trained or informed about the CCTP protocol, so I replied again with all the technical details of the event. The second effective reply I received today was identical: 'Unfortunately, USDC transactions are irreversible by design and cannot be canceled or recalled once they have been initiated. Since this transaction was initiated and processed successfully to an address that does not exist, it is not possible to cancel or recall it at this time. For your reference, please refer to our User Agreement: [https://t.co/525KAf7mmU]' The same reply text, telling me they couldn't help retrieve the assets. Two years ago, in the USDC 2.1 version update, Circle stated they could help users retrieve USDC funds mistakenly transferred to a contract: [https://t.co/YAjcjjox8o] This contradiction is confusing and hard to understand. Indeed, it was my mistake that led to the USDC being transferred to the wrong address. However, I believe I have clearly proven the actual target of the transfer, and the Ethereum address with 24 extra zeros at the end cannot be used by anyone. It's puzzling and disrespectful how Circle's official response was dismissive and showed a lack of respect for their users.
Therefore, I request everyone's help in spreading the word and seeking viable solutions for fund recovery. To whoever provides decisive help in recovering the funds, I will give 40% of the recovered funds as a reward, and 10% will go to the friends who offered help or for charitable purposes.
Thank you for reading this far, and I hope everyone checks contracts carefully before invocation to avoid similar situations.](https://pbs.twimg.com/media/GCXeB2DbcAARHF6.jpg)
I survived the bear market and claimed my $FRAME tokens!
@frame_xyz is the Layer 2 for creators and collectors. If you've traded NFTs on Ethereum and paid royalties in the past two years you're eligible! 🖼️🎄
You can check here 👇 https://t.co/fb5mx22C48
Last Seen Users on Sotwe
Most Popular Users
Elon Musk 
@elonmusk
241.5M followers
Barack Obama
@barackobama
118.8M followers
Cristiano Ronaldo
@cristiano
114.6M followers
Donald J. Trump
@realdonaldtrump
111.8M followers
Narendra Modi
@narendramodi
107.1M followers
Rihanna
@rihanna
98.7M followers
NASA
@nasa
92.3M followers
Justin Bieber
@justinbieber
91.8M followers
KATY PERRY
@katyperry
90.1M followers
Taylor Swift
@taylorswift13
84M followers
Lady Gaga
@ladygaga
75.5M followers
Virat Kohli
@imvkohli
73.5M followers
Kim Kardashian
@kimkardashian
70.9M followers
YouTube
@youtube
68.8M followers
Neymar Jr
@neymarjr
66.5M followers
Bill Gates
@billgates
65.3M followers
Selena Gomez
@selenagomez
63.1M followers
The Ellen Show
@theellenshow
62.2M followers
CNN
@cnn
61.7M followers
X
@x
60.7M followers