counterparties

Your public key. The first and last slot in which a transaction signed by that key touched the system. Which instruments it called. A name, if you set one. That is the complete list. The desk does not look up keys elsewhere, does not associate keys with one another, and does not keep any record that is not already on the chain.

A name is up to thirty-two bytes set by the counterparty with the name instrument and stored in an account only that counterparty can write. Names are shown as set. They are not checked for uniqueness, decency, or accuracy. Two counterparties may have the same name. A counterparty may call itself anything, including the bank's name, and if it does, the desk lists that on the incidents page as impersonation and does nothing else, because there is nothing else the program permits.

These are slots, shown as block times. First seen is the earliest transaction the cluster returns for the key against the program. Last seen is the latest. The cluster's history for any key may be truncated by the RPC provider, in which case first seen will be later than the truth. The desk does not correct for this. It prints what the cluster returned and the time it asked.

The operator key appears in this list like any other, because it signs transactions against the system.¹ Its instruments are initialize, set_rates, settle, hold, and batch_memo. It cannot lock, open, release, or name, because those require a counterparty signer and the program does not permit the operator to act as one. Should the operator key ever appear with one of those instruments beside it, that is a serious incident.