The problem Ethereum Image Service solves

The Problem EIS Solves

One of the significant challenges blockchain applications can address is providing financial benefits to creators of public goods. CC0 images are public goods, and their widespread creation benefits humanity greatly. However, creators of CC0 artworks have traditionally struggled to monetize their work. EIS addresses this issue by encouraging the creation of CC0 artworks while allowing artists to earn revenue through NFT minting and remixing.

Benefits of EIS:

• Encourages Creativity: EIS features a Remix function, offering more opportunities for secondary creations of CC0 artworks. By making images CC0, free modification and derivative works are unlocked, accelerating composability in the art domain through network effects.
• Monetization: Artists can earn revenue from NFT minting and remixing, solving the monetization issue for public goods creators.
  Additionally, service operators using EIS can enhance community engagement, advertising, and monetization. For example, Jesse's billboard remix during Onchain Summer significantly boosted community engagement and publicity (reference). EIS enables such initiatives to become more common and impactful.

Challenges we ran into

Full onchain image registration

• EIS registers very large images, and we conducted extensive research on onchain image compression/decompression and SSTORE2
• We discovered that the Efficax contract is a suitable contract for forking
• However, Efficax is implemented with the Manifold contract, so we forked and adapted it to work with the Zora contract
• Currently, image data exceeding 100kb can be registered in the EIS contract

Fee streaming

• To establish fee streaming for Remix asset creation, we utilized splits
• Splits require management of the distribution flow and withdrawal process, which necessitated extensive testing to ensure functionality
• Now we have flexible royalty streaming with splits

Zora Integration

• Integrated EIS full onchain image with Zora Contract as a custom metadata renderer and splits as a royalty recipient
• Initially, the image was not displayed on the Zora platform due to:
  Zora testnet web app not functioning properly on Base Sepolia, but it was found to work well on the Zora testnet
  Zora contract needing to emit a URI event to prompt the indexer to fetch the data, which we implemented
• Now we have successfully integrated and tested here:
  https://testnet.zora.co/collect/zsep:0x6cd915072796ad62ff4614d6caa436e6354450b6
• Contract code is found here: https://github.com/eistoys/EIS/blob/main/contracts/contracts/ZEIS.sol