Paul Berg

I would keep this issue open. It's a low-priority task, but somewhat important for decentralization purposes. The bytecodes can be copied from Etherscan, but the purpose of reproducing them from...

> But any experienced developer can verify it even right now 1. Not all developers are experienced 2. Even for experienced folks, a little guidance can be helpful, e.g. what...

Until OpenAI adds this (super important) feature to `AGENTS.md` and Codex CLI, you can use my Python script to flatten Markdown files that use Claude’s `@foo.md` file-reference syntax: https://gist.github.com/PaulRBerg/3c78def758cec459b987f6968c8e018d

Thanks @dasanra — so in the code shared in this [StackExchange post](https://ethereum.stackexchange.com/q/168410/24693), the Safe SDK will use `MultiSend`? If yes, could you help us with an answer there, please?

We have a Safe app that runs in the Safe Wallet context as an iframe: [app.sablier.com](https://app.sablier.com) Can you please add me on Telegram (same username as here), so I can...

We haven't talked much about this on Telegram. I still consider that the MultiSend functionality deserves more attention in the Safe docs.

An interim solution is to apply a `@custom` NatSpec tag to document struct fields and enum values. Though I am not sure if I should do it like this: ```solidity...

Any chance this could be included in Solidity v0.8.19? Seems like an easy fix but with lopsided benefits for end users - e.g. OpenZeppelin is currently working on their V5....

I see, thanks anyway @cameel - I do appreciate that you are tied up nowadays.

Am I understanding correctly that #14119 did _not_ add support for documenting struct params/ fields? Based on this [example](https://github.com/veniger/solidity/blob/07def48f4597559f8941a03b46b1c80925b08b9c/test/libsolidity/syntaxTests/natspec/docstring_struct.sol), only the `@title`, `@author`, `@notice`, and `@dev` seem to be supported....