After 6 months of work, we're proud to finally share our first release of our new smart contract language:
Plank v0.1 ๐
To fix the fundamental issues plaguing smart contract development we're rebuilding the language stack from the ground up. ๐๏ธ
Learn more ๐
pretty confident my compiler won't stack too deep ๐
1024 => 1024 value shuffle artificially limited to at most a swap depth of 1 and it still works
yeah for this case I agree.
I think there may still be some value in codifying one of the popular factories as an ERC rather than an EIP, just to standardize and document the address + bytecode so that other chains can more easily replicate what OP etc. have done without hardcoding factories.
Although actually not sure, maybe this would be more of an RIP or whatever they're called
@_Enoch@nero_eth also I disagree that Ethereum shouldn't care about other chains.
The EVM being exported to and used by other chains is a competitive advantage that I think is worth maintaining and caring about.
@_Enoch@nero_eth the problem is that doing this at the application layer can be kind of jank and insecure.
a lot of these deterministic factories are bootsrapped by normal private keys which means they can have different code/contracts on another chains
@_Enoch I realized it was about EIP8024. Thought it was your code because I had only seen the python version from the EIP. good to know.
the `EXCHANGE` encoding is even worse IMO
We've had calculators for decades yet we still want kids to understand how to do basic arithmetic.
I think if you let kids use the power tools from day one whether it's AI/calculators they will almost definitely lose out on the lower level skills (text writing, argumentation, arithmetic, some mathematical reasoning).
But maybe there's a valid question to be asked in whether kids can skip that and just directly learn at the higher abstraction level.
the folly of youth is the belief in the false dichotomy of investing in your future vs. living today.
True wisdom is understanding the challenge is balancing both. Live today, but set something aside so you can live tomorrow.
@danielvf@argotorg It's just easier to apply the wisdom you've gained to a fresh codebase than trying to get a good overview in such an old codebase.
For the tests agree but those are should usually be easy to port over depending on how they've been written
Good work by @danielvf.
I can empathize with a big codebase having tech debt after many years but it's gotten SO bad.
I sincerely hope, for the sake of @argotorg & Solidity that solcore is a fresh implementation. Continuing solc is pure sunk cost.
I've submitted 3 small PR's to solidity that speed via-ir compilation up about 11%.
It's fun to learn about the insides of the compiler we all use, so let's tour each speed up. 1/7
@_matthew_ oh, my bad, I just assumed!
If you're doing it by hand I'd question why use LLMs in the first place? Just write the thing the way you need it right away, no? At least when I've tried to do it like this I've felt like I net lost time
Am I finally being vindicated or what?
Bunch of cracked devs on my TL saying over-indexing on AI generated code was a mistake. Maybe my eyes weren't fooling me after all.
I need to be less hard on myself for still mostly hand coding in 2026 ๐