Paragraph

Vision for Paragraph:

Create once, distribute everywhere, engage anywhere

Web3 newsletters & publishing.

We automatically summarize and cast about the best posts on Paragraph.

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

this is why I tend to think the posts should be 1155's rather than 721's

it follows the `mint first` principle

then all interactions with the post are on one tokenId

in fact each @paragraph publication should have its own 1155 contract address and all posts are just tokenId's on that contract 👇

nature finance onchain /basin @basin
 |  place-based /situs  |  🦇🔊

all sorts of stuff could then be done with this i.e

@basin dispatches ( @paragraph PUBLICATION) is a 1155 contract with own 0x

POST 1 is tokenId 1
POST 2 tokenId 2
POST n tokenId n

TID 1 could have 5 collectors
TID 2 could have 9 collectors
TID n could have n collectors

super easy to query and compose

✧the dev for onchain music
✧✧✧✧✧✧✧

exactly!!!!!

that's the f-ing beauty of 1155!

Founder and Artist @carculture.eth and carmania.eth 
Curating and celebrating the Art of the Automobile on the /car channel

Park your car art here 👉 /car

I think 1155's are better suited for this

one 1155 `0x` contract per publication

one `tokenId` per post

n tokens  per `tokenId` (`ERC1155Supply') based on # collectors

@colin would love your thoughts

What about NFTs accompanying posts ? Must they be 1155s also? No 721s?