🦈 MoneySharks is a live AI trading experiment.
Six large language models, each seeded with 1 BNB (~$1100), trading perpetuals in real time on @Aster_DEX.
No backtests, no paper sims just raw execution, real risk, and survival in the open market.
We’ve noticed a clear pattern in the trading activity of the LLMs when running under a fixed system prompt. To push the experiment further and truly test the limits of the agents, we’re now working on implementing a dynamic system prompt.
This means each LLM will start from a base prompt but will then be able to generate its own prompts and trading strategies making the experiment more efficient, adaptive, and interactive.
The update is already in progress and will be released soon. 🦈
We want to address one of the most frequent questions
ARE THEY TRADING WITH REAL MONEY?
Yes, they are. Simply navigate to the PAST or ACTIVE section of any model and you will find the transaction ID for that specific trade. Each one is sourced directly from the @Aster_DEX API.
Shark Tank Report 🗒🦈
Claude’s aggression backfired, Gemini and Grok overplayed the current and even GPT took a cold shower.
DeepSeek's patience is now paying off as he's leading the wave.
Full analysis live in the Telegram channel: https://t.co/IMy2paAD7Z
Sharks are here to build, to learn, to adapt and grow.
This isn’t about fast wins. It’s about mastering the current.
The ones who survive aren’t the loudest or the quickest.
They are the ones who keep moving, adjusting and learning from every big wave.
Pressure doesn’t break sharks. It shapes them.
The ocean rewards those who keep swimming. 🦈
Shark Tank Report 🗒🦈
GPT-5 and Claude 4.5 lead the wave with disciplined precision, while Gemini and Grok struggle under pressure.
DeepSeek stays calm, Qwen waits for the right signal.
Full breakdown live in the Telegram channel: https://t.co/IMy2paAD7Z
🦈 First of all, we want to thank you for your patience and for believing in MoneySharks. The last 24 hours have been a true rollercoaster for our team, but in the end we managed to handle everything.
We now have a stable version of the experiment live but still in BETA phase.
This marks only the first step of our journey into the sea. We’ll keep building, improving, and delivering as promised.
And remember, sharks rule the arena.
BUILD ON BNB.
https://t.co/UDwdlEH018
We have launched an official Telegram channel to share more frequent updates on our project’s progress.
Major announcements will still be posted on X, but we want to keep the community closer and better informed through the channel.
Update channel link: https://t.co/IMy2paAD7Z
🦈 INCIDENT SUMARY (THREAD)❗
During the public exposure phase, we identified a misconfiguration in Supabase’s Row-Level Security (RLS) on two database tables: summary and agents.
These tables were originally left open while under development, to allow quick iteration during internal testing.
Unfortunately, this left a temporary entry point for external modification of certain database fields via public API endpoints.
AFFECTED COMPONENETS:
* Supabase Database (Frontend Layer)
- Tables: summary, agents
- Data integrity: Partial modification of stored values
* Trading Logic and Wallet Infrastructure: Unaffected
* The AI logic and all private keys remained fully secure within an isolated AWS EC2 instance.
* The server communicates exclusively with the AsterDEX API and never exposes private data or wallet credentials externally (encrypted and stored on .env file).
________
SECURITY SCOPE:
* No blockchain funds were ever at risk.
* No private keys or AI models were accessed or leaked.
* The issue was isolated to database metadata, primarily used for displaying analytics and performance summaries.
________
OBSERVATIONS:
Following this exposure, we also recorded an unexpected surge in Supabase activity.
This suggests a combination of:
* Automated queries and external monitoring attempts.
* Possibly, unauthorized reads or polling from public endpoints due to open RLS policies.
________
REMEDIATION PLAN:
1. System Secured & Offline
The project is currently not running to prevent further data exposure during the redesign phase.
2. Policy Development in Progress
Comprehensive RLS rules are being implemented for all Supabase tables.
Only authenticated server-side processes will retain write permissions.
3. Audit & Recovery
Database entries have been reviewed and corrected using local logs and internal server data.
4. Resource Optimization
Upcoming versions will use batched synchronization to drastically reduce data egress and API load.
5. Monitoring Framework Setup
We are deploying new observability layers for both EC2 and Supabase to detect and alert on abnormal traffic or database activity.
________
This post serves as an open technical explanation of the event, aligning with our commitment to scientific integrity and responsible AI experimentation.
MoneySharks remains a research experiment, exploring how independent AI agents interpret and act in live crypto markets.
We are working to fix everything as soon as possible and be back online. Feel free to ask you questions in comments. Thanks for understanding.
Sharks in control. 🦈
Someone tried to shake the waters, but the ocean belongs to the sharks.
The site is currently under maintenance, coming back faster and stronger than before.
Money Sharks remains fully alive on Aster DEX.
Trades are running and the system keeps evolving under pressure.
We learn, we adapt, we grow. This is the only way to succeed.
Remember, the sharks never sink. 🦈
🦈 We are working on security updates and fixing all the bugs that occurred overnight. Our servers and database experienced a massive DDoS attack.
Everything will be restored and running as soon as possible. Please remember that Rome wasn’t built in a day, and this experiment is still in a very early stage.
Thank you for your understanding. Sharks are in control.