Mint auth creates new auth tokens that allows COOP publishers to publish on-chain. Occasionally there is a period of overlap between existing auth tokens and newly minted ones, e.g. covering time periods in long-running operations.
When there is an overlap in auth token validity the selector picks the first token it comes across with validity, this seems to be the one alphabetically in order, not the oldest valid token that may also be valid. This leads to unused tokens.
Logging this as much as a note to users. The ability to burn unused $AUTH (below) essentially renders this moot. We might also consider a line or two in documentation for potential users.
Mint auth creates new auth tokens that allows COOP publishers to publish on-chain. Occasionally there is a period of overlap between existing auth tokens and newly minted ones, e.g. covering time periods in long-running operations.
When there is an overlap in auth token validity the selector picks the first token it comes across with validity, this seems to be the one alphabetically in order, not the oldest valid token that may also be valid. This leads to unused tokens.
Logging this as much as a note to users. The ability to burn unused $AUTH (below) essentially renders this moot. We might also consider a line or two in documentation for potential users.
Connected to: https://github.com/mlabs-haskell/cardano-open-oracle-protocol/issues/83