Radek

@z0r0zzz Interesting idea. Can you add your related thoughts to this forming ERC of CALMs? eips.ethereum.org/EIPS/eip-8152

how to solve smart contract security once and for all: safe-factory: anyone can send bytecode through this create2/create3 factory *but* it must include signature from audit software *then* the contract is deployable users can trace all deployments to this "safe" factory

@z0r0zzz How are those membership tools considered in other jurisdictions in comparison?

"most crypto assets are not themselves securities" SEC is finally taking some positions on tokens. The most interesting part of their new taxonomy is treatment of "digital tools" as exempt. These can cover "membership". Protocol governance is a practical function of operation.

@pcaversaccio And to play it to the extreme - let's skip Solidity, LLMs can output into assembly (or even bytecode). Prompt only devs can save compile time. And hardcore CS can read assembly anyway. /s

idk man, maybe it's just me but most devs/engineers nowadays are simple translators not true understanders. We're drifting away from a first-principles-based world toward prompt-to-slop engineering where the prompter can't even challenge the output lol. This fucking concerns me! Too many don't understand (or already forgot) how computers work. Ask them how program memory looks and you get nothing. They don't even try since they can always LLM it. IMHO true knowledge and _first principles_ build great things, everything else is temporary slop. My contrarian view is that in the age of LLMs you gain a real edge by not going down the slop engineering route.

@pcaversaccio It is not only you. I see such trend since late 90s.

@HackenProof Another way to fix - add line: user[msg.sender] = u

Spot the Bug 🧠 Claim status update What’s the issue in this code?👇

@aadams @willmorriss4 @DistributedMarz @trent_vanepps You are right we need to improve DX for modular contracts. Including discoverability and linking of already deployed contracts / modules for easier reuse. And ideally to lower delegatecall costs at least for hot contracts.

@willmorriss4 @DistributedMarz @trent_vanepps i am not talking about contract devs lol - im talking about end users as someone who works with a ton of non-crypto native app devs, we should not be making it harder on them to utilize an already very confusing system

can the EVM please raise the contract size limit - its been almost 10 years since it was raised (eip 170 was nov 16) worst off, L2s need to adhere to the contract size limit to be evm equiv, so its not like L2s can experiment either

@smpalladino @OpenZeppelin @mudgen @frangio_ @Amxx Inspired by ERC-8109, ERC-8167 proposes a minimal modular dispatch proxy interface, compatible with past and future innovation. This proposal is not yet final. We are interested in your feedback! You can contribute to the discussion here: ethereum-magicians.org/t/erc-8167-mod…

@aadams @willmorriss4 @DistributedMarz @trent_vanepps WDYM antipattern? Diamonds and similar enable better MVC pattern and facet reusability.

@willmorriss4 @DistributedMarz @trent_vanepps yes ik that but we should not be enshrining an anti-pattern for development

@ZainanZhou @mudgen Yes, easier to read and check. Yet also to add a visual check in form of either block icon or emoji.

@radk @mudgen Oh, you mean breaking the characters in 3 or 4 each batch apart? That's a good idea too. I think some of the platform is already doing it

@ZainanZhou @mudgen No screenshot, just idea. Wrt phone numbers it is like 800 123 456 789. In case of mentioned ERC it could be like 0x 0(12) 123 456 789 abc def 012 345 678 9ab c. Some chains also use emoji based checksum for glance visual check.

@radk @mudgen That sounds an interesting idea @radk. Any screenshot to share?

@HackenProof also EOAs with activated EIP 7702 are filtered out. The design question is why to put there EOA gate at all?

Spot the Bug 🧠 EOA-only gate What’s the issue in this code?👇

@georgeguimaraes I wonder where we lost that decentralised aspect of git... 🤔

Keep one GitHub account for your entire career. Your company's "create a new account" policy is wrong. That account is yours. You can rename it, change the password, add any email. Pro tip: star every private repo you contribute to. When you lose org access, starring keeps your green squares. georgeguimaraes.com/one-github-acc…

@metahacker_ @maxnaut @gregosuri Fix to your statement: "Everywhere else, people see bad UX and say “we should go elsewhere”

@maxnaut @gregosuri The industry’s standard response to awful UX that persists for a decade is now “skill issue” Only in this industry. Everywhere else, people see bad UX and say “we should fix that” No noob user should ever need to know slippage settings

One of the worst things about stablecoins is slippage in value when transferring between tokens. I barely use them anymore due to this uncertainty and accounting nightmare. Banks are a mess to deal with but at least retain value when transferring. Stablecoins are not crypto.

@vjbhandarix JUMPs increase execution costs. Not much, but they do. Use ERC 2535 or newer proxy if you are short of contract space.

Found this cool little detail about modifiers in Solidity: The code inside a modifier is copied into every function that uses it. Let's take this example: modifier onlyOwner() { require(msg.sender == owner, "User is not the Owner"); } function mint() external onlyOwner {} When the contract is compiled, the bytecode for mint() contains the require statement itself. The modifier logic is copied directly into the function. Now think about this, you use onlyOwner in 10 different functions. That require statement gets duplicated 10 times in the bytecode! This increases contract size and can even push you closer to the 24KB EVM bytecode limit. A simple pattern to avoid this is moving the logic into an internal function, like the following: function _isOwner() internal { require(msg.sender == owner, "User is not the Owner"); } modifier onlyOwner() { _isOwner(); _; } Now the modifier only executes a JUMP instruction to _isOwner() instead of copying the entire code block into every function. The result: > Smaller bytecode > Gas efficiency during deployments > Cleaner, more readable code.

@pashov @austingriffith Teaching the "builders" course at the University, I am considering is this suitable for fresh students that should end with a prototype?

🚨Ethereum Developers: you can now install your first AI Auditor in 1 minute - fully autonomous, available 24/7, with multiple sub-agent helpers. Open Source. FREE to use (with your AI model) and already finding vulnerabilities in smart contracts. Link below🫡

@potuz_eth It already exists - foundry's cast command

Great, now tell them to vibe code me a wallet that - runs in the terminal - doesn't track anything from me - Uses my RPC or only endpoints I provide - makes NO OTHER external connections than getting the tx data from a dapp. Wallet privacy violation is just as bad as the browser one.

@solidity_lang Revert custom errors are part of the defined interface. Such stripping has the impact on ERC 3668 compliant contracts - as the example.

The Solidity compiler has a `revertStrings` setting that controls how revert data is handled. There's currently an inconsistency between the legacy and IR pipelines: when set to `strip`, the IR pipeline removes both strings and custom errors from `require` statements, while the legacy pipeline only removes strings. In both cases the code still reverts, the difference is just whether the custom error is included in the revert data. We're aligning the behavior so custom errors are also removed. Are there scenarios where you'd want custom errors preserved while revert strings are stripped?

@z0r0zzz WDYM by storing website? Tx shows setting hash. Can you elaborate?

it costs $0.004216 to store a website on ethereum/wns

@blockscout @gnosischain Working with Chiado is confusing now - related tx was there in mid Jan (still accessible through gnosis-chiado-rpc.publicnode.com, but not via BS ). Now, UI declares no txs, no balance hist , yet hist graph is as expected. Pruning breaks other infra like MPCs.