dmtrbch

@crypto_condom @netflix @warnerbros @Disney @YouTube @TikTokInvestors it's actually these companies that will benefit the most out of Seedance

@crypto_condom @netflix @warnerbros @Disney @YouTube @TikTokInvestors yeah sure, good luck thinking Disney would allow average joe playing with their Spiderman on Seedance in the long run

Creator companies like @netflix, @warnerbros, @Disney, etc are going to open red on Tuesday thanks to Seedance and 4 new LLM updates. Companies with vertical distribution platforms like @YouTube or @TikTokInvestors will be the most obvious first beneficiaries from these updates.

Introducing SFULC, launching soon on @solana. A yield-bearing token offering exposure to a 10% APY private credit strategy. Liquid, tradable, and designed for DeFi from day one.

@AdamRackis When TanStack Start course on FEM? 😀

Just checked out Svelte's remote functions. If I had to choose between building an app with Next, vs SvelteKit I'd choose SvelteKit, and it'd be an easy decision. But the qualitative difference with TanStack is enormous. As always with Svelte you get heavy abstractions optimized for the most common use cases, built in the easiest way possible. This results in an enjoyable experience for most apps, and of course glowing survey results. Easy vs Simple. But breaking out of that 80% common use case is hard. Look at the single-flight mutations code from the docs svelte.dev/docs/kit/remot… You run your mutation, then call refresh() on the relevant query. Easy! TanStack server functions don't have an easy .refresh() method. What was Tanner thinking?! Back up a second, and think about coupling. The sample code in the docs has this in the updatePost RPC await getPost(post.id).set(result); updatePost has to know exactly which queries to update. Now think about a large, mature software application like Jira (however shitty the UX). Think about an update() method that updates a task. Think about how many different UI screens that backend method might be called from. Any of those screens might have *different* queries currently active, which need to be updated. The backend update() method has no way of knowing what data are currently active on the client. Svelte does also allow you to specify this from the call site, on the client. await addLike(item.id).updates(getLikes(item.id)) That gets you closer, but even still, your call sites are cluttered, and coupled. To put a finer point on it: it may not be easy or convenient for the place where you call updatePost to know which queries involving posts are currently active in the UI. So how does TanStack enable things like Single Flight Mutations? You have the mature data-fetching library react-query. It has api's to inspect exactly which queries exist, and are active on the client. You have middleware for your Server Functions that run on the client, and also on the server. Middleware can check the queries currently active on the client via react-query, and note what needs to be re-fetched. Server Functions are *serializable* in TanStack. That makes it VERY easy for client middleware to tell server middleware exactly what to re-fetch, and how. You can tell TanStack's middleware that a given server function needs to update any active queries with a key starting with `[todos]` and be done. Middleware will determine which queries those are, and how they're updated. And react-query is tightly integrated with normal SSR, so you can do all this without sacrificing anything on your initial render performance. Does the TanStack version demo as well as the SvelteKit version, in a few lines of code, lending itself to snarky memes? No. But the TanStack version is more robust and composable, and ready for whatever unhinged edge case you need to accommodate in production. That's why I love it. Easy vs Simple.

It starts here. Strands, our rewards system, is now live. Earn through deposits, referrals and activity across the ecosystem. Early participants get bonus strands. solana.splyce.finance/rewards

Chintai originates. @solana distributes. Chintai tokenizes institutional RWAs and brings them on-chain. Now we're bringing those assets to Solana, the marquee distribution venue for liquidity and real-time settlement. Powered by @SplyceFi and available to anyone with a wallet.

$400T in RWAs. Less than 0.1% onchain. It’s time to bring capital markets to Solana.

@aayushmayush Try this one: rareskills.io/learn-solidity… @RareSkills_io are goated for Solidity deep dives

I was learning ERC20 through cyfrin but he hasn't developed it from scratch. Only open zeppelin import was done. I wanna learn about tokens more. Any recommendations ?

@PatrickAlphaC 2025 -> something something zk 🤫

Took some time off from social media, man did it feel good, but it's important to come back. When I stop posting YouTube videos or tweets, it means we are cooking something up, or I need a break! This break, it was both! Every time I stop posting, it is followed up by something crazy. - 2020 -> Launched the most watched solidity tutorial on earth with Brownie - 2021 -> We did it again with Hardhat - 2022 -> We launched Cyfrin 🤯 (Yes, Cyfrin is less than 3 years old) - 2023 (again) -> We launched CodeHawks & Updraft - 2024 -> The most insane security, assembly, and formal verification tutorials ever - 2025 -> ...you'll see We are a couple months out from it, but you'll see. Ooohhhhh you'll see. For my break, I went to an international weightlifting meet and got 2nd in my age and weight class, so that was cool.

I enjoyed talking to @0xZedz_ about @SplyceFi and how we are integrating tokenized assets into the internet economy.

Billions once gated in TradFi are being unlocked on Solana. Fast. Permissionless. For everyone. Splyce is the home of real-world yield.

@FundableHQ @Starknet 0x06c46234e74cf75da5442595bb2866aad0468cd62b870690133ac24cd5a953de

Drop @starknet wallet addresses

@martypartymusic @ethereum Conventional programmers avoid edge cases. Therefore, attackers find opportunities in edge cases. Therefore, defenders must thoroughly understand edge cases. Therefore, designers should minimize edge cases.

@martypartymusic @ethereum Over the years, the percentage of DeFi hacks due to re-entrancy attacks has significantly decreased. It's one of the least used exploit methods in recent years, but I would agree that this is a bad design decision, especially for a blockchain holding hundreds of billions in TVL

