# Musiquay — Feature: Release Credits > Who engineered? Who performed? Who mixed? Who produced? Everything. The label that edited this format, this batch. Discogs meets Metal Archives meets Bandcamp, decentralized on Nostr. ## Overview The [event roster](./FEATURES_ROSTER.md) documents the live side of the scene — every show, every participant, every setlist. The release credits system does the same for **recorded music**. Every release on Musiquay has full, structured, scene-validated credits. Not just "artist name." The complete picture: who wrote each song, who played what instrument, who produced, who recorded, who mixed, who mastered, which label released it, which plant pressed the vinyl, who designed the cover, who took the band photos, who wrote the liner notes, who managed the artist. Everyone. This is what happens when you combine: - **Bandcamp's** indie ethos and artist-direct model - **Discogs'** obsessive format and edition tracking, down to the pressing plant and catalog number - **Metal Archives'** (Encyclopaedia Metallum) exhaustive credits, lineup details, and community maintenance But decentralized. On Nostr. Community-validated with scene police. Covering all genres. And integrated into the same scene graph that powers the event rosters, the marketplace, and the calendar. ## The Problem This Solves Recorded music metadata is a disaster. - **Streaming platforms** show the artist name and maybe the producer. That's it. The mix engineer, the mastering engineer, the session musicians, the studio, the designer — invisible. Spotify literally has "credits" buried four taps deep and the data is usually incomplete because it comes from distributor metadata, not from the people who actually made the record. - **Bandcamp** lets artists write whatever they want in the description field. Some include detailed credits, most don't. It's unstructured text — you can't search for "all albums mixed by Engineer X." - **Discogs** has incredible data but it's centralized, increasingly commercial, and disconnected from the music itself. You can find out who pressed a vinyl, but you can't play the album from the same page. - **Metal Archives** is exhaustive for metal — every lineup change, every session musician, every split EP — but it only covers metal, and it's a centralized wiki with no cryptographic verification. Musiquay combines all of these into a single, structured, protocol-native system where credits are Nostr events on the same network where the music lives. ## Core Concepts ### Credits as Structured Nostr Events Release credits follow the same model as [event rosters](./FEATURES_ROSTER.md): structured Nostr events with participant tags, roles, and scene police validation. A release credit event references the release (album/EP/single) and tags every participant with their specific role. Each participant is a Nostr pubkey. Each credit is queryable, confirmable, and permanent. ### Every Role on the Record A typical album's credits might include: | Category | Roles | |----------|-------| | **Composition** | Songwriter(s), lyricist(s), composer(s), arranger(s) | | **Performance** | Vocalist, guitarist, bassist, drummer, keyboardist — every instrument. Session musicians. Guest features. | | **Production** | Producer(s), co-producer(s), executive producer | | **Recording** | Recording engineer(s), assistant engineer(s), studio name/location | | **Mixing** | Mix engineer(s), mix assistant(s), mix studio | | **Mastering** | Mastering engineer(s), mastering studio | | **Label** | Label that released it, A&R person, label manager | | **Management** | Artist manager, booking agent who made the deal happen | | **Visual** | Album artwork designer/illustrator, photographer (cover shoot, band photos), layout/typography designer | | **Video** | Music video director, cinematographer, editor, colorist | | **Written** | Liner notes author, translator | | **Manufacturing** | Pressing plant (vinyl), replication plant (CD), duplication house (cassette) | This level of detail already exists — artists know this information, it's printed in liner notes and booklets. Musiquay structures it and makes it searchable, linkable, and permanent. ### Per-Track Credits Credits aren't just at the album level. Each individual track can have its own credit entries: - **Different songwriters per track** — one song might be written by the whole band, another by just the vocalist, another might be a cover. - **Session musicians per track** — a guest cellist on track 3, a horn section on track 7. - **Featured artists** — "Track 5 feat. Artist Y" as a structured, tagged relationship. Both the releasing artist and the featured artist can confirm. - **Different producers per track** — common on albums with multiple production styles. - **Recording details per track** — some tracks recorded at Studio A, others at Studio B with a different engineer. This per-track granularity is what makes the data truly useful. When a session musician's profile shows "performed on 47 tracks across 12 releases," each of those is a specific, confirmable credit on a specific track. ### Format and Edition Tracking This is the Discogs dimension. A release isn't just one thing — it can exist in multiple formats, each with its own credits and details. **A single album might have:** | Edition | Details | |---------|---------| | **Digital** | Released by Label X, mastered by Engineer A (digital master) | | **Vinyl (standard)** | 180g black, mastered by Engineer B (vinyl master), pressed at Plant P, 1000 copies, Cat# ABC-001 | | **Vinyl (limited)** | Colored vinyl, same master, same plant, 300 copies, Cat# ABC-001-LTD, different sleeve | | **CD** | Replicated at Plant Q, includes bonus track, different running order, Cat# ABC-002 | | **Cassette** | Released by Label Y (different territory), duplicated at House R, Cat# XYZ-050 | | **Japanese CD** | Released by Label Z, includes 2 bonus tracks, different artwork, OBI strip, Cat# JP-123 | **Each edition can have unique credits:** - Different mastering for vinyl vs. digital (common — vinyl masters are cut differently). - Different labels for different territories. - Different pressing plants and batch details. - Different artwork or packaging variations. - Bonus tracks with their own session credits. **Edition metadata:** - Catalog number - Barcode / matrix number - Pressing quantity (when public) - Release date (editions may ship at different times) - Territory / region - Manufacturing plant - Format details (weight, color, speed for vinyl; jewel case vs digipak for CD; etc.) This creates a collector's paradise — and it's all on an open protocol. No more checking three different Discogs listings to figure out which pressing you have. ### Scene Police Validation The validation model is identical to [event rosters](./FEATURES_ROSTER.md#scene-police-validation): 1. **The release creator** (usually the artist or label) publishes the initial credits. 2. **Wiki-style contributions** — anyone can suggest additions. A fan who has the liner notes can add missing credits. An engineer who worked on the record but wasn't tagged can add themselves. A label that released a specific edition can add their details. 3. **Tagged participants confirm** with signed Nostr events — cryptographic proof of involvement. 4. **Third-party attestations** — "I was at the recording sessions, can confirm [pubkey] engineered." 5. **Disputes** are visible — incorrect credits can be flagged by participants or witnesses. The same principles apply: the scene is small enough that fabrication is socially costly. A mix engineer with 200 confirmed release credits has a reputation that's expensive to fake. A label with a documented catalog of 50 releases builds credibility event by event, confirmation by confirmation. ## Data Model ### Release Credits Event (Kind 32214) The release credits event references a release (album/EP/single) and documents all participants at the release level. ```json { "kind": 32214, "pubkey": "", "content": "Optional liner notes, release story, recording context.", "tags": [ ["d", ""], ["a", "32211::", "wss://relay.musiquay.com"], ["title", "Credits: Album Name — Artist Name"], ["p", "", "wss://relay.musiquay.com", "producer"], ["p", "", "wss://relay.musiquay.com", "recording-engineer"], ["p", "", "wss://relay.musiquay.com", "mix-engineer"], ["p", "", "wss://relay.musiquay.com", "mastering-engineer"], ["p", "", "wss://relay.musiquay.com", "performer-vocals"], ["p", "", "wss://relay.musiquay.com", "performer-guitar"], ["p", "", "wss://relay.musiquay.com", "performer-bass"], ["p", "", "wss://relay.musiquay.com", "performer-drums"], ["p", "", "wss://relay.musiquay.com", "label"], ["p", "", "wss://relay.musiquay.com", "a-and-r"], ["p", "", "wss://relay.musiquay.com", "manager"], ["p", "", "wss://relay.musiquay.com", "artwork-designer"], ["p", "", "wss://relay.musiquay.com", "photographer"], ["p", "", "wss://relay.musiquay.com", "layout-designer"], ["p", "", "wss://relay.musiquay.com", "liner-notes"], ["studio", "recording", "Studio Name, City"], ["studio", "mix", "Mix Studio Name, City"], ["studio", "mastering", "Mastering Studio Name, City"] ] } ``` ### Track Credits Event (Kind 32215) Per-track credits for specific contributions that vary by song. ```json { "kind": 32215, "pubkey": "", "content": "", "tags": [ ["d", ""], ["a", "32210::", "wss://relay.musiquay.com"], ["a", "32214::", "wss://relay.musiquay.com"], ["p", "", "wss://relay.musiquay.com", "songwriter"], ["p", "", "wss://relay.musiquay.com", "songwriter"], ["p", "", "wss://relay.musiquay.com", "lyricist"], ["p", "", "wss://relay.musiquay.com", "performer-cello"], ["p", "", "wss://relay.musiquay.com", "featured-artist"], ["p", "", "wss://relay.musiquay.com", "producer"] ] } ``` Track credits **inherit** from the release credits and **override** where specific. If the album credits list Producer A, but track 5 was produced by Producer B, the track credit event specifies that. Tracks without their own credit event inherit all credits from the release. The track is referenced by `a` tag (address), not `e` tag (event id) — tracks are addressable and their event id changes on every encoding update. See [FEATURES_MUSIC.md](./FEATURES_MUSIC.md). ### Edition Event (Kind 32216) Each format/edition of a release is a separate event linked to the parent release. ```json { "kind": 32216, "pubkey": "", "content": "First pressing. Black 180g vinyl in gatefold sleeve.", "tags": [ ["d", ""], ["a", "32211::", "wss://relay.musiquay.com"], ["title", "Album Name — Vinyl (First Pressing)"], ["format", "vinyl"], ["format-detail", "180g", "black", "gatefold"], ["catalog", "ABC-001"], ["barcode", "1234567890123"], ["i", "barcode:1234567890123"], ["k", "barcode"], ["quantity", "1000"], ["release-date", "2026-06-15"], ["territory", "EU"], ["p", "", "wss://relay.musiquay.com", "mastering-engineer"], ["p", "", "wss://relay.musiquay.com", "label"], ["p", "", "wss://relay.musiquay.com", "pressing-plant"], ["t", "vinyl"], ["t", "first-pressing"], ["t", "limited"] ] } ``` **Edition-specific credits override release-level credits** where they differ. The vinyl edition might have a different mastering engineer than the digital release. A Japanese CD edition might have a different label. Each edition captures what's unique about that format. The `i`/`k` tags use NIP-73's external-content-ID mechanism for barcode/catalog numbers. NIP-73's supported-ID table does not yet list barcodes; the convention works as-is because `i`/`k` values are open-ended, and the table should be extended upstream when implementation begins. ### Role Vocabulary (Release Credits) Extending the [event roster role vocabulary](./FEATURES_ROSTER.md#role-vocabulary) for the studio and release context: | Category | Role IDs | Description | |----------|----------|-------------| | **Composition** | `songwriter`, `lyricist`, `composer`, `arranger`, `orchestrator` | Who wrote the music and words | | **Performance** | `performer-vocals`, `performer-guitar`, `performer-bass`, `performer-drums`, `performer-keys`, `performer-[instrument]`, `featured-artist` | Who played what. Open-ended — any instrument can be a role ID | | **Production** | `producer`, `co-producer`, `executive-producer` | Studio production | | **Recording** | `recording-engineer`, `assistant-engineer` | Who captured the sound | | **Mixing** | `mix-engineer`, `mix-assistant` | Who mixed it | | **Mastering** | `mastering-engineer` | Who mastered it | | **Label / Business** | `label`, `a-and-r`, `manager`, `booking-agent`, `distributor` | Business side of the release | | **Visual** | `artwork-designer`, `illustrator`, `photographer`, `layout-designer`, `typography` | Visual identity of the release | | **Video** | `video-director`, `cinematographer`, `video-editor`, `colorist`, `vfx` | Music video credits | | **Written** | `liner-notes`, `translator` | Text contributions | | **Manufacturing** | `pressing-plant`, `replication-plant`, `duplication-house`, `print-house` | Physical production — companies as participants | Like the event roster vocabulary, this is a convention, not a rigid schema. New role IDs emerge as the community uses them. ### Confirmation, Attestation, Contribution Events These use the **same mechanisms** as the event roster system — the only difference is what they reference. - **Confirmation:** A participant confirms their release credit. Signed by their key. NIP-32 kind 1985 label event, referencing the release credits event instead of the roster event. - **Attestation:** A third party vouches. "I was at the sessions, can confirm [pubkey] engineered." NIP-32 kind 1985 label event. - **Contribution:** Wiki-style addition. A fan with the liner notes adds the missing mastering engineer. A label adds their edition details. NIP-22 kind 1111 comment scoped to the credits event. Sharing the validation mechanisms between the roster and credits systems means the **scene graph treats them uniformly**. A confirmation is a confirmation, whether it's for a live show or a recording session. A participant's profile aggregates both. ## What the Data Creates ### Complete Discographies Every participant builds a discography through confirmed credits: - **Engineer's discography:** "Mixed 83 releases across 12 labels. Top collaborators: Artist A (7 albums), Artist B (5 albums)." - **Producer's discography:** "Produced 41 releases. Studios: Studio X (23), Studio Y (12), various (6)." - **Session musician's discography:** "Performed on 127 tracks across 34 releases. Instruments: cello (89), viola (38)." - **Designer's discography:** "Artwork for 56 releases. Labels: Label A (12), Label B (8), independent (36)." - **Label catalog:** "47 releases. Formats: vinyl (41), CD (23), digital (47), cassette (12). Active since 2019." This is Metal Archives-level exhaustiveness, for every genre, built by the community, verified by the participants. ### Format Intelligence Edition tracking creates a structured database of physical releases: - **Pressing plant reputation:** Which plants have the most credits? Which are associated with quality pressings? (Social consensus through the graph, not a rating system.) - **Label activity:** A label's complete catalog across all formats and territories. - **Format trends:** How many vinyl releases vs. digital-only? Growing cassette revival? The data shows it. - **Collector information:** Every variant, every pressing quantity, every catalog number — searchable across the protocol. ### Cross-Reference Queries The real power emerges from querying across credits and rosters: - "Find every release mixed by Engineer X" — their studio discography. - "Find every album mastered at Studio Y" — the studio's catalog. - "See Producer Z's complete body of work across all artists" — their creative portfolio. - "Track session musician W's contributions across dozens of artists" — their full performance history. - "Which pressing plant does the most work for indie labels in Europe?" — industry intelligence from structured data. - "Show me every release where Artist A and Engineer B worked together" — collaborative history. - "Find all releases on Label C with vinyl editions" — catalog browsing with format filtering. ### Live + Studio: The Unified Profile This is where release credits and [event rosters](./FEATURES_ROSTER.md) converge into something no other platform offers. An engineer's profile shows: - **Live:** 147 confirmed show rosters — FOH at venues across Portugal, festivals in Spain and France. - **Studio:** 83 confirmed release credits — mixed albums for indie rock, post-punk, and electronic artists. - **Total body of work:** 230+ confirmed credits across live and recorded work. A session musician's profile shows: - **Live:** 89 show rosters — performed with 12 different artists, sat in as guest 23 times. - **Studio:** 127 track credits — cello and viola across 34 releases. - **Setlist features:** "Performed live on Song X 15 times, including the original studio recording." A photographer's profile shows: - **Live:** 200+ show rosters — gig coverage, festival documentation. - **Studio:** 28 release credits — album photography, press shots, cover art. - **Visual portfolio:** All tagged photos from shows + all tagged artwork from releases, in one place. This is the **complete professional identity** of everyone in the scene — live and studio, all on one protocol, all verified by the community. ## Integration with Other Pillars ### Scene Graph Release credits are a primary input to the scene graph, alongside event rosters: - Every confirmed credit creates a connection between participants. - "Worked together on Release X" is a professional relationship link. - Labels, studios, and pressing plants become nodes in the graph with their own connection networks. - The graph grows denser with every release published and every credit confirmed. ### Event Calendar Release credits connect to the calendar through: - **Release events** — an album drop is a calendar event. The credits for the release and the people at the launch party (event roster) are both part of the record. - **Setlist linking** — live setlists reference published tracks, which have credits. A fan watching a setlist can tap through to see who produced, mixed, and played on the studio version. ### Services Marketplace Release credits power marketplace reputation for studio professionals: - A producer's marketplace listing ("available for production") is backed by their release credit history. - A mastering engineer advertising their services links to a catalog of confirmed releases. - A designer's portfolio is their confirmed artwork credits across releases. ### Event Roster The shared validation model means release credits and event rosters form a **unified credits system**: | Dimension | Event Roster | Release Credits | |-----------|-------------|-----------------| | **Subject** | A live event (show, festival, etc.) | A recorded release (album, EP, single) | | **Creator** | Promoter or venue | Artist or label | | **Participants** | Everyone who worked the event | Everyone who worked on the recording | | **Validation** | Scene police — confirmations, attestations, wiki contributions | Scene police — same mechanism | | **Builds** | Live work history | Studio discography | | **Together** | The complete professional profile of everyone in the scene | ## NIP Strategy | Concept | NIP Status | Notes | |---------|------------|-------| | **Release credits event** | Custom kind 32214 | Full participant list for a release, with structured roles. No existing NIP covers studio credits. | | **Track credits event** | Custom kind 32215 | Per-track credits that override/extend release-level credits | | **Edition event** | Custom kind 32216 | Format-specific details, manufacturing credits, catalog info. NIP-73 `i`/`k` tags for external IDs (barcode, UPC, catalog number). | | **Confirmation** | NIP-32 kind 1985 | Same mechanism as roster confirmation — label event referencing the credits target instead of the roster | | **Attestation** | NIP-32 kind 1985 | Same mechanism as roster attestation — label event | | **Contribution** | NIP-22 kind 1111 | Same mechanism as roster contribution — comment scoped to the credits event | | **Participant tagging** | NIP-52 `p` tags with roles | Extended role vocabulary for studio context | The credits system adds **three custom event kinds** (release credits 32214, track credits 32215, edition 32216) and reuses the roster system's validation mechanisms — NIP-32 label events and NIP-22 comments. This reinforces the unified credits architecture — live and studio credits validated and queried the same way. ## UI Concepts ### Release Page An album page on Musiquay shows: - **Music** — tracks with playback, streaming, payment. - **Credits** — full structured credits, grouped by category. Confirmation status visible per entry. Wiki-editable. - **Editions** — all format variants with details. Catalog numbers, pressing info, territorial details. - **Per-track credits** — expand any track to see track-specific credits (session musicians, featured artists, different songwriters). - **Liner notes** — the content field of the credits event, if provided. - **Visual gallery** — album artwork, band photos, all linked to the credited designer/photographer. - **Live history** — via setlist data: "Track 3 has been performed live 47 times, most recently at [linked event]." ### Participant Profile — Studio Section Each credited participant's profile shows: - **Release credits** — chronological, filterable by role, label, year. - **Track count** — total tracks credited across all releases. - **Confirmation rate** — what percentage of their credits are confirmed by others? - **Top collaborators** — which artists, labels, and engineers appear most often alongside them? - **Studios** — which studios they've worked at (derived from studio tags on credit events). ### Label Page A label's Nostr profile aggregates: - **Full catalog** — all releases published under this label. - **Format breakdown** — vinyl, CD, digital, cassette, with edition details. - **Artist roster** — all artists who have releases on the label. - **Credits network** — which engineers, designers, and studios the label works with most. ### Edition Browser For collectors and format enthusiasts: - **Browse editions** of a release — see all variants side by side. - **Manufacturing details** — pressing plant, batch size, catalog number, barcode. - **Edition-specific credits** — different mastering, different artwork, bonus tracks. - **Rarity signals** — pressing quantity, limited editions, territorial exclusives.