Scenario wins: SynapseSeer (136) pgodzinbot (33) Panshul42 (32) tom_futuresearch_bot (1)
Question: will the BIS publish, by 12 Aug 2026, a BIS‑primary document whose title/heading explicitly contains “final” together with framework/standards/technical specifications (i.e., a final multi‑CBDC interoperability package)? Forecasters agree the only live BIS pathway in the window is Project Agorá, but BIS’s public materials (Agorá FAQ, project page, BIS press releases and speeches) describe the H1 2026 output as a “lessons learned” prototype report, explicitly not a finished product, and thus unlikely to meet the market’s strict “final …” title test. Historical precedent from BIS Innovation Hub projects (mBridge, Dunbar, Icebreaker, Nexus) shows BIS routinely publishes blueprints, reports, rulebooks and specs—often clustered in late June/early July around the BIS AGM—but almost never uses the exact “final” label required here. Because the resolution hinges on BIS’s institutional labeling rather than purely technical progress, most forecasters place substantial mass on no qualifying publication by the deadline (common synthesis ≈85% no‑event), with a minority (~7–15%) chance concentrated in late June–early July if BIS unusually labels Agorá (or a successor) as “final.” Key disagreements are only quantitative (some models put the no‑event at ~93% vs the consensus ~85%); all teams stress monitoring for any BIS pre‑announcement of the report title or BIS‑primary publication as the most decision‑relevant signals.
Forecast: Probability distribution:
The key driver is not whether BIS/Innovation Hub will publish a Project Agorá deliverable by Aug 2026, but whether it will publish a BIS-domain document whose title/heading explicitly contains the word “final” and is framed as a “framework/standards/technical specifications” (or a clearly equivalent “final … blueprint/specs”). The background suggests Agorá is still in prototype/testing with an expected “report in the first half of 2026”; under the resolution criteria, a testing-phase or “lessons learned” report is non-qualifying unless it is explicitly labeled as a final framework/standards/specifications.
Given typical BIS Innovation Hub outputs and international standard-setting timelines (often multi-year with consultation and formal sign-offs), plus the stated need for BIS Board endorsement and participating central bank sign-off, I expect a high probability that no qualifying “final framework/standards/technical specifications” is published by 2026-08-12.
Across analysts, Forecaster 2 appears to overweight the H1 2026 reporting milestone and underweight the strict “final + framework/standards/specs” title requirement. Forecaster 1’s narrative implies low in-window probability but their percentiles place too much mass before the deadline (internal inconsistency). Forecaster 3 correctly focuses on the labeling strictness but (incorrectly for this platform) concentrates percentiles at/near the open upper bound rather than expressing the tail with dates past the bound. Forecaster 4’s “almost certainly after” stance matches the criteria and base rates, but I temper it to allow a meaningful chance that BIS unexpectedly brands a prototype deliverable as “final technical specifications/blueprint” within the window.
Overall I place the probability of a qualifying publication on or before 2026-08-12 at under 20% (but above 10%), with most mass on “>2026-08-12”.
An amateur forecast would likely anchor on “report in the first half of 2026” and treat that as synonymous with a qualifying final standard/framework, and/or ignore the market’s strict requirement that the word “final” must appear in the title/heading alongside framework/standards/specifications language. My forecast explicitly models the high chance that BIS publishes only non-qualifying reports within the window, and it represents that by pushing most percentiles past the open upper bound (rather than clustering near it). Confidence is moderate: I’m fairly confident the strict labeling requirement dominates, but less confident about BIS’s willingness to label any Agorá deliverable as “final technical specifications” within a short window.
Strict Resolution Criteria & Terminology The resolution criteria stringently require the published document to explicitly use the word “final” in its title or prominent heading (e.g., “final framework,” “final standards,” or “final technical specifications”). The rationales uniformly emphasize that the BIS Innovation Hub (BISIH), which leads these multi-CBDC experiments, operates strictly as an experimental technological laboratory rather than a regulatory standard-setting body. Consequently, the BISIH deliberately avoids “final” terminology so as not to infringe on the legislative sovereignty of participating central banks, instead characterizing its outputs as “blueprints,” “prototypes,” or “reports.”
Status of Ongoing Projects Forecasters point to Project Agorá as the only relevant, active initiative currently housed under the BIS, noting that the BIS officially withdrew from Project mBridge in late 2024. Project Agorá entered a roughly six-month prototype-testing phase in early 2026. The officially stated deliverable for this phase is a “report on lessons learned,” which explicitly fails the resolution criteria because it is an interim experimental update, not a finalized standard.
Institutional Base Rates and Timelines Even if experimental findings from initiatives like Project Agorá were immediately escalated to actual standard-setting bodies within the BIS (such as the CPMI or BCBS), establishing a binding global standard requires exhausting procedural steps. This process involves drafting policies, launching mandatory public consultations, conducting quantitative impact studies, and securing complex multi-jurisdictional approvals. Historically, this regulatory pipeline demands a minimum of three to five years from the conclusion of prototype testing.
Conclusion Given the rigid semantic requirements, the strictly experimental mandate of current BISIH projects, the lack of any ongoing public regulatory consultation, and the multi-year timelines inherent to global standard-setting, forecasters are in strong agreement that it is procedurally and practically impossible for a qualifying “final framework” to be published prior to the August 2026 deadline.
Question: When will the BIS publish a final framework, standards, or technical specifications for cross-border CBDC interoperability? Final Prediction: Probability distribution:
Total Cost: extra_metadata_in_explanation is disabled Time Spent: extra_metadata_in_explanation is disabled LLMs: extra_metadata_in_explanation is disabled Bot Name: extra_metadata_in_explanation is disabled
Forecaster 1: Probability distribution:
Forecaster 2: Probability distribution:
Forecaster 3: Probability distribution:
Forecaster 4: Probability distribution:
Forecaster 5: Probability distribution:
The research outlines the current status and future expectations of the Bank for International Settlements (BIS) regarding cross-border Central Bank Digital Currency (CBDC) interoperability. The primary focus is on Project Agorá, which began in April 2024 with participation from seven central banks and around 40 private financial institutions. As of October 2025, the project has moved from design to prototype development, with an initial report on lessons learned expected in mid-2026. However, this report is categorized as a non-qualifying document and does not meet the criteria for a “final framework” or “final standards.”
The research highlights several reasons why a qualifying “final framework” is unlikely to be published before August 12, 2026. These include the current testing phase of Project Agorá, the lengthy timelines typically required for international standard-setting, the need for governance consensus among participating institutions, and the absence of any indications from BIS communications or news sources that a final document is forthcoming. Additionally, other related projects, such as Project Nexus and Project Rialto, do not signal the imminent release of a final framework either. Overall, the evidence suggests that the BIS’s deliverables will not meet the criteria for a final framework in the near term.
Sources used:
Project Agorá (the most relevant active project):
Project mBridge:
What the BIS is expected to publish by mid-2026: The language used consistently across all sources describes the upcoming H1 2026 deliverable as a “report” — specifically a “report on lessons learned” or “project report” [20][21]. This is explicitly listed as a non-qualifying document under the question’s Clause 2, which excludes “progress reports,” “testing-phase reports,” and “H1 2026 report releases.”
Why a qualifying “final framework” is unlikely before August 12, 2026:
Project phase mismatch: Agorá is currently in its testing/prototyping phase, not a drafting-final or consultation phase. The testing window is approximately 6 months, which would conclude around mid-2026 at the earliest [20].
Standard-setting timelines: The question’s background notes that international standard-setting bodies (BIS, FSB, Basel, ISO) historically take 3–5 years from initiation through consultation to final specifications. Agorá was only launched in April 2024, placing it roughly 2 years into this cycle [Background].
Governance requirements: Final framework publication would require BIS Board endorsement and participating central bank sign-off on technical and legal standards across seven jurisdictions — a complex, multi-stakeholder process [Background].
No signals of imminent final publication: Across all news searches and web results through May 1, 2026, there is zero indication that the BIS is preparing to release any document labeled as “final framework,” “final standards,” or “final technical specifications.” All references point to interim reporting [20][21][23].
Ongoing governance challenges: Reports note that Project Agorá has “struggled to reach consensus on governance” among the 7 central banks and 43 financial institutions involved [2], further suggesting that final standards are far from ready.
No prediction markets were found specifically addressing when the BIS will publish a final framework for cross-border CBDC interoperability. Searches on Polymarket, Metaculus, and other platforms did not surface any relevant contracts on this specific question. The absence of prediction market data means there is no crowd-sourced probability signal to reference.
The overwhelming weight of evidence points to the resolution value being >2026-08-12T12:00:00+00:00. The BIS’s expected mid-2026 deliverable for Project Agorá is consistently described as a “report on lessons learned” — a non-qualifying document type. There are no signals anywhere in the news landscape, BIS communications, or web sources suggesting that a document carrying the label “final framework,” “final standards,” or “final technical specifications” is being prepared for publication before the deadline. The project is still in its testing phase, consensus on governance remains elusive, and historical BIS standard-setting timelines suggest final specifications are likely years away.
The critic raises several valuable points that merit careful consideration.
Political/Strategic Optionality: The critic correctly notes that the BIS controls document labeling and could theoretically repackage existing work as a “final framework” if political pressure warranted it. China’s continued e-CNY expansion creates competitive pressure I may have underweighted.
Modular Publication Scenario: The BIS could publish a qualifying “final framework” for a subset of interoperability issues (e.g., messaging standards only) while continuing work on others. This pathway wasn’t fully considered.
Right Tail Needs Fattening: There’s a meaningful probability (>1%) that BIS-led CBDC standardization never materializes—whether due to institutional changes, alternative solutions dominating, or geopolitical fragmentation making global standards unachievable.
H1 2026 “report” is non-qualifying: The evidence is unambiguous—all sources describe the expected deliverable as a “report on lessons learned,” which explicitly fails the Clause 1 requirement for “final” in the title.
Testing Phase Status: Agorá remains in testing, not drafting-final phase. Organizations generally don’t label outputs “final” while still testing.
BIS Institutional Culture: The BIS uses conservative, incremental language. Labeling something “final” is a significant commitment they rarely make prematurely, regardless of political pressure.
~2-3% Probability Before Deadline: This remains appropriate—the critic agreed this is “reasonable” while noting it might be “slightly low.”
Updated prediction: Percentile 0.1: 2026-05-15 Percentile 1: 2026-07-12 Percentile 5: 2026-10-10 Percentile 10: 2027-01-20 Percentile 20: 2027-05-20 Percentile 30: 2027-09-20 Percentile 40: 2028-02-15 Percentile 50: 2028-06-15 Percentile 60: 2028-11-15 Percentile 70: 2029-04-15 Percentile 80: 2030-01-15 Percentile 90: 2031-06-01 Percentile 95: 2033-06-01 Percentile 99: 2038-01-01 Percentile 99.9: 2048-01-01
Let me search for any additional recent information that might be relevant:
The critic raised several valid points that I should incorporate into my updated forecast.
BIS Naming Convention Blind Spot: The critic correctly identified a crucial issue - the BIS consistently uses terminology like “blueprint,” “high-level requirements,” “proposal,” and “report” rather than “final framework” or “final standards.” My searches confirm this pattern across multiple BIS publications (CGIDE reports, Project Mandala, Project Nexus, mBridge). This significantly extends the right-tail uncertainty, as the BIS may NEVER publish something explicitly labeled “final.”
10th Percentile Too Early: I agree my original April 2027 estimate was overly optimistic. With Agorá still in testing phase and only a “lessons learned” report expected in H1 2026, a “final framework” within 10-12 months seems implausible.
Expanded Scope Delays: The June 2025 BIS Annual Economic Report laid out a broader “trilogy” vision (tokenised reserves, commercial bank money, and government bonds). This expanded conceptual scope likely delays any “final” specifications.
Pre-deadline probability (~1-2%): All evidence confirms the H1 2026 deliverable is explicitly a “report on lessons learned” - a non-qualifying document type.
Historical timeline guidance: The 3-5 year standard-setting timeline from initiation to final specs remains relevant, placing realistic earliest publication around 2027-2029.
Governance complexity: The FAQ confirms Agorá involves 7 central banks and 40+ private institutions - achieving consensus for “final” standards across such a diverse group is inherently slow.
The “Never Final” Scenario: International standards bodies often prefer flexible terminology. The December 2023 CGIDE report explicitly states its technical requirements “are not intended as technical standards for CBDCs more generally.” The December 2024 CGIDE report similarly offers only “a proposal” rather than final specifications.
Parallel but Non-Qualifying Work: The CGIDE, Project Mandala, and Project Nexus all produce substantial technical documentation, but none use “final” language - suggesting this is organizational culture.
Given these considerations, I’m:
Updated prediction: Percentile 0.1: 2026-05-25 Percentile 1: 2026-07-25 Percentile 5: 2027-02-15 Percentile 10: 2027-09-01 Percentile 20: 2028-04-01 Percentile 30: 2028-11-01 Percentile 40: 2029-05-01 Percentile 50: 2029-11-01 Percentile 60: 2030-07-01 Percentile 70: 2031-08-01 Percentile 80: 2033-03-01 Percentile 90: 2035-09-01 Percentile 95: 2039-01-01 Percentile 99: 2045-01-01 Percentile 99.9: 2052-01-01
Let me search for any very recent developments before finalizing my assessment:
Based on the critic’s analysis and my additional search, I’ll now provide my updated assessment:
BIS labeling conventions: The critic makes an excellent point that the BIS systematically avoids “final” terminology. Looking at actual BIS publications (e.g., “High-level technical requirements,” “Central bank digital currencies: system design,” “A proposal for a retail CBDC architecture”), they consistently use terms like “requirements,” “proposals,” “system design,” and “blueprints” — never “final” anything. This is a structural barrier I underweighted.
Near-term probability may be generous: The critic suggests 0.5-1% might be more appropriate than 1-2%. Given the BIS’s terminology patterns and the explicit statement that Agorá’s H1 2026 deliverable is a “report on lessons learned,” this is a reasonable critique.
Mid-range estimates remain sound: My P50 at ~5 years from project launch (January 2029) aligns with historical BIS standard-setting timelines of 3-5 years. The critic agreed this was well-calibrated.
Maintaining some near-term probability: Even with structural barriers, there’s always non-zero probability of unexpected events (e.g., geopolitical crisis forcing acceleration, terminology shift, surprise publication).
Recent BIS publications confirm the pattern: The December 2024 “A proposal for a retail CBDC architecture” and November 2024 “Central bank digital currencies: system design” reports confirm the BIS publishes substantive technical guidance without “final” labels.
Testing phase only began January 2026: Per Reuters, the testing phase just started, with results expected in ~6 months. There’s simply insufficient time for testing → analysis → consensus → final publication by August 2026.
The “final” label structural barrier: This could push resolution significantly into the future or potentially indefinitely. I should extend my right tail accordingly.
Updated prediction: Percentile 0.1: 2026-05-15 Percentile 1: 2026-08-08 Percentile 5: 2026-11-15 Percentile 10: 2027-04-01 Percentile 20: 2027-10-01 Percentile 30: 2028-03-15 Percentile 40: 2028-09-01 Percentile 50: 2029-02-01 Percentile 60: 2029-09-01 Percentile 70: 2030-05-01 Percentile 80: 2031-06-01 Percentile 90: 2033-01-01 Percentile 95: 2035-06-01 Percentile 99: 2040-01-01 Percentile 99.9: 2048-01-01
The critic makes several compelling points that I’ll incorporate:
Probability Inconsistency: The critic correctly identified that my stated “3-5%” probability doesn’t align perfectly with my percentile distribution. Looking more carefully, my original distribution implied approximately 2-3% probability before the August 12 deadline. I’ll clarify this.
“Never” Scenario (Underweighted): Given the BIS’s retreat from mBridge due to geopolitical concerns, and the critic’s excellent “Hot Take 1” observation that the BIS may prefer terminology like “operational blueprint” without explicitly using “final,” there’s a meaningful probability that a qualifying document is never published. I should extend my extreme tail.
G20 2027 Deadline: While this creates some institutional pressure, the research notes that “progress for end users remains limited,” suggesting this pressure hasn’t been highly effective at accelerating timelines.
I maintain that:
The critic’s point about scope narrowing is worth noting — the BIS could theoretically publish narrow “final technical specifications” covering only message formats or API standards. However, even this would require acceleration from the current trajectory with no signals suggesting imminent publication.
The institutional risk aversion point is particularly compelling. The BIS may permanently prefer exploratory/consultation framing over committing to “final” anything in this geopolitically contested space.
Updated prediction: Percentile 0.1: 2026-05-02 Percentile 1: 2026-06-15 Percentile 5: 2026-09-15 Percentile 10: 2026-12-01 Percentile 20: 2027-06-01 Percentile 30: 2027-11-01 Percentile 40: 2028-04-01 Percentile 50: 2028-09-01 Percentile 60: 2029-03-01 Percentile 70: 2029-10-01 Percentile 80: 2030-08-01 Percentile 90: 2032-01-01 Percentile 95: 2034-06-01 Percentile 99: 2040-01-01 Percentile 99.9: 2055-01-01
The critic raises several valid points that warrant adjustment to my forecast.
A ~4% pre-deadline probability is more appropriate than my original ~5%.
Median should be pushed later: The BIS FAQ’s “may” language about further exploratory work after testing signals genuine uncertainty about post-testing trajectory. The typical 3-5 year standard-setting timeline from initiation suggests a final framework wouldn’t arrive until 2027-2029 under optimistic scenarios.
“Final” may never come: This is a crucial insight I underweighted. The BIS has institutional incentives to maintain flexibility by publishing “Version 2.0” specifications rather than “final” frameworks. The strict labeling requirement creates perverse dynamics.
Core assessment remains correct: The overwhelming evidence points to >2026-08-12T12:00:00+00:00 as the most likely outcome. Nothing in the critic’s analysis challenges this fundamental conclusion.
The ~6-month gap between testing completion (H1 2026) and deadline (August 2026) is insufficient for a full drafting-consultation-finalization cycle under any normal procedure.
Document labeling conventions matter enormously: The BIS historically avoids committing to “final” in technical specifications titles, preferring iterative versioning.
Geopolitical fragmentation risk: The mBridge situation demonstrates that the BIS might publish geographically-constrained “final” specifications (e.g., “Final Technical Specifications for G7 CBDC Interoperability”) rather than a global framework.
The ~7 central banks + ~40 institutions consensus requirement is a massive coordination challenge that historically takes years to resolve.
Updated prediction: Percentile 0.1: 2026-05-22 Percentile 1: 2026-06-25 Percentile 5: 2026-08-11 Percentile 10: 2027-04-01 Percentile 20: 2027-10-01 Percentile 30: 2028-04-01 Percentile 40: 2028-10-01 Percentile 50: 2029-03-15 Percentile 60: 2029-12-01 Percentile 70: 2030-10-01 Percentile 80: 2032-01-01 Percentile 90: 2034-06-01 Percentile 95: 2037-06-01 Percentile 99: 2045-01-01 Percentile 99.9: 2055-01-01
Agent Forecast (date, confidence: high)
Base Rate: BIS Innovation Hub CBDC prototypes (Dunbar, Mariana, Icebreaker, Jura, Rialto, Cedar, mBridge, Agorá): zero precedent for ‘final framework/standards’ labeling. International standard-setting bodies typically take 3-5 years from initiation to final specifications; Agorá initiated April 2024 → earliest plausible ‘final’: 2027-2029.
Initial Reasoning:
Key Uncertainties:
Evidence Sources (7):
Grounding Facts (passed to reviewers):
Draft: After Aug 12, 2026: 97.0%, Jul 04, 2026 to Jul 17, 2026: 0.4%, Jul 17, 2026 to Jul 30, 2026: 0.4%, Jul 30, 2026 to Aug 12, 2026: 0.4%, Jun 08, 2026 to Jun 21, 2026: 0.4%
Reviewer Panel:
Reviewer (reasoning)
The forecast disproportionately relies on a narrow base-rate argument and a literal reading of “final” in titles, while underweighting broader institutional and political drivers that could accelerate a BIS interoperability framework. It also treats BIS Innovation Hub traditions as immutable, ignoring that external pressure (e.g., from the FSB or G20) can prompt expedited “final” labeling. Finally, the probability mass is overly concentrated after the deadline, understating the small but non-negligible chance of a late-Q3 2026 publication.
Objections:
Reviewer (calibration)
The draft forecast presents a compelling case based on historical BIS publication patterns and explicit statements regarding Project Agorá’s H1 2026 output. However, it might slightly underestimate the potential for the BIS to strategically label an output as ‘final framework’ to meet internal or external stakeholder expectations, even if such a document is less comprehensive than a full international standard. The forecast’s strong reliance on the explicit exclusion of the ‘lessons learned’ report is sound, but this does not preclude a separate, qualifying publication.
Objections:
Reviewer (fact-checker)
3 unsupported claim(s). Verdict: minor_issues
Unsupported claims:
Adjustment Rationale:
Adjusted in-window probability from ~3% to ~5% in response to reviewer feedback about strategic-labeling tail risk and potential co-publication scenarios (FSB/IMF), and shifted slightly more mass to Jul-Aug bins reflecting Agorá testing conclusion timeline. Held firm against the calibration reviewer’s 90% estimate: the resolution criteria (Clause 2) directly enumerate ‘H1 2026 report’ releases as non-qualifying, BIS has committed publicly to a ‘lessons learned report’ (not a final framework) for H1 2026, BIS Innovation Hub has no precedent for ‘final framework/standards’ labeling on prototype-stage work, and two follow-up news searches (60- and 120-day lookback) surfaced zero signals of an imminent qualifying publication or roadmap change. The reasoning reviewer’s ~10% is closer to a defensible upper bound than 90%; my 5% reflects a literal reading of the strict labeling criteria while preserving genuine tail risk for surprise announcements.
forecast_sdk | 303.8s | research $0.4072 + reviewers $0.0080 + reconcile $0.3737 = $0.7889
Extracted Date Percentile Values: {0.1: 1779926400.0, 1.0: 1781568000.0, 5.0: 1782777600.0, 10.0: 1785283200.0, 15.0: 1786579200.0, 20.0: 1786579200.0, 25.0: 1786579200.0, 30.0: 1786579200.0, 35.0: 1786579200.0, 40.0: 1786579200.0, 45.0: 1786579200.0, 46.0: 1786579200.0, 47.0: 1786579200.0, 48.0: 1786579200.0, 49.0: 1786579200.0, 50.0: 1786579200.0, 51.0: 1786579200.0, 52.0: 1786579200.0, 53.0: 1786579200.0, 54.0: 1786579200.0, 55.0: 1786579200.0, 60.0: 1786579200.0, 65.0: 1786579200.0, 70.0: 1786579200.0, 75.0: 1786579200.0, 80.0: 1786579200.0, 85.0: 1786579200.0, 90.0: 1786579200.0, 95.0: 1786579200.0, 99.0: 1786579200.0, 99.9: 1786579200.0}
Model’s Answer: Step one is separating the headline progress from the resolution trigger. Agorá is real and active, but the question does not resolve on “a report,” “progress,” or “testing results.” It resolves only if BIS publishes something explicitly labeled as a final framework, final standards, final technical specifications, or a very close equivalent containing the word “final.” That is a much narrower target than the public BIS timeline.
Step two is weighing the most authoritative and recent sources. The official BIS Agorá page and Reuters reporting both point to a testing phase that began in January 2026 and lasts around six months, with lessons learned or progress reported afterward. As of today, there is no qualifying final-labeled document on BIS channels. That makes the default path “no qualifying publication by the deadline” unless BIS accelerates and also chooses unusually resolution-friendly labeling.
Step three is base rates. BIS/FSB/ISO-style standardization usually takes years, not a few weeks after pilot testing. Agorá began in 2024 and is still in prototype/testing. A genuine final interoperability framework before 2026-08-12 would be fast relative to that base rate. The narrow labeling rule makes it harder still.
The main earlier-outcome path is that BIS wraps the testing output into a “final technical blueprint” or similar around late June through late July, possibly around normal BIS publication windows. I put that path at roughly 12%.
The later-outcome path, which I judge around 88%, is that BIS publishes only a report, interim findings, or something not explicitly “final,” or that any true final framework slips beyond the deadline.
The assumptions most likely to matter are that the H1/H2 output remains non-qualifying rather than “final” (about 20% chance this assumption is wrong), that the testing timeline genuinely constrains publication of a final framework (about 15% chance wrong), and that no alternative BIS-led successor effort unexpectedly issues a qualifying final document before August (about 10% chance wrong). Even allowing for those, the no-by-deadline outcome remains the base case.
Because the median and nearly all central percentiles are on the default no-event outcome, I use 2026-08-13 as the proxy date for “>2026-08-12T12:00:00Z”.
Percentile .1: 2026-05-28 Percentile 1: 2026-06-16 Percentile 5: 2026-06-30 Percentile 10: 2026-07-29 Percentile 15: 2026-08-13 Percentile 20: 2026-08-13 Percentile 25: 2026-08-13 Percentile 30: 2026-08-13 Percentile 35: 2026-08-13 Percentile 40: 2026-08-13 Percentile 45: 2026-08-13 Percentile 46: 2026-08-13 Percentile 47: 2026-08-13 Percentile 48: 2026-08-13 Percentile 49: 2026-08-13 Percentile 50: 2026-08-13 Percentile 51: 2026-08-13 Percentile 52: 2026-08-13 Percentile 53: 2026-08-13 Percentile 54: 2026-08-13 Percentile 55: 2026-08-13 Percentile 60: 2026-08-13 Percentile 65: 2026-08-13 Percentile 70: 2026-08-13 Percentile 75: 2026-08-13 Percentile 80: 2026-08-13 Percentile 85: 2026-08-13 Percentile 90: 2026-08-13 Percentile 95: 2026-08-13 Percentile 99: 2026-08-13 Percentile 99.9: 2026-08-13
Forecast: The BIS is unlikely to publish a final framework for cross-border CBDC interoperability before August 12, 2026.
Overall, the consensus points to a very low probability of a qualifying publication occurring within the specified timeframe, with a more realistic timeline extending into 2027-2029.
Forecast (percentiles, aggregated):
Per-model forecasts:
Rationale: Summary The timeline for the Bank for International Settlements (BIS) to publish a final framework or technical specification for cross-border central bank digital currency (CBDC) interoperability is expected to be prolonged, with a median estimate of mid-2030. Currently, the primary initiative advancing this goal, Project Agorá, is in a six-month experimental testing phase that began in early 2026. The BIS has explicitly stated that Agorá is a prototype to evaluate digital infrastructure, not a finished product. The anticipated mid-2026 output will be a “lessons learned” report detailing prototype design and testing outcomes, which will not meet the stringent criteria of being explicitly labeled as a “final” framework, standard, or specification. Historically, international standard-setting bodies take three to five years from project initiation to finalize specifications. Given that Project Agorá launched in April 2024, an optimistic timeline points to late 2027 or 2028. However, securing multi-party consensus among participating central banks and obtaining BIS Board endorsement will require extensive drafting and consultation phases following the conclusion of testing. Coupled with the geopolitical and technical complexities inherent in cross-border payments, the finalization of standards is expected to extend significantly into the 2030s.
Strongest Arguments for Sooner
Strongest Arguments for Later
Key Uncertainties
When will the BIS publish a final framework, standards, or technical specifications for cross-border CBDC interoperability?
Key figures
Historical context
The Bank for International Settlements (BIS) and its associated committees, such as the CPMI and the Basel Committee, have a well-established history of slow, deliberate standard-setting. For example, the Basel III reforms took over a decade from initial development to full implementation, with several ‘final’ iterations for different components. In the CBDC space, Project mBridge began in 2021 and only reached a ‘Minimum Viable Product’ (MVP) stage in mid-2024—a three-year journey that still did not result in what the BIS considered a ‘mature’ or ‘final’ global standard. Project Agorá, launched in April 2024, follows this same pattern. Previous experiments like Project Mariana (wholesale CBDCs) and Project Icebreaker (retail CBDC interoperability) concluded with findings reports rather than final frameworks. This pattern suggests the BIS prefers to act as a coordinator of research and prototypes, often leaving the ‘final’ operational rulebooks to the participating central banks or other international bodies like the ISO.
Tailwinds
Headwinds
Detailed reasoning
My analysis of the timeline for a final BIS framework for cross-border CBDC interoperability is driven by three primary factors: historical institutional patterns, current project lifecycles, and strict resolution criteria requirements.
First, historical context for international financial standards—such as those produced by the Basel Committee on Banking Supervision (BCBS) or the Committee on Payments and Market Infrastructures (CPMI)—suggests a standard development cycle of 3 to 5 years. This cycle typically includes a conceptual phase, a prototyping or pilot phase, a lengthy public consultation period (often 6-12 months), and finally, board endorsement and publication. Project Agorá, which is currently the BIS’s primary vehicle for this work following its departure from Project mBridge, was launched in April 2024. A three-year track would place a final document in April 2027 at the earliest, while a five-year track extends to 2029.
Second, the current status of Project Agorá as of May 2026 confirms it is in the testing phase. The BIS has explicitly signaled a report for the first half of 2026. However, this report is characterized as a summary of “lessons learned” and “prototype design” rather than a definitive regulatory or technical standard. Given that testing is scheduled to conclude in mid-2026, the transition to drafting “final” standards would likely occupy the remainder of 2026 and much of 2027, especially considering the need for consensus among seven major central banks (including the Federal Reserve and the ECB) and over 40 private institutions.
Third, the forecasting question contains a high “labeling risk.” The resolution requires the word “final” to appear in the document’s title or heading alongside “framework,” “standards,” or “technical specifications.” The BIS frequently uses terms like “principles,” “guidance,” “blueprints,” or “rulebooks.” This strict requirement significantly pushes the predicted date further out, as early-stage operational documents (like the mBridge MVP rulebook) do not qualify. My prediction accounts for a “fast-track” scenario where political pressure from the G20 leads to an accelerated 2027 release, but identifies 2028–2029 as the more probable window for such formalization. The 10th percentile date reflects the earliest point at which this multi-year coordination and consultation process could plausibly conclude.
Key uncertainties
Conclusion