What is the major flaw in @ethereum you may not be told about by Tom Lee that has accounted for 80% of blockchain exploits and remains unfixed and unable to be fixed. The re-entrancy bug in Ethereum refers to a vulnerability in smart contracts that allows an attacker to repeatedly call a function before the previous execution completes, potentially draining funds or manipulating contract state. Below is a detailed explanation of the technical issues associated with the re-entrancy bug: 1. What is Re-entrancy? Re-entrancy occurs when a smart contract calls an external contract or sends $ETH to an address, and that external contract or address re-enters the original contract by calling one of its functions again before the initial execution is complete. This can lead to unintended behavior, such as multiple withdrawals of funds. Ethereum smart contracts often use functions like call(), send(), or transfer() to send $ETH or interact with other contracts. These external calls can trigger the recipient contract's fallback function (or other logic) before the calling contract updates its state. If the contract's state (e.g., balances or flags) isn't updated before the external call, the attacker can exploit this by re-entering the function. Consider a vulnerable contract: (Solidity code) contract Vulnerable { mapping(address => uint) public balances; function withdraw() public { uint amount = balances[msg.sender]; require(amount > 0); (bool success, ) = msg.sender.call{value: amount}(""); // External call require(success, "Transfer failed"); balances[msg.sender] = 0; // State update after call } } An attacker deploys a malicious contract with a fallback function that calls withdraw() again: contract Attacker { Vulnerable vulnerable; constructor(address _vulnerable) { vulnerable = Vulnerable(_vulnerable); } fallback() external payable { if (address(vulnerable).balance >= 1 ether) { vulnerable.withdraw(); // Re-enter } } function attack() external { vulnerable.withdraw(); } } When withdraw() sends $ETH (or any erc-20) to the attacker's contract, the fallback function triggers, calling withdraw() again before balances[msg.sender] is set to 0. This allows the attacker to drain the contract's funds. Note: This bug will be exploited forever and will risk anything substancially valauble from being passed through a Ethereum Smart Contract. This renders Ethereum as a "psuedo" Store of Value, simply holding "zipped" Layer 2 transactions with a 7 day escrow window. But dont be misled, Ethereum will never be the Execution Engine that powers the internet. It is a Proof Of Stake Store Of Value at best. But Bitcoin is a better Store of Value and Solana and SUI are exponentially better Execution Engines. You probably dont know about this critical bug in Ethereum that has led to massive losses and limited the use of Ethereum in applications due to the insane amount of defensive code required to protect any functionality from the bug. But within the engineering world, we know about it, have abandoned Ethereum as development tool and have moved to more modern environments and chains with real languages and without re-entrancy risks. But Tom Lee wont tell you that. He is shilling.

@Designer_Misbah it's inspired by Tendermint btw 🙂

mark Zuckerberg abandoned his blockchain. i found the secret behind it. it's called Hotstuff. and you're ngmi if your chain is not using it. let me unpack it 🧵

@Jeyffre Ekubo is doing something interesting in the AMM space. They've just launched their V2 version of the protocol on mainnet, and it seems they have managed to reduce swap gas fees by up to 30% compared to other AMMs

Automated market makers are an outdated solution to having high gas prices and high confirmation times. AMMs by design have zero depth of liquidity. Supplying liquidity with such a simple, non-adaptive, and predictable algorithm is why LPs get abused so easily. Now that blockchains are fast, we should return to order book. Change my mind.

@eagleag_c probably connect github on application page...?

2) For Dev roles, I saw candidates were using others' github profiles to gain interviews, wonder if there is any way to filter this out during the screening phase? (5/7)

We have been hiring for a few roles recently, we have now closed the processes and excited for the new hires to start! I want to thank all the candidates that went through the process; I wish we had more open positions; there's some excellent talent at the moment.

@RealJohnnyTime @StarknetFndn @Om_Santoshwar @MSG_Encrypted @ayur_27 @0xaudron @1techhunter @Pelz_Dev @rejwar @0xLegendaire @AnmolSirola @Icon_70 thanks for the opportunity, I'm sure it will help level up my Cairo game 🚀

IT’S HERE❗️ Together with @Starknetfndn, in no particular order, we are thrilled to welcome 18 new CSCH students to the community 🥁 @Om_Santoshwar @MSG_Encrypted @ayur_27 @0xaudron @1techhunter @Pelz_Dev @rejwar @0xLegendaire @AnmolSirola @Icon_70 @dmtrbch @CipherShade @0xjarix @scarcemrk @ManiVeer198 @Sriki09182003 @Likitd_ @SerahOluwatosin Congratulations! You will be receiving access to the learning platform shortly 🫡 To everyone who did not get in this time, keep up the great work, and I’m sure there will be more opportunities for you in the future 👀 You are also welcome to reach out for individual feedback🤝

@Galois_Capital In my opinion this was in no way an Ethereum issue, so I don't see a reason why should Ethereum hardfork (or rollback, or whatever you name it)

Very much agree.

Together with my team we participated in the Starknet Winter Hackathon and we even managed to secure 2nd place in the DeFi track. I would like to further advance my skills in auditing and writing Cairo smart contracts and the Scolarship is a great opportunity for that.

@RealJohnnyTime @Starknet recently I started learning about the Starknet blockchain and Cairo. For someone without prior experience in Rust, learning Cario was not straightforward, but I've managed to tackle the core concepts and how to write, test, deploy contracts on Starknet