> For the complete documentation index, see [llms.txt](https://smctimes.gitbook.io/smctimes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smctimes.gitbook.io/smctimes/bitmart-just-made-their-biggest-mistake-smcdao-founder-declares-war-after-getting-blocked.md).
# BitMart Just Made Their Biggest Mistake: SMCDAO Founder Declares War After Getting Blocked
The plot just thickened beyond anyone's wildest expectations. After allegedly pocketing $30,000 in listing fees back in 2023 and delivering absolutely nothing, BitMart Exchange has now escalated to their nuclear option: blocking the SMCDAO founder entirely.
### The Block That Broke the Camel's Back
Yesterday, BitMart had the audacity to reach out about listing opportunities - apparently forgetting they allegedly scammed the founder for five figures. Today? Complete radio silence via the block button. It's like robbing someone's house, then blocking them when they ask for their stuff back.
The founder's response wasn't anger - it was stone-cold calculation: **"To fight a bigger adversary, you need to become bigger."**
### The Seven-Fold Revenge Promise
This isn't just about $30,000 anymore. This is about principle, justice, and a promise that should make BitMart's executives lose sleep: **"It doesn't matter how long it takes, I will come back bigger for Bitmart and they will pay 7 times more."**
Seven times $30,000 is $210,000. But something tells us this isn't just about money anymore - it's about sending a message to every exchange that thinks they can allegedly scam projects and hide behind block buttons.
### The Long Game Begins
With Wiki Cat already at 68,000 holders, $12M market cap, and SMCDAO community funds exploding past $270,000, the founder isn't exactly starting from zero. The ecosystem is growing, the community is loyal, and the war chest is building.
BitMart might think blocking someone makes the problem disappear. They're about to learn that blocking someone with resources, determination, and a growing empire just makes them more dangerous.
### David vs. Goliath 2.0
"To fight a bigger adversary, you need to become bigger" isn't just a threat - it's a business strategy. While BitMart rests on their laurels as an established exchange, SMCDAO is building something that could make their entire platform irrelevant.
The blockchain never forgets, the community never forgives, and apparently, the founder never gives up.
### The Countdown Starts Now
BitMart had two chances to make this right:
1. ✗ Honor the original $30,000 listing (allegedly failed)
2. ✗ Respond professionally to the founder's callout (chose the block button instead)
There won't be a third chance. The seven-fold payback promise isn't just revenge - it's a mathematical certainty waiting to happen.
Time is on the founder's side. Growth is on the founder's side. And now, motivation is definitely on the founder's side.
BitMart just turned a business dispute into a personal mission. They're about to find out why that was a very expensive mistake.
***
*This article reflects ongoing disputes and public statements. Legal and business outcomes may vary.*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://smctimes.gitbook.io/smctimes/bitmart-just-made-their-biggest-mistake-smcdao-founder-declares-war-after-getting-blocked.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.