Zoro

543 posts

Zoro banner
Zoro

Zoro

@zoroswap

concentrating dark liquidity. TG: https://t.co/YvxDGadVc9

Katılım Ağustos 2025
28 Takip Edilen493 Takipçiler
Sabitlenmiş Tweet
Zoro
Zoro@zoroswap·
check out our introductory article, it's concise and to the point. 🤺 -your private trading hub(by) @zoroswap/introducing-zoroswap" target="_blank" rel="nofollow noopener">paragraph.com/@zoroswap/intr…
English
14
9
65
8.8K
Zoro
Zoro@zoroswap·
🚨 BREAKING 🚨 ZoroSwap is moving to Ethereum Classic. ZK was never proven.
English
6
1
23
811
Zoro
Zoro@zoroswap·
Hon hon hon, Zoro team is on our way to @EthCC 🇫🇷🥖 see you there!
English
1
0
5
184
Alexander John Lee
Alexander John Lee@alexanderlee314·
“I have nothing to hide” is to privacy what “I have nothing to say” is to free speech.
English
2
6
35
1.5K
Zoro
Zoro@zoroswap·
@bjnpck What you mean brink - WWIII has already started, and blockchain privacy is as important as ever.
English
1
0
0
21
Bojan
Bojan@bjnpck·
We’re on the brink of ww3 and I’m supposed to talk crypto on the French Riviera. Oh well… dms open.
English
6
0
37
2.6K
Zoro
Zoro@zoroswap·
@0xEpochProtocol It's gonna be ok ;) Less baggage, more opportunities.
English
2
0
3
62
EPOCH🦇🔉
EPOCH🦇🔉@0xEpochProtocol·
It's not you, it's us. We're breaking up with "Protocol" Just Epoch now. Single and ready to mingle with mainnet 💅😙 New era, who dis? 🔥
English
32
12
73
3.5K
Zoro
Zoro@zoroswap·
@0xQash Ahead of the curve 💯💯
English
1
0
4
106
Meraki
Meraki@mayrahkeee·
@zoroswap Without scale, this industry isn't going to privacy
English
1
0
0
24
mico
mico@0x0_mico·
@zoroswap when u zoom into getAccount
mico tweet media
English
1
0
2
32
Zoro
Zoro@zoroswap·
@vanebuilds_ @Deon643 There wasn’t any wrongdoing - just the system is fundamentally broken by allowing such transactions to take place. That’s why concentrated liquidity is one of our solutions so shit like this does not happen.
English
2
0
2
12
Deon🐧
Deon🐧@Deon643·
The $49M loss happened because: A massive swap was executed through low liquidity pools. Thou, the router followed instructions exactly but There was no price protection. Instead of order books like centralized exchanges, they rely on liquidity pools. @zoroswap changes the game
Zoro@zoroswap

A user swapped $50M USDT to 324 AAVE, resulting in an instant $49M loss. Founder of Aave Stani remarked: “routers functioned as intended, and the integration followed standard industry practices”. The trade happened on CoWSwap 🐮 @CoWSwap as much as we love you, we are changing the standard industry practises 🫡 We have to.

English
3
0
6
136
Zoro
Zoro@zoroswap·
@vanebuilds_ @Deon643 it can - it went to the pockets of those who sold the 324 AAVE tokens.
English
1
0
3
17
Zoro
Zoro@zoroswap·
@vanebuilds_ @Deon643 it went to the pool providing illiquid liquidity on Sushiswap router 💀
English
1
0
2
22
Long
Long@heynokanoi·
@zoroswap welcome, noob question, faucet always response "Not so fast! Wait 5 secs and try again."
English
1
0
0
12
Zoro
Zoro@zoroswap·
back online - our ZK proofs were too heavy. laser-focused on uni-style pools
Zoro tweet media
English
5
0
13
337
Zoro
Zoro@zoroswap·
A user swapped $50M USDT to 324 AAVE, resulting in an instant $49M loss. Founder of Aave Stani remarked: “routers functioned as intended, and the integration followed standard industry practices”. The trade happened on CoWSwap 🐮 @CoWSwap as much as we love you, we are changing the standard industry practises 🫡 We have to.
Stani@StaniKulechov

Earlier today, a user attempted to buy AAVE using $50M USDT through the Aave interface. Given the unusually large size of the single order, the Aave interface, like most trading interfaces, warned the user about extraordinary slippage and required confirmation via a checkbox. The user confirmed the warning on their mobile device and proceeded with the swap, accepting the high slippage, which ultimately resulted in receiving only 324 AAVE in return. The transaction could not be moved forward without the user explicitly accepting the risk through the confirmation checkbox. The CoW Swap routers functioned as intended, and the integration followed standard industry practices. However, while the user was able to proceed with the swap, the final outcome was clearly far from optimal. Events like this do occur in DeFi, but the scale of this transaction was significantly larger than what is typically seen in the space. We sympathize with the user and will try to make a contact with the user and we will return $600K in fees collected from the transaction. The key takeaway is that while DeFi should remain open and permissionless, allowing users to perform transactions freely, there are additional guardrails the industry can build to better protect users. Our team will be investigating ways to improve these safeguards going forward.

English
7
0
15
619