l--o--l pfp
l--o--l
@l--o--l
What is the "Engine"?
1 reply
1 recast
6 reactions

l--o--l pfp
l--o--l
@l--o--l
The basic smart contract that implements ERC721 for the l--o--l collection, only stores the blueprint of each ship, the (up to) 16 characters. But when a client calls tokenURI(shipId) to get the token details, the smart contract calls an other one, the (rendering) engine. The rendering engine returns to the ERC721 contract the SVG and the traits of the ship. Now, here's the cool part.
1 reply
0 recast
1 reaction

l--o--l pfp
l--o--l
@l--o--l
The ERC721 contract is designed to allow me to configure more "Engines" (up to 256) and each ship can use one of them. Right now, there is only one, the one that generates the images you see. But my hope is that in the future, we will have other engines that either use a totally different artistic style, or implement new features. The simplest version would be an engine that uses a different color theme. Or one that adds various backgrounds. But there could also be a pixelart version. Or even one that lets an artist paint a custom image for your ship, upload it to IPFS, and lets you use it. But there could be more complex ones, that use additional input, like other tokens you hold, or the day of the year, to render something cool. I want |--o--| ships to be a playground for various experiments :-)
0 reply
0 recast
1 reaction