bbuddha

@bbuddha

122 Following

121 Followers

bbuddha pfp

If anyone can pitch in with wisdom (or hyperlinks to wisdom) here, would be much appreciated. Thinking about timing in Eigenlayer’s slashing… https://warpcast.com/bbuddha/0xad9bac5d

0 reply

0 recast

0 reaction

bbuddha pfp

@donnoh.eth @tynes @proto

0 reply

0 recast

0 reaction

bbuddha pfp

What’s the reasoning behind opstack’s “chess clock censorship” assumption? Is this easily detectable? Feels far riskier than an assumption on censorship for a contiguous period of time

1 reply

0 recast

0 reaction

bbuddha pfp

Very cool! What’s the best way to think about the advantages/disadvantages of compiling and executing EVM to native code vs Arbitrum stylus compiling and executing rust to wasm?

0 reply

0 recast

0 reaction

bbuddha pfp

What’s the best way to autogenerate an interface for a contract that - inherits the interfaces of the contracts it inherits - preserves top of function comments. ‘cast interface’ takes an ABI which leads to a lot of duplicated functions from inheritance and gets rid of top of function comments

0 reply

0 recast

0 reaction

bbuddha pfp

Interesting route to go would be enshrining zkVMs (e.g. risc0 proof verification precompile) in addition to zkEVMs. It would allow rollups to innovate on the execution layer while taking advantage of a large L1 enshrined codebase.

0 reply

0 recast

0 reaction

bbuddha pfp

Nice! Wen ethereum state/history on base?

0 reply

0 recast

1 reaction

bbuddha pfp

Do any L2s make static calls within L1 context easy?

0 reply

0 recast

0 reaction

bbuddha pfp

Can you force inclusion of blobs on op stack rollups? Is that even possible validation wise?

0 reply

0 recast

0 reaction

Ansgar pfp

My take: L2s should target very different full node requirements than L1, as they inherit L1 security. The correct endgame is lightweight L1 nodes and datacenter L2 nodes. Importantly, by running an L1 node, users can still verify proofs about the state of the L2, so the end-to-end user flow remains fully trustless.

10 replies

8 recasts

62 reactions

bbuddha pfp

Nice thread! What’s the main risk with bumping up the gas limit? Looks like Base can do 6x Ethereum’s gas throughput. Aren’t eth node requirements conservative enough that Base could make large increases in gas limit without worry?

1 reply

0 recast

0 reaction

bbuddha pfp

Do txs that consume a large majority of the block gas limit (20-30million) take longer to get included onchain than other txs that pay the same gasprice? If so, how much longer do they wait?How much higher do such txs need to pay?

0 reply

0 recast

0 reaction

bbuddha pfp

We’re doing some fun stuff :) Not for gindexes tho https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/src/contracts/libraries/BeaconChainProofs.sol

0 reply

0 recast

1 reaction

bbuddha pfp

Is there a way to create a delegate call tx from a gnosis safe via UI?

0 reply

0 recast

0 reaction

bbuddha pfp

Does anyone have concrete numbers on onchain merkle proof gas costs and how they increase with tree depth?

0 reply

0 recast

2 reactions

bbuddha pfp

I want to get (address, slot) pairs that are at various depths in the state trie for some benchmarking. What’s the easiest way to do this? Ideally on goerli

0 reply

0 recast

0 reaction

bbuddha pfp

hehe, i think i'm not clearly distinguishing EVM memory and RAM my main confusion is that, i would think if the issue is with erasing transient storage on internal tx reverts, then TSTORE could be priced higher but TLOADs could be cheap as they are lookups from RAM like MLOADs. idk if i'm being too simplistic tho :)

0 reply

0 recast

2 reactions

bbuddha pfp

Ah, would that encounter more overhead than a regular MLOAD? seems like they're both an indexed inmem lookup?

1 reply

0 recast

1 reaction

bbuddha pfp

I think state growth isn't a concern since the storage is discarded. Looking at the EIP it seems like the concern is with reverts because each slot written to needs to be erased. I guess erasing different slots from a "not in linear memory" map encounters a lot more overhead than erasing linear memory...

1 reply

0 recast

1 reaction

bbuddha pfp

Have you seen https://www.rollup.codes? Not exactly as clear cut as a particular evm version, but some useful info there

1 reply

0 recast

1 reaction