implement a strategy for each song that finds the artist address

[TimDaub]

• related: https://github.com/neume-network/strategies/issues/321
• for each music NFT find its artist
• in some cases, that may be the person that also minted the NFT initially
• In some cases we'll probably have to figure out the contract semantics to understand which addresses represent the artists

[neatonk]

For zora drops contracts the creator address could be used.

https://github.com/neatonk/strategies/blob/021e33808b29fa15ca9961d0a3e6fc6a06f63689/src/strategies/zora-drops-filter-contracts/transformer.mjs#L27-L31

[TimDaub]

Here's what @reimertz wants:

minter whoever minted the nft artist artist who created the song / track owner who is the current owner of said nft

[TimDaub]

• catalog v2 nicely stores the creator address in the mint transaction: https://etherscan.io/tx/0xe682d75389eaf13500552cfcabd0fe7bdeb14f5273b06bbaa22516c834b5e3f8
• while we probably could also use the minter address, I think it's probably safer accessing this call data directly

[TimDaub]

For Zora (catalog v1), the transaction sender of the mint transaction is likely the artist.

[TimDaub]

For zora artworks usually the minter is the artist unless there are contracts interacting with the zora contract. So actually we should examine catalog v1 specifically.

[TimDaub]

• added transactionHash to call-tokenuri: 57e4f2cf92f28307e7ed6d6a2c9d7ab810c82bf4
• 2b238f0558c731ace55109d3ad919f1e5de80e09 separated getting transaction receipts from get-minter

[TimDaub]

we're now requiring an artist.address property in /schema: https://github.com/neume-network/schema/commit/db192d2fa1a88c84a00f2a074646b94e0f519038

[TimDaub]

For Zora (catalog v1), the transaction sender of the mint transaction is likely the artist.

this was confirmed to me by a catalog contributor