Payment coordination and liquidity efficiency in wholesale payments systems
Bibliographic record
Abstract
A new wholesale payments system launched in Canada in 2021. This real-time gross settlement system, called Lynx, has two types of settlement mechanisms, one allowing offsetting and the other not. This paper studies the decision problem of the Bank of Canada: which of the two settlement mechanisms it should use to send its payments. Using extensive simulation, we show that, mainly due to the benefits of liquidity pooling, Lynx would achieve its highest liquidity efficiency (even better than that of the current Large Value Transfer System (LVTS)) if all payments (urgent and nonurgent) from all participants were sent to the mechanism allowing offsetting. The minimum amount of liquidity required to settle all payments by critical intraday deadlines is approximately C$10 billion, around half the amount of collateral that LVTS participants allocated pre-Covid-19. Since time-critical payments sent to the offsetting mechanism could experience a delay, the high level of liquidity efficiency is accompanied by an increase in the number of participants’ operational interventions (to pledge more collateral or to alter payment priorities) to ensure that those time-critical payments are never delayed. When coordination does not occur, liquidity efficiency can be far lower than in the LVTS. The results highlight that the Bank of Canada helping with coordination is more important than the specific choice of mechanism.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".