Knowledge base

http verified

How the message was submitted

For messages injected over REST: which token submitted them and from which address.

In detail

Provenance, and more useful than it first appears: on a shared node it answers "who sent this", and the token name is a name we choose. A token per customer or per exporter turns this into an attribution field for free. ๐Ÿ”ด The key is spelled autentication โ€” no h. That is the vendor's spelling, observed on the build, and any parser must match it exactly. Correcting it in our code would mean reading a field that does not exist.

What happens if you get it wrong

A parser written from the obvious spelling.The field is always absent and attribution silently disappears.verified by experiment ยท inference