Scale Ethereum Now!
Rayonism is a scaling project around the ETH Global Scaling Hackathon (April 16 - May 14), experimenting with Merge and Sharding Eth1-Eth2 testnets.
Rayonism is a style of abstract art developed in Russia. Rayonists seek to break the barriers between the artist and the public.“ A synthesis of Cubism, Futurism and Orphism.
- M. Larionov, Rayonist Manifesto
Rayonist paintings combine the fragmentation and multi-plane approach of Cubism, the dynamic movement of Futurism and the colourism of Orphism.
Or another intepretation: the art of painting a sharded space with rays to a dynamic runtime.
Merge. Sharding. Specs. Hackathon. Implementation. Testnet.
This is an illustrative roadmap, highly uncertain. Note that this is a month-long (!!!) hackathon. We are ambitious, and may implement some shortcuts to ship.
- March 28: Initial Merge specs land in
- March 29: Rayonism project starts
- Early April: Initial Phase 1 refactor lands in eth2.0-specs, modularizing Sharding
- Early April: target for Eth2-Eth1 devnet following the Merge specs
- April 16: ETHGlobal Scaling Hackathon starts
- Mid April: Sharding minimal viable specs target (No Custody Game or Data Availability Sampling)
- During hackathon:
- develop merge functionality on top of participating Eth1 and Eth2 clients
- develop sharding functionality on top of participating Eth2 clients, enable KZG in EVM on Eth1
- Stretch goal: Initial L2, Optimism-Eth2 prototype
- May 14: Hackathon ends
- Post-hackathon: launch public trial testnet with Merge and Sharding
A project that takes the research and engineering efforts of the Eth1-Eth2 Merge and Sharding, and builds a testnets around the ETHGlobal Scaling Hackathon.
The name is taken from an early abstract art movement with sharding and beacon motives.
And yes, it’s a reference to Optimism. The stretch-goal (if you didn’t think Merge and Sharding are ambitious enough!) is to build a version of Optimism with shard data. This may spin out as post-hackathon effort.
Participate in the hackathon?
It’s the hackathon vibe, acceleration, and involvement we are looking for! Rayonism as a project does not intend to apply for hackathon prizes.
However, others building things on top of our work fully qualify as Hacker, get involved!
If you hack solely on Rayonism, feel free to still register as Hacker, your work may not be eligible, but everyone scaling Ethereum should be welcome at the hackathon.
How can I help?
You’re welcome, although the initial stage of this project is very technical. If you are into UI design or data analysis there may still be good opportunities to help. If you have different skills, and you are motivated, just open a chat with us :)
We are looking to deploy a Merge testnet before fully diving into Sharding. This means we should have an experimental chain with EVM (and same Geth RPC endpoint) to experiment on around the 2nd half of the Scaling Hackathon.
If you want to experiment with EVM on Eth2 Proof of Stake, and want to be on the bleeding edge by running the Catalyst Geth fork, this is for you. Note that you can already run local Merge testnets with Teku and Catalyst, don’t wait for the public testnet if you want to get started!
More to be announced as the Merge testnet engineering makes progress.
After familiarizing yourself with the Eth2 (consensus) - Eth1 (application) Merge design, join the #merge discord channel for any questions.
From there, we maintain the so called “Meta specs”: a fork of the eth2.0-specs that aims to:
- Stabilize Merge changes just enough to target something stable during the hackathon. We attempt to keep in sync with the latest changes in upstream, like the eth2.0-specs, but may lock in something temporarily for testnet-shipping.
- Extend with an experimental simplified version of Sharding
- Coordinate around misc. Hackathon requirements and documentation
The meta specs are in active R&D and unstable until the hackathon starts. When started, focus will change from spec work to implementation work.
On the very very bleeding edge we are experimenting with L2 rollups to utilize shard data-availability, as a stretch-goal when/if we get some form of Sharding done.
There is an idea to re-engineer the Optimism data-transport-layer repo to pull shard data instead of event logs, along with other tweaks, which may enable a (probably post-hackathon) Optimism deployment.
If you are a L2 dev with rollup or other relevant experience, please reach out and we can see when/how your preferred L2 can start using testnet shard data!
Who is participating?
This is collaborative effort between contributors from many teams:
- Merge specs researchers. Mikhail, Guillaume, Vitalik, Danny, protolambda, more
- EF Research team
- Teku, and the Merge-fork of Teku
- Geth, the Catalyst fork
- Lighthouse and Prysm, starting with Merge efforts
- Eth1 clients, developing Merge functionality