Ram pfp

Ram

@hiddentao

66 Following
27 Followers
Ram pfp
Ram
@hiddentao
Current thoughts are to explore: * Twitter posts / replies / mentions and DMs to key NFT accounts * Set aside X no. of NFTs to gift to key people * Subreddits / other forums * Cross-posting on Farcaster / Lens Any suggestions are welcome!
0 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
The bigger challenge up ahead is marketing. I'm totally new to this and am basically experimenting with different marketing methods. I think I need at least a few thousand eyeballs on the collection to make it reach escape velocity.
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
To summarize the lottery: 5% of each trade goes into a pot. Puzzle players will receive lottery tickets (also NFTs!) as they complete tasks. Once the puzzle is completed, a limited no. of winning tickets will be drawn from the pot. These tickets can then claim their share.
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
I can't wait to reveal the website - jigzaw.xyz - as it will go a long way towards explaining the nature of the puzzle, the lottery mechanism. And why the art work has to be the way it is. This is what I'm building this week, due to be ready by next week.
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
Over the past week I've had discussions with friends about how to incentivize people to complete the puzzle and have come up with the idea of a "lottery"...
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
I've looked into actually using Sudoswap instead of my own pool code but at present I'm not sure if the added code complexity and gas cost is worth the effort. Still investigating 🧐
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
In terms of contracts, the @sudoswap-inspired mint-swap pool is code complete. Test coverage is around 97% at the moment, and some of the missing % is due to deficiencies in tooling. It's made me realize that we can do better: https://twitter.com/hiddentao/status/1771648583114109083
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
I drew everything in Figma in the form of layers and then built a custom studio app (a locally hosted React SPA) to test things out as well as build the Jigzaw puzzle from the images: https://twitter.com/jigzaw_xyz/status/1770903501578592298
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
For the art, it took a few iterations to get things to a satisfactory point. My requirements were: * All images must be fully on-chain - this necessarily limits resolution and details to keep file size low. * Images must be scalable - this necessitates SVGs
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
Initially I was simply treating each tile of the Jigzaw as an NFT, until I realized that people really like PFPs. So then I switched to creating PFPs and worked on choosing colour combinations which would allow them to still be used to form an image when combined together.
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
An update on @jigzaw_xyz - a fully on-chain NFT collection with a liquidity pool that I'm building... ✅ Artwork done ✅ Contracts: Mint-swap pool ✅ Contracts: Lottery pot for most engaged fans 💰 👩🏽‍💻 Website - jigzaw.xyz 👩🏽‍💻 Marketing Read on for details ⬇️
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
I'm building an NFT collection @jigzaw_xyz * Fully on-chain on Layer 2 * Mint/Swap pool (inspired by @sudoswap) - guaranteed liquidity * [redacted] - 🤔?? * [redacted - 🤔???? More to come soon!
0 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
6/ I'm still investigating compatibility and support, and will report on further findings in this thread. Here is the Github to the repo for generating the collection and setting token URIs: https://github.com/hiddentao/onchain-nfts
0 reply
0 recast
1 reaction
Ram pfp
Ram
@hiddentao
5/ The polygon collection (with images >3000 bytes) can be viewed at [1]. However, Polyscan doesn't render the images. As of yet Opensea Pro (on Polygon) is unable to load the metadata or image :/ [1] https://polygon.nftscan.com/0x7d6d005ec1cc8ec979fb6d439fbe9c96f9ed3ab0?module=NFTs
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
4/ In Metamask I couldn't get the image to show up in the viewer, though it did in the transaction finalization screen when I tried to send the NFT to another wallet. Perhaps it was a cacheing isssue due to initial metadata being malformed?
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
3/ For still images, there is no need to use the attribute "image_data" [1] instead of "image" in the metadata since "image" is already widely supported and can point to really long image data URIs. [1] https://docs.opensea.io/docs/metadata-standards
1 reply
0 recast
1 reaction
Ram pfp
Ram
@hiddentao
2/ Both SVG and PNG data URIs seem to work. Presumably other file formats would also work. It's expensive to write KB of data to a storage slot (duh!), so an L2/L3 with periods of low gas feed - e.g 1 Gwei - is essential to minimizing overall cost to caller.
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
1/ Did some investigating into storing NFT metadata fully on-chain, especially with respect to large images. First, The data URI length can be several KB (64 KB+) long: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URLs#length_limitations
1 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
Looks like Bun hit 1.0 back in September and I missed it. Reading through the 1.0 release announcement [1], it sounds like a dream replacement for Node and all the problems I've had recently with tooling setup. Time to give it a whirl! [1] https://bun.sh/blog/bun-v1.0
0 reply
0 recast
0 reaction
Ram pfp
Ram
@hiddentao
And thus, the next round of funding is needed to maintain the runway. The startup must pivot, sometimes completely in order to maintain momentum. Much respect to founders who are able to keep going through these periods of uncertainty whilst knowing that in the end the business may still not reach velocity.
0 reply
0 recast
0 reaction