Devansh

🧵Summary of 8 High issues found in the recent C4 audit of @RenzoProtocol Shortly explained, one by one👇

I've officially set a target to become a fully-fledged Rust auditor by Jan 5th Will try to docs my humble steps to learning the language, while sharing valuable resources that I find along my journey github.com/rust-lang/rust… small exercises to get you used to reading and writing

List Of 18 Defi Vulnerabilities + Code Examples: 👇 github.com/0xRajkumar/Def… 1. DOS 2. Delegate call 3. Divide before multiply 4. ERC777-reentrancy 5. Iscontract 6. Outdated cache 7. Overflow 8. Private data 9. Randomness 10. Reentrancy 11. Selfdestruct 12. Side-reentrancy 13. Storage collision 14. Strict equalities 15. Transaction origin 16. Unsafe call 17. Visibility 18. Unchecked External Call

Auditing guidelines for NFT Protocols: olympixai.medium.com/nft-smart-cont…

Stylus is a game changer for @Arbitrum Orbit rollups By enabling devs to write smart contracts in WASM languages like Rust, Stylus expands your rollup’s dev talent pool and increases performance Here’s why that’s important and how Conduit makes Stylus easy to implement

DYM Sponsorships: Onchain permissionless incentives for RollApps! Test it on Playground now: playground.dymension.xyz/dymension/spon… 🧵👇

Scroll is embarking on its first step towards decentralization. 𝐖𝐞 𝐚𝐫𝐞 𝐞𝐱𝐜𝐢𝐭𝐞𝐝 𝐭𝐨 𝐚𝐧𝐧𝐨𝐮𝐧𝐜𝐞 𝐭𝐡𝐞 𝐥𝐚𝐮𝐧𝐜𝐡 𝐨𝐟 𝐭𝐡𝐞 $𝐒𝐂𝐑 𝐭𝐨𝐤𝐞𝐧. Our vision is to provide everyone, everywhere, access to a global distributed network of applications and services. To double down on our global mission, $SCR will soon be available on @Binance Launchpool and via our upcoming airdrop. 🔗: scroll.io/blog/scr-token 1/8 🧵

Our name comes from a mission that we are “𝐒𝐂aling with a 𝐑𝐎𝐋𝐋up” = Scroll 📜 We’re building something unique with a smooth end-user experience that brings the world onchain. We're excited to share our journey so far, our vision, and what's next. 🔗: scroll.io/blog/scroll-ev… 👇 🧵

🎉We are thrilled to announce the integration with @arbitrum ✨ By deploying on #Arbitrum, Pay Protocol aims to build a dynamic, safe, and efficient payment environment. Providing limitless possibilities for users, projects, and developers on Arbitrum through resources synergies

White-labeling protocols are starting to become common, like Morpho and their Gauntlet vaults Should we list both (gauntlet and morpho) as protocols on defillama even though they use the same contracts, or only one (morpho)?

How can I say "I only audit projects built with Foundry" without seeming like a dick?

Wrote a generic (over the number of `bitsPerIteration`) Strauss Shamir impl. The space complexity is O(2 ** 2n), where n is the bitsPerIteration. Because of this, it's important to find a balance between gas cost per iteration and memory expansion cost that comes with reducing the number of iterations by storing precomputed values in memory. OpenZeppelin for example, uses 2 bits per iteration for their P256 verifier. This example uses scalar numbers for simplicity but would also work if used with EC points and operations.

Day 6: An overlooked Solidity resource: Solidity Summits. There have been 3 so far, with the last in Istanbul. Here are links to the 2020, 2022, and 2023 sessions. Also subscribe @ethereum 2020: youtube.com/watch?v=eZERCE… 2022: youtube.com/watch?v=6m5EDu… 2023: youtube.com/watch?v=keVdpq…

Not many people know this, but there's been a full game of smart contract vs smart contract chess on mainnet ~2 years ago Seeing @z0age's contract beat mine was like the happiest moment of that month for me

We're excited to announce that creators can now use ERC721-C from @limitbreak to set and enforce their own creator earnings on OpenSea. What is ERC721-C? ERC721-C is a standard that enables creators to implement programmable and enforceable creator earnings on-chain. It also allows creators to implement custom logic within their collections, opening up new avenues to engage their communities in innovative ways. How does it work? Two weeks ago, we launched a new version of the OpenSea marketplace protocol, Seaport v1.6, and introduced a concept called Seaport Hooks. Simply put, Seaport Hooks allow creators to set conditions that need to be fulfilled before NFTs in their collections can be transferred. This new functionality enables creators to do a lot of cool things, including “adapting” Seaport to be compatible with the creator fee enforcement mechanism of the ERC721-C standard. What do I have to do? It’s simple! If you’ve already deployed an ERC721-C contract, we’ve built a tool for configuring creator earning enforcement in OpenSea with one click. You can find it in the OpenSea Creator Studio under Edit Collection > Earnings. You can also configure NFTs you deploy starting today through the OpenSea Creator Studio to be 721-C compatible in the same manner. For more information for creators, see here: support.opensea.io/en/articles/88… For more dev-centric technical information, see here: docs.opensea.io/docs/creator-f… Who is eligible? In order to leverage the 721-C compatibility hook, an NFT smart contract must already adhere to the 721-C standard or be upgradeable to one. The owner of that smart contract must then configure 721-C compatibility in the OpenSea Creator Studio — 721-C contracts, by default, will not be purchasable on OpenSea (with or without creator earnings) otherwise. Why now? The “hook” capabilities unlocked by Seaport 1.6, such as ERC721-C compatibility, are uniquely enabled by the recent March 13th Dencun upgrade to the Ethereum network. Anything else to know? The spirit of Seaport 1.6 is to allow creators to explore different models of NFT monetization. With that being said, OpenSea’s “earnings matching” policy will help ensure collectors are not unfairly disadvantaged on our site if creator earnings are set at different levels across other NFT marketplaces. This policy won’t impact you if your earnings are configured at the same percentage on OpenSea as other marketplaces. Learn more in the FAQ in our help center article: support.opensea.io/en/articles/88… We’d like to thank the Limit Break team for their work and collaboration in supporting ERC721-C compatibility with Seaport 1.6. To learn more, check out our blog: opensea.io/blog/articles/…

I could write low-level evm code for the rest of my life.

Gas optimisation is an essentially a solved problem. If your Solidity contract is important enough, someone will automatically rewrite it in huff for free. We need to be optimizing for compilation speed to maximize iteration speed.

8 live criticals so far - want to know my secret? - Arbitrum - Balancer - Radiant - RadPie - Prisma - Deri - Sommelier - Polymarket i simply enjoy reading smart contracts and finding ways to break them have easily read over a thousand contracts staring at the same code for hours getting lost on the blockchain months with $0 income and zero bugs found if you want to compete in this arena you need patience and you need to put in the work day in day out or you won't make it also should be extremely ripped and jacked at all times gl anon

The @huff_language huff-rs repo, along with all repos in the github account, has been archived on September 9th. Big thanks to the core team who gave a great deal of unpaid time building the Huff compiler. You might have created more EVM wizards than anyone else in the world 🙏

Day 4: making progress! For Solidity learners, solidity-by-example.org is perfect! It provides code for key Blockchain areas like DeFi, Hacking, Apps, etc. Bonus: from the same owner, @ProgrammerSmart check smartcontract.engineer for courses & challenges 💪