The Shiba Inu community is watching closely as lead ambassador Shytoshi Kusama approaches 74 days without a single post on X. Since May 13, he has not posted, replied, or engaged on the platform.
This isn’t the first time Kusama has gone quiet. A similar pattern emerged in late 2025 and parts of 2026. At that time, he later revealed he was working on an independent AI project, which he disclosed in January.
Kusama has often used X as his main way to talk to the community. He sometimes changed his bio or location to give subtle hints. In recent times, he even used live broadcasts to share updates.
Community Left to Piece Together Clues
Now, with over two months of silence, the community has to rely on other sources. They look at posts from other Shiba Inu ecosystem contributors. They also check on-chain activity for any signs of development.
Past experience shows that after a long break, Kusama usually returns with fresh updates. That pattern is fueling hope that this silence could lead to a major announcement. But as of now, nothing is confirmed.
Some community members feel anxious, while others stay optimistic. Social media is filled with guesses about what Kusama might be building next. His previous AI project was a surprise, and many expect something similar this time.
Shiba Inu Burns Continue Despite Silence
While Kusama stays off X, the community-led burn activities keep going. Data from Shibburn shows that 7.15 million SHIB were burned in the last 24 hours. The daily burn rate is up 66%.
In the past week, 60.58 million SHIB were burned. Over the last 30 days, the total is 288.61 million SHIB burned. Robinhood was the biggest monthly burner. They sent 152,792,823 SHIB to dead wallets in 106 transactions.
All together, more than 410.84 trillion SHIB have been burned across 21,280 transactions. A huge part of that came from Ethereum creator Vitalik Buterin burning 410 trillion SHIB back in May 2021.
For now, the community waits. Will Kusama break his silence soon? No one knows for sure. But the burns show that the ecosystem is still active, even without his direct input.
![]()

