Interface CommonMeta

All the parsed CommonMeta fields, as { "key1": "value", "key2": "value"... }.

See

https://docs.krist.dev/docs/commonmeta.html

For a transaction sent to a name, the "metaname" of the transaction recipient (foo in [email protected]).

For a transaction sent to a name, the name of the transaction recipient (bar.kst in [email protected]). The name suffix will be included.

See

https://docs.krist.dev/docs/commonmeta.html

For a transaction sent to a name, the full recipient of the transaction (e.g. [email protected]). The name suffix will be included.

The recipient is the part of the transaction meta before the first semicolon (;). When attempting to send a transaction to a name such as bar.kst or [email protected], the Krist server will automatically prepend this whole name to the transaction meta, separating it from the original meta with a semicolon if it existed.

See

https://docs.krist.dev/docs/commonmeta.html

The whole return CommonMeta field if it was supplied (e.g. [email protected]).

See

https://docs.krist.dev/docs/commonmeta.html

If the return CommonMeta field was supplied, the "metaname" of the transaction sender (foo in [email protected]).

If the return CommonMeta field was supplied, the name of the transaction sender (bar.kst in [email protected]). The name suffix will be included.

If the return CommonMeta field was supplied, and was a valid Krist name or metaname, the full sender of the transaction (e.g. [email protected]). The name suffix will be included.