💻 I'll be sharing and providing content on Defi projects, my primary focus in the crypto space
🎨 I'm also beginning my public creative journey in Web 3.
Open to criticism and feedback 🤝
See you there🖐️
Voting for Phase 2 builders has started!
If you’ve enjoyed our product, please interact with this post:
• Like
• Retweet
• Reply (any comment)
Each interaction counts as a vote for us and helps us ship more tools for you 🚀
@BidAsk_bot I’ve only just started using this bot
So far I’m happy with it, super convenient and really easy to use.
Looking forward to the next update's 👀
@M1poly If it really gets that far, what happened with Panama will look like nothing, and NATO plus the whole Western security setup will just blow up from the inside 💥
Nice kickoff 🔜
This web protocol has a pretty cool rev share model for creators, curious to see what kind of tokens spin up on it.
Maybe you wanna ape in too?
Wordledotfun
This is not just a word game.
It is an attempt to recover something that was deliberately hidden.
At the core lies a 12-word seed phrase.
It cannot be seen all at once.
It can only be assembled - step by step - following a familiar Wordle-like logic:
letters hint, order deceives, mistakes leave traces.
Players do not act alone.
An AI agent stands in opposition.
It does not tire.
Its attempts recharge slowly than human limits.
It adapts to every incorrect word.
Each move shifts the balance.
Each failure tightens the search.
Even waiting works against you.
$1500 awaits those who reach the end.
@gem_insider@Vivek4real_ Or on the brink of a spectacular crash.
You’ll only know for sure what happens once it starts.
My forecast: the chart goes to the right - take a screenshot 👍
Address poisoning: The silent killer of deposit
One of the most underestimated UX threats in on-chain systems globally.
This is not a story about hack, malicious contract, or dangerous signature.
It’s a case of human inattention - with a $50 million price tag.
What happened?
The user was withdrawing funds from Binance to their EVM address.
After a 50 USDT test transfer, an unfamiliar address appeared in the transaction history just before the main transfer.
That address was generated to match the real one in first & last characters and was injected into еру history via a zero-value (“dust”) transaction.
Since most wallets (including MetaMask and mobile UIs) hide the middle of the address, the user missed the substitution and executed transaction.
As a result, around $50 million USDT was sent to the wrong address.
The key point.
Address poisoning does not rely on protocol vulnerabilities.
It only exploits user habits: copying addresses from transaction history and superficial visual checks.
These schemes are highly automated, low-cost gas, and offer massive ROI, making them extremely popular.
What happened next?
Subsequent on-chain actions were very fast: USDT from the substituted address went through a technical contract and aggregator, spread across DEXs & pools including Curve, Uniswap, converted via stable into ETH (~16,6k ETH), and then sent to Tornado Cash to complicate further tracing.
After the incident, the wallet owner offered to return 98% of the funds, leaving around $1 million as a white-hat bounty.
There has been no response, and most likely there won’t be one.
Key takeaways.
• Never copy addresses blindly from transaction history;
• Fix the destination address in advance (address book, ENS);
• Remember that a successful test transfer is not a reason to relax;
• For large amounts, use hardware wallets and extra confirmations.
This case shows that however experienced you are, a single hasty move can be one of the most expensive mistakes of your life - at least financially.