Curation - Indexing PA's Assembly Press protocol

[djfnd]

Purpose

Starting a thread to think through the "contextual data" indexing workstream, as indicated in my recent Roadmap post.

Specifically, integrating the Assembly Press protocol as a first step on the way of indexing curation, lists, alongside NFT events.

Details

@0xTranqui has put together a walkthrough of the protocol within the PA forum (link). My reading of this is that essentially it emits NFTs with metadata pointing to the list that the created maintains.

I see this as one of hopefully many such approaches to public good curation tooling, and so we should think about a generalised approach on how this should be ingested and presented to onchain music front-ends.

Furthermore, this gets really interesting where we can link across from NFTs that are indexed from onchain events, to where they are included in a curation list.

Initial thoughts

I think there are probably several elements to this, starting with an Assembly Press Strategy to extract and transform the data contained with curation NFTs, outputted into a separate DB environment at first. This would be a "curation" database, alongside the "music NFTs" database, and would in effect be the start of neume segmenting its output, so that front-ends can ingest only what they are interested in.

I am currently struggling to think conceptually about how we link and surface the through lines across the databases (if we need to at all, maybe that's a job for somewhere else in the onchain music stack). So interested in any ideas there.

It's also worth noting that many of the NFTs being curated by Assembly Press will be those created by Zora factory contracts, and so any further steps above and beyond the strategy -> curation DB will likely be roadblocked by our proposed workstream to enable self-elected contracts (nb, will link in here when I/someone creates a thread on that subject).

cc: @neatonk @il3ven @reimertz

I also note that there is heavy reference to soulbound tokens within the walkthrough post, which, combined with your interest in curation in general, makes me feel like this is gonna be very much your bag @TimDaub ;) Would love your thoughts on this topic!!

[neatonk]

GM, as suggested by @salieflewis I'm planning to submit a small proposal to PA that would fund integration docs as a precursor to the Neume integration being discussed here. I'll share a draft of the proposal on the PA forum and link it here for discussion today.

Interested in feedback on scope, specifics, or anything else.

[djfnd]

SGTM!

[neatonk]

Here's the scope for convo:

• Supplement and reword solidity comments as needed to fully document relevant source files.
• Update solidity comments to conform to the NatSpec format and use forge doc to generate HTML API docs from them.
• Create a high-level overview of the system that anyone can use to grok the how, what, and why in a short period of time. Include guidance for integrators with links to the API docs and source code. Existing forum posts may be used as a starting point for this.

[salieflewis]

That sounds great @neatonk

Lmk if there is anything you need from me!

[neatonk]

Here is a draft proposal I've shared in the PA forum for feedback...
https://forum.public---assembly.com/t/draft-assemblypress-integration-docs/371

[djfnd]

Quite an interesting alternative approach to curation from Future Tape - https://mobile.twitter.com/future_tape/status/1643336410181644292

Using the embeddable players as building blocks for curation is quite fun, though not especially composable outside of that stack.

[neatonk]

Oh cool. Looks like we should consider indexing mirror posts as well.