brock pfp

brock

@brock

72 Following
834 Followers
brock pfp
brock
@brock
thank god it can’t see what my other wallets have been doing
3 replies
0 recast
6 reactions
brock pfp
brock
@brock
i was a good boy this round
1 reply
0 recast
2 reactions
brock pfp
brock
@brock
i imagine this is with a relatively high quality nvme tho - which for archive nodes is assumed but as reth moves to more pruned nodes, that storage speed requirement may relax and io speed likely actually is a bottleneck (ssd roughly 7x slower, hdds 35x slower)
1 reply
0 recast
3 reactions
brock pfp
brock
@brock
i still like the pipelining idea we kicked around awhile back of: call to contract -> immediately start a load a page of storage -> hopefully when we ask for storage val it will have been loaded for us would be cool to see a reth benchmark of % time spent by opcode during exec sync stage
2 replies
0 recast
3 reactions
brock pfp
brock
@brock
basically i’m making the argument that simple machines like the EVM are probably optimized pretty well by their implementation languages compiler such that JIT & multi-op ops won’t show much benefit reasoning being that LLVM likely produces better asm + reduces branch prediction misses i could def be wrong
1 reply
0 recast
1 reaction
brock pfp
brock
@brock
i’m not totally convinced this actually will result in much of a speed up personally this comes down to stack machines being extremely trivial to convert into machine code in the first place (see this talk: https://youtu.be/umSuLpjFUf8?feature=shared) i think it may end up resulting in more branch pred misses
1 reply
0 recast
0 reaction
brock pfp
brock
@brock
ethers-rs is the go-to google search for this btw
0 reply
0 recast
0 reaction
brock pfp
brock
@brock
both are great, important part is just doing some form of invariant testing for normal fuzzing recommend foundry tho and if u already have integrated foundry for fuzzing likely you’ll want to use it for invariants as well
1 reply
0 recast
0 reaction
brock pfp
brock
@brock
don’t think you can escape me telling you to do the dance by moving to farcaster
0 reply
0 recast
0 reaction
brock pfp
brock
@brock
a frontend bug == minor inconvenience (but long term underinvestment could be game over) smart contract bug == game over the real issue is lack of reprioritizing after securing contracts
0 reply
0 recast
0 reaction
brock pfp
brock
@brock
gm
0 reply
0 recast
3 reactions