Content pfp
Content
@
0 reply
0 recast
0 reaction

Chainleft pfp
Chainleft
@chainleft
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.
6 replies
0 recast
6 reactions

borged.eth pfp
borged.eth
@borged.eth
I think it is a matter of whether any library like p5js is externally linked or fetched from the blockchain during rendering.
1 reply
0 recast
1 reaction

a1z2 pfp
a1z2
@a1z2
Not sure I understand the question (i'm non-technical). However, my intuition is that when all elements are stored onchain, they become composable and readable to some degree. So those loops and recursive functions become interactive to anyone who want to build on top, no?
1 reply
0 recast
1 reaction

yangwao ā†‘ pfp
yangwao ā†‘
@yangwao
Out of the blue but is there any art on FVM where construction of onchain art could be much cheaper?
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
Is the browser prevented from falsifying the result somehow, compared to the solidity version?
1 reply
0 recast
1 reaction

Simon de la Rouviere pfp
Simon de la Rouviere
@simondlr
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.
1 reply
0 recast
1 reaction

flick the dev šŸŽ©šŸ“¦ pfp
flick the dev šŸŽ©šŸ“¦
@flick
the former is more impressive, the latter is more practical
0 reply
0 recast
1 reaction