Content
@
0 reply
0 recast
0 reaction
Chinmay đšī¸đŋ
@chinmay.eth
Nobody can validate their ideas in vacuum. Share your ideas, and I'll tag the best folks here to get their feedback on them.
2 replies
0 recast
5 reactions
Patchwork
@patchwork
Have you checked out https://patchwork.dev/ yet? Onchain, programable, composable metadata. Text to deployed app (built on Patchwork) coming this year.
1 reply
0 recast
0 reaction
Chinmay đšī¸đŋ
@chinmay.eth
I'm having trouble understanding it. Is it like IPFS but more structured??
1 reply
0 recast
0 reaction
Patchwork
@patchwork
Data is actually onchain. It let's onchain things own other onchain things and data: -Patch an audit report directly to an address (that other smart contracts can read) -Allow NFTs to own other NFTs (and if transferred, the entire ownership hierarchy gets transferred).
2 replies
0 recast
1 reaction
Chinmay đšī¸đŋ
@chinmay.eth
Interesting functionalities. Any live apps that I can check out?
1 reply
0 recast
0 reaction
Patchwork
@patchwork
There are a few, but checkout (collaborative canvas mint) https://canvas.patchwork.dev/ and https://elephants.fun/ (composable pfp with NFTs owning other NFTs)
1 reply
0 recast
0 reaction
Chinmay đšī¸đŋ
@chinmay.eth
Elephants are looking cool. Are those AI generated or are you combining multiple assets to create an image? Regardless, I get your point on what patchwork.dev is. My feedback is that the website and storytelling has to focus more on why data needs to be onchain. Most of the NFT projects that I helped in the past were using S3 buckets to manage assets. They considered IPFS, but it was too much hassle and we didn't get a single consumer complaint about this topic. So, this is a hard sell, but I'm sure you'll be able to come up with a story that showcases the value prop.
1 reply
0 recast
0 reaction