Sabitlenmiş Tweet
so @monad mainnet is here, it's not going away. still not clear about what it does?
monad & chill, and be ready, with this video (sound on)
English
kitty4D.sui.sol (🟣)(🟣)
5.7K posts
kitty4D.sui.sol (🟣)(🟣)
@kitty4DHD
content creator, web3 dev / hacker https://t.co/ga4TtCJlUS $MRC https://t.co/3jFybfmjJn 👙
web3 Katılım Kasım 2021
1.1K Takip Edilen2.5K Takipçiler
Show us your best wins on Shuffle.US, and we'll pick 5 users at random to win 50 SC 💵
Drop your hits + usernames below.
No purchase required. Shuffle.US only 🇺🇸 in eligible areas. 18+ only, T&Cs apply.
English
Quests Are Officially Available in the Dashboard
We’re excited to share an official update for our community: Quests are now available in the Dashboard, with new tasks being added on a постоянной основе to keep participation active and rewarding
This update is focused on:
• Clear visibility of available Quests
• Regular Quest updates you can check anytime
• A simple way to complete tasks and earn points
Open your Dashboard, start completing Quests, and don’t miss new updates
Română
after 3 days of straight vibe coding
you can now bridge while you bridge
bridged.gg is live 🌉
zac.eth 🧙🏻♂️♦️@zacxbt
vibe coding a crypto bridge that's a bridge so you can bridge while you bridge
English
@nom14553 @buttji890 @ikadotxyz yes, tokens are minted, to provide the staking rewards
from ika.xyz/blog/ika-token…
English
@buttji890 @ikadotxyz Nice tool. But coinmarketcap has $ika max supply at 10.25B not 12bil. Are they already minting more tokens or whats going on?
English
I Have Vibe coded a Drizzlet analytics dashboard and a leaderboard 🐙
You can see how much drizzlet is being earned or was earned from certain way & Track the over all progress
The leaderboard page shows where do you stand in the next IkaChans uwu list fellow ZuDder's
⬇️
English
@metropolyse @zachxbt @evilcos @coinbase @im23pds when u repeat the same word 6 times in 2 small paragraphs, it's only human nature that the 7th time comes with a mistake
English
我很疑惑 Coinbase 为什么会有这样的页面，直接让用户输入明文助记词做资产恢复？如此不安全的行为，匪夷所思…@coinbase 我都差点以为子域名被黑了…cc @im23pds
withdraw.commerce.coinbase.com/seed-phrase
中文
because of my mocat, i won 46.15 $PIEVERSE (~$25 rn) from the @Moca_Network + @pieverse_io campaign
thx moca & pieverse! <3
perhaps it's time for u to adopt ur own mocat -
app.moca.network/r/ECHMWD
fyi this is evm so, if u don't ether, don't bother <3
kitty4D.sui.sol (🟣)(🟣)@kitty4DHD
this is my mocat 🐱 proof of my identity on-chain, evolving w every credential i eat. u want one too? adopt ur very own at this url → app.moca.network/r/ECHMWD
English
@crypt_willie @SuiNetwork could @blockvisionhq or @staketab chime in plz :D
how can we know if a project mints more of their token post-launch?
@ikadotxyz provides those urls - a black box ofc (could be hardcoded) - but the explorers don't pull from them anyways
do other projects have urls like theirs?
English
@crypt_willie @SuiNetwork ie,
ika-circulation.ika.xyz/api/total-supp…
ika-circulation.ika.xyz/api/circulatin…
only coinmarketcap uses these urls to report the total
why aren't the 2 "official" block explorers for @SuiNetwork showing the right data - & so how do we know that every sui token doesn't actually have a much greater supply?
English
is it just a @SuiNetwork thing that most explorers, including sites like coingecko and dexscreener, don't report the actual total supply of a token if more were minted post-launch?
or do we really have no idea the total supply of tokens on all blockchains
English
@SUITRUMPCOIN @crypt_willie @SuiNetwork the explorers which deal with on-chain data rely on info provided by projects
& have no way of detecting mint events for a token, like say, even just on a weekly basis, where they can update the supply etc.
so we, the users, have no clue the actual supply of ANY token on sui
English
@kitty4DHD @crypt_willie @SuiNetwork It’s because the two block explorers don’t share information. And the project themselves have to supply the block explorers with their token details if their packages are unique.
Very different to EVM where most things get picked up automatically or with little effort.
English
Yeah, so basically it turns out Meta has been heavily lobbying online age verification laws. They've lobbied over $2,000,000,000 to politicians in form of grants and donations.
x.com/bee_fumo/statu…
🐝🇬🇷@bee_fumo
someone traced the all the non profit grants for the age verification laws old.reddit.com/r/linux/commen…
English
@ShuffleUSA break the piggy bank
un: cenamancan
tia~! <3
English
Guess the game!
Drop your guess and username for a chance to win 50 SC. Three winners will be chosen at random!
No purchase required. Shuffle.US only 🇺🇸 in eligible areas. 18+ only, T&Cs apply.
English
You guys are fast… Here it is: AJ73NK
20 likes and I’ll drop a new code.
Moon Roll@moonroll
10 likes and I’ll drop a code.
English
@moonroll feed it direct to my dm first
like last time
thx
English
@xydotdot yeah it kinda infuriates me, and that literally every place has just copied the same dumb design w/o giving it any thought whatsoever
x.com/kitty4DHD/stat…
kitty4D.sui.sol (🟣)(🟣)@kitty4DHD
this warning text btw - it's not even a bright yellow, the font size is so small that the yield symbol is only recognizable because .. well, for me i think it's due to knowing traffic symbols, i dunno if this blurry triangle can be assumed to be recognized by the world? that RED text btw stands out more, and that's not something that would flag someone of a danger other than, yeah, everything here is gonna be volatile most likely and we're accustomed to that
English
How the fuck is CT grading this response on tone instead of product judgment?
Thinking the issue is that a warning appeared, that a user checked a box, or that the trade could technically be completed, is stupid.
The issue is that a leading interface in DeFi allowed a $50M order to move through a flow where catastrophic execution was an entirely predictable outcome. Once you know the order size, know the available liquidity, know the expected slippage, and know the probable output degradation, responsibility shifts to the system design itself.
At that point, hiding behind user consent is weak as fuck.
Consent inside a badly designed decision environment does not suddenly become good product architecture. Imagine using the same checkbox for acceptable slippage on a normal trade and on a trade that can lose $50M....
What they are doing, through lack of vision and lack of standards, is pushing liability downstream.
What makes this worse is that the solution is obvious.
Extreme order sizes should trigger a different class of interface behavior because they belong to a different class of risk.
Hard execution thresholds, delayed confirmations, forced acknowledgment of minimum output in large font, segmented execution paths, deeper routing logic, stronger friction as size detaches from liquidity, and escalation rules for absurd trades.
None of this requires a research breakthrough.
It requires teams to stop acting like legality at the transaction layer is enough to claim integrity at the product layer.
Aave has enough stature, enough resources, and enough industry visibility to know this.
So when one of the flagship names in crypto answers an event like this with “the warning was shown and the system worked as intended,” what it really communicates is something much uglier: the mindset of too many crypto founders is complacent as fuck, and that is exactly why the industry still struggles to earn the trust it keeps claiming it wants.
Stani.eth@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
@Tyroneael @xydotdot it's not technically "slippage" in this case though. slippage is only a price change after signing.
but yes, there should be additional controls on price impact w/ safe defaults- at the least. it's crazy to me cuz it's such an obvious UI/UX need!
English
@xydotdot Excellent take, I agree completely.
It is not difficult to create two interfaces:
- swap(): accepts up to 3% max slippage.
- swapExtremeConditions(): accepts any slippage, but requires an additional ECDSA signature of a text string such as "I accept full consequences of this"
English
@lukecannon727 @x87c8 @StaniKulechov there are times when a person DOES want to, though. if it's ur own token, or mb it's a utility token (cough) w low liquidity yet u simply need it to do a task
but yeah this is why i think for price impact there should be a % tolerance along with a max USD price difference
English
@kitty4DHD @x87c8 @StaniKulechov The UI should not let you swap with price impact or slippage tolerance that high
Case closed.
English
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
@x87c8 @lukecannon727 @StaniKulechov they could have seen on the UI and again in the wallet confirmation that they were getting a really bad deal
so they were def able to be informed
but the price difference shown on the UI is not called slippage, so the 0.01% tolerance he had set was not applicable on that
English
@kitty4DHD @lukecannon727 @StaniKulechov Are you sure? It sounded like the user clicked a checkbox accepting "the slippage might be high" and then the slippage turned out to be 99℅ of the transaction value
English