Skip to content

auditor: decide which audit info wins during input attribution #2251

Description

@EvanYan1024

Raised in the review of #2199.

Request.AuditRecord overwrites in.OwnerAuditInfo with the locally stored audit info of the spent token's owner wherever the local lookup finds one, keeping the request-carried audit info only as a fallback — so the local store wins today. #2199 corrected the docs to state this actual order.

Whether the preference should be flipped — letting the request metadata pin the exact audit info the sender distributed, with the local store as the fallback — is a semantics call to settle separately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions