RT @maltefr_eth: 1/ Computation Degree Zero. On abstraction in @mathcastles Zero Suite. From my essay in @outland_art in homage to @0x113d….

RT @glitchmarfa: 1/ Enter the Hypercastle. Our E30D #4 exhibition and digital poster is now open for live view and collection in Marfa, TX….

These Solidity "stack too deep" compiler errors are bittersweet because I think other people would be more insane by them than I am. I'm like David Blaine doing "magic tricks" by just being willing to actually stick a sword through his arm.

RT @outland_art: 𝗖𝗿𝗶𝘁𝗶𝗰𝗶𝘀𝗺 | 𝗧𝗛𝗘 𝗠𝗔𝗣 𝗜𝗦 𝗧𝗛𝗘 𝗧𝗘𝗥𝗥𝗜𝗧𝗢𝗥𝗬. "Terraforms is a reminder that the best virtual worlds are imagined, not simulated."….

RT @i_like_calculus: Terraforms by @mathcastles has been one of the most inspiring pieces of art for me. I wrote a long-form essay discussi….

RT @matto__matto: The Hypercastle Explorer application from @hypercastle_exp allows you to explore the Terraforms by @mathcastles hyperstru….

RT @matto__matto: With fresh attention on Terraforms, it’s a good time to remind you that you can explore the hypercastle in 2d and 3d for….

RT @sus_seaweed: Super happy to see the @mathcastles team getting the recognition they deserve. By far one of the coolest and more interes….

RT @neon_dao: Released in December 2021, Terraforms are composed of 11,000 unique artworks.

RT @0xTjo: realistically the only project ive seen that is pure crypto art from a technology standpoint is mathcastles by @0x113d. that bei….

RT @TDR_Bingo: TDR™ X MATHCASTLES. Brand new multi-player / experimental / re-mixable font (re-)living as eternal code on ethereum itself…….

There are likely additional ways of optimizing or organizing this (@dhof has a really nice file compression technique, for example). At the moment we just wanted to put these out for early experiments and to get the conversation started.

You can query the available libraries by name using the readLibrary function. The names are maintained in a list called availableLibraries.

Using EXTCODECOPY costs far less gas than copying data that is already in memory. There should be more than enough gas headroom to use these libraries like ordinary strings, and you can incorporate them into your projects simply by using string.concat.

The technique for uploading the files takes advantage of contract storage for significant gas savings (see . I then added a technique for manually manipulating a dynamic buffer in memory to reassemble the files using the EVM's EXTCODECOPY instruction.

We just put p5.js and three.js onchain, as composable libraries. I designed a system for deploying and reading very large files to the EVM, which makes them available for anyone to incorporate into their works.

A preliminary question is how to get these large files into dynamically generated strings (like tokenURI) since ordinary string concatenation is basically off the table. Might require generalizing the manual-memory-manipulation approach for any endpoint incorporating these files.

Some ongoing questions include: how should the file data be stored? What technical limitations might arise for users who want to incorporate onchain files into their own compositions?.

You can do this by first storing file chunks as contract data (see and pulling in the data using the EVM's `EXTCODECOPY` instruction, which uses far less gas than copying data already in memory.

Thoughts on this technique for serving large files onchain: The main issue is to avoid gas limitations when concatenating huge strings. My solution is to manually copy chunks of data into memory, and then directly manipulate the memory location that stores the string length.