Ipsilon

❤️ EVM Research and EIPs • ⚗️ EOF + EVMMAX • Organizes @evmsummit • Part of @ethereumfndn

[Paweł Bylica @chfast]

Is anyone still using EVMC? I plan to stop maintaining it soon.

https://t.co/mGnv8NXLyu

[Paweł Bylica @chfast]

On this spooky night, we say goodbye to our old friend…

https://t.co/IqKAbcS6Yu

[Paweł Bylica @chfast]

evmone 0.16.0 released. Have fun with CLZ.

https://t.co/ewH0HzN9gs

[Paweł Bylica @chfast]

We've moved evmone's git repository to https://t.co/QrqXkFkNOh

[17 years of song a day @songadaymann]

Someone has to document the ins and outs of Ethereum protocol upgrades and it may as well be me.

[Paweł Bylica @chfast]

I'm trying to reproduce the famous 800x overhead and this is currently impossible because the source code of the benchmarks is not unavailable although the paper states it is.

This is my investigation so far: https://t.co/5XVtpAXYDT

[Paweł Bylica @chfast]

@androolloyd @real_philogy @teamipsilon @solidity_lang Why don't you read the spec then? This is the Rationale section about new EXTCALL instructions' status codes. Please also check the matching specification part.

We are waiting for feedback for exactly 2 years.

https://t.co/NcxhZj0FCb

[Ipsilon @teamipsilon]

The team prepared valuable input to the discussion on @solidity_lang libraries "compilation to EOF" issues.
https://t.co/tGO2mC40Jw
It's worth reading and decide if it's complicated or easy.

[Danno Ferrin @shemnon]

There has been a lot of talk about the promise of RISC-V for Ethereum execution lately, but I don't think there has been sufficient thought about _how_ we get to that place. Here are my thoughts about how the transition could work and how EOF fits in.

https://t.co/oDF6rQMdDm

[Ipsilon @teamipsilon]

A short explainer of why JUMPDEST-analysis exists by @chfast.

It makes code-compilation feasible (fast JIT/AOT execution) and helps preventing certain kind of security problems.

https://t.co/ClbRvT8LY9

[Solidity @solidity_lang]

The EVM Object Format (EOF) is a long-awaited upgrade for the EVM. We wrote about our stance in support of it.

Topics to expect in the post:
✧ Benefits of EOF
✧ Is EOF the only way?
✧ Can we solve "Stack Too Deep" without EOF?
✧ Why not EIP-615/EIP-2315?
✧ Do we really need immediate arguments?
...and more!

Give it a read.
→https://t.co/9JudUIqF2j

[Ipsilon @teamipsilon]

Important EOF opinion from @solidity_lang team https://t.co/OS89MA5F5k

[Ipsilon @teamipsilon]

Ipsilon has heard your feedback about introspection bans in EOF.

In addition to the current plan of record (which we still support) we have three options that do not include the bans which will be discussed at ACDE on Thursday: https://t.co/fL3miFEqyE

See you at Eth O'Clock!

[Ipsilon @teamipsilon]

The contract size limit is nothing compared to Twitter's character limit.

Here are Ipsilon members answering EOF questions in the Ethereum Magicians Forum: https://t.co/wjMOExymOL

[Solidity @solidity_lang]

ICYMI, a major benefit that the experimental EOF support already provides is the elimination of "Stack Too Deep" errors using the SWAPN and DUPN opcodes.

This will make the Yul to EVM transformation in compilation via IR simpler and more efficient.
🔗https://t.co/2ndqSdkw15

[Solidity @solidity_lang]

We are thrilled to release Solidity v0.8.29!

This version of the compiler brings support for EVM Object Format (experimental), custom storage layouts, ethdebug, and more.

📝 Blog: https://t.co/2ndqSdkw15
💾 GitHub: https://t.co/WttwbyVjeA

Follow along for notable features 🧵↓

[Ipsilon @teamipsilon]

What does EOF stands for?

[Ipsilon @teamipsilon]

EVMMAX will revolutionize writing crazy crypto for the EVM 🧑‍🔬

https://t.co/zIpc2UjnXi

[Danno Ferrin @shemnon]

EOF Devnet-2+ will contain mostly "additive" features that are Quality of Life oriented and addressing gaps identified by the community.

These EIPs are listed in priority order. If we need to start getting in ship mode every EIP not yet in a devnet can be deferred.

[Danno Ferrin @shemnon]

EOF Devnet-1 fixes some spec issues that were cut from prague as the were only "nice to have." Nothing major, just a few items we don't want to see in a hypothetical "EOF Quirks" talk.

Compilers and Developer tooling should start targeting the devnets here, because at this point the spec will mostly freeze, allowing only "additive" changes" and (barring serious bugs) no more breaking changes.