Paul Dowman 🔴✨ pfp

Paul Dowman 🔴✨

@pauldowman.eth

492 Following
495 Followers
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
I'd subscribe to pro if it guaranteed no video
0 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Remember when Apple removed the esc key?
0 reply
0 recast
2 reactions
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Got my Devconnect ticket!
0 reply
0 recast
6 reactions
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Nice! I live in Canmore, always happy to meet crypto people IRL, dm if you want to go for a hike or coffee or drink!
0 reply
0 recast
1 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
I'm surprised that dev containers still aren't used for every project. https://containers.dev/
0 reply
0 recast
1 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Exactly. People were working really hard to fractionalize NFTs in 2021
0 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Remember wagmi? We should bring back that vibe
0 reply
0 recast
3 reactions
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
I'm hiring for the Proofs at OP Labs, help us build and secure Optimism! Solidity and/or Go. If you think you'd be a good fit get in touch.
0 reply
0 recast
2 reactions
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Congrats!
0 reply
0 recast
0 reaction
nixo pfp
nixo
@nixo
Checkpoint #2 is live! Accessible updates of the last 4-5 All Core Dev calls. Pectra is live on mainnet in ~a week, are you caught up on ACD? → Successful Hoodi upgrade → Wen history expiry? → Fusaka scope → EOF removed → New ACD call structure post-Pectra https://blog.ethereum.org/2025/04/29/checkpoint-2
2 replies
12 recasts
58 reactions
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
This is really good, thanks for doing it!
1 reply
0 recast
1 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
Another confirmation that general purpose ZK VMs are the future (e.g. RISC Zero, etc). Nobody will write custom circuits. "This is hard to do with rigid zkEVM circuits that hardcode lots of cells and constraints. So we moved to a more general-purpose zkVM architecture - one that’s lighter-weight, extensible, and better suited to proof continuation." https://x.com/Scroll_ZKP/status/1916871844151406649
0 reply
0 recast
1 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
5 gigagas for ethereum in 4 years. It’s at least a new difficulty bomb to make increases be the default. Let’s go 📈 https://github.com/ethereum/EIPs/pull/9698
1 reply
0 recast
2 reactions
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
9/ To sum it up: ✅ 64-bit = more memory ✅ Multithreading = stable GC ✅ MT Cannon = no more memory constraints, even for big blocks And if you like this kind of thing: we're hiring for the proofs team at OP Labs! Get in touch if you think you might be a good fit.
0 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
8/ 🧠 With MT Cannon, multithreading is enabled. That means the garbage collector works → memory is reclaimed → system is stable even on long or heavy runs. More efficient, more robust, more scalable 💪
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
6/ 👻 What happens when we don’t have enough memory? If the op-program runs out of memory, the proof fails. And if proofs fail, bad actors can get away with fraud.
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
7/ 🧵 And why multithreading? The op-program is written in Go. Go’s runtime uses a garbage collector — but it runs on a separate thread. With no multithreading? 🗑️ GC doesn’t run → memory leaks → crash risk → proof fails.
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
5/ 💾 64-bit = no memory limits 🚫 Modern CPUs are 64-bit and can access vastly more memory. By upgrading Cannon to 64-bit, we completely remove the memory bottleneck. More memory = support for larger blocks = more scalability 🚀
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
4/ 💡 Why the 64-bit upgrade? The original Cannon emulated a 32-bit CPU. That was a good place to start, but 32-bit CPUs are very memory-constrained.
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨ pfp
Paul Dowman 🔴✨
@pauldowman.eth
3/ So to give op-program a reproducible environment we run it in Cannon, which emulates a Linux environment on a MIPS CPU. 😅
1 reply
0 recast
0 reaction