marketing

Marketing materials (presentations, posters, flyers)
Log | Files | Refs

NOTES.md (23978B)


      1 # Sources and caveats for the DG FISMA deck
      2 
      3 Every factual claim on a slide is listed here with its source. Items marked
      4 **CHECK** should be verified before the deck is presented. Items marked
      5 **DO NOT SAY** are claims that circulate in our own material but that do not
      6 survive checking — they are listed so nobody reintroduces them.
      7 
      8 ---
      9 
     10 ## Slide 2 — Five disputes, one root cause
     11 
     12 - Council: the Council's own document ST 16695/25 is headed "Mandate for
     13   negotiations with the European Parliament", December 2025. The ECB calls it
     14   a "General Approach". Both are in circulation; the Council's wording is the
     15   accurate one.
     16 - **Parliament has NOT adopted a first-reading position.** OEIL still records
     17   "Awaiting Parliament's position in 1st reading". The 9 July 2026 plenary
     18   vote was a **Rule 72 confirmation of the committee's negotiating mandate**.
     19   The ECB's FAQ loosely says Parliament "adopted its position" — do not copy
     20   that; this audience will know. **Say "Parliament confirmed its negotiating
     21   mandate on 9 July 2026."** The 416-169-22 figures relate to that Rule 72
     22   vote and are **UNCONFIRMED** — the EP does not publish them. Do not quote
     23   a vote count.
     24 - Trilogue opened mid-July 2026. Latest public four-column table is
     25   WK 13561/2026 of 4 September 2026; the outcome of the 30 September 2026
     26   trilogue is not public. ECB pilot: **second half of 2027, 12 months**
     27   (three different ECB formulations circulate — "mid-2027", "H2 2027",
     28   "September 2027"; use H2 2027). First issuance targeted 2029.
     29 - **The Rulebook evidence on the slide.** ECB, "Digital euro scheme
     30   rulebook", version 0.91, DRAFT, 2 July 2026, glossary: *"User Alias — A
     31   unique pseudonymous identifier used to protect user's identity when
     32   processing digital euro payments that can only be attributable to an
     33   identifiable natural or legal person by the payment service provider
     34   distributing the digital euro or by the digital euro user."* Across the
     35   full extracted text of that draft there is no occurrence of "anonymity",
     36   "anonymous" or "blind signature". **CHECK** against the current published
     37   version — it is an interim draft and its own cover notice says so.
     38 - The claim that the Rulebook fixed the architecture before the privacy
     39   question was settled: Gütschow & Lucke, "The proposed design of the digital
     40   euro: A critical analysis", *Digital Finance*, December 2025,
     41   doi:10.1007/s42521-025-00171-2 (peer-reviewed, open access); and
     42   Cannataci, Fehrensen, Gütschow, Kesim, Lucke, "Digital Euro: Frequently
     43   Asked Questions Revisited", arXiv:2601.18644 v2, 8 July 2026.
     44 
     45 ## Slide 3 — "Cash-like" and pseudonymous are not the same thing
     46 
     47 - The de-anonymisation-by-correlation argument and the "no procedure to
     48   obtain a new identifier" point: fqa.t-euro.eu Q9; Jurjen Bos, "Digital
     49   Euro: a missed opportunity for privacy", Medium, 16 October 2026.
     50 - The ECB wording change from "would not **be able to** identify" to "would
     51   not identify": fqa.t-euro.eu Q3, with an Internet Archive citation.
     52   **CHECK** before using it out loud — it is a strong rhetorical point and
     53   will be challenged.
     54 - **"Only PSPs will be able to identify the end user and link that identity
     55   to individual transactions."** ECB, Third progress report on the digital
     56   euro, 16 July 2025, section on technical input on privacy and data
     57   sharing. This is the ECB's own wording and is the strongest single quote
     58   in the deck — read it verbatim.
     59 - Per the ECB's own FAQ, for online transactions the Eurosystem would not
     60   identify users "but PSPs would be able to identify users for the purpose of
     61   compliance with anti-money laundering rules". Privacy is tiered by actor,
     62   not global.
     63 
     64 ## Slide 4 — The demand is already on the record
     65 
     66 - 43% ranked privacy first: ECB public consultation on a digital euro,
     67   reported in the Eurosystem report, April 2021. Quoted in the
     68   epicenter.works open letter.
     69 - 94% / 59%: Deutsche Bundesbank study on payment behaviour, 2020, as cited
     70   by Ballaschk & Paulick (below). Say "the Bundesbank's 2020 payment
     71   behaviour study" — it is a national figure, not euro-area.
     72 - **BIS:** Auer & Böhme, "Central bank digital currency: the quest for
     73   minimally invasive technology", BIS Working Papers No 948, June 2021:
     74   *"All this brings us back to David Chaum ... the time finally seems ripe
     75   for computer scientists and central bankers to join forces and bring to
     76   light a true electronic complement to cash."* Footnote 25 cites Chaum,
     77   Grothoff & Moser (2021). This is the strongest institutional endorsement
     78   available and it is worth quoting.
     79 - **Banca d'Italia:** Urbinati et al., "A digital euro: a contribution to
     80   the discussion on technical design choices", *Mercati, infrastrutture,
     81   sistemi di pagamento*, Questioni istituzionali No. 10, July 2021, §2.6
     82   specifies an eCash component using blind signatures and cites the SNB
     83   paper. **The ECB republished it on its own site** as Eurosystem
     84   experimentation documentation (listed 11 October 2021) — that republication
     85   is the point, so have the ECB URL to hand.
     86 - **Bundesbank staff:** Ballaschk & Paulick, "The public, the private and
     87   the secret: Thoughts on privacy in central bank digital currencies",
     88   *Journal of Payments Strategy & Systems* 15(3), 2021, 277–286, hosted on
     89   bundesbank.de. Describes the Chaum–Grothoff–Moser framework accurately,
     90   then says whether it would "sufficiently and effectively ensure regulatory
     91   compliance is open to debate". Cite as a **staff publication**, not a
     92   Bundesbank position.
     93 - Rapporteur Fernando Navarrete Rojas (EPP) initially proposed a
     94   token-based/offline-first instrument; the June 2026 ECON position moved to
     95   parallel offline plus account-based online. Source: heise, 9 July 2026.
     96   **CHECK** — this is the single most useful fact in the deck for this
     97   audience, and the wording on the slide ("initially proposed a token-based
     98   instrument") should be confirmed against the draft report itself.
     99 - 14 civil-society organisations: "A Call to EU Co-Legislators: The Digital
    100   Euro as an Opportunity for European Privacy", Brussels, 17 June 2026,
    101   organised by epicenter.works, signed by EDRi, Homo Digitalis, Access Now,
    102   Bits of Freedom, Digitalcourage and others — **including Taler Operations
    103   AG and Taler Systems SA**. Declare that interest if the letter is cited.
    104 - The Austrian central bank: Summer & Hermanky, "A digital euro and the
    105   future of cash", OeNB *Monetary Policy & the Economy* Q1-Q2/22. The OeNB
    106   text says GNU Taler **"could be an ideal template"**; the BFH press release
    107   says "recommends". The slide says "has described ... as a possible
    108   template", which matches the OeNB wording. **Do not upgrade this to
    109   "recommends".**
    110 - Related and stronger for this audience because it is a central bank's own
    111   working paper: Martin Summer, "Privacy by design for public digital money",
    112   OeNB Working Paper 278 — the technical authority cited in the open letter.
    113 
    114 ## Slide 5 — The other way to build it
    115 
    116 - Mechanics are as in Dold, "The GNU Taler system: practical and provably
    117   secure electronic payments", PhD thesis, Université de Rennes, 2019.
    118 - **The exchange, not the merchant, detects double-spending.** The draft deck
    119   had this wrong. The merchant deposits the coins and the operator performs
    120   the check.
    121 
    122 ## Slide 6 — Architecture
    123 
    124 - `images/operations.png`, the project's canonical diagram. It labels the
    125   escrow node "Central Bank or Exchange's Bank", which carries the two-tier /
    126   sCBDC story, and it shows the independent Auditor.
    127 
    128 ## Slide 7 — Asymmetric privacy answers AML
    129 
    130 - Welfare-optimality: Katrin Tinn, "A Theory Model of Digital Currency with
    131   Asymmetric Privacy", *Management Science*, 2025,
    132   doi:10.1287/mnsc.2024.06830. Peer-reviewed; this is the strongest
    133   third-party card in the deck and is worth naming out loud.
    134 - Income transparency and KYC at the perimeter: taler.net/en/governments.html
    135   and Dold 2019.
    136 
    137 ## Slides 8–9 — Offline
    138 
    139 - CAP theorem: Gilbert & Lynch, SIGACT News 33(2), 2002. Applied to payments
    140   in Grothoff & Dold, "Why a Digital Euro should be Online-first and
    141   Bearer-based", 26 March 2021 — "There is no third choice."
    142 - Chaum, Fiat & Naor, "Untraceable Electronic Cash", CRYPTO '88: fully
    143   offline anonymous cash cannot *prevent* double-spending.
    144 - Damage scales with transaction volume, not stored balance, and an attacker
    145   can provoke the outage: Grothoff & Dold 2021.
    146 - No European manufacturer of smartphone secure elements: Gross, Sedlmeir,
    147   Babel, Bechtel & Schellinger, SSRN 3891121, 2021.
    148 - The timeline figure is lifted from `2026-dielinke`. Vendors and dates are
    149   rendered in the figure itself; the `\cite` keys were stripped, so no
    150   bibliography is needed. If a reference list is wanted, `extra.bib` is in
    151   this directory and taler.net/en/news/2021-03.html keeps a rolling list of
    152   later breaks (TPM 2.0, Intel SGX/Downfall/Wiretap, AMD SEV-SNP, EUCLEAK on
    153   Infineon/YubiKey).
    154 
    155 ## Slide 10 — Holding limits
    156 
    157 - €3,000 retail / zero for business: Grothoff, Gütschow & Seehausen, "Taler as
    158   a synthetic Central Bank Digital Currency", Springer 2026,
    159   doi:10.1007/978-3-032-22946-5_9, §6.2. ECB analysis of limits up to €3,000
    160   is also in the ECB's own progress reporting; published academic range is
    161   €500–10,000.
    162 - **Banca d'Italia on eCash:** *"anonymity is of an asymmetric type and is
    163   guaranteed only in the phase of using tokens for the payer. During the
    164   withdrawal phase, the system is able to apply all the limits and controls
    165   typical of an account-based system."* (MISP Questioni istituzionali No. 10,
    166   July 2021.) This is the best answer to the holding-limit objection in the
    167   whole pack, because it comes from a Eurosystem national central bank and
    168   sits on the ECB's own website.
    169 - The four levers: Dold, "Taler as the Foundation for a European Retail
    170   Centrally Banked Digital Currency", response to the ECB InnovationLab
    171   expert group, ~2018, requirement V2.
    172 - "Replicates cash rather than deposits, so monetary policy and financial
    173   stability are not materially affected" is a close paraphrase of **Chaum,
    174   Grothoff & Moser, "How to Issue a Central Bank Digital Currency", SNB
    175   Working Paper 3/2021**. Attribute it — a Swiss National Bank working paper
    176   carries more weight here than we do.
    177 
    178 ## Slide 11 — Cost and competition
    179 
    180 - **€1.3bn is cumulative to first issuance in 2029** and covers internal and
    181   external components; **€320m a year from 2029**, which the ECB expects
    182   seigniorage to offset. (Cipollone reportedly said ~€300m/year to an Italian
    183   committee in February 2026 — use the published €320m.)
    184 - **Do not say €1.16bn is "committed".** The five framework agreements of
    185   2 October 2025 have an *estimated* value of €432.1m and a *ceiling* of
    186   €1.164bn; **no payments have been made** and the ECB says scope can be
    187   adjusted if the legislation changes. A sixth procurement (network
    188   connectivity, ceiling €355.3m) has no award notice yet. Ceilings must not
    189   be added to the €1.3bn.
    190 - **The cost of bank adaptation is contested by a factor of three to four,
    191   and that is the honest framing.** PwC *Digital Euro Cost Study*, June 2025,
    192   commissioned by the EBF/ESBG/EACB, 19 banks in nine markets on rulebook
    193   v0.8a: euro-area total **€18bn**, rising to as much as €30bn; average bank
    194   €124m (€110m is the figure excluding offline, multiple accounts and
    195   merchant acquiring). The ECB's rebuttal — "A view on recent assessments of
    196   digital euro investment costs", 10 October 2025, with Roland Berger —
    197   gives **€4bn–€5.77bn**, against the Commission's own 2023 impact assessment
    198   of €2.8bn–€5.4bn. Presenting only the industry number would be one-sided
    199   and this audience will know both.
    200 - Tender turnover thresholds: ECB tender PRO-007480 required average annual
    201   net turnover of €100m overall and €10m in comparable services.
    202 - Reported component costs: up to €55.8m for alias lookup, up to €661m for
    203   offline token development (heise, 9 July 2026). The NGI Taler expert
    204   statement names tender PRO009485 and the €56m figure.
    205   **CHECK before using a number out loud.** The slide deliberately leads with
    206   the *thresholds* (the structural point, and squarely DG FISMA's domain)
    207   rather than with the waste allegation, which reads as sour grapes if it
    208   leads. Saying plainly that we could not bid is what defuses that.
    209 
    210 ## Slide 12 — Sovereignty
    211 
    212 - "Non-discriminatory standard adoptable by any country": the formulation is
    213   from the 2022 Taler CBDC brochure. **DO NOT SAY "without patents"** — a
    214   patent application has since been filed on the offline payment design.
    215 - "What happened with e-mail can happen with payments" and the CLOUD Act
    216   point: epicenter.works open letter, 17 June 2026.
    217 - SuperStack / Open Internet Stack: €32m Horizon Europe to end-2029 under
    218   DG CONNECT, 3 consortia, 70 partners; grant agreements 101298715 (ELFA),
    219   101342483 (SuperFOSS), 101342489 (SuperAPPS), 101342989 (SuperSAFE); €3.8m
    220   passed to third parties as cascade funding. Taler sits in the platform
    221   services layer. Read off the draft deck's own slide 5 at high resolution —
    222   **CHECK against the project pages.** This is an internal-Commission
    223   coherence argument and is worth getting exactly right.
    224 
    225 ## Slide 13 — Inclusion
    226 
    227 - Children cannot open bank accounts; >5 million in the EU aged 10–18
    228   (Eurostat), from "Central Bank Accounts are Dangerous and Unnecessary",
    229   4 March 2022.
    230 - Field testing: the Freetown oral-information-management trial, 21
    231   participants, 6 local languages, only 4 with completed primary school and 6
    232   able to read a five-digit number. After a 24-hour gap, 16 completed all 8
    233   tasks with no errors and 4 completed with two tries and no help — hence
    234   "20 of 21 completed every payment task unaided". 1 failed.
    235   **Say the sample size.** It is 21 people, and overstating it would be the
    236   easiest thing in the deck to discredit.
    237 - Browser and terminal support: the comparison table at fqa.t-euro.eu scores
    238   the digital euro ✗ on browser and terminal.
    239 - COM(2023) 367 (PSR proposal) Art. 88 would forbid making strong
    240   authentication depend on possessing a smartphone — useful in discussion,
    241   but it is a proposal, not in force.
    242 
    243 ## Slide 14 — Where the software actually is
    244 
    245 This slide exists so that the rest of the deck is credible. Keep it honest.
    246 
    247 - Live in Switzerland: Taler Operations AG, Biel. Operating under the **FINMA
    248   sandbox exception** (Banking Ordinance Art. 6 para. 2) with supervision
    249   delegated to **VQF** as the self-regulatory organisation under GwG Art. 14.
    250   **DO NOT SAY "regulated by FINMA" or "audited by the Swiss regulator".**
    251   The operator's own legal notice states it is *not* supervised by FINMA and
    252   that escrowed assets are not covered by deposit insurance.
    253 - CHF 1m ceiling on total public deposits — that is the binding constraint,
    254   and stating it ourselves is what makes the rest believable.
    255   Source: NGI TALER deliverable D2.1, "Swiss Sandbox Report",
    256   Ares(2025)4305905, 28 May 2025.
    257 - Operator limits: withdraw ≤ CHF 2,500/month or 15,000/year; ≤ CHF 1,000 per
    258   transaction. These are *risk-based operator* limits, not a statutory cap on
    259   what citizens may hold — that contrast with the €3,000 ceiling is the point.
    260 - 28,500 transactions/s: Boss, "GNU Taler Scalability", BFH bachelor thesis,
    261   2022, measured on Grid'5000. The euro-area requirement of ~100,000 TPS and
    262   the ~2,000 TPS figure for Switzerland are from the same thesis, attributed
    263   to Giesecke+Devrient. **DO NOT SAY "100,000 TPS capability"** — that is the
    264   requirement, not a measured result, and it appears as a capability claim in
    265   some of our own marketing.
    266 - Hungary: MagNet Bank is a consortium partner and is in internal alpha. One
    267   internal deck says Q2 2027. The slide says "2027 at the earliest", which is
    268   the defensible form. **DO NOT SAY Hungary is live or imminent.**
    269 - Fully offline (both sides) is unsolved. What works is an offline *merchant*
    270   with an online wallet, via one-time passcodes (Huang, Benoist, Grothoff &
    271   Marchano, SUERF Policy Brief 622, June 2023).
    272 - Direct debit / pull payments: structurally impossible for a bearer design —
    273   if the payer holds the value, nothing can be pulled from them. Must be
    274   emulated with a standing instruction in the wallet. Roughly 75% of
    275   euro-area recurring payments are direct debit, so expect this question.
    276 - No user or merchant numbers exist anywhere in our material. **Do not invent
    277   one.** The TOPS merchant map is JavaScript-populated and served empty.
    278 
    279 ## Slide 15 — The objections, and the answers
    280 
    281 This slide exists because DG FISMA will already have read these. The three
    282 quotes are real and should be attributed precisely:
    283 
    284 - **ECB:** "Digital euro — Privacy options", presentation to the Eurogroup,
    285   ECB-PUBLIC, 4 April 2022, slide 4: *"User anonymity is not a desirable
    286   feature, as this would make it impossible to control the amount in
    287   circulation and to prevent money laundering."* Earlier in the same
    288   register: Report on a digital euro, October 2020, §5.1.2 — *"Anonymity may
    289   have to be ruled out"*.
    290 - **BIS:** Annual Economic Report 2021, Chapter III: a token-based CBDC with
    291   full anonymity *"could facilitate illegal activity, and is therefore
    292   unlikely to serve the public interest"*. Note the same chapter concedes
    293   that *"preventing the erosion of privacy warrants a cautious approach to
    294   digital identity"*.
    295 - **Riksbank:** Armelius, Claussen & Hull, "On the possibility of a cash-like
    296   CBDC", staff memo, February 2021: token designs *"appear not to have a
    297   greater capacity"* than account-based ones, and the perception that they do
    298   is *"misguided"*. The opening is that the memo argues a ledger defeats
    299   privacy **by definition** while never engaging a blind-signature design —
    300   it contains no mention of Chaum, blind signatures or Taler. Say that
    301   carefully and without sneering; the authors are serious people.
    302 
    303 Also worth knowing if it comes up: Fabio Panetta told ECON on 14 April 2021
    304 that *"the identity of users could be kept separate from payment data,
    305 allowing only financial intelligence units to obtain this information"* —
    306 which is closer to our model than the ECB's later positions.
    307 
    308 One useful negative: Bindseil & Pantelopoulos, "Towards the holy grail of
    309 cross-border payments", ECB Working Paper No 2693, August 2022, evaluates six
    310 candidate architectures and mentions privacy once, as a drawback bullet on
    311 BigTech stablecoins. Blind signatures, Chaum and anonymity appear nowhere.
    312 Use it only if the conversation turns to cross-border.
    313 
    314 ## Slides 16–18 — The asks
    315 
    316 The four text asks and the pilot ask are ours; items 1 and 3 overlap
    317 deliberately with demands 1 and 3 of the epicenter.works letter, so there is
    318 already a civil-society coalition behind them.
    319 
    320 **Judgement call flagged for you:** cryptographic agility was cut from the
    321 ask slide, per the steer that post-quantum work is ready in theory but not in
    322 implementation. There is no PQC claim anywhere in the deck. If you want it
    323 back, the honest framing is "require that the design be able to replace its
    324 primitives", not "require post-quantum readiness".
    325 
    326 ---
    327 
    328 ## Q&A preparation — the questions that will actually come
    329 
    330 **"Is Taler post-quantum?"**
    331 No, and neither is anything else in production. NGI TALER deliverable D5.3
    332 (Lange & Levin, 28 November 2024) states plainly that Taler's protocols use
    333 only factoring- and discrete-log-based public-key cryptography and are
    334 susceptible to quantum attack. What exists is cipher-agility in the protocol
    335 (RSA and Clause Blind Schnorr are both supported) and a completed design
    336 study. Outstanding: roughly 18–24 months and ~€750k. Note also that
    337 Chaum-style blind signatures are one round trip while the best lattice-based
    338 blind signature proposals need two, so this is not a drop-in substitution.
    339 **Do not let "quantum-proof" marketing from taler-ops.ch or paivana.ai be
    340 attributed to the project** — it contradicts our own published deliverable.
    341 
    342 **"Have you put this to the ECB or the Commission formally?"**
    343 Honest answer: not through the formal channels. There is no Taler submission
    344 on record in the Commission's feedback on COM(2023) 369, Taler is not in the
    345 ECB's Rulebook Development Group as of September 2026, and no Taler
    346 representative has appeared before ECON. The engagement that exists is
    347 academic publication, a 2020 EP written question and our published reply, the
    348 CNIL-organised CPDP panel in May 2026, and the co-signed open letter. This
    349 asymmetry is worth naming before someone else does — and it is an argument
    350 for the meeting, not against it.
    351 
    352 **"Why didn't you bid?"**
    353 The turnover thresholds. Say it plainly and without grievance.
    354 
    355 **"Isn't this just a vendor pitch?"**
    356 The asks are deliberately architecture-neutral and none of them awards
    357 anything to us. Ask 2 explicitly tells the legislator *not* to put the
    358 token choice in the Regulation.
    359 
    360 **Paivana:** the draft deck leaned on it. It is not an NGI TALER partner, it
    361 is not mentioned on taler.net, and its public claims ("quantum-proof",
    362 "audited by Swiss Regulator", "~100,000 TPS", "150,000 users", a "$3–5T"
    363 market) are variously unsourced or contradicted by the project's own
    364 documents. It is deliberately absent from this deck. If agentic payments come
    365 up, the defensible points are that Taler's merchant API already returns HTTP
    366 402 normatively, and that the 402 standardisation space is live and currently
    367 dominated by non-European actors (Nottingham's IETF draft of August 2026; the
    368 x402 Foundation under the Linux Foundation since July 2026 with Google,
    369 Visa, Mastercard, Stripe and Cloudflare as premier members). **Do not quote a
    370 market-size figure** — no independent authority has sized it.
    371 
    372 ---
    373 
    374 ## Build
    375 
    376 `make` (two pdflatex passes; the second is required for the title-page and
    377 header wedge, which use TikZ `remember picture`).
    378 
    379 Style is `taler-macros.tex` as used by 2026-pqc / 2026-rbi / 2026-dielinke.
    380 `\SUB` appears in the footer of every slide and must fit on one line.
    381 
    382 ---
    383 
    384 # Corrections applied October 2026 (after the deck was first drafted)
    385 
    386 - **"Live in Switzerland in regulated CHF, under the FINMA sandbox regime"**
    387   → **"Live in Switzerland in CHF under the FINMA sandbox exemption — not
    388   FINMA-supervised; AML through a recognised SRO".**  The old wording
    389   contradicted the "do not say" note already in this file.  The operator's own
    390   legal notice reads: *"Taler Operations is not supervised by the Swiss
    391   Financial Market Supervisory Authority (FINMA)."*  FINMA confirmed in
    392   December 2022 that the business model falls *outside* licensing under BankV
    393   Art. 6 ¶2 — the opposite of a clearance.  SRO (VQF) membership since
    394   7 March 2024.
    395 - **"v1.5"** → **v1.6**, which is the current release.
    396 - **"28,500 transactions/s measured"** → **"measured at reduced key sizes"**.
    397   The Grid'5000 experiments (Boss & Grothoff, BFH 2022) ran 1024-bit RSA; the
    398   thesis says production would want ≥2048 and argues the gap is recoverable by
    399   switching Libgcrypt→OpenSSL, but that is an argument, not a measurement.  If
    400   pressed on production key sizes, the honest answer is unverified.
    401 - **"Hungary 2027 at the earliest"** → **"Hungary in internal alpha, with no
    402   launch date announced"**.  Our own decks carry launch dates from Q3'2025 to
    403   Q2'2027; Magnet Bank has published none, and its project page gives no
    404   timeline.  Note the EU grant period ends 30 November 2026.
    405 - Layout: on the "Asymmetric privacy answers AML" slide the two closing
    406   bullets were being typeset inside the right-hand column, so they read as a
    407   continuation of the "Payee" list.  They are now a full-width paragraph.
    408 
    409 See NOTES-alt.md for the full sourcing behind these, and for the further
    410 "do not say" items that came out of the same round of checking.