All Cooking Recipes

United States app store
Joined July 2010
Hi guys Happy Wednesday
1
52
Emma Stone retweeted
4,000+ More than 4,000 holders are already part of the $CRYSTALSTONES ecosystem. That's not the finish line. It's the beginning of a much bigger milestone: Real-world value can scale through on-chain!! @crystalstones01 Website: crystalstones.org/ TG t.me/CrystalStones ✅Live on CoinMarketcap & Coingecko ✅ Dexscreener: dexscreener.com/bsc/0x52bF22… CA Bep20 0xe252FCb1Aa2E0876E9B5f3eD1e15B9b4d11A0b00 #CRYSTALSTONES #RWA #BNBChain
44
23
36
4,782
Emma Stone retweeted
GM builders 😼 I don’t even know how to describe this morning lmao. Spent all morning trying to wake Eva up - she finally woke up and immediately beat my ass… Everything according to plan 😹 How’s your morning going?
54
9
91
2,857
Emma Stone retweeted
Buy $CRYSTALSTONES October is knocking 🚀 Don't snooze RWA On Chain @crystalstones01 Website: crystalstones.org/ TG t.me/CrystalStones ✅Live on CoinMarketcap & Coingecko ✅ Dexscreener: dexscreener.com/bsc/0x52bF22… CA Bep20 0xe252FCb1Aa2E0876E9B5f3eD1e15B9b4d11A0b00 #CRYSTALSTONES #RWA #BNBChain
41
22
41
5,876
Emma Stone retweeted
I'm out to take out them bears @crystalstones01 is breaking out to a new ATH and it won't be delayed. It's only wise to take position now! $CRYSTALSTONES BSC: 0xe252FCb1Aa2E0876E9B5f3eD1e15B9b4d11A0b00
18
8
67
1,440
yeah the part where the hacker was still in the logs after 21:22 is crazy they had time but still left money sitting there
History was happening right in front of us. while people were catching me up on what I'd missed over the past two weeks, one of the biggest thefts of the year was underway. Yeah, I'm still talking about @bitget getting cleaned out for $387.5m CT is still talking about how Bitget will cover the losses. researchers are digging through blockchains hoping for a bounty, and @zachxbt is already naming the middlemen laundering the stolen cash. (btw, I hope he actually gets paid for his work this time) I'm obsessed with wallets, so I went digging into how this attack was even possible and what the team did when they spotted it. Mandiant and slowMist lay out the attack vector in their reports. Links if you want to read them: img.bgstatic.com/multiLang/e… github.com/slowmist/Knowledg… But after reading them, I've got more questionss about the team's response than anything else... Three times in Bitget timeline. september 24, all utc: 19:05: Risk controls spot a discrepancy and block withdrawal requests. 20:40: The team starts moving funds to cold wallets. 21:44: They shut down withdrawals, including the transaction signing service. 2 hours and 39 minutes between blocking requests and shutting down signing. Were you guys asleep or what? And the thief didn't just leave some signed transactions behind and walk away. After 21:22, he was still looking through logs, checking request statuses, still trying to steal BTC. So requests were already being blocked. And the hacker was still in there, working inside the infrastructure. Take the usdc transfers. at 20:41, 2.6m usdc gets moved out of the hot wallet address on ethereum: etherscan.io/tx/0xb9f716952b… On Avalanche, that same address has 8.6m USDc left after a series of transfers around 20:40. at 20:55, 8.2M of it goes to the attacker: snowtrace.io/tx/0x4d2d95dadf… Why the hell was that money still there? Did you forget about it? Couldn't move it in time? I don't like kicking people when they're down. But for an exchange this size, this looks negligent. You're already blocking requests, you're moving funds, and the hacker is still working inside your infrastructure. Why were millions in usdc still sitting in that wallet for him to take later? Okay, a third-party vulnerability explains how he got in. But how far he could get into your systems and how fast you could cut him off, that's on you. I don't know what the team had figured out minute by minute during the hack. But being ready for shit like this should've been part of your product from day one. My feed is full of people talking about money leaving Bitget. Looks like net outflows hit roughly half a billion dollars in the first 24 hours after they started bringing withdrawals back. And I get it. nobody wants a security crew that's already there but holds back the homeowner while the thieves carry their stuff out. I'm a fan of decentralization. This just made me more sure of it. I want to control my own money and take responsibility for my own decisions. And if you take on the job of holding other people's funds, you're responsible for keeping them safe. (Protecting them, not paying them back.)
86
Not every move needs a reaction. Sometimes just chill and let the market do its thing
31
The moon looks extra beautiful tonight
25
Not gonna lie the confidential trading angle is probably what makes @ekidenfi stand out to me. A trader shouldn’t necessarily have to broadcast every move just because settlement happens onchain.
11
Getting started on Ekiden is sign in, get access, deposit, then trade. You can use Google or a Canton wallet. The terminal supports limit market and stop orders. You do not need six bridges and a research paper. Open app.ekiden.fi and follow the in-app steps.
13
116
Emma Stone retweeted
History was happening right in front of us. while people were catching me up on what I'd missed over the past two weeks, one of the biggest thefts of the year was underway. Yeah, I'm still talking about @bitget getting cleaned out for $387.5m CT is still talking about how Bitget will cover the losses. researchers are digging through blockchains hoping for a bounty, and @zachxbt is already naming the middlemen laundering the stolen cash. (btw, I hope he actually gets paid for his work this time) I'm obsessed with wallets, so I went digging into how this attack was even possible and what the team did when they spotted it. Mandiant and slowMist lay out the attack vector in their reports. Links if you want to read them: img.bgstatic.com/multiLang/e… github.com/slowmist/Knowledg… But after reading them, I've got more questionss about the team's response than anything else... Three times in Bitget timeline. september 24, all utc: 19:05: Risk controls spot a discrepancy and block withdrawal requests. 20:40: The team starts moving funds to cold wallets. 21:44: They shut down withdrawals, including the transaction signing service. 2 hours and 39 minutes between blocking requests and shutting down signing. Were you guys asleep or what? And the thief didn't just leave some signed transactions behind and walk away. After 21:22, he was still looking through logs, checking request statuses, still trying to steal BTC. So requests were already being blocked. And the hacker was still in there, working inside the infrastructure. Take the usdc transfers. at 20:41, 2.6m usdc gets moved out of the hot wallet address on ethereum: etherscan.io/tx/0xb9f716952b… On Avalanche, that same address has 8.6m USDc left after a series of transfers around 20:40. at 20:55, 8.2M of it goes to the attacker: snowtrace.io/tx/0x4d2d95dadf… Why the hell was that money still there? Did you forget about it? Couldn't move it in time? I don't like kicking people when they're down. But for an exchange this size, this looks negligent. You're already blocking requests, you're moving funds, and the hacker is still working inside your infrastructure. Why were millions in usdc still sitting in that wallet for him to take later? Okay, a third-party vulnerability explains how he got in. But how far he could get into your systems and how fast you could cut him off, that's on you. I don't know what the team had figured out minute by minute during the hack. But being ready for shit like this should've been part of your product from day one. My feed is full of people talking about money leaving Bitget. Looks like net outflows hit roughly half a billion dollars in the first 24 hours after they started bringing withdrawals back. And I get it. nobody wants a security crew that's already there but holds back the homeowner while the thieves carry their stuff out. I'm a fan of decentralization. This just made me more sure of it. I want to control my own money and take responsibility for my own decisions. And if you take on the job of holding other people's funds, you're responsible for keeping them safe. (Protecting them, not paying them back.)
Replying to @Jhett_Green
$352m? If that number checks out, @bitget just made it into the biggest fuckups we’ve talked about here today This post was supposed to be satire… but seriously, this is awful. Really hope the team gets it sorted fast They have a Protection Fund, so I’m less worried about user funds. Bearish for the market. a reminder for users to be careful with their keys. and for those of us building, warm and hot wallets need more layers of protection
107
34
8
306
45,124
They’re clearly using this phase to learn from real trading activity. That’s how a platform gets better before opening up wider.
This Post is from a suspended account. Learn more
19
Emma Stone retweeted
Leverage updates came at the same time as the volume milestone. It gives more control for active strategies without changing the risk approach. Ekiden is adjusting based on real trading. That kind of responsiveness is worth noting. @ekidenfi worth watching atm #Ekiden #Crypto
8
7
5
24
559
Emma Stone retweeted
Most perp DEXs compete on the same things like more leverage, more markets, deeper liquidity, faster execution. @ekidenfi is taking a different angle. It is building the first CLOB-based derivatives exchange on @CantonNetwork, with one feature that immediately changes the trading environment which is positions and account activity are not public by default. That matters because one of DeFi’s biggest weaknesses for professional traders is transparency. On most chains, large positions, liquidation levels, wallet activity and trading behaviour can all be reconstructed from public data. Ekiden is trying to bring perpetual markets into an environment where traders can still get onchain settlement without broadcasting their entire book to the market. And @CantonNetwork is what makes that possible. — ● Canton uses a need-to-know data model. Instead of every transaction being visible to everyone on the network, participants only see the information they are entitled to see. So the trading flow becomes closer to: Trader -> Ekiden CLOB -> confidential execution -> Canton settlement while individual positions and account activity stay outside the public view. That is a very different model from most crypto-native perp venues. Ekiden mainnet is already live, although access is still invite-only and the first rollout is focused on active traders. Less than two weeks after launch, the exchange has reached: • $3.3M+ trading volume • $329K+ TVL • $115K+ open interest • current perpetual markets include $BTC , $ETH , $HYPE , $CC with leverage up to 20x. Those numbers are still early, but the more interesting part is the market structure being tested underneath them. — ● Ekiden is not built like a simple AMM-based perp venue. It uses an institutional-style central limit order book. That gives professional traders access to the kind of execution model they already understand: • Limit orders • Order-book liquidity • Market-making strategies • Algorithmic execution And the infrastructure goes deeper. Ekiden exposes REST and WebSocket APIs, which means market makers and trading firms can connect programmatically instead of relying on a frontend. That matters if Canton’s derivatives market is going to attract professional liquidity. Retail traders care about the interface but professional traders care about latency, API access, execution quality and information leakage. Ekiden is clearly being designed around the second group. — ● The account architecture is also worth noting. Ekiden uses account abstraction to separate: • network identity • funding • trading activity That separation can make institutional trading infrastructure much cleaner. A firm does not necessarily want the same address used for identity, custody, funding and every individual trade. Separating those layers gives traders more flexibility around permissions and operational security. Combined with Canton’s privacy model, it starts looking closer to how institutional trading systems are normally structured. And this is why Ekiden is interesting within the broader @CantonNetwork thesis. Canton already has institutional activity across areas like: • Treasuries • Repo • Collateral • Securities lending • Digital cash But public DeFi and trading infrastructure on the network are still early. If Canton wants to become a broader capital-markets network, it eventually needs more than tokenized assets and settlement. It also needs actual markets around those assets and @ekidenfi is attacking the derivatives layer. The bigger opportunity is not simply offering BTC or ETH perps on another chain. It is building the trading infrastructure that could eventually support confidential derivatives around tokenized financial assets.
1
14
1
24
210
Canton’s design allows true private execution. Ekiden is using it the right way for derivatives. Order flow stays protected while settlement stays on chain. This choice will matter more over time than short term volume.
5
4
4
24
153
Canton’s design allows true private execution. Ekiden is using it the right way for derivatives. Order flow stays protected while settlement stays on chain. This choice will matter more over time than short term volume.
6
3
7
25
403
Emma Stone retweeted
This September was huge for Canton ecosystem updates. Details are in the article 👇
33
22
51
1,982
That support level is definitely worth watching. Ekiden is also building momentum with private trading and growing Mainnet activity. Interesting times ahead.
Perfect bounce exactly where it matters for solana:2zMMhcVQEXDtdE6vsFS7S7D5oUodfJHE8vd1gnBouauv Hold here to next send it higher towards 0.02 The face of crypto will be trading at multi billions valuation
15
I’ve been watching @ekidenfi move from testnet into live trading and the progression is pretty easy to follow. The testnet showed early activity and now the closed Mainnet has passed $3.3M volume. The next part I’m interested in is how the live market develops over time.
10
11
82