Clarification for computed rootOwner in consolidated NFT changes array

[spenweb]

When should a Change object with "field": "rootowner" property (aka rootowner change) be added to the consolidated NFT change array?

I would expect a rootowner change to be added whenever the root owner changes. I see this occurring in the BUY interaction logic but not in the SEND or ACCEPT logic.

Use case

Determine what address owned an NFT at a certain block by looking at the consolidated NFT without having to reference other NFTs.

Reference: rootowner

[adamsteeber]

A user could SEND an NFT to another NFT that they also own which wouldn't change the rootowner field. Also, a user may ACCEPT a pending resource which does not change the rootowner. If the entity in the ACCEPT interaction is NFT, then I suppose that's a more philosophical question: does ownership change when a parcel is offered or when it is accepted?

[spenweb]

I am more considering the case where the SEND interaction involves sending an NFT to a wallet address. I am not seeing in the consolidator code anywhere that handles this case by adding a Change object where the rootowner field changes.

This is an issue when trying to determine what wallet address (rootowner) owned the NFT at an arbitrary block.