On-Chain Art

When the final art is stored fully on-chain, do you think it adds to the concept when Solidity constructs the art via loops, recursive functions, etc as opposed to when these are done in the browser with JS or p5js?

Again, the final piece is on-chain, construction is different.

https://chainleft.art

Dad, data scientist, blockchain native artist.

Power consolidation=evil.

It's dependency turtles all the way down. So crafting say SVG onchain vs p5.js in the browser from the onchain art shouldn't matter *that* much... BUT. I find onchain construction more relevant when it can only work and be modified from onchain state.

Writer, artist, coder, musician. Casts ideas, storytelling, blockchains, systems, art, cities. ❤️ sunsets. he/him.

Subscribe -> https://sceneswithsimon.com

A p5.js script onchain can't be state aware.

This is a really good point I hadn't remembered, that state awareness can enable further use cases (down the line).

I'm curious about how other artists FEEL about that, whether it feels like overcoming a challenge, or sticking to protocol truth, or more permanence, or more 'clean'.

I agree with this point and I think you're referring to SVG because loops aren't possible there, but the comparison I wanted to make was really on equal footing.

The Q is: Say you're doing purely on-chain stored JS/HTML art. No SVG.
Do you use "for" loop in JS, or do it in Solidity?

Honestly, having Solidity do the compilation (in SVG) feels better to me because it's one less dependency than say requiring p5.js. SVG will always have wider support than p5.js.