Actlysis

@0xsadikbaba Same to you bro🫶

Eid Mubarak from medina

@Web3_Vinay Anytime I keep seeing your tweet it motivate me more to push

🦖 Day 277 of learning blockchain 🔗 Today I started diving into Chainlink Payment Abstraction V2 What I learned about the protocol: → V2 replaces Uniswap V3 fixed swaps with a permissionless Dutch auction mechanism where anyone can bid on auctioned assets → How the linear price decay curve works — price starts at a premium and decays to a maximum discount over the auction duration → CowSwap integration via ERC-1271 — smart contracts post limit orders that CowSwap solvers compete to fill → Chainlink Data Streams integration for high frequency price updates during auctions with Data Feeds as fallback → AuctionBidder contract — handles arbitrary swap execution via callbacks, enabling DEX aggregator integration → WorkflowRouter — the onchain security gatekeeper with a 3-layer allowlist (workflowId → target → selector) for CRE workflow payloads

@Wallflower1x0 Enable auto save in case of this happen again

I just deployed and minted my FIRST EVER NFT on Sepolia with Foundry —and it feels surreal!🚀 Funny story: I was deep in the code, forgot to save, and accidentally shut my laptop. When I came back and saw my files gone,everywhere first blur😭,anyways I rebuilt it and minted it.

@Nischay42 Yh

@actlysis So you both brothers are in programming, that's interesting

Day 13 of #learningDsa Explored Graphs —undirected, directed, and weighted graphs. Learned how graphs can be stored using matrix representation and implemented an adjacency matrix creating a graph class, adding edges, and printing the matrix #DSA #LearningInPublic

@rosarioborgesi @OpenZeppelin Like they used to say there is no shortcut to success

@actlysis @OpenZeppelin I already knew most of them because I had studied Solidity by example vulnerabilities github.com/rosarioborgesi…

⚡Day 6 of Ethernaut with @OpenZeppelin ⚙️ Challenge 11: Elevator ✅ Challenge 10: Re-entrancy ✅ Challenge 09: King ✅ Challenge 08: Vault ✅ Challenge 07: Force ✅ Challenge 06: Delegation ✅ Challenge 05: Token ✅ Challenge 04: Telephone ✅ Challenge 03: Coin Flip ✅ Challenge 02: Fallout ✅ Challenge 01: Fallback ✅ Challenge 00: Hello Ethernaut Github 👇 github.com/rosarioborgesi…

@rosarioborgesi @OpenZeppelin Ohh

@Nischay42 Matrix I used to see my brother solving it

@actlysis Hmm really which topic?

🗓️ Day 50 – Smart Contract Journey 🚀 🔹Topic: Calldata Manipulation & ABI Encoding 📚 Key Learnings: ✅ Completed Switch level ✅ Learnt how to use cast pretty-calldata to format and break down calldata into readable segments (selector, offsets, lengths, data) ✅ Learnt how to craft custom calldata ✅ Corrected misunderstanding of how the EVM perceives calldata ✅ Understood that offsets point to where data is located, and at that location the first value is the data length before copying ✅ Understood that the EVM reads calldata in 32-byte words 💡 Security Mindset: Contracts that enforce access control using fixed positional bytes in calldata can be manipulated by attackers through crafted offsets and layout tricks 💡 Reflection: I initially assumed calldata had a rigid structure (head offset then size), but in reality it’s more flexible, understanding offsets changed how I see calldata and exposed how it can be abused

@WakeFramework Ohh thanks a lot♥️

@actlysis Hey! Thanks for the feedback. Much appreciated. The solution is simple, just remove these 2 entries in VS Code settings of the extension. Also, consider removing this entry to enable vulnerability detections in test files (although it's not recommended).

Most Solidity bugs in factory contracts hide in one place: the gap between what the factory deploys and what the registry assumes it deployed. Factories look simple until initialization parameters interact with proxy patterns or create2 salt collisions across chains. The patterns are well-documented. The edge cases are not. This is where fuzz testing earns its keep. Throwing thousands of deployment sequences at a factory contract reveals state assumptions that unit tests treat as given. Wake's fuzzer is built for exactly this kind of guided exploration, testing the contract logic itself rather than a mathematical model of it. Solid educational content for anyone leveling up their Solidity architecture.

@timsilva112 @zksync @zkSyncDevs Ohh

@actlysis @zksync @zkSyncDevs This one is actually not from my end It's from their package 🌝

Today's #solidity grind:Merkle Airdrop contd ✅signature standards ✅ took a quick quiz ✅Decoding ECDSA #signatures ✅Transaction types intro ✅Blob #Transactions ✅Understanding Type 113 transaction ✅Took another quick quiz ✅Implementing Signatures ✅Another quiz 😪

@GoldManeDesign Needed this alot😪♥️

When things go wrong, as they sometimes will, And the road you're trudging seems all uphill, When the funds are low and the debts are high, And you want to smile, but you have to sigh, When care is pressing you down a bit, Rest if you must, but don't you quit. 👇

@Wallflower1x0 Keep on going 💯🔥

Day 63 of my #Blockchain journey! 🎯 Today’s study : ✅ An introduction to Ethereum improvement proposals, ERC-20, and the ERC-20 token standard. ✅ Built an ERC-20 token manually with Foundry. ✅ Implemented an ERC-20 token using OpenZeppelin contracts and Foundry.

@_mannythegreat_ Nice🔥🔥

Constantly updating this... 🚀🛸 mannychaindev.vercel.app

@0xECL_ State corruption risks in foundry test files?

🌱 Day 52 of learning blockchain 📚 Today focused on null-value handling. ✅ Explored zero values in dynamic arrays ✅ Observed logic gaps on removal ✅ Traced state corruption risks 🧠 lesson: “null” must be handled deliberately

@timsilva112 @zksync @zkSyncDevs You can debug it I believe in you🔥

✅Modifying my test ✅Testing on zksync @zksync @zkSyncDevs i ran into a bug that might need your attention

@Abdulra75754192 @Jeyffre Word!

"If you're nothing without AI, then you are nothing with AI" ~@Jeyffre Scholz

@_0xshunya_ @CyfrinUpdraft Keep going 💪

Done with the Airdrop and Signature section of advanced Foundry course of @CyfrinUpdraft . Learnt about various txn types, merkle based claims, and lot of debugging.