OptionalcommitProducing losing-state edge, never the triggering/winning commit.
OptionalepochMLS epoch of that fork node.
OptionalpayloadThe decrypted Marmot app payload bytes of the invalidated message.
OptionalrumorOptionaltagHex confirmation tag of the losing fork-tree node it decrypted against.
Optionaltransport
An MLS application message that decrypted only on a losing/abandoned branch (
protocol-core/inbound-processing.md,convergence.md). Either it was tentatively delivered asacceptedon a branch a later convergence rewind abandoned (Marmot v2 delivers eagerly), or it only ever decrypted on a non-canonical fork node during the tree sweep. The spec requires it be reported asinvalidated, not delivered as accepted output — but the local API is free to expose where it decrypted so a consumer (e.g. a full-history debugger) can still attribute it to its fork.messageis the MLS application message (the encrypted wrapper);payloadis its decrypted Marmot app payload bytes, so a consumer can identify the rumor being retracted (e.g. to withdraw it from a UI, or to record it under its fork).tagandepochidentify the losing branch:tagis the hex MLS confirmation tag of the fork-tree node the payload decrypted against (an application message does not change the epoch or confirmation tag, so the node is the delivery branch), andepochis that node's MLS epoch. All three are populated for invalidations the engine produces; they are optional only for backward compatibility with consumers that ignore them.