CLIVEBREMNER
local
RECEIVED
TREASURY

glossary

TS/R
PLAIN MEANINGS FOR THE WORDS THIS DESK USES
TS/R/1

terms

static, in the order a new reader needs them
TERMMEANING
the bookThe set of all accounts owned by the system program. It is on-chain state, read live, not a database this desk keeps.
the floatPooled value that has not been assigned to any position. The open instrument draws from it and the settle instrument returns to it.
positionOne obligation between the float and a counterparty. It names an amount, a collateral account, and the batch window in which it is due to clear.
collateralValue a counterparty has locked against one or more positions. It is not released while a position it backs is open.
counterpartyAny account that has signed a transaction calling one of the system's instruments. This desk knows the key and nothing else.
instrumentOne Anchor instruction with one purpose, one signer requirement, and one fixed set of accounts. There are nine.
settleThe instrument that returns a position's amount plus fee to the float and closes the position.
settlementAn entry that has been carried by a transaction which reached finality. It is a record, not an intention.
finalityThe point at which the cluster will not reorganise a transaction away. This desk reports nothing as settled before it.
confirmedA transaction the cluster has accepted but not yet finalised. This desk does not display these as settled.
finalizedThe confirmation status this desk requires before an entry appears on the settlements page.
batchOne run of the overnight process, identified by a number stored in the config account.
batch windowThe length of time each day, in seconds, during which the settle instrument may be called.
batch numberA monotonically increasing counter. A position names the batch number in which it is eligible to settle.
rate sheetThree numbers in the config account: the collateral ratio, the fee, and the batch window.
basis pointOne hundredth of one percent. The ratio and the fee are both written in basis points to avoid rounding arguments.
holdA mark placed on a position when the batch finds its collateral below ratio. It moves no value.
releaseThe instrument that returns collateral to a counterparty once it backs no open position.
lockThe instrument that moves value into a collateral account so that a position can be opened against it.
operatorThe role that signs the administrative instruments. In practice, this desk.
operator keyThe single hardware-held key the program accepts for initialize, set_rates, hold, and batch_memo.
PDAA program-derived address. An account whose address is computed from seeds and owned by the program rather than by a private key.
seedOne of the inputs used to derive a program-derived address. The seeds for every account are listed on the instruments page.
bumpThe extra byte used to push a derived address off the elliptic curve so that no private key can exist for it.
mintThe account that defines a token, including how many decimal places its base units carry.
base unitsThe smallest indivisible amount of a token. Every amount in the program is stored this way and divided only for display.
decimalsThe number of places to shift a base unit amount to show it as a person would write it.
vaultThe token account that actually holds locked or pooled value, owned by the program and derived from the account it serves.
memoTwo different things: a short dated note I write on this site, and a small piece of text attached to a transaction on chain.
interfaceThe published description of every instrument, account, and argument the program accepts.
IDLThe file format that interface description is stored in. It is read from the chain rather than bundled into this site.
slotThe cluster's unit of time. Every transaction is recorded in one.
block timeThe wall clock time the cluster assigned to a slot. Every date on this site comes from it.
signatureThe identifier of a transaction. It is the thing to quote when writing to the desk about an entry.
lamportThe smallest unit of the cluster's own token, used for fees and rent.
rentThe lamports an account must hold to stay open. Closing a position returns them.
incidentAnything that did not go as written. Each one gets a line on the incidents page and, if it required a decision, a memo.
change controlThe rule that every production change is announced by memo before it happens and recorded after it happens.
working dayMonday to Friday, excluding the bank's holidays. Notice periods on this site are counted in these.
address orderThe order positions are settled in: by the bytes of their addresses, lowest first. Arbitrary and fixed.
archive nodeAn RPC node that keeps the full history of the chain. This site does not assume one.
discriminatorThe first eight bytes of instruction data, identifying the instrument.
effective batchThe batch number from which a rate change applies.
entryA finalized transaction against the system. A line in the book.
heldThe state of a position the batch declined to settle. Still open, still collateralized.
impersonationA self-set name that claims to be the bank or the desk. Listed, not prevented.
little-endianThe byte order arguments are stored in. Least significant byte first.
nonceA number a counterparty supplies to make each position's address unique.
reason codeA small integer on hold saying why. Zero, one, or two.
rerunA batch started again after a stop. Produces a second opening memo.
reviewReading a held position and deciding whether a memo is needed.
token accountAn account holding a balance of one mint for one owner.
vaultA token account owned by a program-derived address. No key controls it.
windowThe period each day in which settle may be called for the current batch.
END OF GLOSSARY