151 forecasts. The original words.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-003-v1 — Bank of England Synchronisation

Forecast ID / Version: PVR-003-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 4 October 2026
Cohort: Core
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

5.1 Decision Object / Control Locus / ancestry

Decision Object: Bank of England RTGS Synchronisation capability
Decision-Control Locus: primarily Bank of England-controlled, with material industry/operator and external-ledger implementation dependencies
Ancestry: Project Meridian → Meridian FX / Meridian Securities → Synchronisation Lab → planned live Synchronisation service

This is one programme lineage.

Experimental predecessors are not independent confirmations of the later live-service outcome.

5.2 Use case / jurisdiction / horizon

Use case: conditional / atomic settlement of assets on external ledgers against central-bank money in the Bank of England's RTGS service
Jurisdiction: United Kingdom
Horizon: 31 December 2028

5.3 Primary Resolution Object

> Primary Maturity Milestone: live Bank of England Synchronisation capability available for actual settlement use, beyond the non-live Synchronisation Lab.

A lab demonstration, prototype or policy statement alone does not resolve this forecast as a Hit.

5.4 Principal Scored Claim

> The Bank of England will launch a live Synchronisation capability for RTGS, enabling conditional settlement in central-bank money against assets on external ledgers, by 31 December 2028.

5.5 Observability / permitted specificity

Observability State: O3 for programme intent and target milestone; O2 for final implementation detail

The Bank has publicly:

- committed to live delivery targeted for 2028;
- launched the Synchronisation Lab in 2026;
- selected 18 organisations for the Lab;
- described real use cases including tokenised securities, FX, collateral optimisation and housing;
- placed 2027 preparations for live synchronisation on the RTGS change roadmap;
- described RT2 as technically able to support this direction.

Permitted specificity: maturity milestone only.

No official forecast is made here on:

- which Synchronisation Operator(s) will be selected;
- exact technical vendor;
- exact production architecture of each external ledger;
- exact launch month;
- exact usage scale after launch.

5.6 Call / Forecast Label

> STRONG LEAN

5.7 Strongest Alternative

> Delivery slips beyond 2028 or is materially narrowed because operator design, ecosystem readiness, regulatory/operational dependencies, RTGS settlement-hour changes or external-ledger integration prove harder than expected.

A second alternative is that synchronisation remains available only in restricted/pilot form rather than entering genuine live service by the horizon.

5.8 Load-Bearing Evidence / Warrant

The maturity case is unusually strong for a multi-year institutional programme because several distinct commitment layers are already public:

1. Explicit delivery commitment.
In May 2026 the Bank and FCA stated that the Bank is committing to launch a live Synchronisation service, targeted for 2028.

2. Active implementation pathway.
The 2026 Synchronisation Lab is not merely conceptual. Eighteen organisations are participating across house purchases, collateral optimisation, FX PvP and tokenised-securities DvP.

3. Built infrastructure base.
RT2 is already live. Synchronisation is an extension of renewed RTGS rather than an entirely new greenfield core settlement system.

4. Multi-stage experimental ancestry.
Meridian, Meridian FX and Meridian Securities have already tested the synchronisation concept across multiple transaction types.

5. Forward implementation sequencing.
The Bank's RTGS/CHAPS roadmap places 2027 work around preparations for live synchronisation and 2028+ delivery of major strategic improvements.

6. Policy consistency.
The Bank's broader wholesale-tokenisation policy explicitly seeks central-bank-money settlement for tokenised markets and treats Synchronisation as one of the core delivery mechanisms.

Taken together, this is stronger than an exploratory roadmap.

The public record reflects institutional commitment, active implementation work and an existing production RTGS base.

5.9 Material contradiction / private residual

Material unresolved variables include:

- final Synchronisation Operator model;
- final operating rules;
- technical integration standards;
- security/cyber approval;
- production onboarding;
- interaction with extended RTGS/CHAPS settlement hours;
- final scope at launch;
- possible sequencing delays across 2027–2028.

These are meaningful execution risks.

They do not currently make the delay alternative comparably supported.

5.10 Falsifier / Next Observable

Falsifiers

The Strong Lean materially weakens if the Bank:

- formally moves the live-service target beyond 2028;
- abandons the Synchronisation service;
- replaces it with a materially different approach that does not provide the defined capability;
- discloses a blocking legal, technical or operational dependency inconsistent with 2028 delivery.

Next observables

High-value prospective updates include:

- 2027 wholesale-experimentation summary;
- named Synchronisation Operator pathway;
- production design / onboarding material;
- formal 2027 RTGS implementation milestones;
- settlement-hours decisions affecting operating capability;
- live-service rulebooks or production documentation.

Any material new evidence is classified under v0.4 U1/U2/U3/U4 update semantics.

5.11 Resolution Rule

Hit

By 31 December 2028, the Bank of England makes a live Synchronisation capability available for real settlement use in RTGS, permitting conditional central-bank-money settlement against assets or transactions on external ledgers.

Miss

The horizon expires without such a live capability, and the target remains materially intact.

Target Invalidated

Only if an externally demonstrated change materially eliminates or transforms the originally frozen decision object so that ordinary Hit/Miss is no longer valid.

A mere delay is not Target Invalidated.

5.12 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local, primarily direct Bank of England sources
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

No optional v0.4 specialist module was necessary.

The Lean Core was sufficient.

5.13 Lead-time state

Initial Call: Strong Lean — 4 October 2026
First Lean-or-better at scored specificity: 4 October 2026
Last-pre-resolution call: currently v1
Resolution: open

Primary lead time will be measured prospectively from 4 October 2026 to the qualifying resolution event.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-004-v1 — HKMA EnsembleTx 24/7 tokenised-central-bank-money settlement

Forecast ID / Version: PVR-004-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 4 October 2026
Cohort: Core
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

12.1 Decision Object / Control Locus / ancestry

Decision Object: HKMA EnsembleTx pilot environment / next-stage tokenised settlement capability
Decision-Control Locus: primarily HKMA-controlled infrastructure programme, with material bank/industry implementation dependencies
Ancestry: Project Ensemble Sandbox → EnsembleTx real-value pilot → prospective 24/7 tokenised-central-bank-money settlement capability

This is one programme lineage.

Earlier Sandbox experiments and current real-value pilot activity are predecessor states, not independent confirmations.

12.2 Use case / jurisdiction / horizon

Use case: settlement of tokenised deposits / tokenised-asset transactions using tokenised central-bank money on a 24/7 basis
Jurisdiction: Hong Kong
Horizon: 31 December 2027

12.3 Primary Resolution Object

> Primary Maturity Milestone: EnsembleTx, or its direct successor within Project Ensemble, supports real settlement using tokenised central-bank money on a 24/7 basis.

A policy statement, prototype or ordinary RTGS-backed settlement using tokenised commercial-bank deposits does not by itself resolve this forecast as a Hit.

12.4 Principal Scored Claim

> By 31 December 2027, HKMA will enable within EnsembleTx or its direct Project Ensemble successor a live/pilot-capable 24/7 settlement function using tokenised central-bank money for tokenised financial transactions.

12.5 Observability / permitted specificity

Observability State: O3 for programme direction and intended capability; O1–O2 for exact technical implementation

The public record establishes that:

- EnsembleTx is already the real-value pilot phase of Project Ensemble;
- it supports real-value tokenised HKD deposits and digital-asset transactions in a controlled environment;
- current settlement relies on the HKD RTGS framework;
- HKMA repeatedly states that the pilot environment will be progressively upgraded to support tokenised-central-bank-money settlement on a 24/7 basis;
- HKMA leadership describes round-the-clock settlement in tokenised central-bank money as the programme's next goal;
- HKMA/HKFMI has dedicated work capacity around next-generation tokenised-central-bank-money initiatives.

Permitted specificity: maturity/capability only.

No official forecast is made here on:

- exact wholesale-CBDC architecture;
- exact ledger/platform;
- whether the central-bank-money representation is branded e-HKD or another instrument;
- exact bank participants at resolution;
- exact implementation date within the horizon;
- full production scale.

12.6 Call / Forecast Label

> STRONG LEAN

12.7 Strongest Alternative

> EnsembleTx remains a real-value pilot based mainly on tokenised commercial-bank deposits and conventional/RTGS-backed settlement while the 24/7 tokenised-central-bank-money upgrade slips beyond 2027 or remains experimental rather than operationally usable.

Material drivers of that alternative include:

- central-bank-money design still being finalized;
- operational resilience / cyber requirements;
- interoperability and bank-integration complexity;
- legal/governance questions;
- difficulty moving from controlled pilot settlement to round-the-clock operation.

12.8 Load-Bearing Evidence / Warrant

The maturity case is strong because the 24/7 tokenised-central-bank-money capability is not merely an analyst inference.

1. Existing real-value pilot. HKMA launched EnsembleTx in November 2025 as the pilot phase of Project Ensemble, enabling participating banks and industry players to conduct real-value tokenised HKD-deposit and digital-asset transactions in a controlled environment.

2. Explicit next-stage objective. HKMA's 2025 Annual Report states that EnsembleTx will operate throughout 2026 and that the pilot environment will be progressively enhanced, including support for settlement in tokenised central-bank money on a 24/7 basis.

3. Repeated institutional commitment. A May 2026 Legislative Council briefing repeats that the EnsembleTx environment will be progressively upgraded and enhanced to support 24/7 settlement of tokenised deposits in tokenised central-bank money.

4. Leadership-level statement. The HKMA Chief Executive's annual statement describes the current real-value RTGS-linked pilot and identifies the next goal as round-the-clock settlement in tokenised central-bank money.

5. Organizational implementation capacity. HKFMI/HKMA has explicitly recruited for next-generation tokenised-central-bank-money work, including project delivery, system integration and blockchain/payment-system responsibilities.

6. Existing ecosystem and infrastructure. Project Ensemble already has a large tokenised-deposit bank community, real-value transaction experience, prior end-to-end tokenisation use cases, an existing RTGS settlement base, and dedicated ongoing pilot operation.

The target therefore requires an infrastructure upgrade rather than creation of the entire ecosystem from zero.

12.9 Material contradiction / private residual

Important uncertainties remain:

- exact tokenised-central-bank-money instrument;
- technical architecture;
- operating model;
- bank integration;
- liquidity-management design;
- resilience/cyber controls;
- legal treatment;
- whether 24/7 operation first appears as controlled pilot capability or broad production service.

The public evidence does not establish a hard end-2026 deadline.

That is why this forecast uses a 31 December 2027 horizon rather than converting the “2026 and beyond” roadmap into an unsupported 2026 deadline.

The delay alternative is real, but it is not currently comparably supported.

12.10 Falsifier / Next Observable

Falsifiers

The Strong Lean materially weakens if HKMA:

- formally removes tokenised-central-bank-money settlement from Project Ensemble;
- replaces the 24/7 objective with a materially different settlement model;
- pushes the capability beyond 2027;
- discloses a blocking operational, legal or technical dependency inconsistent with the horizon;
- winds down EnsembleTx without a direct successor carrying the same capability.

Next observables

High-value updates include:

- explicit technical architecture for tokenised central-bank money;
- 24/7 pilot/production testing announcement;
- participant onboarding for the upgraded settlement leg;
- direct linkage to an e-HKD / wholesale-CBDC mechanism;
- rulebook or operating-model publication;
- announcement of first transactions using tokenised central-bank money.

12.11 Resolution Rule

Hit

By 31 December 2027, HKMA enables within EnsembleTx or its direct successor a real usable pilot/live function supporting 24/7 settlement of tokenised financial transactions using tokenised central-bank money.

Miss

The horizon expires without that capability while the underlying Project Ensemble target remains materially intact.

Target Invalidated

Only if an externally demonstrated change eliminates or materially transforms the original decision object such that ordinary Hit/Miss is no longer meaningful.

A simple delay is a Miss, not Target Invalidated.

12.12 Research Burden Signature

Evidence trajectory: narrow/direct + ordinary multi-source, dominated by primary HKMA material
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

The Lean Core was sufficient.

12.13 Lead-time state

Initial Call: Strong Lean — 4 October 2026
First Lean-or-better at scored specificity: 4 October 2026
Last-pre-resolution call: currently v1
Resolution: open

Primary lead time will be measured prospectively from 4 October 2026 to the qualifying resolution event.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-005-v1 — DTCC Collateral AppChain production go-live

Forecast ID / Version: PVR-005-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 4 October 2026
Cohort: Core
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

19.1 Forecast object

Decision Object: DTCC Collateral AppChain production launch
Decision-Control Locus: primarily DTCC-controlled, with participant, integration and technology-provider dependencies
Ancestry: Great Collateral Experiment → Collateral AppChain production build → Q4 2026 production go-live
Use case: shared infrastructure for tokenised collateral mobility, valuation, eligibility, optimisation, settlement and 24/7 collateral operations
Jurisdiction: United States / global market-infrastructure service
Horizon: 31 December 2026

19.2 Primary Resolution Object

> Primary Maturity Milestone: DTCC formally launches the Collateral AppChain as a production-ready / operational service available for real institutional collateral workflows.

A demo, experiment, white paper, marketing page or limited internal test alone does not count as a Hit.

19.3 Principal Scored Claim

> DTCC will launch the Collateral AppChain as a production-ready operational service by 31 December 2026.

19.4 Observability / permitted specificity

Observability: O3 for programme direction and announced go-live window; O2 for exact launch scope / participant use.

Public evidence establishes that DTCC moved the platform from the Great Collateral Experiment toward production, publicly integrated Chainlink CRE/data standards into material orchestration and automation functions, and repeatedly stated that the AppChain is expected to go live in Q4 2026.

Permitted specificity: maturity milestone only.

No call is made on exact launch date, first participants, volumes, adoption scale, economic impact or full capability breadth at launch.

19.5 Call / Forecast Label

> STRONG LEAN

19.6 Strongest Alternative

> The AppChain misses the Q4 2026 production window and slips into 2027 because participant readiness, integration, operational controls, security, legal/compliance requirements or production hardening take longer than DTCC's published schedule.

A secondary alternative is a nominal or limited launch too restricted to satisfy the production-ready resolution rule.

19.7 Load-Bearing Warrant

1. DTCC explicitly states a Q4 2026 go-live expectation.
2. DTCC characterises the AppChain as the infrastructure carrying its collateral experiment into production, not another research exercise.
3. DTCC says the platform was built with production requirements such as scalability, reliability and integration into existing market structures.
4. Chainlink CRE and data standards are publicly specified for orchestration, automation, valuation, eligibility and post-trade workflows.
5. DTCC's product material now presents a defined infrastructure product for 24/7 collateral operations and mobility.

The main remaining uncertainty is launch execution and initial production scope, not whether DTCC intends to build the product.

19.8 Material contradiction / private residual

Unresolved variables include final production-readiness testing, participant onboarding, security/cyber approval, operating controls, exact launch scope and legal/compliance readiness.

The call is intentionally narrow: production go-live by year-end 2026. It does not forecast rapid adoption or high volume.

19.9 Falsifier / Next Observable

The call weakens materially if DTCC moves launch beyond Q4 2026, reclassifies the AppChain as continued experimentation, announces a material delay, discloses blockers inconsistent with year-end launch, or narrows the product so that no production-ready service actually launches.

Key next observables: formal launch announcement, first production participant, production collateral-movement evidence, client onboarding material or revised schedule.

19.10 Resolution Rule

Hit: by 31 December 2026 DTCC formally launches the Collateral AppChain as a production-ready or operational service for real institutional collateral workflows.
Miss: the horizon expires without such a launch while the programme remains intact.
Target Invalidated: only if an external change eliminates or materially transforms the original target. A slip into 2027 is a Miss.

19.11 Burden / lead-time state

Evidence trajectory: narrow/direct + ordinary multi-source, dominated by DTCC primary material
Deep Research: No
Specialist modules: None
Burden Category: Light
Initial Call: Strong Lean — 4 October 2026
First Lean-or-better: 4 October 2026
Resolution: open

Because the announced target is already Q4 2026, classify PVR-005 as:

> SHORT-LEAD CONTROL CASE

A future Hit cannot be presented as strong evidence that v0.4 forecasts architecture early. It can support prospective discipline and calibration. A Miss would be informative against over-trusting explicit institutional roadmaps.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-006-v1 — DTC Tokenization Service full launch

Forecast ID / Version: PVR-006-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 4 October 2026
Cohort: Core
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

25.1 Forecast object

Decision Object: DTC Tokenization Service transition from limited production trades to full service launch
Decision-Control Locus: primarily DTC/DTCC-controlled, with participant, network and operational dependencies
Ancestry: SEC No-Action Letter → service development / industry working group → July 2026 limited production trades → October 2026 service launch
Use case: tokenized representations of DTC-custodied securities with existing investor protections and multi-network interoperability
Jurisdiction: United States
Horizon: 31 October 2026

25.2 Primary Resolution Object

> Primary Maturity Milestone: DTC formally launches the Tokenization Service for ordinary participant use beyond the July 2026 limited production-trades event.

The July 15 production trades are predecessor evidence and do not resolve this forecast as a Hit.

25.3 Principal Scored Claim

> DTC will formally launch its Tokenization Service by 31 October 2026.

25.4 Observability / permitted specificity

Observability: O3 for programme maturity and announced launch month; O2 for exact initial scope and network availability.

Public evidence establishes:

- DTC received SEC no-action authorization in December 2025;
- the service was developed with a large cross-section of market participants;
- DTCC publicly scheduled limited production trades for July 2026 and full service launch for October 2026;
- those July production trades were successfully completed using tokenized DTC-custodied assets across multiple real use cases;
- after those trades, DTCC continued to describe them as a milestone paving the way for the expected October launch;
- current DTCC product material still describes multiple compatible chains as anticipated for launch later in 2026 rather than reporting a completed pre-cutoff full-service launch.

Permitted specificity: service-launch maturity only.

No call is made on exact launch day, first-launch participant count, volume, adoption, exact chain set, or economic impact.

25.5 Call / Forecast Label

> STRONG LEAN

25.6 Strongest Alternative

> DTC delays the full Tokenization Service launch beyond October 2026 despite successful July production trades, because operational onboarding, network integration, compliance controls, participant readiness or production hardening remain incomplete.

A second alternative is that DTCC declares only another restricted/limited production phase rather than the full service launch defined here.

25.7 Load-Bearing Warrant

1. Regulatory authorization already exists. The SEC No-Action Letter permits DTC to offer the defined service for eligible assets.
2. The announced launch sequence is explicit. DTCC publicly set July 2026 for limited production trades and October 2026 for service launch.
3. The July milestone succeeded. Real DTC-custodied assets were tokenized and used in production transactions including repo, securities trades, collateral and cross-chain workflows.
4. Broad industry participation exists. The development and July production programme involved a large set of major TradFi and digital-market firms.
5. DTCC continued to reaffirm the October launch after July. The successful production event was framed as setting the stage for, rather than replacing, the full service launch.

The remaining uncertainty is launch execution over a very short horizon.

25.8 Material contradiction / private residual

Unresolved variables include exact onboarding state, final production controls, chain-by-chain readiness, participant permissions, launch scope and whether all planned features arrive on day one.

These uncertainties create genuine delay risk but do not currently outweigh the explicit schedule plus successful production precursor.

25.9 Falsifier / Next Observable

The Strong Lean weakens materially if DTCC formally postpones the service, describes October as another limited phase, discloses unresolved regulatory/operational blockers, or allows October to pass without a qualifying full launch.

The primary next observable is a formal launch announcement or revised launch schedule.

25.10 Resolution Rule

Hit: by 31 October 2026, DTC formally launches the Tokenization Service for participant use beyond the July limited-production event.
Miss: October 2026 ends without that full launch while the programme remains intact.
Target Invalidated: only if an external change eliminates or materially transforms the original target. A delay into November/December is a Miss under this forecast.

25.11 Burden / lead-time state

Evidence trajectory: narrow/direct, dominated by DTCC primary material
Deep Research: No
Specialist modules: None
Burden Category: Light
Initial Call: Strong Lean — 4 October 2026
First Lean-or-better: 4 October 2026
Resolution: open

Classify PVR-006 as:

> EXTREME SHORT-LEAD CONTROL CASE

A future Hit has minimal value as evidence of early predictive skill. It mainly tests whether the method handles announced near-term milestones honestly and preserves a miss if the roadmap slips.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-007-v1 — ECB / Eurosystem Appia network architecture

Forecast ID / Version: PVR-007-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 4 October 2026
Cohort: Core
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture Selection

32.1 Decision Object / Control Locus / ancestry

Decision Object: Eurosystem long-term network-layer architecture for the Appia European tokenised wholesale-finance ecosystem
Decision-Control Locus: Eurosystem-led, with substantial market, public-sector, legal/regulatory and national-central-bank input
Ancestry: 2024 Eurosystem DLT exploratory work → 2025 Pontes/Appia dual-track strategy → 2026 Appia roadmap + Pontes launch → 2028 Appia blueprint

Pontes and Appia are one coordinated strategic lineage. Pontes is current operating infrastructure and a path-dependence input to Appia, not an independent confirmation of the eventual Appia architecture.

32.2 Use case / jurisdiction / horizon

Use case: network topology and central-bank-money architecture for integrated European tokenised wholesale financial markets
Jurisdiction: Eurosystem / European wholesale financial markets
Horizon: 31 December 2028

32.3 Primary Resolution Object

> Primary Architecture Slot: ecosystem network topology / central-bank-money settlement and interoperability layer defined by the Appia blueprint.

The forecast resolves at the family level.

It does not require the blueprint to name one vendor, one DLT protocol, or one production implementation.

32.4 Principal Scored Claim

> By 31 December 2028, the Appia blueprint will favor a federated/interoperable or hybrid European tokenised-finance architecture in which multiple DLT networks can remain connected through common standards and a Eurosystem central-bank-money core/anchor, rather than prescribing migration of the wholesale ecosystem onto one exclusive shared European ledger.

This is an architecture-family forecast.

32.5 Observability / permitted specificity

Observability State: O2 for network-architecture family; O1 for final topology; O0–O1 for exact provider/platform

Public evidence establishes:

- Appia is explicitly comparing a single shared ledger, multiple interconnected networks, and combinations of the two;
- interoperability and common standards are formal Appia building blocks;
- Pontes already connects multiple market DLT platforms to Eurosystem central-bank-money settlement;
- Pontes is intended to evolve into a core component of the Appia ecosystem;
- the Eurosystem repeatedly emphasizes competition, resilience, interoperability, strategic autonomy and avoidance of fragmentation;
- the ECB has explicitly described a model in which a Eurosystem-operated ledger is connected to privately operated DLT networks as one live architecture option.

Permitted specificity: architecture family only.

No official forecast is made on:

- one exact network topology;
- one Eurosystem ledger design;
- one DLT protocol;
- one commercial provider;
- whether reserves and financial assets ultimately sit on the same ledger;
- exact governance implementation;
- exact number of networks.

32.6 Live candidate field

Candidate A — Single shared European ledger

One common infrastructure hosts central-bank money, private money and/or financial assets, with service competition above the shared network.

Candidate B — Eurosystem core ledger + connected private DLT networks

The Eurosystem provides tokenised central-bank-money infrastructure on a core network while market DLTs remain externally connected.

Candidate C — Multiple interconnected ledgers

Multiple DLT networks continue to host assets and possibly settlement assets, linked by interoperability, standards and central-bank-money mechanisms.

Candidate D — Hybrid / combined topology

Elements of a shared utility coexist with multiple interoperable networks.

All four remain publicly live as of the freeze.

32.7 Call / Forecast Label

> LEAN

Architecture-family call

> Federated / interoperable / hybrid topology over an exclusive single-ledger topology.

The call deliberately groups Candidates B, C and D against Candidate A.

It does not claim enough observability to distinguish B vs C vs D.

32.8 Strongest Alternative

> The Appia blueprint selects a single European shared ledger as the primary long-term architecture, with central-bank money and a large share of tokenised wholesale-market activity consolidated onto one common infrastructure.

This alternative has genuine support:

- a single shared ledger could reduce fragmentation by design;
- it could simplify atomic settlement;
- it could concentrate shared standards and governance;
- ECB officials continue to present it as a serious option.

Therefore the forecast does not clear Strong Lean.

32.9 Load-Bearing Evidence / Warrant

1. Pontes creates real multi-network path dependence

Pontes is already live and is designed to bridge market DLT platforms to Eurosystem central-bank-money settlement.

The initial Pontes participant set includes multiple distinct DLT operators rather than one mandated common market ledger.

This means the Eurosystem is accumulating operational experience around coexistence with multiple market networks.

2. Appia explicitly prioritizes interoperability

The Appia roadmap contains dedicated analytical and practical work on:

- asset interoperability;
- common standards and data formats;
- movement across DLT platforms;
- cross-chain interoperability and synchronisation;
- collateral mobility across networks.

A programme built around those questions has structural compatibility with a multi-network or hybrid outcome.

3. Competition and resilience favor preserving network plurality

ECB materials repeatedly frame multiple interconnected networks as offering:

- infrastructure-level competition;
- redundancy;
- resilience.

Those are explicit Appia policy objectives.

A single shared ledger may achieve integration, but it sacrifices some of the infrastructure-level diversity that the Eurosystem says it values.

4. The Eurosystem is not treating Pontes as temporary throwaway infrastructure

ECB officials state that:

> Pontes will evolve into a core component of the Appia ecosystem.

That materially favors architectures in which a Eurosystem settlement/core component interoperates with surrounding networks rather than a clean-sheet replacement in which every market actor moves onto one new shared ledger.

5. The Eurosystem's public language already normalizes a network-of-networks vision

ECB communications describe the objective as making tokenised networks connect rather than remain siloed and describe Appia as examining central-bank-money and collateral services across different DLT networks.

That does not prove the final decision, but it provides directional evidence.

32.10 Material contradiction / private residual

The call remains only Lean because substantial uncertainty is intentionally unresolved.

Material contradictions

- The ECB explicitly describes a single unified European ledger as a serious architecture option.
- A shared ledger could maximize atomicity and reduce fragmentation more directly than cross-network interoperability.
- The Eurosystem could conclude that strategic autonomy and monetary-control requirements justify a more centralized common infrastructure.
- Appia is explicitly evidence-driven and intends to use practical work and market input before choosing.

Private / unresolved variables

- future technical performance of Pontes;
- market preference;
- legal harmonisation;
- costs of interoperability;
- cross-chain risk;
- resilience results;
- collateral-control requirements;
- geopolitical / sovereignty considerations;
- whether private networks converge voluntarily on common infrastructure.

These variables could still move the blueprint toward Candidate A.

32.11 Falsifier / Next Observable

Falsifiers

The Lean materially weakens if:

- Appia analytical work begins explicitly preferring one unified shared ledger;
- the Eurosystem announces a migration strategy away from multiple market DLTs toward a single common infrastructure;
- Pontes is repositioned as a temporary bridge that will be superseded rather than evolve into Appia;
- interoperability work is deprioritized because the Eurosystem chooses consolidation;
- consultation/contact-group evidence strongly converges on one shared-ledger topology.

Next observables

High-value prospective evidence includes:

- Appia contact-group meeting summaries;
- results from network-configuration experiments;
- interoperability / standardisation work products;
- Pontes enhancement roadmap;
- Appia updates on central-bank-money infrastructure design;
- collateral-control architecture work;
- any interim preference among single-ledger, connected-core, multi-ledger or hybrid configurations.

32.12 Resolution Rule

Hit

The 2028 Appia blueprint endorses a long-term architecture in which multiple DLT networks continue to coexist and interoperate, or a hybrid architecture preserving materially distinct networks around a Eurosystem central-bank-money/core infrastructure.

Miss

The 2028 Appia blueprint instead selects an exclusive or predominantly single European shared ledger as the primary wholesale tokenised-finance architecture, with multi-network interoperability demoted to a marginal/legacy role.

Still Open

The blueprint does not make a sufficiently discriminating network-architecture recommendation by the horizon.

Target Invalidated

Only if the Eurosystem materially abandons or transforms Appia such that the frozen architecture-selection object ceases to exist.

32.13 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local, dominated by ECB/Eurosystem primary material
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Moderate

The burden is Moderate rather than Light because the target requires genuine comparison among multiple live architecture families and explicit separation of family-level from exact-topology inference.

No specialist module was activated.

The Lean Core was sufficient because the architecture alternatives and load-bearing topology evidence are already explicit in the primary record.

32.14 Lead-time state

Initial Call: Lean — 4 October 2026
First Lean-or-better at scored specificity: 4 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 December 2028

This is not a short-lead control.

If resolved in 2028 as planned, the initial family call carries roughly two years of potential lead time.

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-009-v1 — HM Treasury DIGIT first issuance

Forecast ID / Version: PVR-009-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Wave 2 inherited target / completed later in campaign
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

198.1 Decision Object / Control Locus / ancestry

Decision Object: conversion of DIGIT from selected-platform / pre-issuance implementation into the UK's first live digitally native government bond issuance.

Decision-Control Locus: HM Treasury and UK Debt Management Office, with HSBC Orion, Joint Lead Managers, LSEG, DSS regulators, listing and settlement dependencies.

Ancestry: policy commitment → market engagement → competitive DLT procurement → HSBC Orion selection → DSS Gate 2 → HSBC/LSEG bilateral-link work → Joint Lead Manager appointment → investor engagement → first issuance.

198.2 Use case / jurisdiction / horizon

Use case: digitally native sovereign debt issuance, lifecycle management, on-chain settlement and investor access.

Jurisdiction: United Kingdom

Horizon: 31 March 2027

198.3 Primary Resolution Object

> Primary Maturity Milestone: HM Treasury completes the first live DIGIT issuance on HSBC Orion within the Digital Securities Sandbox by 31 March 2027.

198.4 Principal Scored Claim

> HM Treasury will complete the first live Digital Gilt Instrument issuance on HSBC Orion by 31 March 2027.

198.5 Observability / permitted specificity

Observability State: O3 High

Public evidence directly establishes:

- issuer;
- product design;
- platform;
- DSS status;
- infrastructure partner;
- lead-manager group;
- current issuance window.

Permitted specificity: first issuance on HSBC Orion by quarter-end.

No official forecast is made on:

- exact issue date;
- issue size;
- pricing;
- investor allocation;
- secondary-market volume;
- whether DIGIT becomes collateral-eligible immediately;
- subsequent DIGIT issuance frequency;
- permanent post-sandbox architecture.

198.6 Call / Forecast Label

> STRONG LEAN

198.7 Strongest Alternative

> The programme remains intact and procurement remains complete, but final listing, documentation, legislation, settlement integration, investor-engagement, market-condition or operational issues delay the first issuance beyond 31 March 2027.

The strongest alternative is timing slippage, not programme abandonment or provider replacement.

198.8 Load-Bearing Warrant

1. Core provider selection is complete

HSBC / HSBC Orion was selected after competitive procurement.

2. The platform has crossed the live-regulatory gate

HSBC received DSS Gate 2 approval.

Under DSS rules, Gate 2 permits live business involving real digital securities.

3. Connectivity implementation is underway

HSBC and LSEG are developing a bilateral DSD link to improve investor access.

4. The sovereign issuer has repeatedly reaffirmed the deadline

HM Treasury continues to state that the first transaction is expected by Q1 2027.

This is not an analyst-selected horizon.

5. Distribution procurement is now complete

On the freeze date, HM Treasury appointed six Joint Lead Managers:

- Barclays;
- HSBC;
- Lloyds;
- Morgan Stanley;
- NatWest;
- RBC Capital Markets.

HM Treasury states that the appointment completes the procurement process and enables investor engagement to begin.

6. Broader authorities are actively supporting the pilot

The Bank of England is supporting DIGIT through:

- DSS implementation;
- work on cash-settlement options;
- consideration of DIGIT eligibility as collateral in monetary operations.

7. Remaining uncertainty is execution-level

The programme is not free of delay risk.

But the major institutional, procurement, platform and regulatory-enablement branches are sufficiently mature that first issuance by the government's own Q1 2027 horizon is clearly favored over delay.

This supports Strong Lean.

198.9 Material contradiction / private residual

Material unresolved variables include:

- final issuance documentation;
- investor book;
- exact issue size and pricing;
- final listing approvals / mechanics;
- settlement rehearsals;
- exact cash-settlement configuration;
- market conditions;
- DSS secondary-legislation timing;
- operational readiness across the Joint Lead Managers;
- final transaction date.

These variables can shift the date without invalidating the programme.

198.10 Falsifier / Next Observable

The Strong Lean weakens materially if:

- HM Treasury revises the issuance target beyond Q1 2027;
- a material DSS / platform / listing blocker becomes public;
- investor engagement is delayed or procurement needs to be reopened;
- HSBC Orion's DIGIT readiness is materially constrained;
- required settlement / legal infrastructure is not ready by early 2027.

The Strong Lean strengthens if:

- final terms / prospectus / issuance documentation are published;
- LSE admission is formally approved;
- a dated syndication / issuance schedule is announced;
- investor bookbuilding begins;
- final settlement testing is publicly confirmed.

Any qualifying post-freeze evidence is a U1 Evidence Update.

198.11 Resolution Rule

Hit

By 31 March 2027, HM Treasury completes the first live issuance of DIGIT on HSBC Orion within the DSS.

Miss

31 March 2027 passes without qualifying issuance while the programme remains materially intact.

An issuance in April 2027 or later is a Miss under PVR-009-v1.

Still Open

Not ordinarily applicable after the fixed horizon unless authoritative evidence establishes that issuance legally / operationally occurred by 31 March but public confirmation timing is genuinely ambiguous.

Target Invalidated

Only if an external event materially eliminates or transforms the sovereign digital-gilt programme such that the original issuance object no longer exists.

198.12 Research Burden Signature

Evidence trajectory: narrow/direct primary-source path
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

198.13 Lead-time state

Initial Call: Strong Lean — 6 October 2026
First Lean-or-Better at scored specificity: 6 October 2026
Primary predictive lead-time clock: STARTED — 6 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 March 2027

No predictive lead-time credit is backdated to PVR-009's earlier Target-Detection admission.

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-010-v1 — ECB own-funds investment in tokenised securities

Forecast ID / Version: PVR-010-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 4 October 2026
Cohort: Core
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

39.1 Decision Object / Control Locus / ancestry

Decision Object: ECB own-funds tokenised-securities investment programme
Decision-Control Locus: ECB Executive Board-controlled portfolio implementation, with market issuance, operational and Pontes-settlement dependencies
Ancestry: ECB tokenised-finance strategy → Pontes production launch → 21 September 2026 own-funds investment preparation → first executed purchase

This is a distinct ECB investor-side programme object.

It is related to Pontes/Appia but must not be scored as another independent confirmation of the Appia architecture forecast.

39.2 Use case / jurisdiction / horizon

Use case: direct ECB investment of a small portion of its non-monetary-policy own-funds portfolio in eligible tokenised securities, settled in central-bank money via Pontes
Jurisdiction: Eurosystem / euro area
Horizon: 31 December 2027

39.3 Primary Resolution Object

> Primary Maturity Milestone: the ECB completes at least one actual purchase of an eligible tokenised security for its own-funds portfolio, with settlement via Pontes.

The following do not count as a Hit by themselves:

- preparatory work;
- Executive Board approval of operational details;
- publication of investment criteria;
- portfolio-system changes;
- Pontes availability;
- another institution's tokenised-security purchase.

The forecast requires an actual ECB investment transaction.

39.4 Principal Scored Claim

> By 31 December 2027, the ECB will execute at least one investment from its own-funds portfolio into an eligible tokenised security, with the transaction settled in central-bank money via Pontes.

39.5 Observability / permitted specificity

Observability State: O3 for programme intent and intended settlement mechanism; O2 for asset universe; O1 for exact timing/security

The ECB has publicly established that:

- preparatory work has begun;
- the ECB intends to invest a small portion of its own funds directly in tokenised securities;
- the purchases are intended to provide practical experience across the full investment lifecycle;
- settlement will occur in central-bank money via Pontes;
- initial eligible targets are euro-denominated securities issued by euro-area central governments, regional governments, agencies and European supranational institutions;
- final operational details and timing remain to be decided by the Executive Board after preparatory work.

Permitted specificity: first-purchase maturity milestone.

No forecast is made on:

- exact security;
- issuer;
- DLT platform;
- purchase date;
- investment size;
- number of purchases;
- subsequent portfolio allocation.

39.6 Call / Forecast Label

> LEAN

39.7 Strongest Alternative

> Preparatory work is completed or substantially advanced, but the Executive Board delays the first purchase beyond 2027 because eligible issuance, liquidity, portfolio/risk controls, operational integration or market conditions are not yet satisfactory.

A second alternative is that the programme proceeds only through observation/testing rather than an actual portfolio transaction within the horizon.

This alternative remains credible because the ECB explicitly has not yet fixed the timing.

39.8 Load-Bearing Evidence / Warrant

1. Explicit institutional intent

The ECB did not merely announce a study.

On 21 September 2026 it announced that it had launched preparatory work to invest a small portion of its own funds in tokenised securities.

That is materially stronger than an exploratory research statement.

2. Defined economic purpose

The programme is intended to give the ECB direct practical experience as an investor across:

- trade execution;
- settlement;
- systems;
- portfolio management.

Those objectives require actual transactions to be fully achieved.

3. Defined settlement infrastructure

Pontes launched on the same day and is already available to settle wholesale tokenised-asset transactions in central-bank money.

The forecast therefore does not depend on a still-hypothetical settlement platform.

4. Defined initial asset universe

The ECB has already narrowed the intended first investments to euro-denominated public-sector and European supranational securities.

That reduces scope uncertainty.

5. Existing market supply

By March 2026, the ECB stated that European issuers had already placed close to €4 billion of DLT-based fixed-income instruments since 2021, including sovereign issuance.

Pontes' initial ecosystem also includes public-sector / supranational market participants such as the European Investment Bank, KfW, NRW.BANK and Caisse des Dépôts et Consignations.

This does not guarantee a qualifying purchase opportunity, but it reduces the risk that the programme lacks any plausible eligible supply.

6. ECB portfolio precedent for bounded innovation

The ECB's own-funds portfolio already incorporates policy-driven allocation changes, including green-asset expansion and a small allocation to Paris-aligned equity ETFs beginning in 2024.

That does not prove the tokenised programme will proceed, but it supports the proposition that the own-funds portfolio can accommodate deliberately bounded experimental allocation changes.

39.9 Material contradiction / private residual

The forecast is only Lean because the most important timing variable is explicitly unresolved.

The ECB states that after preparatory work is complete, its Executive Board will determine:

- operational details;
- timing;

while considering:

- tokenised issuance development;
- the broader tokenised-finance ecosystem.

Material residuals include:

- exact risk-control treatment;
- custody/accounting implementation;
- execution arrangements;
- eligible-security liquidity;
- portfolio-limit design;
- internal operational readiness;
- suitable issuance availability;
- transaction economics.

A first purchase by end-2027 is therefore a directional forecast, not a declared ECB deadline.

39.10 Falsifier / Next Observable

Falsifiers

The Lean materially weakens if:

- the ECB explicitly postpones investments beyond 2027;
- preparatory work reveals unresolved operational/risk obstacles;
- the Executive Board decides not to proceed with actual investment;
- Pontes cannot support the required settlement workflow;
- eligible public-sector/supranational issuance is judged too thin or unsuitable.

Next observables

High-value updates include:

- Executive Board decision on operational details/timing;
- investment mandate or eligibility documentation;
- custody/portfolio-system implementation;
- first eligible issuer/security announcement linked to the programme;
- first ECB purchase;
- annual-report disclosure of tokenised holdings.

39.11 Resolution Rule

Hit

By 31 December 2027, the ECB executes at least one actual own-funds purchase of an eligible tokenised security and settles the transaction in central-bank money via Pontes.

Miss

The horizon expires without such a purchase while the programme remains materially intact.

Still Open

Not applicable after the fixed 2027 horizon unless public evidence establishes that the originally defined resolution event occurred but confirmation timing remains genuinely unresolved.

Target Invalidated

Only if an externally demonstrated change eliminates or materially transforms the programme such that ordinary Hit/Miss is no longer meaningful.

A delay beyond 2027 is a Miss.

39.12 Research Burden Signature

Evidence trajectory: ordinary target-local, dominated by ECB primary material
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

The Lean Core was sufficient.

39.13 Lead-time state

Initial Call: Lean — 4 October 2026
First Lean-or-better at scored specificity: 4 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 December 2027

If the first purchase occurs during 2027, this forecast will carry materially more lead time than the DTCC short-lead controls but less than the 2028 BoE/Appia cases.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-013-v1 — BankChain Alliance technology partner

Forecast ID / Version: PVR-013-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 5 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture Selection

50.1 Decision Object / Control Locus / ancestry

Decision Object: technology partner / platform underpinning the BankChain Alliance common blockchain network
Decision-Control Locus: BankChain Alliance governance, informed by participating bankers/state banking associations and the RFP process
Ancestry: state-bank-association collaboration → BankChain Alliance formation → technology-partner RFP → provider/platform selection → 2027 network launch

50.2 Use case / jurisdiction / horizon

Use case: common bank-owned blockchain infrastructure supporting tokenised deposits, stablecoins, programmable payments and automated settlement
Jurisdiction: United States
Horizon: 31 December 2027

50.3 Primary Resolution Object

> Primary Architecture Slot: technology partner / core blockchain platform used to implement the BankChain Alliance network.

Resolution requires a publicly attributable partner/platform selection or deployed production platform.

50.4 Principal Scored Claim

> NO CALL on the exact BankChain Alliance technology partner/platform as of 5 October 2026.

No named provider currently clears Lean.

This is the official v1 disposition.

50.5 Observability / permitted specificity

Observability State:

- programme intent: O3;
- architecture principles: O2–O3;
- exact technology partner: O1.

The public record strongly establishes:

- industry ownership/governance;
- a common blockchain network;
- interoperability with other networks;
- a 2027 launch target;
- active RFP/provider-selection work;
- strong emphasis on regulatory/compliance requirements.

The public record does not establish:

- a named shortlist;
- candidate-specific demonstrations for the BankChain Alliance target;
- a binding vendor relationship;
- provider-specific operating dependency;
- sufficiently discriminating public evidence favoring one provider.

Under v0.4, exact-provider specificity is therefore not earned.

50.6 Candidate field

Credible provider/platform families include, without implying equal probability:

- enterprise / permissioned blockchain infrastructure providers;
- interoperability/orchestration providers;
- bank-governed distributed-ledger platforms;
- public or public-derived blockchain technology adapted to controlled bank governance;
- a purpose-built alliance technology stack;
- an incumbent U.S. bank-tokenisation network/provider relationship not yet publicly disclosed.

Named industry platforms such as Quant, Canton/Digital Asset, R3/Corda, Ethereum/Besu-derived infrastructure, Avalanche-derived infrastructure and other bank-grade vendors are conceivable market candidates.

But generic capability is not target-specific evidence.

They remain candidate classes, not scored leaders.

50.7 Strongest Alternative to abstention

The strongest alternative to No Call is:

> issue a Lean on whichever provider appears most institutionally adjacent or technically suited.

That approach is rejected at v1 because the BankChain Alliance itself states that partner selection is ongoing, while no public candidate-specific evidence currently distinguishes one provider sufficiently from serious alternatives.

The prior TCH/Quant selection is relevant to the market environment but does not establish BankChain Alliance selection.

50.8 Load-Bearing warrant

1. The decision is genuinely unresolved

BankChain Alliance explicitly says it is in a technology-partner selection process.

2. Architecture principles are visible but provider evidence is not

The alliance has disclosed what it values:

- bank ownership;
- bank governance;
- compliance;
- interoperability;
- shared infrastructure.

Those constraints narrow the provider class but do not uniquely identify a vendor.

3. RFP process raises the evidence bar

Once a formal selection process is underway, generic relationship heuristics are particularly dangerous.

A provider can be technically plausible and still lose on:

- governance;
- economics;
- ownership structure;
- compliance;
- integration;
- commercial terms;
- procurement considerations.

4. Development evidence warned against exact-provider overreach

v0.4 exists partly because exact-provider variables are often private until late.

PVR-013 is a direct prospective test of whether abstention protects calibration in exactly that environment.

50.9 Material contradiction / private residual

The main residual is the selection process itself.

Likely private variables include:

- RFP respondents;
- scoring;
- cost;
- ownership/equity terms;
- control rights;
- regulatory/compliance review;
- technical benchmarks;
- validator/governance design;
- integration commitments;
- security assessment.

These variables are sufficiently load-bearing that public market adjacency cannot substitute for them.

50.10 Falsifier / update trigger

No Call should be reopened when target-specific evidence emerges, including:

- named finalist(s);
- alliance/vendor pilot;
- candidate-specific RFP disclosure;
- alliance investment or ownership relationship;
- technical demonstration tied directly to the alliance;
- board/member statement favoring one platform;
- partner-selection announcement.

Such evidence would ordinarily be a U1 Evidence Update.

50.11 Resolution Rule

Exact-provider resolution

The target resolves when BankChain Alliance publicly selects or deploys the technology partner/core platform that underpins the network.

No Call evaluation

No Call is not a Hit or Miss on provider identity.

It counts as:

- abstention;
- lost exact-provider coverage;
- calibration protection.

If a provider was in fact publicly distinguishable at this freeze and the method failed to identify it, later review may count that against exact-provider opportunity/coverage quality.

50.12 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Moderate

Moderate burden reflects:

- explicit provider-selection research;
- candidate-specific counter-search;
- RFP/private-residual assessment;
- need to resist generic vendor-proximity guessing.

50.13 Lead-time state

Initial Call: No Call — 5 October 2026
First Lean-or-better: not yet reached
Last-pre-resolution call: currently v1
Resolution: open

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-014-v1 — Global 21-institution USD stablecoin network architecture

Forecast ID / Version: PVR-014-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 5 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture Selection

56.1 Decision Object / Control Locus / ancestry

Decision Object: production blockchain/network architecture for the 21-institution consortium's first USD stablecoin
Decision-Control Locus: jointly controlled through the planned consortium company, subject to regulatory and commercial constraints
Ancestry: October 2025 ten-bank public-blockchain exploration → September 2026 21-institution company commitment → H1 2027 production stablecoin

56.2 Horizon

Resolution horizon: 30 June 2027

56.3 Primary Resolution Object

> Primary Architecture Slot: production ledger/network environment on which the consortium stablecoin is issued and made available to users.

56.4 Principal Scored Claim

> The consortium's initial USD stablecoin will be made available in production on at least one public blockchain, with bank-grade compliance/governance layered around the instrument, rather than being confined to a dedicated private/permissioned consortium ledger.

This is a family-level architecture forecast.

56.5 Observability / permitted specificity

Observability State: O2 for architecture family; O0–O1 for exact chain/provider.

The September 2026 announcement does not name a chain, but explicitly states that it follows the October 2025 initiative in which the initial ten banks were exploring a reserve-backed stable payment asset available on public blockchains.

The expanded group also defines use cases spanning:

- wholesale;
- institutional;
- retail;
- cross-border payments;
- digital-asset settlement.

Those use cases are structurally compatible with broad public-chain availability, though not proof of one exact network.

Permitted specificity: public-blockchain family only.

No forecast is made on:

- Ethereum;
- Solana;
- Avalanche;
- Canton;
- any exact L1/L2;
- single-chain versus multichain;
- exact wallet/custody architecture.

56.6 Call / Forecast Label

> LEAN

56.7 Strongest Alternative

> The expanded 21-member consortium abandons the predecessor public-blockchain design and launches primarily on a dedicated/private bank-controlled network, with public-chain connectivity deferred or absent at initial launch.

This alternative remains credible because:

- the September 2026 release omits an explicit chain commitment;
- the membership changed materially from the 2025 exploration group;
- bank-grade compliance/governance may favor stronger permissioning;
- final company, issuer, custody and technical architecture remain undisclosed.

56.8 Load-Bearing Warrant

1. Direct predecessor intent. The October 2025 joint statement explicitly targeted a stable payment asset available on public blockchains.
2. Explicit continuity. The September 2026 21-member announcement says the new commitment follows that earlier initiative.
3. Use-case fit. Digital-asset settlement and broad cross-border/retail reach favor interoperability with public digital-asset markets rather than a private-only island.
4. No evidence of architectural reversal. The later release omits the chain but does not state that the public-blockchain design has been abandoned.

The omission prevents Strong Lean, but the inherited architecture direction is still materially stronger than a clean-sheet private-only hypothesis.

56.9 Material contradiction / private residual

Unresolved variables include:

- company incorporation and governance;
- issuer jurisdiction;
- reserve custodian;
- regulatory licensing;
- blockchain selection;
- wallet access model;
- compliance controls;
- chain-specific operational risk;
- whether the initial release is single-chain or multichain.

56.10 Falsifier / update triggers

The Lean weakens materially if:

- the consortium selects a private/permissioned network as the sole production ledger;
- the new company states public chains are deferred or rejected;
- compliance design requires closed-network distribution only;
- a dedicated bank-owned ledger becomes the declared production architecture.

High-value U1 updates include company formation, chain announcement, technology-partner announcement, issuer/custodian disclosure and testnet/pilot deployment.

56.11 Resolution Rule

Hit The first production USD stablecoin is issued or made available on at least one public blockchain by the launch horizon.

Miss The first production stablecoin is instead confined to a dedicated/private permissioned ledger, with no production public-blockchain availability at launch.

Still Open The product has not launched and no sufficiently binding architecture decision is public by 30 June 2027.

56.12 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local, anchored in consortium-member primary releases
Deep Research: No
Specialist modules: None
Burden Category: Moderate

56.13 Lead-time state

Initial Call: Lean — 5 October 2026
First Lean-or-better: 5 October 2026
Resolution: open

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-015-v1 — MUFG / Mizuho / SMBC jointly issued stablecoin infrastructure

Forecast ID / Version: PVR-015-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 5 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture / Platform Selection

57.1 Decision Object / Control Locus / ancestry

Decision Object: core issuance infrastructure/platform for the jointly issued three-megabank stablecoin
Decision-Control Locus: joint three-bank council, with trust-bank, regulatory and technical-provider input
Ancestry: FSA-supported 2025 joint-issuance PoC → June 2026 three-bank council → FY2026 live transactions

57.2 Horizon

Resolution horizon: 31 March 2027

57.3 Primary Resolution Object

> Primary Architecture Slot: core stablecoin issuance/management infrastructure used for live commercial issuance.

The trustee identity and underlying blockchain network are separate diagnostic questions.

57.4 Principal Scored Claim

> Progmat will be selected or retained as the core issuance infrastructure for the three-bank jointly issued stablecoin used in live commercial transactions by 31 March 2027.

Underlying blockchain deployment may still span one or more networks.

57.5 Observability / permitted specificity

Observability State: O2 for Progmat path dependence; O1 for final production selection.

Direct evidence establishes:

- the prior FSA-supported PoC involved Mizuho, MUFG, SMBC, Mitsubishi Corporation, Mitsubishi UFJ Trust and Progmat, Inc.;
- the PoC tested lawful/practical joint issuance by multiple banking groups;
- the June 2026 three-bank announcement explicitly says the new council will examine the potential development of the issuance infrastructure, system design, scheme and governance;
- the production infrastructure therefore remains formally unresolved.

Progmat separately operates Progmat Coin, infrastructure specifically designed for regulated trust-type stablecoin issuance and multi-chain/public-blockchain deployment.

Permitted specificity: exact core issuance-infrastructure provider, but not exact underlying chain.

57.6 Call / Forecast Label

> LEAN — PROGMAT

Not Strong Lean.

57.7 Strongest Alternative

> The council selects another issuance-platform provider or a newly built joint-bank infrastructure, while Progmat's role remains limited to the predecessor PoC or adjacent interoperability work.

This alternative is credible because the June 2026 council announcement explicitly leaves issuance-infrastructure development open.

Contemporaneous Japanese reporting also states that the trust bank and system-platform provider were still to be selected.

57.8 Load-Bearing Warrant

1. Target-specific predecessor participation. Progmat was not merely ecosystem-adjacent; it was a named applicant in the exact FSA-supported joint-issuance experiment with all three banks.
2. Relevant reusable infrastructure. Progmat Coin is purpose-built for Japanese regulated stablecoin issuance under the trust structure used by the target.
3. Institutional continuity. Mitsubishi UFJ Trust, a core Progmat-related institution and prior PoC participant, is directly relevant to the trust-type issuance model.
4. Switching-cost logic. Reusing a platform already involved in legal/compliance experimentation lowers implementation and operational risk under a March 2027 commercialization deadline.
5. Open selection prevents overconfidence. The banks explicitly created a council to examine issuance infrastructure rather than announcing Progmat as already selected.

That combination is sufficient for Lean but not Strong Lean.

57.9 Material contradiction / private residual

The key adverse fact is procedural:

> the production infrastructure is still being examined.

Private variables likely include:

- platform RFP/comparison;
- trustee selection;
- system integration;
- cost;
- governance neutrality;
- cybersecurity;
- scalability;
- bank-specific integration;
- chain selection;
- regulatory interpretation.

A rival provider can still win.

57.10 Falsifier / update triggers

The Progmat Lean weakens materially if:

- the council announces another platform/provider;
- Progmat is excluded from production work;
- a new bank-owned infrastructure is selected;
- the trust bank chooses a different issuance-management stack;
- the project architecture changes materially from the PoC model.

High-value U1 updates include named platform selection, council technical documentation, trustee selection, production-chain announcement and live transaction evidence.

57.11 Resolution Rule

Hit Progmat / Progmat Coin is publicly selected, retained or demonstrably used as the core issuance-management infrastructure for the live joint stablecoin.

Miss Another platform/provider is selected as the core issuance infrastructure and Progmat is not the production core.

Still Open No binding production-platform selection is publicly resolvable by 31 March 2027 and live transactions have not clarified the provider.

57.12 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local with Japanese primary-source review
Deep Research: No
Specialist modules: None
Burden Category: Moderate

57.13 Lead-time state

Initial Call: Lean — Progmat — 5 October 2026
First Lean-or-better: 5 October 2026
Resolution: open

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-016-v1 — Bank of England long-term wholesale central-bank-money settlement architecture

Forecast ID / Version: PVR-016-v1
Method: Institutional Architecture Forecasting v0.4
Freeze / evidence cutoff: 5 October 2026
Cohort: Core
Task: F1 — Architecture Selection

109.1 Decision object / control locus / ancestry

Decision Object: longer-term strategic architecture for providing sterling central-bank-money settlement to tokenised wholesale markets after the initial Synchronisation rollout.

Decision-Control Locus: Bank of England, with market, regulatory, legal, infrastructure and international experimentation inputs.

Ancestry: renewed RTGS / RT2 → Meridian → Meridian FX / Securities → Synchronisation Lab → production-targeted Synchronisation → comparative wholesale experimentation → long-term architecture choice.

This ancestry overlaps with PVR-003 but the scored decision object does not.

109.2 Horizon

> 31 December 2028

The Bank's planned 2027 integrated wholesale-experiment synthesis is a principal discriminator, not automatically the final resolution event.

109.3 Primary Resolution Object

> Primary Architecture Slot: the Bank of England's strategic sterling central-bank-money settlement model for tokenised wholesale markets after comparative assessment of Synchronisation/RTGS enhancement and native tokenised-CBM alternatives.

The resolution object is not whether Synchronisation launches, whether wCBDC is technically feasible, whether a particular DLT participates in an experiment, whether the UK tokenised market grows, or whether tokenised deposits coexist with RTGS.

109.4 Candidate field

Candidate A — RT2 / Synchronisation-centric evolution Sterling central-bank money remains principally in RT2. Synchronisation and related RTGS enhancements provide the principal mechanism for connecting central-bank money to tokenised markets.

Candidate B — Bank-operated native tokenised CBM A material Bank-operated wholesale-CBDC / tokenised-CBM rail becomes a strategic settlement architecture.

Candidate C — native CBM on external programmable infrastructure Sterling central-bank money is enabled on controlled external programmable ledgers that the Bank does not fully operate.

Candidate D — persistent hybrid RT2 / Synchronisation remains strategically central while a genuinely native tokenised-CBM capability is added for selected use cases because it provides material functionality that A cannot adequately provide.

109.5 Principal Scored Claim

> By 31 December 2028, the Bank of England's strategic architecture for sterling central-bank-money settlement in tokenised wholesale markets will remain centered on RT2, with Synchronisation and related RTGS enhancements serving as the principal mechanism for connecting central-bank money to tokenised-market infrastructures, rather than native tokenised central-bank money becoming a co-equal or dominant strategic settlement rail.

This is a family-level architecture forecast.

Ordinary coexistence of tokenised deposits, private DLT systems, external asset ledgers, Omnibus arrangements, longer hours, APIs or experimentation with native CBM does not by itself make Candidate D win.

109.6 Call / Forecast Label

> LEAN — RT2 / SYNCHRONISATION-CENTRIC EVOLUTION

Not Strong Lean.

109.7 Strongest Alternative

> Candidate D — persistent hybrid

The strongest losing path is that RT2/Synchronisation remains material but the Bank concludes that important DLT-native wholesale use cases require persistent native tokenised sterling central-bank money because same-ledger programmability, composability, collateral/liquidity functionality or cross-border execution provides material incremental value that Synchronisation cannot adequately reproduce.

Candidates B and C are best treated, at current observability, as possible implementation branches of a native-CBM addition unless they ultimately displace RT2/Synchronisation as the architecture's center of gravity.

109.8 Observability / permitted specificity

Architecture family: O2
Exact native-CBM topology: O1
Exact ledger / provider / network: O0–O1

Permitted specificity: architecture family only.

No forecast is made on a named wCBDC platform, Bank-operated versus externally operated native-CBM implementation, permissioned versus permissionless final topology, a specific DLT network, a specific Synchronisation Operator, or a public token.

109.9 Load-bearing warrant

The Lean rests on an observable asymmetry:

1. Candidate A already has implementation path dependence: renewed RT2, Future Roadmap, APIs/connectivity, longer-hours capability, Meridian experiments, Synchronisation operator design, assurance/tariff work, Synchronisation Lab, and a production-targeted 2028 capability.
2. Native CBM still must earn incremental value: the Bank's comparative programme explicitly asks whether wholesale CBDC provides meaningful advantages beyond Synchronisation.
3. Atomicity alone is not decisive: Synchronisation already supports atomic settlement, while Meridian Securities demonstrated programmable repo and liquidity-management functionality without tokenising CBM.
4. Liquidity and governance currently favor A: RT2 preserves one established sterling-CBM liquidity pool, mature legal/finality arrangements, Bank governance, technology neutrality and heterogeneous-ledger support.
5. Industry demand is outcome-led rather than wCBDC-led: collateral mobility, post-trade efficiency, interoperability and settlement certainty are clearer than demand for one native-CBM rail.

> Candidate A is the implemented baseline; D/B/C require a positive incremental-value result.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-018-v1 — DTC Tokenization Service next additional external public blockchain network

Forecast ID / Version: PVR-018-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 5 October 2026
Lane: Opportunistic Discovery / Core-FMI connection intelligence
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Network / Architecture Selection

132.1 Decision object / control locus / ancestry

Decision Object: the next external public Layer 1 or Layer 2 blockchain network, beyond Canton and Stellar, that DTCC/DTC publicly selects, approves or enters a concrete implementation path to support DTC-tokenized assets through the DTC Tokenization Service.

Decision-Control Locus: DTC / DTCC, materially informed by DTC Participant demand and internal legal, regulatory, security, resilience, governance, engineering, integration and commercial evaluation.

Ancestry: DTC no-action authorization → Canton selection / implementation → Stellar selection / planned integration → multi-chain Tokenization Service expansion → next additional external public L1/L2 selection.

The DTCC Collateral AppChain is private, DTCC-controlled infrastructure and does not qualify as the unresolved external-public-network resolution object.

132.2 Use case / jurisdiction / horizon

Use case: external public-chain support for DTC-tokenized securities and related participant workflows under DTC-controlled token, wallet, monitoring and entitlement architecture.
Jurisdiction: United States / DTC regulated market infrastructure
Horizon: 31 December 2027

132.3 Primary Resolution Object

> Primary Architecture Slot: the next additional external public L1/L2 network, after Canton and Stellar, that DTC/DTCC authoritatively commits to supporting for DTC-tokenized assets.

The forecast does not resolve on generic ecosystem participation, a vendor relationship, an interoperability demonstration or a public network being technically compatible with DTC requirements.

132.4 Principal Scored Claim

> NO CALL — exact next external public network as of 5 October 2026.

No external public L1/L2 beyond Canton and Stellar clears Lean at the scored exact-network specificity.

This is the official PVR-018-v1 disposition.

132.5 Observability / permitted specificity

Selection-framework / process observability: O2
Exact-network observability: O1

The public record establishes substantial selection-process structure, including:

- legal / regulatory / compliance gating;
- reliability, resilience and security review;
- governance and consensus review;
- DTC observability and control requirements;
- participant demand;
- use-case alignment;
- market / ecosystem position;
- integration feasibility and cost;
- scalability and operating-cost stability;
- proven institutional deployment;
- DTCC-infrastructure compatibility;
- additional L2-specific dependency and continuity analysis.

The public record does not establish the candidate-specific state required to discriminate the next network, including:

- which networks are currently under DTC/DTCC review;
- network-specific DTC Participant demand;
- internal legal/regulatory conclusions;
- candidate-specific security/resilience/governance scores;
- integration effort and cost estimates;
- private demonstrations and test results;
- commercial arrangements;
- approval or implementation sequencing.

Permitted specificity: exact network remains the scored resolution object, but the evidence does not support a directional Lean at that specificity.

132.6 Diagnostic contender interpretations — explicitly unscored

The research identifies two useful but non-scored interpretive lanes:

EVM / Ethereum-family interpretation

DTCC has meaningful implementation ancestry through Hyperledger Besu, ComposerX support for ERC token frameworks and DTC recognition of ERC-3643 as a compliance-aware token protocol.

Status:

> DIAGNOSTIC IMPLEMENTATION-ANCESTRY INTERPRETATION ONLY — NOT A SCORED FORECAST, NOT AN OFFICIAL CANDIDATE RANKING.

Solana interpretation

Solana has materially relevant institutional tokenization activity and technical control features that can map to portions of DTC's requirements.

Status:

> DIAGNOSTIC INSTITUTIONAL / USE-CASE INTERPRETATION ONLY — NOT A SCORED FORECAST, NOT AN OFFICIAL CANDIDATE RANKING.

No ordinal ranking between EVM/Ethereum-family and Solana is frozen in the official forecast record.

Other public networks and L2s remain possible where the private DTC-specific variables support them.

132.7 Strongest alternative to abstention

The strongest alternative to the No Call disposition is to issue a directional Lean from DTCC's existing EVM/Besu/ERC implementation ancestry.

That approach is rejected at v1 because:

1. DTCC already selected architecturally different Stellar after substantial EVM/Besu/ERC ancestry existed;
2. ComposerX / LedgerScan is intentionally multi-network and reduces the strength of simple stack-lock-in inference;
3. DTCC's published evaluation framework uses multiple business, regulatory and operational criteria rather than EVM compatibility alone;
4. no State-A target-specific evidence shows DTC selecting, integrating or prioritizing public Ethereum or a named EVM L2 for this Tokenization Service expansion.

The same logic prevents Solana's institutional-use adjacency or technical capability from becoming a scored Lean without a DTC-specific bridge.

132.8 Load-bearing warrant

The No Call rests on the following asymmetry:

1. The selection process is real and observable. DTC explicitly plans continuing L1/L2 expansion and publishes meaningful qualification/prioritization criteria.
2. The resolved precedents are real. Canton and Stellar have already crossed from generic capability into DTC-specific selection/implementation state.
3. No third public network has crossed that evidentiary boundary in State A. No additional external public L1/L2 produced qualifying public DTC Tokenization Service selection, implementation or production-network evidence by the cutoff.
4. The most discriminating remaining variables are candidate-specific and predominantly private. Participant demand, internal risk/legal assessment, integration cost, private testing and sequencing could readily overturn a generic ancestry-based inference.
5. Generic capability does not discriminate the outcome. Multiple network families can plausibly satisfy the public technology and compliance framework through base-layer, token-layer and supporting-technology combinations.

The correct forecast behavior is therefore abstention at exact-network specificity rather than manufacturing a directional winner from adjacent evidence.

132.9 Material contradiction / private residual

The material residual includes:

- actual networks under internal review;
- actual network requests from DTC Participants;
- candidate-specific legal/regulatory analysis;
- internal security, resilience and governance assessments;
- network-specific integration effort and operating cost;
- private demonstrations / implementation tests;
- commercial terms or foundation/infrastructure-provider arrangements;
- internal launch sequencing.

These variables are sufficiently decision-relevant that public ecosystem strength, technical features or institutional tokenization activity cannot substitute for them.

132.10 Public Evidence Ceiling

> PUBLIC EVIDENCE CEILING REACHED FOR CURRENT EXACT-NETWORK DISCRIMINATION.

This ceiling is scoped to the State-A evidence field as of 5 October 2026.

It does not mean future public evidence cannot support a directional forecast.

It means additional generic comparison of public networks currently has low expected decision value relative to the missing DTC-specific variables.

132.11 Falsifier / next observable / U1 triggers

Reopen PVR-018 on material target-specific State-B evidence such as:

1. DTCC/DTC naming another external public L1/L2 under evaluation or integration;
2. network-specific DTC Participant demand disclosure;
3. a Tokenization Service pilot or implementation tied to a specific additional public network;
4. a signed DTCC/network partnership tied specifically to DTC-tokenized assets;
5. network-specific integration or engineering commitment;
6. addition of another external public network to the official eligible/supported network set;
7. candidate-specific security, legal, governance or technical evaluation disclosure;
8. equivalent authoritative evidence materially discriminating one network from credible alternatives.

A qualifying post-freeze item is ordinarily classified as U1 — EVIDENCE UPDATE.

Do not reopen for another round of generic throughput, TVL, validator-count, fee, market-cap or broad institutional-adoption comparison absent a target-specific bridge.

132.12 Resolution Rule

Qualifying resolution

PVR-018 resolves when DTCC/DTC first publicly:

- names another external public L1/L2 as an eligible/supported Tokenization Service network;
- signs a network partnership specifically tied to DTC-tokenized assets;
- announces concrete target-specific implementation for another external public network;
- or makes an equivalent authoritative commitment that materially fixes the next network selection.

Non-qualifying events

The following do not by themselves resolve the target:

- generic experiments;
- Industry Working Group membership;
- vendor participation;
- generic interoperability demonstrations;
- a participant using a network elsewhere;
- network-foundation capability claims;
- token-standard compatibility without DTC-specific commitment.

Simultaneous-selection rule

If DTCC/DTC authoritatively announces multiple qualifying new external public networks simultaneously without a disclosed sequencing order, record the resolution as a joint next-selection set.

Do not manufacture a single-network winner after the fact.

No Call evaluation

The initial No Call is not itself a Hit or Miss on network identity.

It counts as:

- abstention at exact-network specificity;
- lost exact-network directional coverage;
- calibration protection if no candidate was sufficiently distinguishable at freeze.

If later review demonstrates that one network was publicly distinguishable at the State-A cutoff and the method failed to identify it, that may count against specificity-opportunity / coverage quality.

132.13 State-B / U1 status at initial freeze

> PVR-018 STATE-B U1 QUEUE: EMPTY

No material post-5-October-2026 evidence is incorporated into PVR-018-v1.

The initial official forecast is frozen entirely on State-A evidence.

132.14 Research Burden Signature

Evidence trajectory: broad target-local / multi-source with candidate and challenger search
Deep Research: Yes
Independent load-bearing-artifact verification: Yes
Specialist modules: None
External resolver: None
Continuity / handoff burden: Extended
Burden Category: Heavy

The Heavy classification is warranted by Deep Research, independent primary-artifact verification and extended control-window continuity.

132.15 Lead-time state

Target freeze: 5 October 2026
Initial Call: No Call — 5 October 2026
First Lean-or-Better: NOT YET ESTABLISHED
Predictive lead-time clock: NOT STARTED
Last-pre-resolution call: currently PVR-018-v1
Resolution: open

Because PVR-018-v1 is a No Call, 5 October 2026 is not a First Lean-or-Better date and does not start predictive lead-time measurement.

If later qualifying State-B evidence produces a U1 upgrade to Lean or Strong Lean at the scored specificity:

> First Lean-or-Better begins on the date that qualifying directional call is first earned.

It must not be backdated to 5 October 2026.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-019-v1 — The Clearing House On-Chain Money Initiative participating-institution availability

Forecast ID / Version: PVR-019-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

142.1 Decision Object / Control Locus / ancestry

Decision Object: The Clearing House On-Chain Money Initiative transition from development / implementation into availability for participating financial institutions.

Decision-Control Locus: primarily The Clearing House, with Quant implementation, member-bank integration, operating-rule, legal/compliance and participant-readiness dependencies.

Ancestry: bank-led initiative announcement → provider selection → implementation / onboarding → participating-institution availability.

The provider-selection object is already resolved and is not rescored here.

142.2 Use case / jurisdiction / horizon

Use case: clearing and settlement of tokenized commercial-bank deposits, linked to existing U.S. fiat-payment rails including RTP and CHIPS.

Jurisdiction: United States

Horizon: 30 June 2027

142.3 Primary Resolution Object

> Primary Maturity Milestone: The Clearing House formally makes the On-Chain Money Initiative available to participating financial institutions for real tokenized-deposit clearing and settlement beyond closed development, demonstration or pilot-only status.

A technology demonstration, implementation update, closed test, bank statement of support or another provider announcement does not by itself resolve the forecast as a Hit.

A limited initial launch may qualify if The Clearing House establishes that the network is genuinely available for participating-institution use.

142.4 Principal Scored Claim

> By 30 June 2027, The Clearing House will make the On-Chain Money Initiative available to participating financial institutions for real tokenized-deposit clearing and settlement.

142.5 Observability / permitted specificity

Observability State: O3 for programme direction and announced H1 2027 availability window; O2 for exact launch scope, participant readiness and first-use conditions.

Public evidence establishes:

- a real bank-led programme;
- The Clearing House as operator;
- broad support from major U.S. and international banks active in the U.S. market;
- a selected implementation provider;
- a defined interoperability / orchestration / transaction-management role;
- connection to RTP and CHIPS;
- an explicit H1 2027 availability expectation.

Permitted specificity: participating-institution availability / maturity milestone only.

No official forecast is made on:

- exact launch day;
- exact first participant set;
- transaction volume;
- deposit balances;
- specific customer use cases;
- exact blockchain / ledger composition;
- Fusion use;
- QNT gas, staking, lockup or token demand;
- Quant contract economics.

142.6 Call / Forecast Label

> LEAN

Strong Lean is not earned at the initial freeze.

142.7 Strongest Alternative

> The programme remains intact but participating-institution availability slips beyond H1 2027 because bank onboarding, operating rules, integration, legal/compliance work, security/resilience hardening or production-readiness testing take longer than the public schedule implies.

A second alternative is that TCH reaches only a restricted testing / pilot state by 30 June 2027 rather than genuine participating-institution availability.

142.8 Load-Bearing Warrant

1. The programme is institutionally real

The initiative was announced by The Clearing House with broad public support from major banks.

This is not an unowned technology proposal.

2. The implementation provider is already selected

On 24 September 2026, The Clearing House selected Quant for the network's interoperability, orchestration and transaction-management layer.

That materially reduces provider-selection uncertainty.

3. The launch / availability window is explicit

The Clearing House states that the network is expected to become available to participating institutions in the first half of 2027.

The forecast horizon therefore follows the originating institution's own public timetable rather than an analyst-invented date.

4. The programme builds around incumbent payment infrastructure

The target architecture connects to established TCH-operated rails including RTP and CHIPS.

This lowers the risk associated with building an entirely independent payments institution from scratch.

5. Broad bank demand / sponsorship exists

The originating announcement records support from a large set of major banks and explicitly positions the service as bank-led infrastructure for tokenized deposits.

This does not prove each bank will be live at launch, but it materially reduces demand-side existence risk.

6. Implementation risk remains material

Unlike the strongest near-production control cases, no public pre-freeze evidence establishes a completed On-Chain Money production pilot or launch-ready transaction.

The H1 2027 language is an expectation, not a completed precursor.

That is why the call remains Lean rather than Strong Lean.

142.9 Material contradiction / private residual

Material unresolved variables include:

- exact bank onboarding state;
- final participant operating rules;
- bank-side tokenized-deposit issuance readiness;
- compliance / legal treatment;
- security and resilience testing;
- integration into member-bank systems;
- exact relationship between the shared network and bank-side TDaaS implementations;
- exact initial use-case scope;
- whether the first release is broad production, restricted availability or pilot-like;
- whether H1 2027 timing slips.

No public evidence at the freeze resolves these execution details.

142.10 Falsifier / Next Observable

The Lean weakens materially if:

- TCH formally moves availability beyond H1 2027;
- the initiative is reframed as a longer pilot / testing programme;
- bank onboarding is materially delayed;
- significant regulatory, legal, security or operating-rule blockers become public;
- the selected implementation architecture is materially reworked in a way that invalidates the current launch sequence.

High-value next observables include:

- named launch participants;
- operating rules / participation documentation;
- bank onboarding announcements;
- production testing;
- first live tokenized-deposit clearing / settlement;
- formal network-availability announcement;
- revised schedule.

Any qualifying post-freeze evidence is a U1 Evidence Update.

142.11 Resolution Rule

Hit

By 30 June 2027, The Clearing House formally launches or makes the On-Chain Money Initiative available to participating financial institutions for real tokenized-deposit clearing and settlement beyond closed development or pilot-only activity.

Miss

30 June 2027 passes without qualifying participating-institution availability while the programme remains materially intact.

A launch in July 2027 or later is a Miss under PVR-019-v1.

Still Open

Not ordinarily applicable after the fixed horizon unless authoritative evidence establishes that qualifying availability occurred by 30 June but public confirmation timing remains genuinely ambiguous.

Target Invalidated

Only if an external change abandons or materially transforms the programme such that the original maturity object is no longer meaningful.

142.12 Research Burden Signature

Evidence trajectory: narrow/direct, dominated by The Clearing House primary material
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

142.13 Lead-time state

Initial Call: Lean — 6 October 2026
First Lean-or-Better at scored specificity: 6 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 30 June 2027

The primary scored predictive lead-time clock begins on 6 October 2026.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-020-v1 — Project Harmonia first-cohort go-live

Forecast ID / Version: PVR-020-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

151.1 Decision Object / Control Locus / ancestry

Decision Object: conversion of Project Harmonia from RFP / admission process into a live first cohort of regulated tokenized funds distributed through Allfunds via Solana.

Decision-Control Locus: multi-party, centered on the Project Harmonia Admission Committee and programme operators, with:

- Solana Foundation chairing the Admission Committee;
- Particula providing primary risk-assessment input;
- Allfunds participating in onboarding / distribution requirements;
- ioBuilders / Asseto providing technical integration;
- applicant issuers / asset managers satisfying legal, operational, custody and technical requirements.

Ancestry: June Allfunds/Solana expansion announcement → September RFP → October due diligence → November admissions → Q1 2027 integration/go-live.

151.2 Use case / jurisdiction / horizon

Use case: institutional and on-chain distribution of regulated tokenized collective investment funds through a shared Allfunds–Solana distribution bridge.

Jurisdiction: cross-border / supported Allfunds jurisdictions, with eligible fund domiciles including major EU/EEA jurisdictions and other accepted regulated markets.

Horizon: 31 March 2027

151.3 Primary Resolution Object

> Primary Maturity Milestone: at least one Project Harmonia-admitted regulated tokenized fund is live for distribution through the Allfunds network via Solana by 31 March 2027.

The following do not count as a Hit by themselves:

- an application;
- shortlist inclusion;
- risk rating;
- admission decision without go-live;
- technical demonstration;
- general Allfunds–Solana connectivity;
- an unrelated tokenized fund already existing on Solana.

151.4 Principal Scored Claim

> By 31 March 2027, Project Harmonia will put at least one admitted regulated tokenized fund live for distribution through the Allfunds network via Solana.

151.5 Observability / permitted specificity

Observability State: O3 for programme timeline, RFP process and Solana / Allfunds architecture; O2 for applicant field and implementation readiness.

Permitted specificity: first-cohort go-live / maturity milestone.

No official forecast is made on:

- exact winning fund;
- exact issuer;
- number of admitted funds;
- funded AUM;
- transaction volume;
- investor count;
- whether a particular existing Solana fund applies;
- whether a specific Allfunds client distributes or invests;
- SOL price or proportional SOL token demand.

151.6 Call / Forecast Label

> LEAN

Strong Lean is not earned.

151.7 Strongest Alternative

> The RFP produces admissions or conditional admissions, but legal, operational, technical, custody, onboarding or integration work prevents any admitted fund from becoming live through Allfunds via Solana by 31 March 2027.

A second adverse path is that the RFP fails to produce a qualifying first cohort because applicant quality / eligibility is insufficient.

151.8 Load-Bearing Warrant

1. Allfunds has already committed to the underlying Solana distribution direction

The underlying chain / distribution decision is not hypothetical.

Allfunds announced the expansion to Solana before the RFP.

2. The programme has crossed from announcement into a formal operating process

The RFP is live with:

- a fixed submission deadline;
- formal eligibility criteria;
- structured diligence;
- independent assessment;
- documented admission governance;
- a scheduled admission-decision month;
- an explicit integration step.

This is materially stronger than a roadmap statement.

3. Track A reduces one important execution dependency

Track A is designed for funds already live and operational on Solana.

A successful Track-A applicant therefore does not require the underlying fund to be created from scratch before Allfunds integration.

4. The programme has a named technical integration layer

ioBuilders / Asseto provides the Allfunds–Solana integration path.

The project is therefore not relying on an unidentified future integration mechanism.

5. Q1 2027 is the programme's own current go-live target

The forecast horizon follows the active RFP's own schedule rather than an analyst-selected date.

6. But the applicant / admission state remains private and execution-heavy

The public record does not establish:

- applicant count;
- applicant quality;
- final admission decisions;
- current onboarding completion;
- whether any Track-A applicant has cleared all Allfunds requirements.

The programme's own disclaimer explicitly rejects any guarantee of admission or commercial outcome.

This residual is sufficient to prevent Strong Lean.

151.9 Material contradiction / private residual

Material private or unresolved variables include:

- applicant identities;
- applicant legal / regulatory quality;
- Particula risk ratings;
- Admission Committee deliberations;
- Allfunds onboarding decisions;
- custody / transfer-agent readiness;
- smart-contract / security remediation;
- settlement / liquidity arrangements;
- commercial terms;
- operational integration progress;
- whether any admitted fund is ready for live distribution by quarter-end.

151.10 Falsifier / Next Observable

The Lean weakens materially if:

- the 24 October application window is extended materially;
- November admission decisions are delayed;
- no qualifying admissions are announced;
- the programme revises Q1 2027 go-live timing;
- admitted funds are described as requiring substantial additional build / regulatory work;
- technical or legal integration blockers emerge.

The Lean strengthens if:

- one or more Track-A funds are publicly shortlisted;
- November winners are announced on schedule;
- a named admitted fund is already technically integrated;
- Allfunds publishes a production launch date inside Q1.

Any qualifying post-freeze development is a U1 Evidence Update.

151.11 Resolution Rule

Hit

By 31 March 2027, authoritative programme / Allfunds evidence establishes that at least one Project Harmonia-admitted regulated tokenized fund is live for distribution through the Allfunds network via Solana.

Miss

31 March 2027 passes without a qualifying live admitted fund while the programme remains materially intact.

A launch after 31 March 2027 is a Miss under PVR-020-v1.

Still Open

Not ordinarily applicable after the fixed horizon unless credible evidence establishes that qualifying go-live occurred by the horizon but public confirmation timing is genuinely ambiguous.

Target Invalidated

Only if the programme is abandoned or materially transformed such that the frozen first-cohort distribution object ceases to exist.

151.12 Research Burden Signature

Evidence trajectory: narrow/direct target-local
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

151.13 Lead-time state

Initial Call: Lean — 6 October 2026
First Lean-or-Better at scored specificity: 6 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 March 2027

The primary scored predictive lead-time clock begins on 6 October 2026.

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-021-v1 — Qivalis regulated euro-stablecoin launch

Forecast ID / Version: PVR-021-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Opportunistic Discovery / short-horizon maturity control
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

160.1 Decision Object / Control Locus / ancestry

Decision Object: conversion of Qivalis from authorised-in-progress / implementation state into actual regulated issuance of its euro-denominated stablecoin.

Decision-Control Locus: Qivalis management and shareholder consortium, with a load-bearing external regulatory dependency on De Nederlandsche Bank.

Ancestry: consortium formation → dedicated issuer incorporation → governance buildout → 37-bank expansion → regulatory / technical / operational preparation → EMI authorisation → regulated stablecoin issuance.

160.2 Use case / jurisdiction / horizon

Use case: regulated euro-denominated on-chain settlement and payment infrastructure for institutional and broader compliant counterparties.

Jurisdiction: Netherlands / European Union, with pan-European bank consortium scope.

Horizon: 31 December 2026

160.3 Primary Resolution Object

> Primary Maturity Milestone: Qivalis begins regulated issuance / commercial launch of its euro-denominated stablecoin by 31 December 2026.

A management appointment, regulatory-progress update, technical completion claim or DNB authorisation without actual launch does not by itself qualify as a Hit.

160.4 Principal Scored Claim

> Qivalis will begin regulated issuance / commercial launch of its euro-denominated stablecoin by 31 December 2026.

160.5 Observability / permitted specificity

Observability State: O3 for programme existence and stated year-end launch objective; O1–O2 for actual regulatory / production readiness.

Permitted specificity: launch / maturity milestone only.

No official forecast is made on:

- exact blockchain network;
- exact technology provider;
- exact distribution partners;
- launch date within Q4;
- launch supply;
- transaction volume;
- number of active member banks at launch;
- stablecoin market share;
- public-token implications for any external blockchain.

160.6 Call / Forecast Label

> LIVE CONTENDER

A Lean is not earned at the initial freeze.

The year-end launch path is genuinely live and supported, but public evidence does not sufficiently discriminate it from a launch delay into 2027.

160.7 Why not Lean

The affirmative path has meaningful support:

- large committed bank consortium;
- dedicated issuer;
- active governance and staffing;
- repeated technical / operational-readiness statements;
- explicit launch target;
- the launch target was reaffirmed on 5 October 2026.

But the strongest alternative remains comparably credible because:

- DNB authorisation is still outstanding;
- Qivalis publicly states it is not yet authorised;
- no public evidence establishes the completeness / substantive-assessment stage of the EMI application;
- DNB licensing clocks can be delayed or suspended;
- no public production-readiness milestone proves issuance can begin immediately after approval.

The method therefore withholds Lean.

160.8 Strongest Alternative

> Qivalis remains institutionally intact and continues toward launch, but DNB authorisation and/or final operational readiness slips beyond 31 December 2026, pushing first regulated issuance into 2027.

This alternative does not require programme failure.

A modest regulatory or implementation delay is sufficient to produce a Miss under the frozen horizon.

160.9 Load-Bearing Warrant

Affirmative evidence

1. Large shareholder base
- 37 European banks materially reduces the risk that the programme is an unfunded or weakly sponsored experiment.

2. Dedicated institution
- Qivalis B.V. is an incorporated operating vehicle rather than an informal consortium label.

3. Repeated schedule continuity
- the H2 2026 launch objective has persisted through multiple public updates.

4. Fresh reaffirmation
- on 5 October 2026, one day before the freeze, Qivalis explicitly said it plans to launch before year-end.

5. Operational buildout
- technical implementation, operational readiness, governance and compliance buildout have been publicly described.

Adverse / limiting evidence

1. Authorisation remains unresolved
- Qivalis is not yet authorised at the cutoff.

2. Regulatory state is largely private
- public materials do not reveal whether DNB considers the application complete or near decision.

3. Licensing duration is variable
- DNB's statutory three-month period begins after completeness and may be suspended.

4. Launch readiness is not independently demonstrated
- no public evidence establishes final production readiness, first issuance mechanics or distribution activation.

These facts support a live launch path but not a directional Lean.

160.10 Falsifier / Next Observable

The launch path strengthens materially if:

- DNB grants Qivalis EMI authorisation;
- Qivalis announces completed regulatory approval;
- a dated commercial launch is announced;
- first distribution / exchange / member-bank partners are named for launch;
- token issuance contracts / production availability are publicly confirmed.

The path weakens materially if:

- Qivalis revises its launch target into 2027;
- DNB requests material additional work or delays become public;
- management describes the programme as awaiting substantial technical / operational work after authorisation;
- year-end passes without launch.

Any qualifying post-freeze evidence is a U1 Evidence Update.

160.11 Resolution Rule

Hit

By 31 December 2026, Qivalis begins regulated issuance / commercial availability of its euro-denominated stablecoin under the authorised operating entity.

Miss

31 December 2026 passes without qualifying launch while the Qivalis programme remains materially intact.

A launch in January 2027 or later is a Miss under PVR-021-v1.

Still Open

Not ordinarily applicable after the fixed horizon unless credible evidence establishes that launch occurred by 31 December but public confirmation timing is genuinely ambiguous.

Target Invalidated

Only if an external legal / regulatory or corporate event eliminates or materially transforms the programme such that the original launch object no longer exists.

160.12 Research Burden Signature

Evidence trajectory: narrow/direct
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Light

160.13 Lead-time state

Initial Call: Live Contender — 6 October 2026
First Lean-or-Better at scored specificity: NOT ESTABLISHED
Primary predictive lead-time clock: NOT STARTED
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 December 2026

If later State-B evidence earns Lean or Strong Lean before resolution, the lead-time clock begins on that later date.

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-022-v1 — Great British Tokenised Deposits post-pilot programme state

Forecast ID / Version: PVR-022-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F2 — Programme State

169.1 Decision Object / Control Locus / ancestry

Decision Object: GBTD programme state after completion of the 2026 pilot phase.

Decision-Control Locus: participating bank consortium / UK Finance, with material Bank of England, PRA, FCA, payments-infrastructure, governance and commercial dependencies.

Ancestry: UK RLN experimentation → GBTD pilot programme → live customer transactions → digital-asset settlement pilots / Synchronisation Lab → post-pilot FMI-development decision.

169.2 Use case / jurisdiction / horizon

Use case: interoperable tokenised sterling commercial-bank deposits for programmable payments and tokenised-asset settlement.

Jurisdiction: United Kingdom

Horizon: 30 June 2027

169.3 Primary Resolution Object

> Primary Programme Variable / State Transition: GBTD transitions from the 2026 pilot programme into an active post-pilot 2027 build / implementation phase for shared tokenised-deposit financial-market infrastructure.

169.4 Principal Scored Claim

> By 30 June 2027, GBTD will have transitioned into an active post-pilot build / implementation phase for shared UK tokenised-deposit infrastructure, rather than having been paused, concluded or returned to exploratory-only status after the 2026 pilots.

169.5 Observability / permitted specificity

Observability State: O3 for programme direction / public sponsorship; O2 for exact post-pilot governance and implementation model.

Permitted specificity: programme continuation / build state only.

No official forecast is made on:

- exact legal form of the FMI;
- exact operator / owner;
- exact production provider;
- Quant's final production role;
- Fusion use;
- QNT usage;
- exact ledger / blockchain architecture;
- exact public launch date;
- transaction volume;
- nationwide adoption rate.

169.6 Call / Forecast Label

> STRONG LEAN

This is the campaign's first official F2 forecast.

169.7 Strongest Alternative

> The 2026 pilots remain technically successful, but the consortium does not enter a genuine post-pilot FMI build by 30 June 2027 because governance, regulatory perimeter, commercial ownership, integration with the wider UK payments-modernisation programme or bank commitment remains unresolved.

A second alternative is that GBTD's work is absorbed into a broader payments-infrastructure initiative in a way that materially closes GBTD as a distinct post-pilot programme.

169.8 Load-Bearing Warrant

1. Strong institutional sponsorship

GBTD is supported by seven major UK banking institutions / building society participants.

This is not a single-vendor product seeking customers after the fact.

2. Successful live transactions have already occurred

The programme crossed an important maturity barrier in September 2026 through real customer transactions.

This reduces technical / organisational feasibility risk.

3. The current programme is still expanding its test scope

Digital-asset settlement pilots are expected after the retail live-pilot milestone.

This is inconsistent with a programme already winding down.

4. The consortium has explicitly described a 2027 FMI path

GBTD written evidence states that end-2026 pilots will inform the approach to building GBTD as a new FMI platform in 2027.

That is direct programme-state evidence.

5. Recent UK Finance policy activity supports continuity

UK Finance's September 2026 Autumn Budget submission explicitly calls for sustained delivery of the GBTD initiative.

6. The Bank of England policy environment is supportive rather than blocking

The Bank publicly states that:

- banks are expected to innovate in tokenised deposits;
- the Bank is working with banks to design and implement tokenised money;
- future UK payment infrastructure should interoperate with tokenised deposits and other forms of regulated money.

The Bank's Digital Securities Sandbox also recognises tokenised deposits as an acceptable form of commercial bank money for settlement.

7. GBTD is connected to adjacent official infrastructure work

GBTD is a participant in the Bank's Synchronisation Lab for bond/gilt settlement and multi-purpose orchestration.

That creates another path for continued institutional relevance after the current retail pilots.

8. The strongest alternative is material but not comparably supported

Post-pilot governance, ownership and regulatory details remain unresolved.

However, current evidence overwhelmingly points toward continuation / implementation rather than termination.

That is sufficient for Strong Lean at programme-state specificity, while remaining insufficient for exact FMI/provider/ledger architecture.

169.9 Material contradiction / private residual

Material unresolved variables include:

- formal post-pilot consortium decision process;
- funding and ownership structure;
- future operator;
- regulatory recognition / supervision;
- exact relationship with next-generation retail payments infrastructure;
- commercial model;
- exact role of participating banks;
- exact production technology;
- whether programme branding / legal structure changes.

These variables can alter implementation form.

They do not presently defeat the broader continuation/build claim.

169.10 Falsifier / Next Observable

The Strong Lean weakens materially if:

- UK Finance describes GBTD as ending after the 2026 pilots;
- participant banks materially withdraw;
- further digital-asset pilots are cancelled;
- the consortium enters a prolonged reassessment without an active 2027 build;
- regulators identify a structural blocker to interbank tokenised-deposit infrastructure;
- the programme is subsumed into another initiative in a way that terminates GBTD rather than continuing its work.

The Strong Lean strengthens if:

- UK Finance formally announces a 2027 build phase;
- operating-company / FMI governance is announced;
- funding / ownership commitments are disclosed;
- production participants are named;
- a formal implementation timetable is published.

Any qualifying post-freeze evidence is a U1 Evidence Update.

169.11 Resolution Rule

Hit

By 30 June 2027, authoritative evidence establishes that GBTD has entered an active post-pilot build, implementation or operationalisation phase for shared UK tokenised-deposit infrastructure.

A successor legal / operating entity may qualify if authoritative evidence establishes continuity of the GBTD programme and its shared tokenised-deposit infrastructure mission.

Miss

By 30 June 2027:

- GBTD has been paused or concluded after the pilots; or
- no active post-pilot build / implementation phase exists and the programme remains only exploratory / under indefinite reassessment.

Still Open

Use only if public evidence by the horizon is genuinely insufficient to distinguish active implementation from dormant / unresolved state.

Target Invalidated

Only if an external structural event transforms the UK payments landscape such that the frozen GBTD programme-state object ceases to be meaningfully resolvable.

169.12 Research Burden Signature

Evidence trajectory: narrow/direct multi-source target-local
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Moderate

169.13 Lead-time state

Initial Call: Strong Lean — 6 October 2026
First Lean-or-Better at scored specificity: 6 October 2026
Primary predictive lead-time clock: STARTED — 6 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 30 June 2027

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-023-v1 — GBTD post-pilot principal shared-infrastructure provider

Forecast ID / Version: PVR-023-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture / Provider Selection

178.1 Decision Object / Control Locus / ancestry

Decision Object: principal provider of the shared programmable-money / interoperability / orchestration technology layer for GBTD's post-pilot FMI build.

Decision-Control Locus: future GBTD operating / ownership structure and participating-bank governance, with UK Finance and public-policy / regulatory inputs.

Ancestry: UK RLN multi-vendor experimentation → Quant selected for GBTD live phase → live customer transactions on Quant-developed shared platform → post-pilot 2027 FMI build.

178.2 Use case / jurisdiction / horizon

Use case: shared interoperability, programmability and transaction coordination across bank-issued tokenised sterling deposits and connected payment / asset-settlement rails.

Jurisdiction: United Kingdom

Horizon: 31 December 2027

178.3 Primary Resolution Object

> Primary Architecture Slot: principal shared programmable-money / interoperability / orchestration technology provider for the post-pilot GBTD FMI build.

This does not require one provider to own every technology layer.

178.4 Principal Scored Claim

> Quant will remain the principal technology provider for GBTD's shared programmable-money / interoperability / orchestration infrastructure when the programme enters its post-pilot 2027 FMI build / production architecture.

178.5 Observability / permitted specificity

Observability State: O2 for post-pilot provider selection; O3 for current-provider ancestry and exact present role.

Permitted specificity: exact provider for the defined shared-infrastructure slot.

No official forecast is made on:

- exclusive single-vendor status;
- operating-company ownership;
- bank internal tokenisation engines;
- systems integrator;
- DLT / base chain;
- QuantNet versus Overledger versus another Quant product label;
- Fusion;
- QNT gas / staking / lockup;
- commercial contract value.

178.6 Call / Forecast Label

> LEAN — QUANT

Strong Lean is not earned.

178.7 Strongest Alternative

> The new GBTD operating / governance entity retains the functional architecture demonstrated in the pilot but re-procures or materially redistributes the production technology role, leaving Quant as a secondary / transition provider or replacing it with another principal shared-infrastructure provider.

A second alternative is a genuinely multi-provider production architecture in which no single provider occupies the principal role forecast here.

178.8 Load-Bearing Warrant

1. Exact target-specific selection

Quant was not merely adjacent to GBTD.

It was selected to provide the current programme's technology infrastructure.

2. Exact-role continuity

Quant's role is not generic DLT capability.

Its current function maps directly to the prospective slot:

- programmability;
- interoperability;
- orchestration;
- connection across bank systems / ledgers and existing payment rails.

3. Live implementation path dependence

UK Finance independently confirms that real GBTD customer transactions were executed on the shared platform developed by Quant.

The current system is therefore working infrastructure, not a prototype presentation.

4. Same programme / same participants

The post-pilot FMI is intended as the continuation of the GBTD programme rather than an unrelated greenfield initiative.

The same institutional participants have invested in and learned on the current platform.

5. Provider-field consolidation already occurred once

The earlier UK RLN experimentation used a broader technology team including R3, Quant, DXC and Coadjute.

The later GBTD programme selected Quant to develop the shared live platform.

That observed narrowing is stronger evidence than generic provider reputation.

6. Switching is possible but not free

A production provider change would need to preserve:

- participant integrations;
- existing programme logic;
- interoperability;
- programmability;
- regulatory / operational controls;
- current live workflows;
- future digital-asset settlement integration.

This creates meaningful path dependence.

7. But long-term governance is genuinely unresolved

UK Finance has stated publicly that:

- platform ownership / operating-company structure remains under development;
- industry ownership and governance are important;
- future critical infrastructure requires robust balance sheet, risk and operating capacity;
- the final company / commercial model remains a live design issue.

Those factors create a credible re-procurement / role-splitting path.

Therefore Quant is meaningfully favored, but not dominant enough for Strong Lean.

178.9 Material contradiction / private residual

Unresolved private variables include:

- future GBTD company formation;
- shareholder / ownership structure;
- procurement policy;
- technology-contract duration;
- commercial terms;
- operating-company risk requirements;
- production vendor due diligence;
- systems-integrator model;
- whether Quant's current role is transferred, re-contracted or competed;
- whether another provider becomes principal for a newly defined production layer.

178.10 Falsifier / Next Observable

The Lean weakens materially if:

- GBTD announces a competitive production-technology procurement that materially reopens Quant's slot;
- another provider is named for the shared interoperability / orchestration layer;
- Quant's role is explicitly described as pilot-only;
- the future operating entity adopts architecture incompatible with Quant's current principal role;
- the production stack splits the shared layer so no principal provider exists.

The Lean strengthens materially if:

- Quant receives a production / 2027 implementation contract;
- the future GBTD company identifies Quant as core technology provider;
- further 2026 / 2027 digital-asset transactions run on the Quant-built infrastructure;
- bank participants or UK Finance describe the existing platform as the foundation of the production FMI.

Any qualifying post-freeze evidence is a U1 Evidence Update.

178.11 Resolution Rule

Hit

By 31 December 2027, authoritative evidence establishes Quant as the principal provider of the shared programmability / interoperability / orchestration infrastructure for the post-pilot GBTD production / FMI build.

Quant may share the overall stack with systems integrators, bank technology, DLT providers or other specialist vendors and still qualify, provided it retains the principal role in the frozen architecture slot.

Miss

A different provider becomes principal for the defined slot, or the final production architecture materially distributes / replaces the role such that Quant is no longer the principal shared-infrastructure provider.

Still Open

If the GBTD post-pilot build remains active by the horizon but the principal provider is not publicly resolvable, the forecast remains unresolved / insufficiently observable rather than inventing a winner.

Target Invalidated

If GBTD is terminated or transformed before a post-pilot provider decision in a way that eliminates the frozen architecture slot, apply target-invalidation rules rather than manufacturing a provider miss.

178.12 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Moderate

178.13 Lead-time state

Initial Call: Lean — Quant — 6 October 2026
First Lean-or-Better at scored specificity: 6 October 2026
Primary predictive lead-time clock: STARTED — 6 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 December 2027

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-024-v1 — RBA near-term central-bank-money settlement architecture for tokenised wholesale finance

Forecast ID / Version: PVR-024-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 6 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture Selection

188.1 Decision Object / Control Locus / ancestry

Decision Object: principal near-term RBA architecture for settling tokenised wholesale assets and exchanging tokenised private money in central-bank money.

Decision-Control Locus: Reserve Bank of Australia, with Payments System Board / RITS Modernisation, financial-stability, industry and regulatory inputs.

Ancestry: CBDC pilot → Project Acacia → synchronisation / ESA and tokenised-reserve experiments → September 2026 RITS tokenisation consultation → 2027 broader RITS Modernisation consultation / design.

188.2 Use case / jurisdiction / horizon

Use case: wholesale tokenised-asset DvP and exchange of tokenised private money with settlement finality in Australian central-bank money.

Jurisdiction: Australia

Horizon: 31 December 2027

188.3 Primary Resolution Object

> Primary Architecture Slot: near-term central-bank-money settlement architecture connecting tokenised wholesale markets to the RBA.

188.4 Principal Scored Claim

> Through the next substantive RITS-modernisation / post-consultation architecture stage by 31 December 2027, the RBA will retain enhanced RITS/FSS settlement in existing central-bank reserves, connected to tokenised platforms through synchronisation/interoperability mechanisms, as the principal near-term architecture; tokenised central-bank reserves will remain exploratory, longer-term or supplementary rather than a co-equal or dominant production rail.

188.5 Observability / permitted specificity

Observability State: O3 for current architecture field, sequencing and policy direction; O2 for final detailed RITS-modernisation design.

Permitted specificity: architecture family.

No official forecast is made on:

- exact synchronisation operator;
- exact DLT;
- exact external platform;
- exact feeder / messaging technology;
- exact reserve-lock mechanism;
- final tokenised-reserve issuance design;
- long-run post-2027 architecture;
- any public crypto token.

188.6 Call / Forecast Label

> STRONG LEAN — RITS/FSS SYNCHRONISATION-CENTRIC NEAR-TERM ARCHITECTURE

188.7 Strongest Alternative

> Industry feedback and post-Acacia implementation evidence cause the RBA to accelerate tokenised central-bank reserves into a co-equal strategic production architecture during the 2027 design stage, rather than treating them as a later complement to synchronisation.

A weaker alternative is persistent strategic ambiguity with no architecture sufficiently established by the horizon.

188.8 Load-Bearing Warrant

1. Near-term / longer-term distinction is explicit

The September consultation itself makes existing-service support the primary near-term focus and tokenised reserves a longer-term capability question.

2. Synchronisation already works with the existing monetary core

Project Acacia demonstrated that DvP and private-token interchange can use existing ESA balances under synchronisation arrangements.

3. RBA leadership has articulated sequential architecture

The public policy sequence is:

> existing infrastructure / synchronisation first → deeper tokenised-reserve role if market scale and systemic importance justify it.

4. RITS is not a passive legacy system

The RBA is beginning a multi-year strategic modernisation programme for RITS.

That creates a live institutional path for adapting the existing authoritative settlement core rather than replacing it.

5. Formal tokenised-reserve decision is explicitly less mature

The RBA says formal decisions on issuance may take time.

That creates a material maturity asymmetry between the two paths.

6. Tokenised reserves remain a credible challenger

Their potential benefits are real and Project Acacia gave them practical evidence.

Therefore the forecast permits continued research, pilots and supplementary design without treating those developments as a miss.

7. Strong Lean is earned only at near-term architecture-family specificity

The call would not support:

- Strong Lean against eventual tokenised reserves;
- exact-vendor prediction;
- exact synchronisation design.

At the narrower near-term architecture-family level, the public sequencing is sufficiently dominant.

188.9 Material contradiction / private residual

Material unresolved variables include:

- consultation submissions;
- demand for 24/7 atomic settlement;
- whether existing RITS/FSS locking / reservation functions prove sufficient;
- industry preferences for tokenised reserves;
- liquidity-fragmentation costs;
- legal finality / operational resilience requirements;
- scale and speed of tokenised wholesale-market adoption;
- RITS Modernisation design constraints;
- cross-border use cases;
- financial-stability assessment of systemic tokenised markets.

188.10 Falsifier / Next Observable

The Strong Lean weakens materially if:

- RBA post-consultation documents elevate tokenised reserves into the main near-term implementation path;
- a funded tokenised-reserve production programme is announced for 2027;
- RITS/FSS synchronisation is judged insufficient for material target use cases;
- industry submissions reveal broad reliance on tokenised reserves that materially changes RBA sequencing;
- RBA's 2027 RITS Modernisation position shifts away from synchronisation as the principal connection model.

The Strong Lean strengthens if:

- the post-consultation roadmap funds RITS/FSS synchronisation enhancements;
- the 2027 RITS Modernisation consultation embeds tokenised-platform connectivity / reserve-locking / feeder improvements;
- tokenised-reserve work remains explicitly research / experimental;
- real tokenised-market deployments use RITS/FSS-linked synchronisation.

Any qualifying post-freeze evidence is a U1 Evidence Update.

188.11 Resolution Rule

Hit

By 31 December 2027, authoritative RBA policy, consultation output, funded design or implementation evidence establishes enhanced RITS/FSS plus synchronisation/interoperability with external tokenised platforms as the principal near-term architecture for central-bank-money settlement of tokenised wholesale activity, while tokenised reserves remain exploratory, longer-term or supplementary.

Miss

By 31 December 2027, the RBA commits to tokenised central-bank reserves as a co-equal or dominant near-term strategic production architecture for material wholesale tokenised activity, displacing the forecasted synchronisation-first sequencing.

Still Open

If the RBA has not established a sufficiently clear post-consultation architecture position by 31 December 2027 and neither path has become materially strategic enough for adjudication, mark Still Open rather than manufacture a resolution.

Target Invalidated

Only if a major external legal / institutional change removes the relevant RBA settlement-architecture decision object.

188.12 Research Burden Signature

Evidence trajectory: narrow/direct multi-source, overwhelmingly RBA primary evidence
Deep Research: No
Specialist modules: None
External resolver: None
Continuity burden: Ordinary
Burden Category: Moderate

188.13 Lead-time state

Initial Call: Strong Lean — RITS/FSS synchronisation-centric — 6 October 2026
First Lean-or-Better at scored specificity: 6 October 2026
Primary predictive lead-time clock: STARTED — 6 October 2026
Last-pre-resolution call: currently v1
Resolution: open
Horizon: 31 December 2027

Dated historical updates

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-025-v1 — Nasdaq Equity Tokens first live issuer-sponsored activity

Forecast ID / Version: PVR-025-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 7 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

206.1 Decision Object / Control Locus / ancestry

Decision Object: conversion of Nasdaq Equity Tokens (NETs) from approved market structure / commercial infrastructure build into at least one genuine live issuer-sponsored tokenised-equity implementation.

Decision-Control Locus: Nasdaq, participating issuer(s), Payward/xStocks distribution infrastructure, DTC/post-trade dependencies and applicable regulatory/operational controls.

Ancestry: Nasdaq tokenised-securities rule proposal → SEC approval → NET framework → Nasdaq/Payward strategic partnership → $100M Nasdaq Ventures investment → Q2 2027 launch target → first issuer-sponsored live NET.

206.2 Use case / jurisdiction / horizon

Use case: rights-preserving, issuer-sponsored tokenised equities distributed across regulated / onchain market infrastructure.

Jurisdiction: United States / global distribution interfaces.

Horizon: 30 June 2027

206.3 Primary Resolution Object

> Primary Maturity Milestone: at least one genuine issuer-sponsored Nasdaq Equity Token becomes operational for real market activity under the NET framework.

206.4 Principal Scored Claim

> By 30 June 2027, Nasdaq will make at least one Nasdaq Equity Token operational in real issuer-sponsored tokenised-equity activity under the NET framework, rather than remaining at design/integration stage.

206.5 Observability / permitted specificity

Observability State: O3 for programme direction, regulatory permission and target timing; O2 for issuer/onboarding readiness.

No forecast is made on:

- the first issuer identity;
- first tokenised stock ticker;
- exact public chain / settlement rail;
- first-day liquidity or volume;
- market share;
- any crypto-token investment implication.

206.6 Call / Forecast Label

> LEAN

206.7 Strongest Alternative

> Nasdaq remains committed to NETs, but issuer onboarding, DTC/post-trade integration, Payward/xStocks connectivity, operational readiness or commercial sequencing delays the first genuine live NET beyond Q2 2027.

206.8 Load-Bearing Warrant

1. The SEC approved Nasdaq's rule change on 18 March 2026, materially closing the core exchange-rule barrier to trading securities in tokenised form.
2. Nasdaq and Payward have an explicit NET infrastructure partnership rather than generic adjacency.
3. Nasdaq Ventures agreed to invest $100 million in Payward, creating meaningful commitment cost and strategic alignment.
4. Nasdaq states that operational and commercial infrastructure is being advanced with an expectation to launch NETs in Q2 2027.
5. Payward/xStocks provides relevant existing tokenised-equity distribution ancestry.
6. The principal remaining deficit is live issuer conversion rather than basic regulatory permission or project sponsorship.

The absence of a publicly named first issuer prevents Strong Lean.

206.9 Material contradiction / private residual

- first issuer not public;
- issuer legal/governance readiness;
- DTC/post-trade integration details;
- exact ownership-record synchronization;
- distribution restrictions;
- market-maker/liquidity readiness;
- production testing;
- exact launch sequencing.

206.10 Falsifier / next observable

The Lean weakens materially if Nasdaq revises the Q2 2027 target, issuer onboarding stalls, DTC integration is delayed, or NET architecture is materially redesigned.

The Lean strengthens with a named issuer, final issuance documentation, dated launch schedule, completed production integration or live onboarding/testing.

Any qualifying post-freeze evidence is U1.

206.11 Resolution Rule

Hit: by 30 June 2027, at least one genuine issuer-sponsored NET is operational for real market activity under the NET framework.
Miss: 30 June 2027 passes without qualifying production while the NET programme remains materially intact.
Still Open: only if authoritative evidence makes actual pre-horizon production status genuinely indeterminate.
Target Invalidated: only if an external change eliminates or materially transforms the frozen NET decision object.

A prototype, demo, infrastructure announcement, issuer intention without production, or unrelated tokenised-equity activity does not count.

206.12 Research Burden Signature

Evidence trajectory: narrow/direct primary + target-local corroboration
Deep Research: No
Specialist modules: None
Burden Category: Moderate

206.13 Lead-time state

Initial Call: Lean — 7 October 2026
First Lean-or-Better: 7 October 2026
Resolution: open

206.14 Source register

- SEC, Release No. 34-105047 / SR-NASDAQ-2025-072, 18 Mar 2026 — approval of Nasdaq tokenised-securities rule change: https://www.sec.gov/rules-regulations/self-regulatory-organization-rulemaking/sr-nasdaq-2025-072
- Nasdaq, 10 Sep 2026 — Payward expansion, $100M investment and Q2 2027 NET target: https://ir.nasdaq.com/node/110981
- Payward, 10 Sep 2026 — reciprocal NET infrastructure announcement: https://www.payward.com/press-release/payward-nasdaq-tokenized-equities

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-026-v1 — Project Pythagore first production NEU CP issuance

Forecast ID / Version: PVR-026-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 7 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

207.1 Decision Object / Control Locus / ancestry

Decision Object: conversion of Project Pythagore from development/pilot build into first production issuance of tokenised NEU CP with central-bank-money settlement through Pontes.

Decision-Control Locus: Banque de France + Euroclear France, with issuers, home agents, underwriters, investors, custodians and Eurosystem Pontes dependencies.

Ancestry: 2025 Pythagore launch → Euroclear DLT infrastructure build → Pontes implementation → Pontes live Sep 2026 → first production NEU CP issue → 2027 ramp-up → later market migration.

207.2 Use case / jurisdiction / horizon

Use case: tokenised short-term corporate debt issuance and settlement in wholesale central-bank money.

Jurisdiction: France / Eurosystem.

Horizon: 31 December 2026

207.3 Primary Resolution Object

> Primary Maturity Milestone: at least one production NEU CP security is issued through the Pythagore architecture by year-end 2026.

207.4 Principal Scored Claim

> By 31 December 2026, Project Pythagore will complete at least one production issuance of tokenised NEU CP on Euroclear's new DLT infrastructure with the cash leg settled in central-bank money through Pontes.

207.5 Observability / permitted specificity

Observability State: O3 for programme timing/architecture; O2 for final issuer/readiness state.

No forecast is made on:

- first issuer identity;
- issue size;
- exact transaction date;
- 2027 volume;
- full-market migration pace;
- any public crypto network/token.

207.6 Call / Forecast Label

> STRONG LEAN

207.7 Strongest Alternative

> Euroclear/Pontes interoperability, issuer onboarding, custody/servicing, legal or operational testing slips slightly and pushes the first production issue into early 2027 while the programme remains intact.

207.8 Load-Bearing Warrant

1. Pontes launched on 21 September 2026, closing a major cash-leg dependency.
2. Banque de France's current project page states the collective ambition is first issues in production by end-2026.
3. The same current page identifies a 2027 ramp-up phase and later market migration, distinguishing the 2026 production milestone from later scaling.
4. Banque de France Governor François Villeroy de Galhau reaffirmed on 2 October 2026 that Pontes central-bank tokens will enable settlement of tokenised NEU CP by year-end.
5. The market-design group already spans the relevant issuer/agent/investor/custody roles; issuers represented in the co-design group account for roughly half of NEU CP exposures.
6. The underlying NEU CP market is already large and operational rather than an invented sandbox asset class.

Contradictory historical signal

An earlier 2025/early-2026 formulation referred to an end-2026 pilot or later 2027 sequencing.

That contradiction is preserved, but later and more direct Banque de France evidence explicitly uses production / first-issue language and was reaffirmed days before freeze.

207.9 Material contradiction / private residual

- exact first issuer;
- final issue documentation;
- operational onboarding;
- custody/servicing workflows;
- Euroclear/Pontes production integration;
- legal/settlement edge cases;
- last-mile transaction readiness.

207.10 Falsifier / next observable

The call weakens materially with an explicit postponement into 2027, unresolved Pontes integration, issuer onboarding failure or reclassification back to pilot-only status.

The call strengthens with a named first issuer, production documentation, transaction date or Euroclear/Banque de France readiness confirmation.

Any qualifying post-freeze evidence is U1.

207.11 Resolution Rule

Hit: by 31 Dec 2026, at least one actual production NEU CP security is issued under Pythagore with the intended Euroclear/Pontes central-bank-money settlement architecture.
Miss: 31 Dec 2026 passes without qualifying production while the programme remains materially intact. A January 2027 first issue remains a Miss.
Still Open: only if authoritative evidence makes actual pre-horizon production status genuinely indeterminate.
Target Invalidated: only if an external change eliminates or materially transforms the frozen issuance object.

A demo, simulated trade, readiness announcement or Pontes-only transaction does not count.

207.12 Research Burden Signature

Evidence trajectory: narrow/direct primary-source path
Deep Research: No
Specialist modules: None
Burden Category: Moderate

207.13 Lead-time state

Initial Call: Strong Lean — 7 October 2026
First Lean-or-Better: 7 October 2026
Resolution: open

207.14 Source register

- Banque de France, Pythagore project page — current production timeline: https://www.banque-france.fr/en/pythagore-project-neu-cp-neu-mtn-market-modernization
- Banque de France, 2 Oct 2026 Governor speech — year-end settlement reaffirmation: https://www.banque-france.fr/en/governors-interventions/marking-our-tenth-anniversary-one-conviction-two-principles-and-three-challenges
- ECB, 21 Sep 2026 — Pontes launch: https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921~e754847a7b.el.html
- Banque de France, 2026 NEU CP tokenisation discussion: https://www.banque-france.fr/system/files/2026-06/DE_S1E13_ENG.pdf

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-027-v1 — Korea Securities Depository tokenised-securities production platform

Forecast ID / Version: PVR-027-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 7 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F3 — Maturity / Conversion

208.1 Decision Object / Control Locus / ancestry

Decision Object: conversion of KSD's tokenised-securities infrastructure from testbed / implementation into live production operation under South Korea's new statutory regime.

Decision-Control Locus: Korea Securities Depository with FSC/regulatory rulemaking, Samsung SDS implementation, participant connectivity and securities-industry dependencies.

Ancestry: statutory reform → 2024 functional analysis → 2025 testbed → 2026 production-platform contract → participant connectivity/testing → 4 Feb 2027 legal effective date → live Phase-1 operation.

208.2 Use case / jurisdiction / horizon

Use case: legally recognised tokenised issuance/registration and related securities-market infrastructure.

Jurisdiction: South Korea.

Horizon: 31 March 2027

208.3 Primary Resolution Object

> Primary Maturity Milestone: KSD's production tokenised-securities infrastructure is operational for live issuance/registration activity under Phase 1.

208.4 Principal Scored Claim

> By 31 March 2027, Korea Securities Depository's production tokenised-securities platform will be operational for live issuance/registration activity under South Korea's Phase-1 tokenised-securities regime.

208.5 Observability / permitted specificity

Observability State: O3 for legal/regulatory programme and implementation timing; O2 for exact participant / first-security readiness.

No forecast is made on:

- exact public blockchain;
- public crypto token;
- first issuer/security;
- early volume;
- long-run market share.

208.6 Call / Forecast Label

> STRONG LEAN

208.7 Strongest Alternative

> The legal regime takes effect but final subordinate rules, participant integration, scenario testing, security remediation or production-readiness issues delay KSD's live operating platform beyond Q1 2027.

208.8 Load-Bearing Warrant

1. Revised legislation is scheduled to take effect 4 February 2027.
2. FSC's September roadmap explicitly sequences securities firms and KSD infrastructure work ahead of that date.
3. FSC's 1 October subordinate-rule package is specifically designed to enable tokenised issuance/circulation from the legal effective date.
4. Samsung SDS holds the actual KSD production implementation contract.
5. The same implementation lineage already completed functional analysis in 2024 and a testbed in 2025.
6. Samsung SDS states the production system is targeted for completion by February 2027 and is intended for live transaction processing, not another testbed.
7. The remaining risks are final implementation/regulatory/participant readiness rather than project sponsorship or vendor discovery.

208.9 Material contradiction / private residual

- final subordinate-rule approval;
- participant connectivity;
- scenario testing;
- security / operational remediation;
- first live issuer;
- exact launch date within the statutory window.

208.10 Falsifier / next observable

The call weakens materially with legal-effective-date revision, KSD platform delay, failed participant testing, significant remediation or FSC postponement.

It strengthens with final rule adoption, testing completion, formal platform-opening confirmation or first live registrations.

Any qualifying post-freeze evidence is U1.

208.11 Resolution Rule

Hit: by 31 Mar 2027, KSD's tokenised-securities production infrastructure is open for actual live-market issuance/registration under Phase 1.
Miss: 31 Mar 2027 passes without qualifying production while the programme remains intact.
Still Open: only if authoritative evidence makes actual pre-horizon production status genuinely indeterminate.
Target Invalidated: only if an external legal/institutional change eliminates or materially transforms the frozen object.

A testbed, readiness statement or completed build without live-market operation does not count.

208.12 Research Burden Signature

Evidence trajectory: direct regulator + contracted implementation provider
Deep Research: No
Specialist modules: None
Burden Category: Moderate

208.13 Lead-time state

Initial Call: Strong Lean — 7 October 2026
First Lean-or-Better: 7 October 2026
Resolution: open

208.14 Source register

- Financial Services Commission, 4 Sep 2026 — policy roadmap / Feb 2027 regime: https://fsc.go.kr/eng/pr010101/87653
- Financial Services Commission, 1 Oct 2026 — subordinate-rule proposal: https://www.fsc.go.kr/eng/pr010101/87834
- Samsung SDS, 8 May 2026 — KSD production-platform contract / Feb 2027 completion: https://www.samsungsds.com/en/news/tk-260508.html

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-029-v1 — Bank of England Synchronisation Operator market structure

Forecast ID / Version: PVR-029-v1
Method: Institutional Architecture Forecasting v0.4
Freeze date / evidence cutoff: 7 October 2026
Cohort: Opportunistic Discovery
Forecast status: OFFICIAL PROSPECTIVE FORECAST
Task: F1 — Architecture Selection

210.1 Decision Object / Control Locus / ancestry

Decision Object: operating-market structure for the private Synchronisation Operator layer around the Bank of England's future live RT2 synchronisation capability.

Decision-Control Locus: Bank of England policy/service design and operator regulatory framework, with industry business-model and resilience inputs.

Ancestry: Meridian / Meridian FX / Meridian Securities → Synchronisation Lab → prospective SO business-model testing → 2027 policy/service design → future live RT2 Synchronisation service.

This forecast is distinct from:

- PVR-003, which scores whether live Synchronisation capability launches;
- PVR-016, which scores the broader long-term wholesale central-bank-money architecture.

Neither older forecast scores the operator-market structure.

210.2 Use case / jurisdiction / horizon

Use case: private-sector orchestration of conditional / atomic transactions connecting RT2 central-bank money to external asset/payment ledgers.

Jurisdiction: United Kingdom.

Horizon: 31 December 2027

210.3 Primary Resolution Object

> Primary Architecture Slot: market structure / operator model for the Synchronisation Operator layer.

210.4 Principal Scored Claim

> By 31 December 2027, the Bank of England's formal design for the live RT2 synchronisation service will preserve a plural private Synchronisation Operator model in which multiple qualifying operators can provide synchronisation services, rather than appointing one exclusive synchronisation operator or internalising the orchestration role into a single central utility.

210.5 Observability / permitted specificity

Observability State: O2/O3 at architecture-family level; exact winners O0–O1.

No forecast is made on:

- exact operator names;
- whether any tracked crypto company wins;
- exact number of operators;
- operator market shares;
- operator technology stacks;
- public-chain selection.

210.6 Call / Forecast Label

> STRONG LEAN — PLURAL / MULTI-OPERATOR PRIVATE-OPERATOR MODEL

210.7 Strongest Alternative

> Operational-resilience, regulatory-supervision, fragmentation or business-model concerns cause the Bank to converge on one privileged operator / single utility, or to internalise enough orchestration that private operator plurality ceases to be a meaningful architecture layer.

210.8 Load-Bearing Warrant

1. The Synchronisation Lab selected 18 organisations as prospective Synchronisation Operators across diverse use cases.
2. The Lab explicitly exists to test how multiple prospective operators interact with RT2 and to inform future live-service design.
3. Bank of England leadership has described the intended model as the Bank providing RTGS functionality while private-sector Synchronisation Operators develop and deliver specific products, explicitly linking this to competition and innovation.
4. The operating/legal concept anticipates operator-specific relationships/rulebooks rather than a single mandatory Bank-run orchestration utility.
5. Earlier Bank work explicitly considered single-versus-multiple-operator tradeoffs; monopoly risk to innovation is therefore a recognised architectural variable rather than an invented analyst alternative.
6. 2027 is a genuine policy/design observation window ahead of later live-service delivery.

The evidence supports architecture-family specificity, not provider selection.

210.9 Material contradiction / private residual

- final operator eligibility standards;
- prudential / operational-resilience regime;
- interoperability requirements among operators;
- economics of operating multiple services;
- whether one operator gains de facto dominance despite formal openness;
- legal liability / settlement-finality arrangements;
- exact 2027 policy timing.

210.10 Falsifier / next observable

The call weakens materially with:

- procurement for one exclusive operator;
- a Bank decision favoring one mandatory utility;
- formal internalisation of orchestration;
- regulation that in practice permits only one operator;
- explicit policy reversal on competition/plurality.

It strengthens with open eligibility/assurance standards, multiple formally qualified operators, separate operator rulebooks/contracts or explicit 2027 design language preserving operator competition.

Any qualifying post-freeze evidence is U1.

210.11 Resolution Rule

Hit: by 31 Dec 2027, authoritative Bank design/regulatory/implementation evidence establishes an open/plural framework allowing at least two genuinely independent qualifying private Synchronisation Operators to provide services.
Miss: the Bank selects one exclusive operator, creates one mandatory utility, or internalises orchestration such that private operator plurality is no longer a meaningful layer.
Still Open: the operating model remains publicly insufficiently specified by horizon.
Target Invalidated: only if an external change eliminates the Synchronisation Operator decision object itself.

210.12 Research Burden Signature

Evidence trajectory: ordinary multi-source target-local, dominated by direct Bank of England materials
Deep Research: No
Specialist modules: None
Burden Category: Moderate

210.13 Lead-time state

Initial Call: Strong Lean — 7 October 2026
First Lean-or-Better: 7 October 2026
Resolution: open

210.14 Source register

- Bank of England, Synchronisation Lab — 18 selected organisations / design aims: https://www.bankofengland.co.uk/payment-and-settlement/rtgs-future-roadmap/synchro-lab
- Bank of England, RTGS 2 speech — private operators / competition and innovation: https://www.bankofengland.co.uk/speech/2025/june/victoria-cleland-keynote-speech-at-the-uk-finance-digital-innovation-summit
- Bank of England, Wholesale experiments programme — 2027 reporting / 2028 live path: https://www.bankofengland.co.uk/payment-and-settlement/payments-innovation/wholesale-experiments-programme
- Bank of England, RTGS/CHAPS settlement-hours paper — multiple SO / external-ledger operating context: https://www.bankofengland.co.uk/paper/2026/cp/extending-rtgs-and-chaps-settlement-hours-next-steps

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-030-v1 — Bank of Korea Project Hangang Phase II broader public real-transaction resumption

Local forecast authority: Institutional Architecture Forecasting v0.4 Frozen Trial.
Entry date / evidence cutoff: 12 October 2026 (Asia/Seoul; no future observations used).
Entry status: NEW OFFICIAL PROSPECTIVE F3 FORECAST; frozen as v1.
Parent: Existing PVR v3.0 and 22 counted active official forecast objects are wholly untouched; this is a distinct, event-driven 23rd eligible prospective object, not a revision or outcome claim. PVR-030 was previously unused, and is assigned here for the first time.
Cohort: post-initial-cohort event-driven discovery; do not pool with original cohort for unfair pre-commitment coverage analysis.

Minimum official forecast record (v0.4)

1. Forecast ID / version / method: PVR-030-v1; v0.4 Lean Core; no specialist module.
2. Freeze date / cutoff: 12 October 2026, South Korea local date.
3. Decision object, locus and ancestry: Bank of Korea and participating domestic banks, within the Project Hangang Phase II monetary-infrastructure programme. Locus: central-bank coordination + bank rollout + existing financial-regulatory permissions. Ancestry: 2025 Phase I public real transactions → July 2026 expanded permissions → already operating government EV-charger subsidy use case → future wider general-public Phase II transactions. This is one programme and is not an independent platform-selection forecast.
4. Task: F3 — Maturity / Conversion.
5. Use case / jurisdiction / horizon: consumer-facing, bank-deposit-token real payment transactions using wholesale central-bank digital money infrastructure; South Korea; 31 December 2026.
6. Primary resolution object: The first renewed Phase II general-public real-transaction exercise distinct from the already operating EV-charger subsidy project, involving participating-bank deposit tokens used in actual payment/transfer transactions by users; not mere permission, registration, app demo or a new press statement announcing intent.
7. Principal Scored Claim: By 31 December 2026, the Bank of Korea and participating banks will resume at least one qualifying general-public, real-value transaction phase under Project Hangang Phase II beyond the already operating government EV-charger subsidy application.
8. Observability and specificity: O2–O3 for programme status/schedule, O1–O2 for precise bank rollout and actual participant activity. Forecasts timing of F3 milestone only. No forecast of exact public chain, coin, banks' transaction volumes, permanent issuance, commercial-scale conversion or retail CBDC adoption.
9. Call / label: LEAN — qualifying public Phase II real-value transaction resumption by 2026 year-end. This is an ordinal directional judgment, *not a numeric probability*.
10. Strongest live alternative: consumer-facing phase is deferred to 2027 or remains in technical/closed preparation, while the separately operating government subsidy project continues; risk could arise from bank integration, consumer protections, onboarding, technical/security readiness or coordination.
11. Evidence basis: (a) Bank of Korea, 8 October 2026, Office of Digital Currency article explicitly describing final preparations by BOK and participating banks for resumption of general-public follow-up real transactions within 2026; also distinguishes already operating EV subsidy; https://www.bok.or.kr/portal/bbs/B0000347/view.do?depth=201106&menuNo=201106&nttId=11065408&programType=newsData&relate=Y ; (b) Financial Services Commission, 15 July 2026, formal designation/additional approval of Gyeongnam Bank and iM Bank and amended authorizations for seven incumbent banks, broader wallets, merchants and transfer functions; https://www.fsc.go.kr/no010101/87338 ; (c) BOK 2025 Phase I report / 2026 Phase II programme source; https://www.bok.or.kr/eng/bbs/E0000654/view.do?menuNo=400048&nttId=10095216 . Secondary check: Yonhap July 2026 conditional launch reporting (not used as primary warrant).
12. Load-bearing warrant / contradiction / private residual: Direct originator timeline only four days old + specific regulatory expansion + real already operating Phase II government application + banks said to be in final preparation support a timely F3 Lean. Counterweight: the broader public phase had been anticipated earlier (September was discussed conditionally) and remained future as of Oct8, demonstrating schedule slippage risk. Number of live outside users, firm merchant/bank activation dates, test controls and any postponed gate remain private. The correct object is resumption of a new public testing episode, not Phase II existence; the latter is already known.
13. Falsifier / next observable: official BOK participating-bank notice or verified transaction evidence of public launch; or explicit revised start in 2027; test at 31 Dec 2026 and re-check in first two weeks January for dated evidence. No admission of a Hit without proof qualifying transfers occurred.
14. Resolution rule: Hit only if dated regulator/BOK/bank documentation (or equivalently direct robust transaction evidence) verifies general-public Phase II genuine transactions commenced by 23:59 Korea Standard Time 31 Dec 2026, and clearly separates that from 2025 Phase I and 2026 existing EV subsidy. Miss if reliable evidence establishes no such public Phase II transactions by deadline. If reporting lacks enough information to settle the condition, preserve Expired Unresolved and investigate rather than claim a Hit. No retroactive scope widening. Later 2027 transactions cannot rescue a missed 2026 deadline.
15. Burden signature / specialist: Ordinary multi-source, primarily Korean-language regulator/central-bank materials; translation cautiously interpreted; no Deep Research, no S1–S4 specialist, no external test; Moderate because of exact maturity disambiguation and non-English original. Native/simple announced-roadmap heuristic may reach same Lean, so zero demonstrated incremental method lift.

Prospective-integrity audit

- Outcome leakage: as of freeze Oct12, originator still says future public follow-up. Prior Phase I and Phase II subsidy actions explicitly excluded. No newly located public proof of qualifying broader public phase before cutoff. Searches cannot prove absolute absence; negative-evidence risk preserved.
- Decision ancestry: existing BoK programme, not multiple independent bank votes. No public-token attribution.
- Task integrity: F3, not F1 platform selection or F2 sovereign CBDC policy choice.
- Comparator: unexposed independent Native/Lean comparator not obtained, so no causal lift claim.
- Scoring: primary scored lead-time clock begins Oct12, only if forecast truly issued before a qualifying transaction. Initial call = first Lean = this v1; later evidence changes append a new version with U1/U2/U3/U4 class, never overwrite v1.
- Research stopping: current primary evidence is adequate for this narrow Lean; exact transaction dates require future observation, not another retrospective deep-research run. Reopen on verified pre-deadline launch, regulator delay, bank security block or change of task scope.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-031-v1 — ClearToken UK DSS first qualifying securities settlement 1. ID / method: PVR-031-v1; Institutional Architecture Forecasting v0.4 Lean Core; F3 maturity/conversion. 2. Prospective issue / cutoff: 12 October 2026 (UK local date); evidence is available through that date, excluding any later outcome. 3. Decision object/locus/ancestry: ClearToken CSD Limited, its contracting issuers and cash/settlement participants, within the Bank of England UK Digital Securities Sandbox. Commercial execution requires operator, clients and compliance; BoE gate permission does not itself create a transaction. Distinct from PVR-009 HM Treasury DIGIT/HSBC Orion and other HSBC CSD processes. 4. Task/primary resolution object: F3 — first qualifying, real funded securities issuance or transfer settled under ClearToken CSD's Gate 2 digital-securities-depository authority, not permit receipt or mere technical readiness. 5. Jurisdiction/use/horizon: UK; regulated tokenized securities issuance/settlement; 31 December 2027, UK local date. This is an analyst-chosen forecast horizon, not an originator-guaranteed go-live date. 6. One Principal Scored Claim: By 31 December 2027 ClearToken CSD Limited will have processed at least one publicly verifiable, legally effective, funded issuance or securities transfer involving a named eligible security and real institutional economic counterparties under its DSS Gate 2 authorization. The cash leg must be identified and lawful under applicable SAN conditions; it need not be a stablecoin or public Ethereum. 7. Observability/specificity: O2–O3 for regulatory authorization and firm launch statements, O1–O2 for first trade details. F3 first execution only, no exact-chain, settlement-stablecoin, CCP authorization or recurring volume forecast. 8. Call: LEAN. Concrete regulatory Gate 2 approval and explicit commercial build/Consensys partnership favor execution before end-2027, but first client transaction, cash agent, instrument and regulatory conditions are still uncertain. 9. Strongest alternative: ClearToken remains approved and builds infrastructure but first funded eligible issuer securities issuance/transfer is delayed beyond 2027, or adoption concentrates in its separate payment-services business without the CSD's settlement milestone. 10. Evidence basis: ClearToken 22 Sep. Gate 2 statement https://cleartoken.io/news/press-releases/cleartoken-approved-to-operate-a-digital-securities-depository-in-the-bank-of-englands-digital-securities-sandbox/ ; ClearToken and Consensys 8 Oct. partnership https://cleartoken.io/news/press-releases/cleartoken-and-consensys-partner-to-bring-24-7-settlement-infrastructure-to-wholesale-markets/ ; regulator DSS dashboard and operator-specific SAN referenced in Master v2.6. These documents establish eligibility and trajectory, not that the target event has occurred. 11. Load-bearing warrant/private residual: A named market-facing depository has a specific live-regulatory gate and technology partners; time to December 2027 permits practical commercialization. The unresolved economic participation, regulatory qualification, bank cash settlement, contracting, and final product design leave realistic failure routes. Standalone CCP authorization and a named stablecoin are not required for this narrow event. 12. Falsifier/next observation: A CSD-sanctioned securities transaction report with security ID, date, legal finality and actual consideration; alternatively a regulator suspension, conversion to payment-only service, or public delay. A press release without qualifying transaction information requires independent verification. 13. Resolution: Hit if qualifying dated independent issuer/ClearToken/BoE records demonstrate actual funded transaction by 23:59 31 Dec 2027 UK time. Miss if authoritative evidence establishes no qualifying transaction by deadline; absent publicly sufficient proof use Expired Unresolved pending checking, do not declare an unearned hit. Gate2 permission, Consensys collaboration, or other ClearToken entity transactions alone do not satisfy. 14. Other forecast constraints: Family/chain and ETH token impact explicitly not scored. Secondary cash-leg observations can be used in separate research but cannot rescue this F3 miss. 15. Burden signature: ordinary multi-source + SAN cross-reference; no deep research; no specialist S1–S4; Moderate. Simple roadmap/permission heuristic may reach the same Lean—no incremental-skill claim.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-032-v1 — SMBC Nikko / Nethermind DeFi Gateway functional milestone 1. ID/method: PVR-032-v1; Institutional Architecture Forecasting v0.4 Lean Core; F3 maturity/conversion. 2. Prospective issue / cutoff: 12 October 2026 (Japan local date). Existing October 2 announcement is antecedent; target future milestone is not counted today. 3. Decision object/locus/ancestry: SMBC Nikko and Nethermind, with Uniswap Labs and partners providing technology/commercial support; bank/securities regulatory and internal-controls dependencies. One single joint gateway programme, not independent partner wins. 4. Task/primary resolution object: F3 — a *demonstrably functioning* gateway implementation using Uniswap v4 liquidity pools with the proposed transaction compliance hooks; not a press statement that development is underway. 5. Jurisdiction/use/horizon: Japan; compliant onchain trading infrastructure; 31 December 2027, Japan local date (analyst horizon beyond publicly stated mid-2027 technical completion target). 6. Principal Scored Claim: By 31 December 2027 the SMBC Nikko–Nethermind DeFi Gateway will demonstrate an operational Uniswap v4-based pool/gateway implementation executing at least one verifiable end-to-end test trade with its intended compliance controls active. Permissioned sandbox/testnet qualification is allowed; this is not a claim of Japanese retail-customer production or scale. 7. Observability/specificity: O2 for public development and planned technical architecture; O1–O2 for verifiable detailed implementation evidence. Specificity limited to promised Uniswap v4 protocol family/technical F3 outcome, which was already publicly chosen and is not a novel F1 architecture-selection forecast. 8. Call: LEAN based on named institution, developers, source technology, controls design, stated mid-2027 build ambition and end-2027 buffer. Regulatory/user-facing production remains unproven. 9. Strongest alternative: project fails technical/integration/privacy/compliance acceptance or does not exhibit its promised controlled swap pathway by end-2027 despite continuing to publish technical work; or is materially redesigned away from Uniswap v4. 10. Evidence basis: Uniswap official 2 Oct. 2026 https://blog.uniswap.org/es-ES/smbc-nikko-and-nethermind-are-building-a-defi-gateway-for-japan-on-uniswap-v4 ; SMBC Nikko release linked from that originator statement. Do not construe a build announcement as live traded public securities. 11. Warrant/private residual: Real named parties and actual designed hooks make functional proof more likely than an unnamed speculative integration. Privacy/cyber, legal compliance and implementation dependencies can still derail even a public prototype. The forecast deliberately captures technical milestone at source-supported specificity. 12. Falsifier/next observable: named live demonstration with transaction record and functioning compliance checks, technical repo/demo, operator release; or confirmed project delay/rearchitecture/abandonment. 13. Resolution: Hit if dated primary operator/developer technical proof demonstrates actual execution with onchain or reproducible test evidence by 23:59 31 Dec 2027 JST. Prototype/test execution is acceptable; investor-funded production without demonstrable hook execution is not automatically a hit. Miss with authoritative noncompletion beyond deadline; if not ascertainable, Expired Unresolved until evidence adjudication. No retrospective narrowing/widening. 14. Secondary outcomes: real regulated Japanese investors actually fund trades, recurring depth, actual UNI fee/burn capture, Base fee exposure — none scored here. A separate commercial-conversion forecast needs independent evidence and event definition. 15. Burden signature: narrow originating-source research; no Deep Research or specialist activation; Light/Moderate. A standard declared-roadmap heuristic likely makes a similar forecast; predictive superiority not asserted.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-033-v1 — Ripple Prime real recurring XRPL post-trade settlement 1. ID / task / method: PVR-033-v1; F3 maturity / conversion; v0.4 Lean Core. 2. First forecast / cutoff: 12 October 2026, U.S. date. BatchV1_1 XRPL mainnet activation 9 October 2026 is already known antecedent evidence; no specific Ripple Prime production conversion is claimed to be established at the forecast freeze. 3. Actor / decision locus / ancestry: Ripple Prime, formerly Hidden Road, controlled by Ripple, with its outside prime clients and regulated clearing/settlement counterparties. One common Ripple-operated migration programme. Separate from Ripple Payments, Ripple Treasury and unrelated XRPL developers. 4. Primary milestone and horizon: F3 — *repeat real institutional post-trade economic settlement using XRPL Mainnet by 31 December 2027*. The end-2027 cutoff is analyst-selected, not a contractual go-live promise. 5. Single principal scored claim: By 31 December 2027, at least one existing Ripple Prime institutional prime-brokerage, clearing, financing, or post-trade service will process legally meaningful, real-value post-trade obligations through the XRP Ledger mainnet in repeat production, demonstrated across at least two separate calendar months and involving at least one genuine outside institutional counterparty. XRPL need not be the exclusive or majority settlement system; mere internal tests, demo asset transfers and exchange access do not qualify. Batch can support settlement but need not be used in every qualifying payment. 6. Observability and specificity: O2 for company-controlled programme and public XRPL feature status; O1–O2 for named internal client settlement attribution and legal nexus. Specificity: XRPL Mainnet exact network for F3, not a new F1 provider choice (Ripple already stated its target chain). No numerical >50% migration or exclusive-rail assertion. 7. Call: LEAN (first issue). Chain choice is directly declared by controlling owner, ownership/integration incentives are high, and XRPL now supports atomic operations up to eight inner transactions. Recurring qualified production in 14+ months is favored over zero conversion, but not certain. 8. Strongest credible alternative: Ripple Prime expands profitably through EDX, regulated futures, swap financing, broker accounts and bilateral/offchain netting while XRPL remains limited to pilots, treasury movements or externally unlinked transactions; regulatory/custody/clearing workflows delay material legal onchain settlement. The alternative is not Prime unexpectedly selecting Stellar. 9. Supporting dated sources: Ripple 8 Apr 2025 original Hidden Road announcement https://ripple.com/ripple-press/ripple-acquires-prime-broker-hidden-road/ ; Ripple 24 Oct 2025 acquisition close https://ripple.com/insights/ripple-closes-hidden-road-acquisition/ ; XRPL standards final XLS-56 https://github.com/XRPLF/XRPL-Standards/blob/master/XLS-0056-batch/README.md ; XRPLF xrpld v3.4.1 and fixBatchV1_2 enabled https://github.com/XRPLF/rippled/releases ; contemporary independent mainnet observation https://www.homannsoftware.com/2026/10/09/xrpl-batch-live-atomic-transactions-completion-evidence/ ; original Ripple-specific research handoff and Oct 12 Ledger. Batch is two to eight transactions per wrapper, not high-volume offchain compression itself. 10. Private-state uncertainties: exact clearing entity, netting architecture, legal title/finality recognition, counterparty consent, service launch gating, custody, privacy, whether any actual production footprint will be publicly linkable. A direct first-party company statement without identifiable business workflow should not be mistaken for traceable settlement proof. 11. Update triggers/falsifier: issuer/operator names participating institutions and shows actual ledger transaction and underlying service; multi-month recurrence; or public technical/regulatory failure, cancellation or explicit offchain-only policy. Scaled firm revenue on its own does not count. 12. Resolution: HIT when primary institution/participant records and/or credible externally corroborated transaction evidence demonstrate the frozen activity by 23:59 31 Dec 2027, U.S. Eastern; MISS on authoritative nonoccurrence beyond deadline; otherwise EXPIRED UNRESOLVED pending targeted public evidence audit. No qualitative one-off promotional narrative alone. A productive enterprise migration would strengthen the network thesis but not prove externally sourced XRP principal or balances: RLUSD and other issued instruments are separate. 13. Burden: ordinary multi-source + focused technical amendment comparison; no Deep Research / specialist module; Moderate. Baseline: announced company roadmap with owner-control incentive.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-034-v1 — Marketnode distribution of a BNY Investments fund on Stellar 1. ID / task / method: PVR-034-v1; F3 commercial distribution; v0.4 Lean Core. 2. First freeze: 12 Oct 2026; neither a named funded BNY fund token nor an outside investor position was confirmed in reviewed originating statements before cutoff. 3. Decision object / ancestry: BNY Investments fund manager and Marketnode platform/distribution entity with regulated fund administrator, custody and external institutional/accredited investors; distinct from Franklin Templeton BENJI, 21X Stellar, and DTCC Stellar. 4. Milestone / horizon: first verified funded outside investor participation in at least one specifically identified BNY Investments-managed fund represented/transacted on Stellar via Marketnode by 31 Dec 2027 (analyst deadline). 5. Principal scored claim: By 31 December 2027, Marketnode will facilitate at least one externally funded institutional or eligible accredited-investor position in a specifically named BNY Investments fund, represented by a live token on the Stellar network under a documented enforceable investor entitlement, not merely a zero-balance prototype or announced shelf capacity. The chain is an already named intended rail, not a hidden F1 choice. 6. Observability: O2 program/chain intent; O1–O2 live holders, subscription/accounting terms. No claim of chain-exclusive BNY distribution, legally authoritative share register residing entirely on Stellar, or XLM proportional demand. 7. Call: LEAN. BNY name, Marketnode operational distribution infrastructure, Stellar's mature regulated-token controls and explicit joint commercial statement favor first investor use within ~14 months. The strongest alternative is delay to fund/security documentation, distribution onboarding or a change to mere offchain mirroring/multichain access without externally funded Stellar positions. 8. Basis: Marketnode 31 Jul 2026 https://www.marketnode.com/knowledge/marketnode-to-offer-bny-investments-funds-on-stellar-network ; Marketnode current partner/programme gateway https://www.marketnode.com/gateway ; Marketnode institutional partner inventory https://www.marketnode.com/ ; historical Stellar fund rails https://stellar.org/solutions/real-world-assets . 9. Falsifier/update: named fund and issuer terms, token issuance and real investor receipt, subscriptions/redeems; cancellation or announced exclusive migration away from Stellar; no source should presume all BNY AUM is onchain. 10. Resolution: HIT if named issuer and/or Marketnode plus investor/fund servicing documentation substantiate a real funded entitlement connected to Stellar before year-end 2027 Singapore local; MISS on authoritative demonstrated lack of a qualifying event by deadline; otherwise EXPIRED UNRESOLVED. Sole press announcement without funded investor positioning fails. 11. Token attribution: Stellar adoption ≠ XLM-denominated invested principal; fee/reserve demand should be measured separately. 12. Burden: narrow/direct primary-source cross-check, no specialist modules, Light/Moderate; company roadmap simple challenger likely similarly confident.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-035-v1 — Bottomline's Chainlink-enabled Global Pay Connect first outside bank production 1. ID / task / method: PVR-035-v1; F3 institutional client conversion; v0.4 Lean Core. 2. Freeze date: 12 Oct 2026. Global Pay Connect was launched 17 Sep 2026, and Chainlink strategic integration is announced; no named independent bank's recurring onchain activity through this exact connector was confirmed in this work. 3. Control locus / ancestry: Bottomline operates Global Pay Connect, Chainlink operates interoperability components, independent adopting bank controls usage and settlement routing; one upstream integration programme, not 600 individually announced bank wins. 4. Milestone/horizon: first externally identifiable bank production cross-network onchain value/payment workflow via the Bottomline-Chainlink module by 31 Dec 2027 (analyst deadline). 5. Principal scored claim: By 31 December 2027, at least one separately named financial institution that is not Bottomline or Chainlink will publicly substantiate having sent or received repeat real-value payments or tokenized-bank-value transfers through Global Pay Connect's Chainlink-enabled connectivity in production, as distinct from using Bottomline only for traditional ISO 20022/Swift messaging. Repeat use means business activity on separate dates with material value, not a press demo. 6. Observability: O2 for released integration; O1–O2 bank-specific realized workflow; F3 not an F1 universal Chainlink award. Do not equate existing 600+ Bottomline bank customers or platform-wide $16T to Chainlink revenue/traffic. 7. Call: LEAN. Large incumbent bank-connectivity distribution and available launched module create a plausible first-customer funnel by end 2027. Strongest alternative: customers use Global Pay Connect solely for conventional cross-border connectivity, while chain modules see tests or compliance/procurement stalls. 8. Source: Bottomline 17 Sep 2026 official release https://www.bottomline.com/newsroom/press-releases/bottomline-launches-global-pay-connect-provide-financial-institutions-future-proofed-payment-messaging-ecosystem ; Chainlink 2.0 partner announcement https://chain.link/blog/introducing-ccip-2-0 ; canonical Ledger LINK-BOTTOMLINE-01. 9. Falsifier / next proof: named bank deployment release and actual production records; named bank rejects module or deployment delayed; lack of bank-specific evidence means unresolved, not a positive hit. 10. Resolution: HIT only on independently attributable bank production with real value, identified Chainlink connection and repeat usage by 31 Dec 2027 23:59 New York time; MISS on affirmative no deployment after cutoff, otherwise EXPIRED UNRESOLVED pending evidence audit. 11. LINK token fork: Chainlink service adoption does not establish how much vendor revenue flows through Payment Abstraction into LINK retained inventory. 12. Burden: ordinary vendor/partner release comparison, no Deep Research/specialists, Light/Moderate. Company-scale heuristic likely predicts some conversion also.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-036-v1 — Archax deploys a second independent-manager funded fund on Aptos 1. ID / task / method: PVR-036-v1; F3 fund product conversion; v0.4 Lean Core. 2. Freeze: 12 Oct 2026. Archax's March 2026 announcement established Aptos integration and first MembersCap fund pathway. It did not prove a *second independently managed qualifying fund* with external funded positions on Aptos. 3. Actor / ancestry: Archax as regulated issuance/distribution technology partner; fund's independently controlled manager/issuer, separate from Aptos Foundation and MembersCap. Do not count 100 supported assets as 100 Aptos issuances. 4. Milestone/horizon: first additional non-MembersCap externally funded regulated fund represented on Aptos via Archax by 31 Dec 2027 (analyst deadline). 5. Principal scored claim: By 31 December 2027, Archax will support at least one explicitly identified, legally eligible fund sponsored/managed by an institution independent of MembersCap and the Aptos Foundation, with a real externally funded ownership/exposure position represented and transferable through Aptos Mainnet. A copied listing, pre-minted empty asset, or a fund issued solely on Hedera/Cardano/Solana fails. 6. Observability: O2 for integration and product pipeline; O1–O2 live position investor/legal rights. Aptos is already chosen as one venue, so the new uncertainty is commercial conversion of an additional outside issuer, not an unexplained hidden new F1 chain selection. 7. Call: LEAN, close to Live Contender owing to no independently named next fund. Archax's established multi-manager regulated fund distribution on other networks, explicit Aptos integration, and 2026 announced funds/equities/debt pipeline favor at least one additional funded fund by late 2027. Opponent: Aptos remains a demonstration/first-sponsor-only lane while Archax deploys independent issuers on other chains and permissioning/market demand delay funding. 8. Evidence: Aptos/Archax 10 Mar 2026 originator https://aptosnetwork.com/currents/archax-integrates-with-aptos ; MembersCap press archive https://www.memberscap.com/press ; original Aptos audited report / Ledger APT chapter. 9. Falsifier / next event: fund manager-signed release, identified fund/security class, outside funded holders, Aptos issuance/address/trade, legal rights. A general 100-product compatibility claim is insufficient. 10. Resolution: HIT if first named independent-manager qualifying funded fund position on Aptos via Archax is evidenced before 23:59 31 Dec 2027 GMT; MISS if authoritative completion audit establishes no such funded fund by cutoff; otherwise EXPIRED UNRESOLVED until investigated. 11. Token fork: APT fee and staking demand do not rise proportionally with represented fund AUM absent explicit mechanism. 12. Burden: direct originator evidence plus comparative asset background, no Deep Research/specialist, Moderate. Roadmap-vs-delivery baseline should be kept as comparator.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-037-v1 — Ripple Prime cross-asset XRPL post-trade operating depth Task and governance: F3 maturity/depth; Ripple Prime/Hidden Road legal operating entities control prime-brokerage and clearing processes, external participants control their own participation, XRPL consensus controls ledger behavior. This is a descendant of PVR-033-v1, not an independent new customer/programme ancestry. A PVR-033 hit does not imply a PVR-037 hit, and both hits may not be double-counted as two independent Ripple adoption decisions.

Freeze: 12 Oct 2026. Deadline: 31 Dec 2027 23:59 New York time. Observability: O2 for corporate roadmap/technical capabilities and customer commercial relationship; O1 for XRPL-attributed real post-trade across asset classes. Specificity: named network XRPL (already selected/intended), actual *depth and breadth of settled obligations* is unresolved.

PRINCIPAL SCORED CLAIM — LEAN: By December 31, 2027, Ripple Prime will operate qualifying real-value XRPL Mainnet post-trade settlement workflows relating to both (A) digital-asset trading or financing and (B) at least one non-crypto traditional financial instrument category—such as FX, securities financing or equity/derivative exposures—with repeat qualifying production use on three separate calendar months, involving at least one externally controlled institutional client or counterparty. Cash may settle in RLUSD or another issued asset; XRP need not be the settlement principal. Off-chain trade matching, risk and netting are allowed, but the final economically relevant obligation or ledger-controlled payment/transfer must occur on XRPL. Merely emitting audit hashes, test tokens, transfers between Ripple treasury addresses, RLUSD for generic payments, or an occasional demonstration does not qualify.

Why we lean: Ripple's controlling acquisition provides incentive and implementation power, and its April 2025 institutional announcement expressly directed Hidden Road post-trade activity toward XRPL. The 9 Oct 2026 activation of BatchV1_1 enables groups of up to eight transactions as one all-or-nothing operation, useful for net-settlement outputs or linked DvP legs. Ripple's 6 Oct 2026 Brevan Howard deal expands actual multi-asset external customer reach. Public June 30 holdings establish large XRP treasury exposure, though the economics of a user-owned asset cannot be assumed to dictate customer obligations. Ripple Prime's existing May 2026 EDX collaboration shows operational capacity for conventional net settlement alongside other rails. The thesis is cross-asset selective migration, not an assertion all conventional accounts vanish.

Strongest alternative: Ripple Prime commercially grows multi-asset brokerage but retains most non-crypto legal clearing/settlement in legacy systems and uses XRPL only for cryptocurrency-specific or RLUSD collateral/account demonstration. Legal netting, customer custody, confidential infrastructure, and institutional change-management may inhibit the cross-asset conversion by deadline.

Decisive proof and falsifier: institution-authored Ripple Prime and at least one external participant statements describing on-XRPL production by asset class and separated dates; legal/operating descriptions, attributable XRPL settlement records, independent custodian/trade reports. A public XRPL token alone is insufficient. Confirmed digital-only conversion with no qualifying noncrypto production through deadline would MISS this *cross-asset* claim, even if PVR-033 wins. If the full operating event remains materially unobservable, do not manufacture a hit from inference; adjudicate Expired Unresolved under the frozen rule after reasonable evidence search.

Research and comparative burden: moderate target-local primary research; no conditional specialist module. Simple company-owning-the-ledger roadmap heuristic is a credible comparator, not treated as evidence of unique forecasting-method lift. Token economics: distinguish (a) legal settlement of RLUSD/principal, (b) XRPL transaction fees paid in XRP, (c) voluntary XRP liquidity inventory, (d) Ripple-owned XRP holdings and price/reflexivity.

Primary source anchors: Ripple acquisition statement (Apr 8, 2025) https://ripple.com/ripple-press/ripple-acquires-prime-broker-hidden-road/ ; Ripple–EDX (May 19, 2026) https://ripple.com/ripple-press/ripple-prime-partners-with-edx-to-bridge-institutional-access-to-digital-asset-liquidity/ ; Brevan Howard (Oct 6, 2026) https://ripple.com/ripple-press/ripple-and-brevan-howard-deepen-relationship/ ; Ripple XRP treasury snapshot (Jun 30, 2026) https://ripple.com/xrp/ ; XRPL protocol (Batch) https://xrpl.org/docs/references/protocol/transactions/types/batch ; XRPLF Oct 9 security activation report https://xrpl.org/blog/2026/vulnerabilitydisclosurereport-bug-20261009 .

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-038-v1 — DTC Tokenization Service reaches two asset classes on Stellar Task: F3 commercial breadth; DTC/DTCC controls tokenization service and eligible DTC books; participant custodians and issuers control which legally eligible assets they use. Same DTC Tokenization Service programme ancestry as PVR-006 (service launch) and PVR-018 (additional chain No Call), but different resolved maturity proposition. This is NOT evidence of a previously hidden Stellar selection—DTCC announced Stellar on 27 May 2026.

Freeze: 12 Oct 2026. Deadline: 31 Dec 2027 New York time. Observability: O2 for DTCC and SDF network architecture, O1–O2 for asset-class-specific funded transfer operations. PRINCIPAL SCORED CLAIM — LEAN (higher risk): By December 31, 2027, DTC's regulated Tokenization Service will have represented and processed qualifying participant-directed token movement on Stellar Mainnet involving actual DTC-custodied securities in each of two distinct asset categories: (1) U.S. Treasury bills/notes/bonds and (2) U.S.-listed equities or index-tracking exchange-traded funds. For each category the record must establish real DTC-eligible assets, legal entitlements, production movement/holder state and DTCC attribution to Stellar, not merely framework connectivity or unbacked demo assets. Two categories can be used by the same DTC participant but must each have a qualifying real tokenized holding/transfer.

Why we lean, with explicit uncertainty: DTCC selected Stellar as a planned second major public-network connection, targeted asset availability in H1 2027, and publicly identified precisely these two eligible asset families for evaluation. May 2026 DTCC industry-working-group development, July real production trades and a standards-first multi-network service create capacity to expand beyond only Treasury representation. There is still an important source-based legal/technical limit: DTCC's March 2026 FAQ says that, at service launch, securities transactions will not be settled in digitized form; some corporate-action activity remains offchain. Thus our claim is qualified onchain DTC token holdings/transfers, not an atomic onchain cash-versus-security settlement or a claim that the public chain replaces DTC's ultimate account controls.

Strongest alternative: Stellar integration slips to late 2027; only U.S. Treasuries enter production on Stellar; listed equity/ETF eligibility, custodian onboarding or participant demand is delayed; other networks take first activity in the second class. Falsifier: an issuer/venue listing or a DTC service launch on Canton, with no qualifying equity/ETF plus Treasury token movement on Stellar by deadline, fails. Resolution: require DTC, participating broker/custodian, official service records or independently corroborated chain records demonstrating DTC origin and both classes. No positive score from unverified token lookalikes. If no sufficient independent proof to adjudicate absence, Expired Unresolved, not retroactive success.

Burden: moderate multi-primary crosswalk; no Deep Research or formal modules. Base-rate company-roadmap heuristic strongly favors at least a Treasury token; broader *two-class Stellar* use is the exposed risk. Token separation: tokenized securities balances are not XLM-denominated institutional holdings; XLM captures network resource/fee reserves only unless separate inventory exists.

Primary sources: DTCC May 27 Stellar launch https://www.dtcc.com/press-releases/2026/tokenization-service-to-connect-with-stellar-public-blockchain-as-dtc-advances-multi-chain-strategy ; DTCC May 4 industry group https://www.dtcc.com/press-releases/2026/dtcc-advances-development-of-new-tokenization-service ; DTCC July production milestone https://www.dtcc.com/press-releases/2026/dtcc-turns-tokenization-into-reality ; DTCC March FAQ https://www.dtcc.com/-/media/Files/Downloads/digital-assets/dtc-tokenization-service-faq.pdf .

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-039-v1 — Fiserv/Solana Roughrider reaches an actual ten-institution operating cohort Task: F3 institution uptake and repeat real funding; controlling programme ancestry is Fiserv Digital Asset Platform + Bank of North Dakota Roughrider, with licensed stablecoin issuer VersaBank, Fireblocks, and independently governed North Dakota bank/credit-union adopters. Fiserv chose Solana already; the question is actual bank activation and repeat funded money movement. This is a different conversion object from general Fiserv platform launch, which occurred Oct 1.

Freeze: 12 Oct 2026. Deadline: 31 Dec 2027 North Dakota local time. Observability: O2 for named platform/network and eligible financial-institution network; O1–O2 for participant-by-participant realized operations. PRINCIPAL SCORED CLAIM — LEAN (higher risk): By December 31, 2027, at least TEN distinct independent North Dakota-eligible regulated banks or credit unions, excluding Bank of North Dakota and the issuing/reserve-service entity VersaBank, will have completed genuine funded bank-to-bank Roughrider Coin transfers using Fiserv infrastructure and Solana settlement, and the programme will have evidenced such funded bank transfers in at least TWO separate calendar months. Count distinct legally governed bank/credit-union entities, not consumer user accounts, branches, wallets, announced eligibles or controlled subsidiaries of the same bank.

Why we lean: Fiserv itself declared the platform live with financial institution clients Oct 1, and described Bank of North Dakota's already launched real use case. The platform uses Solana for transaction processing and embeds custody/integration into bank-familiar Commercial Center; the eligible state network encompasses over 90 banks/CUs. These are real distribution advantages. Our claimed conversion ratio is at least ten genuinely active institutions, not '90 active' and not the trivial 'a second bank tried it.'

Strongest alternative: formal availability does not become broad funded bank usage; operational risk, reserve/settlement economics and conventional rails inhibit activation; bank counts remain undisclosed and existing customers merely retain eligibility. Falsifier: by deadline no attested ten actual distinct institutions plus repeat calendar-month transfer activity. Resolution: Fiserv, BND, regulator, VersaBank or independent participating-bank aggregate certification explicitly verifying number of active bank/CU entities and real funded transactions on Solana, with at least two dated months. An aggregate credible independent audit with stated counting methodology can qualify; generic 90+ eligible statement cannot. Evidence may be commercially private; preserve Expired Unresolved if fact cannot be established rather than guessing or treating silence as proof of a miss.

Burden: moderate institutional adoption verification; no specialist module. Token separation: use of Solana for settlement incurs SOL-denominated network fees but does not prove institutions buy persistent SOL balances or that dollar transfer principal is SOL demand.

Primary sources: Fiserv live Oct 1 https://investors.fiserv.com/news-releases/news-release-details/fiserv-digital-asset-platform-goes-live-financial-institution ; Fiserv original Roughrider announcement Oct 8 2025 https://investors.fiserv.com/news-releases/news-release-details/bank-north-dakota-and-fiserv-partner-launch-roughrider-coin .

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-040-v1 — Two DISTINCT Ripple operating business families convert real value to XRPL 1. Forecast ID / Version / Method: PVR-040-v1; Frozen Institutional Architecture Forecasting v0.4 / Lean Core. 2. Freeze / evidence cutoff: 12 October 2026; first formal issue of THIS two-family depth target. 3. Decision object / control / ancestry: Ripple-controlled/managed institutional product operations across Prime, Payments, Treasury and tokenized capital-markets servicing, conditioned on externally governed clients, issuers and legal settlement parties. Distinct umbrella *business-family breadth* outcome. Dependent on already frozen PVR-033/PVR-037 for Prime events and the independent Payments/finance branches; never count common transactions twice. 4. Task: F3 — independently attributable commercial adoption maturity, NOT an undisclosed chain-selection F1. 5. Use / jurisdiction / horizon: Global Ripple commercial clients and XRPL Mainnet; deadline 31 December 2027 23:59 U.S. Eastern (analyst-set). 6. Primary Resolution Object: Repeat economically effective XRPL/Mainnet activities in at least TWO DISTINCT existing Ripple-operated/orchestrated institutional business families. Eligible families: (A) Prime post-trade/clearing/financing; (B) enterprise Ripple Payments corridor under Ripple product routing; (C) Ripple Treasury third-party-initiated fund movements; (D) issuer/fund servicing in which Ripple's integrated platform/partner controls live issuance/redemption/financing, beyond one-off token creation. A single transaction repackaged in two brands counts only once. 7. Principal Scored Claim: By 31 Dec 2027, at least TWO eligible distinct Ripple-involved business families will each evidence actual externally financed XRPL Mainnet production financial activity across at least TWO separate calendar months, with at least TWO separately controlled external institution/customer counterparties across the complete qualifying set. Settled cash/security/collateral effect must exist, not a custody wallet install or press announcement. 8. Observability / permitted specificity: O2 public business launch, O1–O2 for chain-attributed customer financial activity; can claim exact XRPL chain but NOT 50% of Ripple company's total dollar volume or XRP token acquisition. Private firm volumes/counterparty identities may impair final scoring. 9. Call / label: LEAN (speculative, material breadth/depth); directional yes. Multiple existing business routes and parent incentives favor two qualifying production lines, but proof of separate lines with independently financed repeat clients is missing and ambitious. 10. Strongest alternative: Ripple Prime reaches some XRPL output, while Payments/Treasury remain conventional, another chain or internally netted; tokenized-fund/single issuer activity remains too small to meet second repeat family; headline integrated business revenue grows without two on-XRPL financial lines. 11. Evidence basis / controlling sources: Oct12 Ledger XRP chapter and stable IDs; 9 Oct full Ripple-to-XRPL handoff; Ripple Hidden Road Apr 2025, Bitso June 2026, Treasury Apr 2026, ZILO/Licuido Aug 2026, CSD BR Sep 2026, XRPL October Batch activation (sources in Master §4). Do not treat BNY BUIDL RLUSD redemptions on another chain as XRPL activity. 12. Load-bearing warrant / contradictions: Corporate control + explicit original migration, available batching/permissioned market rails, Bitso corridor work, original financial-software customer access. Contradiction: Ripple services are multichain/conventional, custody often omnibus, collateral mirroring may not move RLUSD, fund rights may remain with offchain TA/CSD, customer consents unknown. 13. Falsifier / trigger: Authoritative year-end 2027 record demonstrates fewer than two qualifying business lines, sole demo/pilot, or no external recurring cash/asset flow. Upgrade triggers: independently named repeat XRPL Mainnet Prime and Ripple Payments/Treasury/issuer client confirmations on dates in two months each. 14. Resolution rule: HIT only upon eligible independent primary-source plus traceable economic/chain corroboration proving two families' recurring production, ≥2 independent institution/customer counterparties and proper months by horizon. MISS only upon sufficiently authoritative contrary evidence; otherwise EXPIRED UNRESOLVED after targeted evidence investigation. Prime-only success never suffices. Independent institutions may use an agent to sign, but must have externally controlled economic exposure. 15. Burden signature / modules: Moderate, 4-company-locus/source crosswalk and ledger attribution; no specialist module. A straightforward own-platform roadmap heuristic is a strong baseline comparator. Token economics: actual XRPL transfers vs XRP use/standing balances/market buying separated.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-041-v1 — RLUSD / MXNB U.S.–Mexico regulated enterprise payments on XRPL 1. ID / method: PVR-041-v1; v0.4 Lean Core. 2. Freeze date: 12 October 2026. 3. Decision/control/ancestry: Ripple Payments + Bitso Business, Mexican peso stablecoin issuer/market makers and independently controlled enterprise sending/receiving clients; specific descendant of Ledger XRP-BITSO-MXNB-01 / research XRP-F04, may count as one family satisfying PVR-040 but NOT two independent case wins. 4. Task: F3 funded cross-border payments/cash-leg maturity, NOT F1 first chain disclosure. 5. Use/jurisdiction/horizon: USD/MXN enterprise corridor, XRPL Mainnet PermissionedDEX or permissioned access architecture; by 31 December 2027 23:59 Mexico City time. 6. Primary Resolution Object: funded Ripple Payments enterprise currency exchange/settlement using BOTH XRPL-based RLUSD and MXNB as onchain value legs; two actual separate institution/customer-controlled senders/beneficiaries required. 7. Principal claim: By end 2027, at least TWO independent enterprise/bank payment customers will have performed settled real-value RLUSD↔MXNB enterprise corridor exchanges using XRPL Mainnet's authorized DEX/access infrastructure with qualifying funded operations in at least THREE separate calendar months. Token listing, self-churn transfers and single synthetic demo do not count. 8. Observability/specificity: O2 on product/pair intent, O1 on enterprise users, volumes and exact routing; exact chain XRPL known. Cannot assume all corridor payments are XRP-bridged. 9. Call: LEAN (demand-conversion bet): mature Ripple-Bitso relationship, specific announced RLUSD/MXNB architecture and regulatory design support rollout, despite real unresolved external client adoption. 10. Alternative: conventional fiat cross-border routing persists; MXNB/RLUSD issuance exists but DEX volumes remain immaterial/demo-only; trade converts off XRPL or avoids permissioned book architecture; customer onboarding slow. 11. Evidence sources: Ripple 9 June 2026 / public June 11 primary announcement https://ripple.com/ripple-press/ripple-and-bitso-expand-partnership/ ; Ledger XRP-BITSO-MXNB-01, XRP-PDEX-AUTOBRIDGE-01, XRP-PDEX-DIRECT-PAIR-BYPASS-01; 9 Oct XRPL handoff §5.2. 12. Warrant & contradiction: specific local-currency stablecoin and existing enterprise corridor provide real business motivation; permissioned counterparty onboarding, liquidity, FX spreads, regulatory approvals, competition and choice of settlement legs are substantial unknowns. XRP bridge/liquidity not guaranteed by direct pair usage. 13. Falsifier/trigger: no bank/enterprise client Mainnet RLUSD/MXNB authorized settlement use across three months; announcement-only pair; demonstrable abandonment. Watch pair and trust-line issuer addresses, approved counterparty participation, external client descriptions and dated settlement cycles. 14. Resolution: HIT on public first-party Ripple/Bitso/client statement or auditable verified ledger data establishing two separately governed customers, three dated calendar months and real USD/MXN commercial conversion; no assumption that market maker self-swaps count as end-customer demand. MISS with confirmed below-threshold result; otherwise EXPIRED UNRESOLVED when customer/route privacy blocks adjudication. 15. Burden: Moderate with customer/counterparty forensic cross-check; no specialist module. Token separation: RLUSD/MXNB not equivalent to sustained XRP liquidity or externally funded buying.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-042-v1 — CSD BR shifts from *record mirroring* to *native securities use on XRPL* 1. ID/method: PVR-042-v1; v0.4 Lean Core. 2. Freeze date: 12 October 2026, after official Sep 29 2026 CSD BR/Ripple phase-one disclosure; native CRI/CRA trade not established as of cutoff. 3. Decision/control/ancestry: CSD BR Brazilian regulated FMI and its authorized issuance/trading participants, with issuer/originator, asset custodian and relevant Brazilian regulator. A distinct institution from Ripple Prime; working index IFC-049 and research XRP-F01 CSD BR mirror-family descendant. Ripple vendor cannot unilaterally satisfy legal authoritative issuance/settlement. 4. Task: F3 consequential regulated native asset/trading expansion following initial mirror; NOT forecast of prior XRPL selection. 5. Use/jurisdiction/horizon: Brazil regulated securities (CRI/CRA real estate or agribusiness receivables securitizations), XRPL Mainnet; 31 December 2028 23:59 São Paulo time (longer analyst horizon due to legal constraints). 6. Primary Resolution Object: XRPL-based securities tokens as operationally effective security interests/transferable regulated positions under CSD BR's authorized arrangements, involving primary issuance or conversion and real transfer/trade to an economically independent authorized institution. Cannot remain solely an immutable mirror/audit record of movements executed exclusively at CSD BR. 7. Principal claim: By end 2028, CSD BR and at least one separately governed Brazilian issuer/originator will enable actual XRPL Mainnet issuance of a qualifying regulated CRI or CRA tokenized security, followed by at least ONE real-value legally operative transfer or trade between TWO separately governed authorized participant firms, under CSD BR's documented regulatory/operating rules. A mirroring of BTG funds alone does not satisfy. Even if CSD BR maintains an authoritative registry, the XRPL transaction must do more than copy a finalized offchain movement: documented effective asset or participant position change resulting from the XRPL operation. 8. Observability/permitted specificity: O2 first-phase operating and roadmap, O1–O2 legal impact/participant onchain trade; F3 named XRPL chain, not newly undisclosed selection. Regulated confidentiality and rulebook can obscure proofs. 9. Call: LEAN, deliberately ambitious / borderline: CSD BR itself identifies native issuance and authorized trading as next phases, CRI/CRA specifically, and already built a regulator-compatible onchain phase with BTG; but no dated binding contract for this outcome and further legal/operational requirements can block. This is more uncertain than a routine launch prediction. 10. Strongest alternative: conservative mirror layer remains dominant; CRI/CRA rights/title and authorized trades remain only in CSD BR's conventional registry, with XRPL for audit; other token rails win actual transfer activity, or licensing/investor demand delays the rollout beyond 2028. 11. Evidence source: CSD BR/Ripple first-phase Sep 29, 2026 original official statement https://ripple.com/ripple-press/csdbr-and-ripple-use-the-xrpl-blockchain-to-expand-brazils-financial-market-infrastructure/ (sections HOW THE MODEL WORKS; NEXT STEPS). Canonical Ledger XRP-CSD-BR-BTG-MIRROR-01 and Ripple handoff §5.4. 12. Load-bearing warrant/contradictions: CSD BR operates regulated depository/settlement infrastructure, has purpose-built authorized XRPL asset controls and explicitly sketches CRI/CRA native issuance/trading. But current regulated state deliberately preserves official record offchain, technology is permissioned, authorization and investor demand are uncertain; issuance ≠ secondary trade. Longer end-2028 mitigates near-term gating without eliminating uncertainty. 13. Falsifier/update: documentary statement that native CRI/CRA issuance/participant onchain trading is cancelled, left solely to mirror, or not operational by cutoff; named issuer, registry contract changes, first funded subscriptions, independent participant asset transfer and ledger transaction constitute triggers. A single fund-share mirrored hash is no evidence of this claim. 14. Resolution: HIT only on CSD BR/issuer/participants' first-party evidence plus legally effective operating arrangement and XRPL Mainnet activity proving BOTH genuine native CRI/CRA asset and independently controlled participant transaction by cutoff. MISS on authoritative failure/nonoccurrence, otherwise EXPIRED UNRESOLVED if confidentiality prevents proof. No inference from CSD BR's BRL 22T assets that any such notional is on XRPL. 15. Burden: Moderate/Heavy, require primary Brazilian legal/CSD record and operational trade checking; specialist modules not activated without a precise unresolved legal dispute. Strong potential Deep Research referral if source opinions diverge about whether onchain trade can be legally authoritative. Token implications remain XRP transaction fees / optional market-liquidity inventory, NOT automatic XRP demand from security notional.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-043-v1 — DTC Canton moves beyond a scheduled integration into repeat participant activity 1. ID / method: PVR-043-v1; Institutional Architecture Forecasting v0.4, Lean Core. 2. Freeze / evidence cutoff: 12 October 2026; newly issued claim, not backdated to previous Canton selection. 3. Decision / owner / ancestry: DTC/DTCC service operators plus independently governed DTC participant firms choosing to transfer DTC-custodied tokenized securities on Canton; DTCC–Digital Asset original 2025 selection and July 2026 limited transactions are PREDECESSOR EVIDENCE, not prospective wins. 4. Task: F3 substantive adoption depth; NOT F1 new chain choice and NOT PVR-006 service launch. 5. Use / place / horizon: real DTC-custodied U.S. Treasury/equity/ETF token transfer activity attributed to Canton Network, by December 31, 2027 New York time. 6. Primary resolution object: sustained independent participant use on Canton within DTC's regulated tokenization service after general service opening. 7. Principal scored claim: By end 2027, at least THREE independently governed DTC participant firms will each have conducted at least ONE real-value, participant-directed DTC Tokenization Service movement of eligible DTC-custodied securities on Canton; qualifying participant activity will have occurred in at least THREE distinct calendar months after 12 October 2026. One omnibus agent signing for distinct participants is acceptable if underlying economic and participant attribution is independently evidenced. July 2026 one-day production event excluded, as are self-churn demos. 8. Observability / limits: O2 public asset service and Canton rail; O1 for exact participant and month count. Aggregate DTC certification of number of truly active distinct participant legal entities can suffice; raw private Canton privacy views may prevent public adjudication. Avoid assuming Canton activity implies ordinary fee-bearing public Global Synchronizer traffic or CC burn. 9. Forecast: LEAN — meaningful adoption, not just capability. Named initial rail, major participant engagement and DTC strategic commitment favor broadening; 3 real independently controlled users over multiple months is not promised. 10. Strongest alternative: technically available Canton rail has few funded users; activity on Stellar/AppChain or offchain DTC records dominates; no independent adoption details surface. 11. Primary evidence: DTCC/DA initial Treasury partnership (2025) https://www.dtcc.com/press-releases/2025/dtcc-and-digital-asset-partner-to-tokenize-dtc-custodied-us-treasury-securities ; May 2026 >50-firm working group https://www.dtcc.com/press-releases/2026/dtcc-advances-development-of-new-tokenization-service ; July production https://www.dtcc.com/press-releases/2026/dtcc-turns-tokenization-into-reality ; DTC FAQ https://www.dtcc.com/-/media/Files/Downloads/digital-assets/dtc-tokenization-service-faq.pdf ; October 12 Ledger CAN-DTCC-01. 12. Warrant / adverse evidence: existing legal authorization, actual production precedent, identifiable market participants. DTC's March FAQ says launch securities not settled in digitized form; private Canton controls and participant procurement can slow scaling. Transfer/representational movement must not be characterized as wholesale atomic securities/cash DvP. 13. Falsification / update: authoritative tally showing fewer than three real distinct participants, or no three postcutoff qualifying months by horizon; broadened programme scope, onboarding notices, actual custody/transfer statements and verified DTC records trigger review. 14. Scoring: Hit only with three entity-specific or verifiable aggregated participant confirmations and at least three calendar months of legal DTC-service Mainnet movements. If genuine activity remains confidential and cannot be evaluated, Expired Unresolved; a known failure to achieve thresholds is Miss. 15. Burden / token economics: Moderate-to-heavy participant/rail crosswalk; no conditional modules. Canton-family work may bypass public CC paid traffic; CC acquisition is separate.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-044-v1 — DTCC collateral operations use Chainlink CRE repeatedly with independent institutions 1. ID / method: PVR-044-v1; v0.4 Lean Core. 2. Freeze: 12 October 2026, before the projected operating-depth outcome. 3. Decision and control: DTCC Collateral AppChain operating team and independently governed clients; Chainlink CRE and data standard are already publicly selected technology for the planned orchestration layer. This is a child of PVR-005 production-go-live, not a second technology-procurement F1 win. 4. Task: F3 operational institutional adoption. 5. Use / horizon: collateral valuation, eligibility, margin or legally effective collateral movement on the DTCC Collateral AppChain, by December 31, 2027. 6. Primary object: actual multi-client, repeated CRE-orchestrated real-value collateral operations in a DTCC production service. 7. Principal scored claim: By end 2027, DTCC Collateral AppChain will have processed qualifying production collateral workflows involving at least TWO independently governed external financial firms as economic collateral providers, receivers or controllers, with Chainlink CRE performing a material data-validation or workflow-orchestration role, in at least THREE distinct calendar months. Mere price feed visibility, simulation or closed test by DTCC alone fails. Named customer plus operational confirmation or equally clear independently audited disclosure is required. 8. Observability: O2 DTCC product and technology announcements, O1 for external customer/frequency/CRE role; could be confidential. Do not infer public Chainlink network revenue or LINK purchase volumes. 9. Call: LEAN, elevated execution risk. DTCC names CRE's operational roles in its production design and launched a participant-wide collateral initiative; real third-party frequency remains unproven. 10. Strongest alternative: service launches but real custody/pledge/margin workflows remain traditional or proprietary; CRE appears only in data tests; few outside customer activities qualify. 11. Sources: DTCC May 12 2026 DTCC/Chainlink announcement https://www.dtcc.com/press-releases/2026/dtcc-collaborates-with-chainlink-to-advance-24-7-collateral-management ; May 15 production infrastructure essay https://www.dtcc.com/insights/2026/the-dtcc-collateral-appchain-from-experiment-to-production-infrastructure ; October 12 canonical Ledger LINK-DTCC-COLLATERAL-APPCHAIN-01, LINK-DTCC-COLLATERAL-01 and LINK-FULCRUM-01 (distinguish prior historical transactions and Sibos demo). 12. Support / contradiction: explicit integration in eligibility/valuation/orchestration with multi-party model supports rollout. Adoption path may be long, pricing/business contracts private, technical orchestration may have other service providers. 13. Disconfirm / monitor: DTCC confirms deployment without recurring CRE workflows or only pilots through deadline; named client reports, workflow logs, multi-month operator statements trigger review. 14. Resolution: Hit only with credible DTCC and/or independent client attribution to actual real-value production, two external legal firms and three operating months. Without sufficient proof after diligence, Expired Unresolved; if reliable affirmative evidence shows no such programme, Miss. No counting a May demonstration as a 2027 operation. 15. Burden / token economics: Moderate-heavy independent collateral economics/CRE attribution; no specialist modules. Contract revenue may route into LINK through payment abstraction, but that path is not part of the scored outcome and not proven by activity alone.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-045-v1 — DTC moves beyond onchain representation into legally operative digital DvP 1. ID / method: PVR-045-v1; v0.4 Lean Core. 2. Freeze: 12 October 2026. The 2026 July limited production trades already happened and are excluded. 3. Decision / owner: DTC/DTCC and authorized participants, securities regulators, and approved issuer/payment providers jointly control finality design and formal participant rule permissions; descendant of DTC Tokenization Service and March 2026 FAQ. 4. Task: F2/F3 architecture scope expansion and real-value execution, distinct from PVR-006 service launch and PVR-038 two asset classes on Stellar. 5. Use / horizon: DTC-custodied eligible security, cash-versus-security transfer under explicitly approved legally effective DvP arrangements using one or more DTC-accepted blockchains; by December 31, 2028. 6. Primary object: service-grade digital settlement outcome in which both security entitlement and cash-leg obligations settle with a legally enforceable DvP binding, not merely digital representation recorded after offchain settlement. 7. Principal scored claim: By end 2028, DTC will have authorized and supported a non-demonstration, financially binding digital DvP workflow for an actual DTC-custodied eligible security involving TWO economically independent institutional participants, where a digital-asset securities transfer under the DTC service is conditional on an authorized digital cash leg and produces operative legal settlement finality. A single real trade suffices only if it occurs under ongoing ordinary commercial service permissions *after launch* and not a time-boxed special event. 8. Observability: O1–O2 for amendments to participant agreements and service rules; O1–O2 trade finality, cash issuer and transfer. Chain choice UNKNOWN; do not specify or imply Ethereum, Canton or Stellar winner from current material. 9. Call: SPECULATIVE LEAN, most fragile of batch. DTCC says it will explore digitized settlement after initial launch; time-to-2028 could permit a narrow regulated extension, but no binding deadline exists and permission may require extensive new rulemaking. 10. Strongest alternative: DTC keeps ultimate securities settlement conventional and onchain tokens remain representations/transfers; optional secondary transactions occur outside DTC's own direct settlement service; formal cash and securities finality remain segregated. 11. Source anchors: DTC FAQ March 3 2026 (states initial transactions not settled in digitized form and future exploration) https://www.dtcc.com/-/media/Files/Downloads/digital-assets/dtc-tokenization-service-faq.pdf ; DTCC tokenized asset authorization Dec 2025 https://www.dtcc.com/press-releases/2025/paving-the-way-to-tokenized-dtc-custodied-assets ; DTCC May 27 Stellar release https://www.dtcc.com/press-releases/2026/tokenization-service-to-connect-with-stellar-public-blockchain-as-dtc-advances-multi-chain-strategy ; DTCC July 2026 limited event https://www.dtcc.com/press-releases/2026/dtcc-turns-tokenization-into-reality . 12. Warrant / limit: target is materially different from announced next chain or two-class issuance; DTC's infrastructure goals include collateral and settlement mobility, but its March operating scope expressly limits launch. July DvP-like trades were limited production and do not establish ordinary permitted service capability. 13. Falsifier / surveillance: failure to authorize any ordinary DTC-service cash/securities digital settlement by end-2028; monitor SEC/DTC rule filings, amended service terms, first outside production participant and actual legal settlement documentation. 14. Resolution: Hit only with binding service rule or unambiguous DTC/operator authorization AND at least one qualified independent-customer real-money operation showing both asset and cash finality. Secondary venue-only trading without DTC-service settlement or July 2026 showcase does NOT hit. Miss with established nonoccurrence; Expired Unresolved if external observability prevents adjudication. 15. Burden / token effect: Heavy legal/regulatory primary-source checking later; targeted Deep Research justified ONLY if decisive changes in legal boundary become contested. Cash leg and legal settlement do not imply any particular native token acquisition.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-046-v1 — Ripple Treasury develops a multi-corporate-client XRPL payments channel 1. ID / method: PVR-046-v1; v0.4 Lean Core. 2. Freeze: 12 October 2026, following release of digital-asset account functionality; not a claim such production already occurred. 3. Owner / ancestry: Ripple Treasury / GTreasury operator, independent corporate treasurers, regulated custodians/financial service providers and payment counterparties; child of broad Ripple full-stack PVR-040, but separately controlled client adoption. 4. Task: F3 economically material client-breadth conversion, not Ripple corporate payments volume attribution. 5. Use / horizon: direct client-initiated third-party enterprise treasury outgoing payment or fund transfer whose asset movement settles on XRPL Mainnet and is instructed/authorized through Ripple Treasury; by December 31, 2028. 6. Resolution object: recurring bank/corporate operating fund movement managed through Treasury and actually executed on XRPL, as distinct from dashboard consolidation. 7. Claim: By end 2028, at least THREE separately governed non-Ripple corporate or institutional treasury customers will each have used Ripple Treasury to initiate real external XRPL Mainnet RLUSD or other authorized token transfers in their operations, with at least THREE separate calendar months of such aggregate programme activity. Group subsidiaries sharing one treasury decision count as one customer; no same-day test transfers. 8. Observability: O2 product features, O1 exact client, instruction path, Mainnet and frequency; named customers or independently audited aggregate verification allowed. Do not equate Ripple Treasury's previously reported $13T traditional payment volume with XRPL activity. 9. Call: LEAN, ambitious multi-client extension, driven by installed TMS distribution and native digital-asset account capability, but operational movement is genuinely prospective. 10. Alternative: Ripple Treasury excels as multi-rail reporting, AI and fiat liquidity platform but customers keep payments on SWIFT/ACH/SEPA or other chains; corporate compliance inhibits XRPL fund movements. 11. Sources: Ripple Treasury Apr 1 launch https://treasury.ripple.com/news/ripple-treasury-launches-first-treasury-management-system-tms-digital-asset ; Ripple's current rail-agnostic workflow guide https://treasury.ripple.com/posts/what-a-digital-payment-looks-like-ripple-treasury ; 9 Oct Ripple handoff §5.3; canonical Ledger XRP-RIPPLE-TREASURY-GTREASURY-01. 12. Warrant / contrary: functional convergence and enterprise installed base present large distribution option; vendor explicitly describes Treasury as rail-agnostic and true client XRPL execution not yet demonstrated. 13. Falsifier: fewer than three qualifying external clients or insufficient repeat month spread; watch external CFO announcements, custody statements, treasury integration APIs and traceable asset legs. 14. Resolution: Hit only after confirming real independently governed clients, actual Treasury payment-instruction role, external financially consequential XRPL Mainnet asset settlement, and three dated months. If confidentiality blocks adjudication, Expired Unresolved rather than assumed success. 15. Burden / token economics: Moderate-heavy vendor+client proof; no modules. RLUSD transactions incur low XRP fees, not proportional XRP principal demand; optional holdings/market purchases separately measured.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-047-v1 — Ripple fund tokenization expands to *funded institutional collateral use* 1. ID / method: PVR-047-v1; v0.4 Lean Core. 2. Freeze: 12 October 2026, after Aviva collaboration and ZILO/Licuido investment but before claimed multi-fund financed collateral outcome. 3. Owner / ancestry: Ripple-linked transfer agent/issuer technology ZILO/Licuido, independent fund managers, regulated custodian and an economically independent lender/secured financing recipient; distinct from CSD BR statutory title prediction PVR-042, but a Ripple-involved capital-markets descendant of PVR-040. 4. Task: F3 vertical depth from tokenized issuance to collateralized credit / lien enforceability. 5. Use / horizon: XRPL Mainnet regulated fund units/share classes and at least one financed pledge/lien recognized by lender; by December 31, 2028. 6. Primary object: two independent real fund managers using XRPL-linked investor interests and one actually funded institutional collateral finance transaction backed by those interests, with recognized legal rights. 7. Claim: By end 2028, at least TWO independent regulated fund managers will have outstanding, actually funded XRPL Mainnet issued/operated fund-interest tokens developed using Ripple's institutional issuance/transfer-agency/custody ecosystem, and at least ONE of those funds will support a real-value, legally effective collateral pledge securing funded credit to an economically independent borrower from a separately governed lender. Collateral eligibility, legal memorandum, dashboard pledge or simulated loan does not count. 8. Observability: O2 fund token public issuances, O1 legal enforceability, funded loan and current beneficial interests. Cash loan may settle offchain, but collateral pledge's XRPL operation and legal effect must be established. 9. Call: SPECULATIVE LEAN. Existing manager connections and a deliberate transfer-agency/issuance/collateral stack warrant the thesis, but lending risk appetite and enforceability are nontrivial and could delay beyond deadline. 10. Strongest alternative: fund share classes proliferate on XRPL but actual credit underwriting and security-interest perfection occur only in conventional systems; lenders choose Canton, Ethereum, Solana or private venues for financed reuse; no two-manager threshold. 11. Sources: Aviva/Ripple Feb 11 2026 partnership https://ripple.com/ripple-press/aviva-investors-seeks-to-tokenise-products-on-the-xrp-ledger-in-collaboration-with-ripple/ ; Aug 3 ZILO/Licuido https://ripple.com/ripple-press/ripple-strengthens-digital-capital-markets-infrastructure-with-investments-in-zilo-and-licuido/ ; Oct12 Ledger XRP-AVIVA-USD-LIQUIDITY-01; 9 Oct Ripple migration handoff §5.3. Historical tokenized fund use does NOT satisfy financed collateral claim. 12. Warrant / contradiction: capital market servicing ecosystem explicitly targets asset portability and collateral; incumbent custody, perfection of pledges, transfer restrictions, asset eligibility and credit risk may prevent legally effective funded use. No deduction of XRP principal demand from dollar AUM. 13. Falsifier: zero legally effective funded independent lender collateral transactions by end2028, or fewer than two independently controlled funded manager tokens; named third-party lender/custodian and loan documentation would strengthen confidence. 14. Resolution: Hit only with two managers and a true signed+funded non-intragroup lending obligation secured by an operative XRPL-linked interest. Published quantitative aggregate can be redacted if external legal parties and economic effect confirmed; unverifiable private financing becomes Expired Unresolved, not automatic hit. 15. Burden / token economics: Heavy legal and financial primary-source investigation on maturity; bounded specialist legal deep research only on a decisive disputed title/pledge case. Funds tokenized AUM ≠ XRP held, fees are de minimis without additional separate acquisition channel.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-048-v1 — Spanish multibank tokenized deposits convert to recurring private HashSphere operations 1. ID/method: PVR-048-v1; frozen forecasting method v0.4 Lean Core. 2. First issue / evidence cutoff: 12 October 2026. The 9 July 2026 proof of concept is known *historical evidence*, not a scored outcome. 3. Decision and owner / ancestry: Cecabank as neutral operator and ABANCA, Ibercaja, Kutxabank and Unicaja as distinct bank balance-sheet/operations decision-makers; Asseto/ioBuilders and Hashgraph as suppliers. Candidate IFC-041/091. Distinct from other banks/consortia; all five banks belong to one common Cecabank network decision family. 4. Task: F2/F3 — continue the shared-bank model into actual operational production; exact pilot-family HashSphere technology already known and not a new F1 selection. 5. Scope / horizon: real tokenized euro commercial-bank deposits and interbank payments/settlement in Spain; 31 December 2028 23:59 Madrid time. 6. Primary resolution object: bank-issued commercial deposits genuinely transferred between separate bank-controlled clients/accounts through a Cecabank-mediated shared DLT operation, with legal/bank-book settlement and verified HashSphere use; no simulated value. 7. ONE scored prediction: By end-2028, at least THREE distinct participating Spanish banks (Cecabank and/or ABANCA, Ibercaja, Kutxabank, Unicaja) will use a commercially authorized Cecabank-coordinated Asseto/HashSphere-family production service to perform externally funded real-value tokenized-deposit operations between at least TWO different banking legal entities, with qualifying settled activity in at least THREE distinct calendar months. Merely continued proof-of-concept activity, demo test liquidity and one-week cutovers do not qualify; funding and bank-ledger reconciliation must be real. 8. Observability/specificity: O2 named pilot, O1 production clients, account-level attribution and duration. Independent operator/bank disclosures may establish aggregate bank-months if confidential HashSphere transaction records are inaccessible. Private HashSphere use is not public Hedera Mainnet activity. 9. Call: SPECULATIVE LEAN for this ambitious three-bank, three-month production conversion; the operational pilot was concrete and bank-governed, but commercial authorization, custody and participant readiness remain unknown. 10. Strongest alternative: pilot knowledge disseminates but operators use ordinary Spanish/EU payments; privately tokenized books remain internal/small; Cecabank does not productize common settlement; a Eurosystem solution or other vendor supersedes HashSphere. 11. Primary source basis: Cecabank's July 9 official pilot publication https://www.cecabank.es/eng/abanca-cecabank-ibercaja-kutxabank-y-unicaja-completan-la-primera-prueba-multibanco-en-espana-de-depositos-tokenizados/ ; independent bank Unicaja's July 9 release https://www.unicajabanco.com/en/sala-de-comunicacion/buscador-noticias/2026/07/participacion-en-la-primera-prueba-multibanco-en-espana-de-depos ; supplier engineering case study https://hashgraph.com/case-study/cecabank/ ; Asseto technical account transfer account https://www.asseto.io/tokenization-case-studies/tokenized-deposits ; Oct12 Ledger HBAR-CECABANK-TOKENIZED-DEPOSITS-01 and HBAR-HASHSPHERE-01. 12. Load-bearing warrant and counterevidence: five named banks actually exchanged tokenized deposits in a regulated-liability-mimicking test; a neutral bank operated linked technical accounts, providing reusable operational architecture. Contrary: no bank confirms an authorized, externally funded, ordinary commercial multi-month service. Public Hedera participation is *optionality only*. 13. Falsifier/update trigger: credible record of termination, replacement or exclusively sandbox use through end-2028; signed launch, named bank go-live, three monthly settlement attestations, bank control/legal account arrangements can upgrade or resolve. 14. Adjudication: Hit only with regulator/bank/operator primary confirmation of commercial real-value activity, at least three separately governed bank operators, two different legal bank entities in a settled transfer, and three qualifying months. Miss if authoritative evidence establishes failure. If production is truly hidden from public verification despite diligent investigation: Expired Unresolved, not assumed Hit. 15. Burden/modules/token: Moderate multi-bank evidence + legal bank-deposit settlement checking; no specialist module now. Private HashSphere ≠ public Hedera transaction fee and does not establish HBAR buying, HBAR Mainnet adoption or HBAR tokenomics capture.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-049-v1 — Athens Exchange converts Sui order-book research into investor-funded EBB capital raising 1. ID/method: PVR-049-v1; v0.4 Lean Core. 2. First issue: 12 October 2026, after 2024 ATHEX partner selection and April 2025 technical design/PoC announcements. 3. Owner/ancestry: Athens Exchange Group's EBB operator, approved securities offer issuer and member brokers/investors, with Mysten Labs as design supplier; candidate IFC-044. ATHEX's existing conventional EBB issuance is excluded. 4. Task: F3 conversion from technical concept into real securities capital-raising infrastructure; not prediction of 2024 Sui selection. 5. Scope/horizon: Greece regulated ATHEX Electronic Book Building bids/allocation workflow using Sui Mainnet; 31 December 2028 23:59 Athens time. 6. Resolution object: a live real-world fundraising offer in which Sui processes a legally operative or exchange-authorized onchain order-book bid and allocation, tied to real investor subscriptions and securities rights. 7. ONE scored prediction: By end-2028, ATHEX will execute at least ONE genuine investor-funded securities capital-raising event through its upgraded Electronic Book Building system in which a Sui Mainnet smart-contract/order-book operation has an explicitly acknowledged production role in recording or coordinating real investor bids AND allocation, and at least TWO independently controlled exchange-member banks/brokers or investing institutions participate. Tokenized publicity, testnet transactions, an issuer using ordinary EBB without Sui, or a mere Sui receipt mirror fails. 8. Observability: O2 technical plans and exchange public offerings, O1 Mainnet onchain mapping and participant contracts; the claim is Sui's functional authorized EBB role, not that the definitive shareholder registry necessarily moves to Sui. 9. Call: SPECULATIVE LEAN. Years of named design work and specific ZK privacy solution motivate the projection; a 2025 PoC with no confirmed production by the October 2026 cutoff signals execution/scope risk. 10. Strongest alternative: ATHEX maintains existing EBB workflows, deploys only a sandbox/book-building demo or zero-knowledge privacy layer with no production on Sui, or legally books securities offchain and never uses Sui for an operative bid/allocation. 11. Primary sources: ATHEX original 6 Mar 2024 https://www.athexgroup.gr/documents/10180/7351528/Mysten%2BLabs%2BPress%2BRelease.pdf/c082388d-8d49-4387-94b7-945c39ccdf11 ; ATHEX Apr 16 2025 official https://www.athexgroup.gr/sites/default/files/2025-04/PR-Mysten-Labs-en.pdf ; Sui matched announcement https://www.sui.io/blog/athex-onchain-order-book-design ; Oct12 Ledger SUI-ATHEX-01. 12. Warrant/adverse: ATHEX controls relevant EBB workflow and formally completed requirements engineering; cryptographic privacy was specifically addressed. No production mandate, approved issuer or contract for first live Sui EBB event identified. Conventional EBB has actual successful securities offerings and is a strong incumbent. 13. Falsifier/update: definitive programme halt, a non-Sui production order book, or year-end 2028 with no independently subscribed Sui-coordinated offer. Watch exchange EBB notices identifying chain, audited Mainnet events, prospectuses and member participation. 14. Resolution: Hit only on primary exchange/issuer/member evidence linking one real subscribed securities offering and two genuine independent financial parties to a meaningful Sui Mainnet bid/allocation role. Mere existing EBB fundraiser must be ruled out. If private mapping prevents proof after research, Expired Unresolved; confirmed failure is Miss. 15. Burden/modules/token: Moderate-to-heavy capital-markets offer and onchain provenance, no specialist module at issue. Actual Sui execution needs some SUI gas but offering proceeds, investor securities principal and underwriter compensation are not SUI demand.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-050-v1 — FIS Project Keystone becomes repeat multibank operating money rather than design consortium 1. ID/method: PVR-050-v1; v0.4 Lean Core. 2. First issue: 12 October 2026, following Apr 30 2026 FIS announcement of member-owned Project Keystone and Apr 29 FIS Lyriq technical availability. 3. Owner/ancestry: FIS platform, bank-owned Keystone network governance, separately regulated founding banks (publicly identified include Citizens, Fifth Third, Huntington, KeyBank and M&T); candidate IFC-003; distinct from Fiserv/Solana Roughrider and from Swift ledger. The vendor cannot compel an independent bank to issue liabilities. 4. Task: F2/F3 bank-governed operating-model continuation and material interbank adoption; not F1 first announcement of private bank-administered architecture. 5. Scope/horizon: U.S. bank-issued tokenized deposits across bank-owned Project Keystone and bank-authorized books, by 31 December 2028 23:59 Eastern time. 6. Resolution object: bank-funded legally recognized digital deposits on an operational shared bank-governed infrastructure, including independently originated bank-to-bank transfers with final bank-book effects. 7. ONE scored prediction: By end-2028, at least THREE separately chartered founding Project Keystone banks will have joined an operational shared bank-controlled tokenized-deposit service, and at least TWO distinct pairs of those banks will have completed funded, legally effective bank-to-bank transfers through that common service, with actual qualifying interbank production activity in THREE different calendar months. Vendor simulation, 2026 proofs-of-concept, mere bank membership, or fake intra-group funding fail. 8. Observability: O2 consortium design, O1 bank-charter authorizations, two distinct transfer pairings and monthly transactions. Public aggregate attestation acceptable if it proves required number of banks/pairs/months. 9. Call: LEAN (commercial multibank commitment bet). FIS controls valuable bank infrastructure and the announcement commits a shared governance/issue/transfer/settle mission; real three-bank production and deposit liabilities remain prospective. 10. Strongest alternative: banks use Lyriq only individually, pilots don't result in shared cash network, most members prioritize RTP/FedNow/Swift or an alternative shared-deposit project, so no repeated cross-bank Keystone use. 11. Primary sources: FIS Apr 30 2026 https://www.investor.fisglobal.com/news-releases/news-release-details/fis-and-leading-financial-institutions-build-their-own-digital ; FIS Apr 29 Lyriq https://www.fisglobal.com/about-us/media-room/press-release/2026/fis-launches-new-platform-giving-banks-control-over-digital-money ; research original register IFC-003 (Run C RC-001). These are proposed design/production-ready software statements, NOT real Keystone settlement evidence. 12. Warrant/adverse: named independently chartered financial institutions, cross-core bank governance, atomic deposit settlement design and FIS integration competence. Banks retain approval/control; public release identifies only five of six banks and does not evidence any full commercial bank-to-bank settlement. 13. Falsifier/update: documented bank exit, banking regulator limits, only one-bank production or no real interbank liquidity transfers by 2028. Bank-specific deposit terms, operating network rulebook, first interbank funded settlement attestations are upgrade triggers. 14. Resolution: Hit requires >=3 independently chartered founding banks, >=2 different real sending/receiving bank pairs, >=3 actual production calendar months. Vendor assertion of addressable bank footprint is not proof. Miss on evidence of no qualifying production at deadline; Expired Unresolved if private data cannot establish threshold. 15. Burden/modules/token: Moderate interbank-source triangulation; modules default off. This is a shared private bank deposit system hypothesis; no FIS-related blockchain adoption means QNT, HBAR, XRP, SOL, CC or any public crypto token captures value.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-051-v1 — tZERO's Sui integration attracts an independent regulated issuer and repeat outside trading 1. ID/method: PVR-051-v1; v0.4 Lean Core. 2. Freeze/date: 12 October 2026, following tZERO's Aug 25 Sui integration/partnership announcement. 3. Decision / owner / ancestry: tZERO's relevant licensed securities entities AND an economically independent security issuer, approved brokers/participants and investors; candidate IFC-045. Separate from PVR-049 ATHEX, although both depend on general Sui tokenization success. 4. Task: F3 production conversion of U.S. regulated securities infrastructure, not F1 first supplier integration, which was disclosed Aug 25. 5. Scope/horizon: an eligible SEC/FINRA-regulated or properly exempt U.S. issuer instrument hosted on Sui Mainnet and processed via the tZERO platform; 31 December 2028 23:59 Eastern time. 6. Resolution object: independently controlled first issuer funds/security entitlements actually onboarded and real-value investor or broker securities transactions routed through tZERO's production regulatory arrangement, with explicit Sui record/proof role. 7. ONE scored prediction: By end-2028, at least ONE legally independent non-tZERO/non-Mysten issuer will have issued or converted a genuinely outstanding investor-funded digital security (including legally valid security entitlement if properly described) on Sui Mainnet through tZERO-supported infrastructure, and at least TWO real-value investor-to-investor or investor-to-issuer eligible regulated transactions involving this Sui security will have occurred in TWO distinct calendar months. Merely whitelisting Sui, custody testing, transferring tZERO-owned inventory or existing tZERO trades on different chains does not count. 8. Observability: O2 integration announcement, O1 investor/issuer identity and settled Sui record; regulatory permission must match instrument/venue rather than assuming all tZERO affiliates support everything. Different private holder accounts alone do not guarantee distinct owners. 9. Call: SPECULATIVE LEAN. A licensed securities operator integrated the chain for a stated institutional mission, but without a named first issuer or committed investor, real trading is a significant further step. 10. Strongest alternative: tZERO offers Sui as a supported option without securing a funded issuer, existing participants favor other chains or offchain securities, or tZERO supports Sui custody but not economically meaningful trading. 11. Primary sources: tZERO Aug 25 2026 https://www.tzero.com/news/blockchain-infrastructure-firm-tzero-announces-direct-integration-with-sui-for-institutional ; Sui parallel statement https://www.sui.io/blog/tzero-sui-institutional-digital-securities-infra ; Oct12 Ledger SUI-TZERO-SECURITIES-01. 12. Warrant/adverse: direct regulated market infrastructure supplier rather than aspirational L1 declaration. Available broker-dealer, custody, TA and compliance services reduce barriers but do not create a client's business case. No independently funded Sui-tZERO issuer/trade identified in this pass. 13. Falsification/update: named issuer legal/security terms, custody settlement and client trade records can resolve; tZERO offering mere chain capability with no actual funded issuer by deadline is a Miss if established. 14. Scoring: Hit requires new independent issuer/real funded securities and at least two eligible Sui-attributed transactions across distinct months under appropriate approvals; cannot count conventional-chain tZERO transactions or Sui testnet. Absence of public transaction detail after diligence → Expired Unresolved rather than assumed adoption. 15. Burden/modules/token: Moderate issuer/regulatory/onchain crosswalk; no specialist module. SUI gas and network security are separate from securities-notional or tZERO commercial revenues, and no substantial SUI acquisition inferred.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-052-v1 — Korean tokenized securities have genuinely multi-ledger production under KSD 1. ID and method: PVR-052-v1; v0.4 final frozen Lean Core. 2. First-issue date / evidence cutoff: 12 October 2026; no funded future issuances are credited at issuance. 3. Decision owner / ancestry: Korea Securities Depository controlling reconciliation; at least two separately regulated Korean brokerage/account-management operators controlling their distinct DLT ledgers; candidate IFC-016/017 plus Sept/Oct 2026 new independent provider evidence. Korean FSC controls regulatory permissions. KSD + brokers share legal system dependency; do not count as independent sovereign predictions. 4. F-task: F1 architecture plurality in production + F3 substantial commercial conversion; NOT "KSD chose Samsung SDS," which was publicly announced in May. 5. Geography / horizon: Korean legally recognized tokenized securities; 31 December 2028 23:59 Korea Standard Time. 6. Primary decision to resolve: whether at least two different blockchain implementation families are operated under separate accountable securities account managers for actual investor-owned registered tokenized securities reconciled with KSD, rather than one shared sole registered DLT. 7. ONE scored forward claim: By end-2028, at least TWO distinctly governed Korean broker/account-management institutions will each operate a legally effective, KSD-recognized tokenized-securities issuance/holding ledger with REAL funded external investor positions, and the TWO active ledgers will demonstrably use DIFFERENT underlying blockchain implementation families (e.g. Besu-family versus Avalanche-family; exact pair not predetermined). The investor/security rights must be effective under the Korean regime; both ledger instances must record genuine outstanding funded assets. Standalone proofs, a single broker running two stacks, read-only mirrors and issuer test tokens do not count. 8. Observability / specificity: O2 legal/vendor plans; O1 identity of two broker operators, live security IDs, invested holders and technology family. Licensed operator disclosures, regulator/KSD statements or audited chain artifacts may verify private-chain cases. Treat unverifiable operational family as Expired Unresolved, not hit by guesswork. 9. Directional call: SPECULATIVE LEAN for meaningful multi-architecture first-wave operation rather than forced single-stack centralization by 2028. 10. Strongest alternative: all registered initial securities use one KSD-centered or KoSTO shared DLT; brokerage alternatives remain pilots, offchain distributor mirrors or are prohibited/delayed by regulator; securities issuance exists on only one compatible implementation family. 11. Primary and independently corroborating sources: FSC Sept 4 https://www.fsc.go.kr/eng/pr010101/87653 ; FSC Oct 1 https://www.fsc.go.kr/eng/pr010101/87834 ; KSD implementation vendor Samsung SDS May 8 https://www.samsungsds.com/en/news/tk-260508.html ; Koscom primary shared-platform page https://www.koscom.co.kr/portal/main/contents.do?menuNo=200637 ; KoSTO technical https://www.koscom.co.kr/portal/main/contents.do?menuNo=200666 ; SECONDARY exact competitor-stack reports https://en.sedaily.com/finance/2026/09/06/hanwha-securities-builds-avalanche-based-token-securities and https://en.sedaily.com/finance/2026/09/27/brokerages-split-over-building-own-token-platforms-or . Secondary articles not treated as fully verified primary vendor contracts. 12. Warrant vs counterevidence: regulatory architecture anticipates multiple authorized account-manager ledgers and KSD-wide integration; distinct brokers have materially different technical partners. Against: regulator's finalized node/registry terms and bank/operator investment costs could cause consolidation; no verified separate legally funded competitor issuance by cutoff. 13. Falsifier / update: regulator prohibits separate broker ledgers; two-year rollout remains sandbox; by end-2028 no two distinct live securities-bearing ledger families; or KSD sources reveal one shared production DLT only. Track actual approved operators/identifiers, investor-financed issuance and network codebases. 14. Resolution rule: Hit only if two different broker-controlled ledger operators, two different network *families*, and funded legally recognized securities all proven at deadline. Miss with credible negative evidence; expired unresolved if private evidence cannot establish. "Supports compatibility" does not prove live issuer, and two independent assets on one tech stack is insufficient. 15. Scope/token and test caution: network-family deployment, not AVAX/ETH/OP coin fee demand. Besu permissions do not imply Ethereum mainnet; dedicated Avalanche infrastructure can bypass C-Chain/AVAX demand; KSD rules on ledger use fees do not prove zero gas or public chain prohibition. Qualitative call, no calibrated probability or method superiority claim.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-053-v1 — Swiss CHF stablecoin project gains genuine multibank commercial depth 1. ID and method: PVR-053-v1; v0.4 frozen Lean Core. 2. First issue: 12 October 2026; prior sandbox CHFD minted since late June 2026 is historical, excluded from score. 3. Owner/ancestry: Swiss Stablecoin AG as CHFD technology/issuer programme, and at least two separately chartered participants from UBS, PostFinance, Sygnum, Raiffeisen, ZKB, BCV; SIX/TWINT distribution roles distinct; candidate IFC-006. Distinct from SNB Project Helvetia pilot. 4. Task: F2/F3 commercially authorized continuation/operating model, not F1 secret exact chain selection. 5. Market/horizon: Swiss franc stablecoin CHFD; 31 December 2028 23:59 Zurich time. 6. Resolution object: separately authorized commercial client/bank CHF-denominated liability and transfer events on CHFD outside a protected proof/sandbox environment, observable as ordinary legally effective transactions. 7. ONE scored claim: By end-2028, at least TWO independently regulated Swiss banks that participated in the 2026 CHFD sandbox will conduct REAL commercially authorized CHFD transfer/settlement activity on a common Swiss Stablecoin programme instrument with qualifying externally funded transactions in at least THREE distinct calendar months. At least one transfer/settlement must involve different legal bank institutions or independently controlled external customers; a bank holding a test wallet or a completed sandbox exercise fails. 8. Observability: O2 nine named sandbox participants; O1 named commercial banks, stablecoin redemption/funding terms, bank-book reconciliation and separate months of real-value use; suitable regulator/issuer/bank attestations if chain privacy. 9. Call: SPECULATIVE LEAN, nontrivial early-commercial multibank conversion. 10. Strongest alternative: the consortium concludes the exercises but does not authorize a common broadly available CHF instrument; banks use SIC, deposit-token internal books, tokenized central-bank money through Helvetia or competing private payment systems. 11. Source basis: UBS Apr 8 https://www.ubs.com/global/en/media/display-page-ndp/en-20260408-stablecoin.html ; PostFinance Apr 8 https://www.postfinance.ch/en/about-us/media/newsroom/chf-stablecoin-sandbox.html ; Sygnum Sept 8 https://www.sygnum.com/news/chf-stablecoin-sandbox-enters-test-phase-and-adds-six-and-twint-as-new-partners/ ; TWINT Sept 8 https://www.twint.ch/en/company/media/chf-stablecoin-sandbox-enters-test-phase-and-adds-six-and-twint-as-new-partners/ . No exact token chain inferred. 12. Warrant and counter: six original banks/issuer plus SIX and TWINT generate banking, payment and FMI commercial interest; test instrument already technically operational. No ordinary commercial CHFD issuance, fully defined legal issuer liability, or licensed broad-bank participant operating service proved by cutoff. 13. Failure/upgrade: formal termination or sandbox-only status, no two independent banks, no real-value independent settlement in three months by Dec 2028 => miss if independently confirmable. Commercial launch documents, audited transfers and 2+ bank attestations strengthen it. 14. Hit criterion: two distinct regulated bank legal entities actually process authorized CHFD commercial transfers at least three months, with external economic effect; investor promises, demo-only activity and peer-independent lab settlement excluded. Expired Unresolved if secrecy prevents assessment despite investigation. 15. Token/counterfactual: CHFD is not SNB wCBDC, is not ZCHF, and does not prove use of public Hedera, Canton, XRPL, Stellar or any native token. The outcome remains a private Swiss-monetary-infrastructure call until exact chain and actual token capture verified. No unearned calibrated probability.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-054-v1 — KB Securities distributes a real funded OP Mainnet institutional fund 1. ID/method: PVR-054-v1, v0.4 Lean Core. 2. Issue/cutoff: 12 October 2026; September 23 2026 tri-party MoU is known and NOT counted as future success. 3. Decision owner/ancestry: KB Securities and independent fund manager / actual Korean qualified investor as economic issuer/distributor/controllers; Securitize technical/transfer-agent supplier; Optimism OP Mainnet operator; separate from KSD central vendor and other Korean broker platform users. 4. F-task: F3 customer-funded production conversion on a specified actual public network; vendor/provider named in prior agreement so NOT an undisclosed F1 chain-selection success. 5. Horizon: Korean institutional fund distribution 31 December 2028 23:59 Korean Standard Time. 6. Resolution: a specifically identifiable KB-origin/KB-sponsored tokenized money market or KB Asset Management strategy share/unit issued or distributed in funded real financial operation by eligible external professional investors using OP Mainnet settlement/holding contracts. 7. ONE scored prediction: By end-2028, KB Securities or a KB-sponsored regulated asset manager will complete a real externally funded launch or distribution of at least ONE identifiable institutional money-market or KB Asset Management-origin fund product using OP MAINNET tokens for operative client beneficial fund positions or legally operative investor transfers, with independently controlled professional investor balances or transfers present in at least TWO distinct calendar months. A mere OP test token, MOU, smart-contract deployment without investor funds, Korea-only broker custody with unrelated chain marketing or use solely of another private OP Stack chain fails. 8. Observability: O2 agreement, product intent; O1 fund identifiers, first actual independent client subscription/redemption, OP Mainnet transaction/contract source and month-separated funded holdings. 9. Call: SPECULATIVE LEAN for KB public OP Mainnet fund conversion by late 2028; regulator/client agreement and Korean fund issuance/distribution rules are substantial gating factors. 10. Alternative: KB remains at MoU and proof-of-concept; offers access to conventional fund records or a private domestic KSD-coordinated ledger; tokenizes elsewhere on OP Stack or another EVM, or selects a global tokenized fund not operated on OP Mainnet. 11. Sources: Optimism/KBS/Securitize Sept 23 partner release https://optimism.io/blog/kb-securities-securitize-optimism-tokenized-funds-op-mainnet ; Korean FSC Sept 4 roadmap https://www.fsc.go.kr/eng/pr010101/87653 and Oct1 consultation https://www.fsc.go.kr/eng/pr010101/87834 ; Oct6 Securitize/LG CNS agreement https://investors.securitize.io/news/news-details/2026/Securitize-and-LG-CNS-Partner-to-Advance-Tokenized-Assets-in-South-Korea/default.aspx . Different supplier's Oct6 announcement does not itself mean a funded KB launch. 12. Warrant/counter: KB explicitly targets money-market and flagship fund strategies via OP Mainnet, partner Securitize has applicable live tooling and Korean legal changes create tailwind. Yet the MoU and regulatory development give neither product-specific approval, signed investment funds, nor exact live transfer/settlement commitments. 13. Update/falsifier: OP Mainnet issuer authorization, fund contract, initial funded institutional investor, independent investor ownership on mainnet and activity in two months = positive resolution; programme discontinued, alternate chain/custody path, or end-2028 no funded product = miss. 14. Scoring: Hit requires named funded fund with actual OP Mainnet link and independently controlled investor rights over at least two months; testnet, self-issued treasury-only display, OP Stack-only alternate chain and protocol capability excluded. If verifiability inaccessible despite efforts, Expired Unresolved. 15. Value-capture and overlap: OP Mainnet fee payment need not create a major direct OP token purchase; Ethereum L2 settlement economics distinct from ETH mainnet demand. PVR-052 shares Korean regulator timing and public/private ledger restrictions but tests a different decision owner/outcome. Confidence is an uncalibrated qualitative hypothesis, not investment advice.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-055-v1 — AMINA/Tokeny's first live 21X issuer takes the Polygon PoS settlement path

1. ID / version / Method: PVR-055-v1; Institutional Architecture Forecasting v0.4 Lean Core.
2. Freeze date / evidence cutoff: October 12, 2026 (America/New_York). The announced March 2026 AMINA sponsorship and 21X's historical Polygon/Stellar venue availability are NOT future successes.
3. Decision object / control / ancestry: Separately controlled outside securities issuer (not yet publicly named) with AMINA Bank AG as regulated listing sponsor, Tokeny (Apex Group) as compliant issuance platform, and 21X AG as regulated venue operator; distributed issuer/listing/venue control. Working candidate ancestry IFC-020 (AMINA/Tokeny/21X). Group-adjacent but institutionally distinct from Investre IFC-021; shares the same 21X market operator/regulatory dependencies.
4. Official task: F1 exact network/platform for the qualifying issuer's first real 21X secondary transaction, not predicting 21X itself chooses Polygon for the first time.
5. Use/jurisdiction/horizon: Issuer-sponsored regulated transferable security issued through AMINA + Tokeny's ERC-3643 technology and offered through EU-regulated 21X DLT TSS; 31 December 2028 at 23:59 Frankfurt time.
6. Primary Resolution Object: Network used for the legally operative 21X market transaction settlement of the first independent AMINA-sponsored Tokeny ERC-3643 security reaching funded outside-investor secondary trading; Polygon proof-of-stake public network is the hypothesized chain. Initial Tokeny token deployment on Polygon while the *actual 21X market trade* executes only on another network does NOT score a hit.
7. ONE principal scored claim: No later than 31 December 2028, at least ONE securities issuer independent of AMINA, 21X and Tokeny will introduce an AMINA-sponsored, Tokeny ERC-3643-issued security to live regulated 21X trading, with at least ONE bona fide independently funded secondary purchase/sale between economically separate eligible participants that is executed/settled on the public Polygon PoS chain. Issuer/token must be identified. Venue/issuer legal instrument and onchain trade must refer to the same security. Unsupported claims of venue compatibility, an AMINA sponsor agreement, a token's initial issue without investor trade, other EVM chains, Polygon CDK private networks, or mirror-only movements FAIL. If no qualifying AMINA-sponsored issue reaches actual trade by deadline, the composite prospective claim MISSES rather than scoring a hypothetical conditional chain choice as a hit.
8. Observability / specificity: O2 public sponsor/venue technical selection and firm Tokeny network list; O1 first actual independent issuer's legal issue, network confirmation and trade; exact Polygon call is speculative and depends on nonpublic client architecture. Full deployed security address/transaction or regulator/operator/issuer attestations are decisive.
9. Direction / strength: SPECULATIVE LEAN — Polygon PoS. Earned discriminator: Tokeny supports Polygon ERC-3643 deployments and 21X already runs a regulated Polygon venue, while native Stellar is not the currently documented Tokeny ERC-3643 issuance path. Arc is EVM-compatible and has 21X's new tested integration, so the margin is not large. This is explicitly NOT Strong Lean or a calibrated >50% probability claim.
10. Strongest alternative: 21X Arc becomes a production EVM venue and wins the first sponsor issue; or the issuer selects a different 21X network (Stellar/other EVM); or programme remains a sponsor-level sales channel without real trading by end-2028. Issuer may launch token elsewhere and bridge it; bridge alone is insufficient.
11. Evidence references: 21X/AMINA March 9 https://21x.eu/amina-becomes-first-regulated-bank-on-21x/ ; Tokeny official supported network list https://docs.tokeny.com/docs/tokenize-assets ; ERC-3643 EVM interface https://docs.tokeny.com/docs/ecosystem-interoperability ; 21X May rulebook change https://21x.eu/announcement/21x-ag-rulebook-amendment-announcement-may-2026/ ; 21X Oct 1 Arc test https://21x.eu/21x-group-announces-collaboration-with-circle-as-it-joins-arc-as-a-day-1-launch-partner/ . Frozen Ledger context XLM-21X-REGULATED-DISTRIBUTION-01 and Master IFC-020 are inherited evidence, not newly rewritten facts.
12. Warrant and contradiction: Actual compatible Polygon issuance tools + established regulated Polygon settlement architecture reduce implementation friction. Against this, client issuer preference and platform-specific contract portability are private; 21X's latest Arc tests specifically undermine any assumption of sole Polygon routing. AMINA sponsor does not command independent issuer to use Tokeny or a particular 21X ledger without agreement. F1 exact-chain overreach risk acknowledged.
13. Falsifier/update: First qualifying Tokeny/AMINA/21X issuer settles a real trade on Stellar, Arc or another network; regulatory rule forbids Polygon path; contract/prospectus lists an exclusive alternative; sponsor route abandoned; no qualifying funded trade by deadline. Reopen on first named issuer, ISIN, offering memorandum, deployment address, 21X listing order/trade and venue settlement network, or any substantive new rulebook change.
14. Resolution: HIT only when independent issuer + Tokeny ERC-3643 + AMINA sponsorship + regulated 21X real third-party funded trade + Polygon PoS execution all proved. MISS if chain differs, transaction remains merely a demo, or qualifying trade has not occurred by deadline and this is verifiable; EXPIRED UNRESOLVED only if decisive private records are unavailable despite proportionate investigation. No rescue by Tokeny-issued assets on Polygon that were never regulated-traded through 21X.
15. Burden / specialists / token firewall: Moderate (ordinary multi-source primary research; direct protocol documentation, no Deep Research, no specialist module, ordinary continuity). Fee gas ≠ significant POL accumulation, Polygon deployment ≠ Ethereum L1 fee burn, and Tokeny middleware economics ≠ public-network token economics.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-056-v1 — First Investre native UCITS becomes a repeatedly traded regulated 21X fund

1. ID / method: PVR-056-v1, Institutional Architecture Forecasting v0.4 Lean Core.
2. First issue / cutoff: October 12, 2026. The September 9 collaboration is historical and not scored as an outcome.
3. Decision owner / ancestry: Independent Luxembourg UCITS management company/regulated fund issuer, Investre as CSSF-authorized Control Agent, 21X AG as separately controlled BaFin-regulated DLT TSS, investors and market makers; IFC-021. Common 21X operational dependency with PVR-055; no assumption that same issuer or same chosen chain.
4. Task: F3 significant maturity / business conversion, not F1 exact chain selection.
5. Use/geography/horizon: Natively issued transferable UCITS fund units with regulated secondary trading in EU; 31 December 2028 at 23:59 Luxembourg time.
6. Primary resolution object: First externally funded Luxembourg-regulated *native* UCITS fund utilizing Investre Control Agent records and 21X venue actual secondary market trading, with active qualified investor participation across separate months.
7. ONE scored claim: By end-2028, at least ONE identifiable independently governed UCITS fund manager will have a genuine legally native-on-DLT UCITS class/issue supported by Investre's Control Agent framework, with real externally subscribed investor fund positions and bona fide non-affiliated secondary trades through the 21X regulated DLT TSS in at least TWO different calendar months. It is not enough that a fund is approved, displayed as listed, tokenized as a mirror of an exclusively offchain register, or has primary fund subscriptions/redemptions without outside secondary matches. Require independently controlled investor and market-facing participants, not affiliated test swaps.
8. Observability: O2 regulation and partner intent, O1 actual issuer/class and investor transactions; chain identity deliberately left open (Polygon, Stellar, Arc if later admitted). Trade and legal effect must be demonstrable through venue/issuer filings or verifiable ledger plus named product identifiers.
9. Call: SPECULATIVE LEAN that a real native UCITS/21X secondary conversion happens by end-2028, conditional on meaningful commercial demand and issuer regulatory scope. This is more consequential than a first fund token/deployment and cannot be scored on partnership activity.
10. Strongest alternative: Investre wins Control Agent fund mandates but retains liquidity through bilateral fund issuer-redemption/market-maker DvP, or 21X lists products without repeat matched secondary trades; traditional fund distributors/TA systems prevail; permissions/rules prevent UCITS traded under the DLT Pilot or limit activity past 2028.
11. Primary sources: 21X/Investre Sept 9 https://21x.eu/investre-and-21x-partner-to-bring-natively-tokenized-funds-to-a-regulated-exchange/ ; Investre counterparty copy https://www.investre.eu/post/investre-and-21x-partner-to-bring-natively-tokenised-funds-to-a-regulated-exchange ; Investre regulated product architecture https://www.investre.eu/ ; Investre secondary trading FAQs https://www.investre.eu/faqs ; 21X venue rulebook version https://21x.eu/document/21x-ag-rulebook/ . Master inherited IFC-021 analyses; same operator dependency as PVR-055.
12. Warrant/contrary evidence: A registered onchain-fund Control Agent plus a regulated multi-asset DLT trading venue resolves two distinct infrastructure needs. Issuer, effective register, qualified investor suitability, securities DvP cash finality, market-maker/secondary demand and two months of liquidity are not yet proven. Without outside orders, it may become a technically elegant token register rather than an exchange success.
13. Falsifier/trigger: announcement of an actual named regulated UCITS manager, ISIN/class register and first matched nonaffiliated 21X order; no such funded trading in two separate months by deadline; legal limitation excluding qualifying UCITS; fund's official sole register remains offchain with token mirror. Avoid confusing Investre's internal pilot OTC DvP with a 21X multilateral trade.
14. Resolution: HIT requires all of independent UCITS issuer, native legal register, funded external holdings, and 21X real two-month secondary trades. MISS if impossible/not achieved by deadline; EXPIRED UNRESOLVED if trade counterparty information legally inaccessible but credible public inquiry unsuccessful. Chain may be any legally permitted venue chain; no Polygon accuracy credited.
15. Burden / modules / token firewall: Moderate, multi-source issuer/venue regulatory primary research; no Deep Research or specialist. Actual shares / cash DvP do not prove utility-token holding; Stellar transaction fees negligible relative to fund notional; Polygon/Arc benefit requires chain attribution and fees/inventory separately.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-057-v1 — Securitize US stock entitlements gain genuine independent regulated cross-venue liquidity on Solana

1. ID / method: PVR-057-v1, forecasting v0.4 Lean Core.
2. First issue/evidence cutoff: October 12, 2026. Initial October 8 Solana launch and named future venue plans are historical facts, not forecast successes.
3. Decision/control/ancestry: Securitize as entitlement token programme and broker/financial intermediary; independently operated NYSE ATS and/or OKXICE tokenized-securities venue as regulatory/operator decision loci; separate investors/market makers; capital-markets / regulated-entitlement liquidity decision family. Inherited IFC-082 concerns future lending/collateral but is a different primary milestone: no credit adoption is predicted here.
4. Task: F3 multi-venue real production conversion, not F1 initial Securitize choice of Solana.
5. Use/jurisdiction/horizon: U.S. equities Article 8 1:1-backed security-entitlement tokens, regulated U.S. and/or authorized cross-border securities trading; 31 December 2028 at 23:59 New York time.
6. Primary Resolution Object: Actual independently managed regulated venue matching/settlement of an identified Solana-resident Securitize Stocks security-entitlement instrument beyond Securitize's own registered broker-dealer marketplace.
7. ONE scored claim: By end-2028, at least ONE of the separately operated NYSE ATS or OKXICE TSV will execute/settle genuine independently funded third-party purchases and sales of at least TWO distinct Securitize Stocks Article 8 security-entitlement instruments whose legally relevant token balances/trades reside on Solana, with qualifying trade activity in at least THREE separate calendar months. Only an outside venue counts, with separated economic buyers/sellers or verifiable independently funded matching; a token listed but not traded, internal broker cross, test orders, swaps in unbacked price exposure, token mirrored on another chain, or a wholly separate issuer-sponsored share token FAIL.
8. Observability/permitted specificity: O2 explicit operator intentions, Securitize production technology; O1 venues' licensing, rules, order execution, wallet identities and cross-venue legal entitlement flow. Solana exposure is already public for *original* Securitize programme but the future outside venue's Solana choice and actual trade are unproven. Public chain record alone may not fully establish UCC legal effect.
9. Call: SPECULATIVE LEAN for at least one external venue becoming economically real on Solana by end-2028. The two-venue optionality does not mean each has independently selected Solana; only one must convert. Regulatory approval and commercial liquidity remain substantive risks.
10. Strongest alternative: neither outside venue obtains the required functioning market infrastructure by deadline; only Securitize's own trading venue gains liquidity; NYSE/OKXICE handles a different token category or EVM/Arc wrapped architecture, or conventional DTCC custody/legal model excludes external Solana-resident entitlement settlement.
11. Evidence: Securitize official October 8 https://investors.securitize.io/news/news-details/2026/Securitize-Launches-Global-Onchain-Trading-of-U-S--Stocks-with-Security-Entitlements/default.aspx ; issuer release syndication https://www.nasdaq.com/press-release/securitize-launches-global-onchain-trading-us-stocks-security-entitlements-2026-10-08 ; canonical October 12 Ledger's SOL-SECURITIZE-STOCKS-01 (read-only); earlier Master legal-entitlement vs issuer-sponsored distinction. No venue's launch is certified from intentions alone.
12. Warrant and contradictions: Initial regulated Solana asset issuance/trading + liquid reference equities + two prospective major external distribution venues means a realistic path to commercial cross-venue access. Opposing risks: market structure, rights portability and ATS/TSV license/trading rules, custody synchronization and venue financing, different preferred network choices, no guaranteed external market maker/trading demand. Named stock issuers did NOT themselves approve this tokenized share register; rights are intermediary entitlements.
13. Falsifier/reopen: one/both venue(s) go live but do not support these exact entitlements on Solana; formally abandon plan or choose different ledger; operational venue excludes eligible investors/actual assets; after deadline fewer than two instruments or three independent trade months. Verify operating rulebook, token balances and trades, named venue/issuer attestation and legal custody/settlement chain.
14. Resolution: HIT only when externally operated venue + two exact Solana-resident backed security-entitlement instruments + independently funded trading + three months demonstrated. MISS with verified failure/alternative, or if no qualifying real external venue activity by deadline; EXPIRED UNRESOLVED if market makers/trades are confidential with no credible public means of establishing even venue-sourced proof. Legacy NYSE cash-equities market volume does not satisfy. PVR-025 Nasdaq issuer-sponsored forecast is separate.
15. Burden / specialists / token firewall: Moderate; primary operator filing/launch-source comparison, no Deep Research or modules; ordinary continuity. Venue notional is not SOL investment demand, and security entitlement ≠ issuer-sponsored native share ownership. Proof of one qualified outside venue is one integrated scored result, not independent validated predictions for each underlying listed company.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-058-v1 — J.P. Morgan JLTXX extends from Ethereum/Solana to actual funded Base holdings

1. ID/version/method: PVR-058-v1; Institutional Architecture Forecasting v0.4 Lean Core.
2. First issue/evidence cutoff: 12 October 2026; JLTXX Ethereum + Solana and JPMD Base are separately pre-existing facts, not future prediction wins.
3. Decision object/control/ancestry: J.P. Morgan Asset Management, legally constituted JLTXX fund and its authorized service providers for fund token network availability; Kinexys multi-chain issuance infrastructure; JPMD/Payments group has a distinct cash-product control locus. Existing inherited IFC-047 (JLTXX Ethereum collateral) has a *different* primary financial function. No assumed all-J.P.-Morgan single technical mandate.
4. Task: F1 exact network selection, conditioned on actual funded fund participation, not F3 credit or JPMD adoption.
5. Use/jurisdiction/horizon: U.S. registered JLTXX tokenized government money-market fund share-class issuance/transfer on Base public Ethereum L2 for permitted institutional investors; 31 December 2028, 23:59 New York time.
6. Primary resolution object: Exact first additional public token-ownership / transfer ledger that the *existing JLTXX fund* authorizes after currently available Ethereum and Solana.
7. ONE principal scored claim: By end-2028, Base will be the first additional public blockchain authorized by the JLTXX governing prospectus/official investor terms after Ethereum and Solana for legally meaningful Token Class share balances, and qualified non-affiliated investors will hold genuinely funded Base-native JLTXX fund tokens at two consecutive month-end snapshots. A custody UI mirror, wrapped copy of JLTXX without fund-recognized token-holder rights, unregistered promotional Base contract, or unrelated JPMAM fund fails.
8. Observability/specificity: O2 for SEC filings, current supported chains and Base JPMD; O1 for future internal fund-network roadmap, actual investor mandates, technical integration and two-month holdings. Exact Base permitted as a deliberately exposed speculative forecast because the institution's settlement-money and asset-tokenization technology share a Kinexys operating interface, not because a Base fund selection is public.
9. Call/label: SPECULATIVE LEAN: Base wins JLTXX's next qualifying funded expansion among candidate networks by end-2028. This is an ordinal judgment with no calibrated numerical probability.
10. Strongest alternative: JLTXX stays Ethereum/Solana, or next selects Canton, Polygon, Avalanche, Stellar, another EVM L2, or a bank-controlled/private distribution platform; its investor demand does not overlap JPMD-eligible Base users. Existing chains may deliver sufficient reach without extra compliance expenditure.
11. Evidence/reference: SEC JLTXX October 1, 2026 prospectus supplement [J1]; J.P. Morgan November 2025 production JPMD Base press [J2]; J.P. Morgan May 2026 Kinexys fund platform interface [J3]; original May JLTXX official fund launch [J4]; current audited Oct 12 Ledger ETH-JPMAM-JLTXX-01 is read-only. Source precedence SEC > bank claim > analyst inference.
12. Warrant/contradiction/private residual: Shared bank operating group, live public Base bank money, and Kinexys fund issuance give Base an unusually actionable *same-institution securities-versus-cash convergence* rationale. But JPMD's payment-user set may be distinct from JLTXX's money-fund investor set; product compliance, custodian support, token-holder whitelist and demand may favor current Ethereum and Solana. No direct Base JLTXX decision has been found or is asserted.
13. Falsifier/next observable: first effective SEC supplement making another *additional* public chain available before Base; Base instrument prospectus inclusion but zero funded two-month holdings; formal permanent Base exclusion; initial eligible investor disclosures and token deployments; actual JLTXX subscription/redemption settlements with JPMD would raise confidence but are not required for this scored claim.
14. Resolution: HIT only if Base is chronologically the first additional public chain authorized after Ethereum and Solana, and is named in operative JLTXX documents and bona fide non-affiliated investor balances funded and present at two *consecutive* month-ends by cutoff; MISS if no qualifying Base fund issuance/holders by 2028 given adequate public documentary access or if another additional public network becomes effective first (even if Base is added later); EXPIRED UNRESOLVED if legal data or holdings are truly inaccessible after credible primary-source recovery. Generic Kinexys Base JPMD use, or JLTXX Solana use, is irrelevant to HIT.
15. Burden/modules/token: Moderate; Lean Core and targeted primary research only, specialist modules OFF. Prediction favors Base network usage, not ownership of ETH or COIN or a named private-company fee. Distinguish L2 gas/settlement economics and issuer treasury/custody balance from ETH buy pressure.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-059-v1 — Swift ledger converts first live tests into persistent commercial customer payment rails

1. ID/version/method: PVR-059-v1; v0.4 Lean Core.
2. First issue/evidence cutoff: 12 October 2026; Swift's 2026 multibank, multicurrency live transactions are historical proof, not scored here; inherited PVR-001 remains void.
3. Decision/control/ancestry: Swift shared-ledger scheme/operator + at least ten independently owned banks and their business units; legally final cash obligations remain with banks and RTGS/correspondent rails. Parent working DEV-03 and IFC-005/036; distinct from TCH PVR-019, Qivalis PVR-021, Ripple Payments PVR-041 and FIS PVR-050.
4. Task: F3 move from first live/pilot cross-institution payments to recurring *commercial customer* production breadth.
5. Use/jurisdiction/horizon: 24/7 interbank coordination of tokenized deposit commitments for corporate/financial-institution end customers across at least two non-identical currency pairs; 31 December 2028 23:59 Brussels time.
6. Primary resolution object: Persistent, customer-initiated production adoption of Swift's shared EVM/Besu-compatible ledger for bank deposit payment orchestration, not just Swift messaging, traditional gpi, or a nonledger fast-payment scheme.
7. ONE principal scored claim: By end-2028 at least TEN independent banking groups will have processed real externally initiated customer-originated or customer-benefiting payments via Swift's shared tokenized-deposit ledger in at least THREE distinct calendar months within a rolling six-month period, spanning at least TWO currency pairs; at least FIVE of those TEN must each have repeat qualifying activity in TWO of the three months. Named bank attestation or independently verifiable official operating reports must distinguish customer/business usage from all-party pilot demonstrations. No requirement that all ten disclose individual amounts.
8. Observability: O2 bank/Swift statements + current operating roster; O1 actual transactional frequency, customer origin and identities. Breadth is institution count, *not ten independent technology selections*.
9. Call: LEAN, commercially conditional. Considerable institution/technology credibility exists; uncertain customer demand, bank economics and settlement windows leave room for material underperformance.
10. Strongest alternative: banks retain shared ledger largely as a proof/treasury coordination network, while international corporate flows migrate through conventional Swift integrations, TCH, instant-payments networks, Swift's nonledger retail scheme, stablecoins, or bank-specific systems; scarce commercial customers and final settlement friction prevent ongoing multibank use.
11. Evidence: Swift March 30 Besu MVP architecture [W1]; July 9 17-bank cohort [W2]; September 28 report already used by most cohort members [W3]; HSBC/Standard Chartered August real deal [W4]; Citi/FAB/OCBC Sep 2 [W5]; Singapore DBS/OCBC/UOB Sept 10 [W6]; current primary Ledger maintains independent token-vs-software separation.
12. Warrant/contradiction: Rapid 2026 integration across disparate bank architectures and multiple currencies is an unusually strong installed pilot base; operational incentives include after-hours corporate liquidity and a common bank-to-bank commitment state. However Swift's use of existing final settlement can preserve banking-hour liquidity constraints; customer orchestration may not convert from sponsored pilot to commercial price-bearing demand. A participant roster or 'available' flag is insufficient to claim adoption breadth.
13. Falsifier/trigger: report of abandonment/indefinite freeze; drop back to bespoke pilots; explicit lack of customer-originated traffic; new 2027–2028 audited Swift operating statistics; named cross-bank commercial corridors and customer attestations. If 2026 first-mover payments continue but fail three-month repeat requirements, scored claim misses.
14. Resolution: HIT only for ten distinct independent bank groups, two actual currency pairs, and repeated commercial customer-benefiting real economic transfers in the specified months, with ≥5 banks appearing twice. Same bank's subsidiaries count once. Swift's customer legacy payments or an independent Oracle/Chainlink CRE demonstration without ledger usage fail. MISS if threshold not met by end-2028 under adequate verification; if material bank-private data cannot be recovered, EXPIRED UNRESOLVED is permissible but not a Hit.
15. Burden/modules/token: Moderate; Lean Core, no specialist module. Besu code does not imply Ethereum Mainnet execution, ETH gas or LINK/ QNT economics. Chainlink, Oracle, IBM and core-bank integrations compete for provider capture; their implementation is not individually forecast by this record.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-060-v1 — Euroclear turns a Canton collateral working group into recurring independently financed collateral mobility

1. ID/version/method: PVR-060-v1; v0.4 Lean Core.
2. First issue/evidence cutoff: 12 October 2026. Feb 2025 Euroclear-Canton GCN intent and Feb 2026 working-group repo transactions are historical, *not* already qualifying production conversion.
3. Decision/control/ancestry: Euroclear collateral/mobility operations, Digital Asset/Canton GCN infrastructure and at least two legally independent outside dealer/collateral-using counterparties; rulebook/asset owner and financing counterparties are not assumed to share one legal entity. Relevant IFC-012/090; DTCC PVR-043/044/045 use different primary operator/settlement objects.
4. Task: F3 first-phase/consortium transaction proof to funded Euroclear-involved collateral finance activity.
5. Use/jurisdiction/horizon: Cross-border institutional collateral pledge, release, substitution, intraday repo or margin financing using lawfully recognizable securities/cash positions through Canton; 31 December 2028 23:59 Brussels time.
6. Primary resolution object: The actual operating collateral/financing service relationship connecting Euroclear-controlled/serviced assets to Canton GCN applications, rather than technology-group membership.
7. ONE principal scored claim: By end-2028 a Euroclear-operated or Euroclear-authorized collateral service will support real, externally funded securities collateral movements on a Canton-family network with at least TWO independently controlled dealer/secured-lending counterparties, totaling at least €500 million in verified cumulative *executed* collateral face-value-equivalent and qualifying transfers or finance transactions during at least TWO separate calendar months. Purely tokenized inventory, internal balance mirrors, no-risk regulator demos, simulator trades and the pre-cutoff industry working-group exercises do not count. One pledged position recycled repeatedly cannot be booked as distinct notional without reporting actual executed movements.
8. Observability: O2 named operator/partners, nature of collateral initiative and regulator eligibility; O1 realized financed values, protocol location (global vs dedicated synchronizer), legal control, independent counterparties and whether Euroclear actually operates in live production.
9. Call: SPECULATIVE LEAN that meaningful Canton-family collateral mobility wins this Euroclear relationship; deliberately requires real funded scale, not just successful repo demonstration.
10. Strongest alternative: Euroclear's existing D-FMI, connected CSD architecture and conventional collateral-management services remain operative, while Canton stays complementary proof/coordination or private bespoke channels without €500m executed mobility; other operators such as JPM Kinexys, Fnality, TCH, traditional tri-party agents or private Besu win principal finance workflows.
11. Evidence/reference: Euroclear 2025 Digital Asset GCN first-phase announcement [E1]; Canton Feb 24 2026 working-group cross-border intraday repo with Euroclear among named participants [E2]; Euroclear Apr 14, 2026 DLT-securities Eurosystem collateral context [E3]; governance draft dedicated-synchronizer universal CC burn Oct 9 2026 [CC1]. Ledger CAN-* facts remain evidence authority for separated Canton/CC mechanisms, not overwritten.
12. Warrant/contradiction/private residual: Financial logic for shared collateral mobilization is strong, and Euroclear participation plus repeated industry-wide repo trial demonstrates a pathway to legally controlled inventory. But Euroclear's specific production-service approval, product scope, committed customer economics and legal source-of-truth are unresolved. Canton Global Synchronizer use is not guaranteed; private/dedicated Canton synchronizer can bypass current CC burn. Higher collateral velocity can be capital-efficient but does not necessarily imply huge blockchain fee intensity.
13. Falsifier/trigger: Euroclear openly chooses independent legacy/private infrastructure exclusively for this product; Canton role remains reporting/PoC; Euroclear does not approve a live collateral service; insufficient counterparties or genuine notional; first service contract, bank dealer rulebook, verified securities eligibility, asset-control agreement, auditor-attested real transaction population.
14. Resolution: HIT requires legally controlled Euroclear-attributable external financing/collateral role, Canton-family execution, two independent counterparties, €500m executed cumulative movements and two distinct months by deadline. Does not require public Global Synchronizer or CC burning. MISS if production fails or only unqualified demonstrations exist under adequate sources; if commercial volumes are genuinely confidential despite efforts to verify, EXPIRED UNRESOLVED rather than manufactured Hit or automatic Miss.
15. Burden/modules/token: Moderate-to-high, targeted primary Euroclear + counterparties + Canton synchronizer checks; specialist module OFF pending an actual contradiction. Canton-family win does not establish public-Canton CC utility. Current draft universal burn is not activated; classify token effect UNKNOWN until actual traffic payer, path, CC burn and external buys verified.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-061-v1 — Citi's SIX private-share depositary receipts replicate across independent corporate issuers

1. ID/version/method: PVR-061-v1, v0.4 Lean Core.
2. First issue/evidence cutoff: 12 October 2026; the June 11 Kaleido digital depositary-receipt transaction is historical launch evidence, not a prediction hit.
3. Decision/control/ancestry: Citi Issuer Services/Custody/Wealth operating stack, SIX regulated digital securities/custody platform, and distinct independent private-company boards/owners accepting receipt issuance; initial Kaleido is a Citi Ventures portfolio company and excluded. No hidden assumption that private-company share registrars adopt public blockchain.
4. Task: F3 regulated tokenized private-equity rights distribution and outside investor funding depth, not F1 SIX's already made infrastructure selection.
5. Use/jurisdiction/horizon: Privately held corporate equity represented by legally effective Citi-issued tokenized depositary receipts and settled/custodied through the SIX digital-securities infrastructure; 31 December 2028 23:59 New York time.
6. Primary resolution object: Independently controlled non-affiliated private company adoption of Citi's digital receipt issuance/custody programme with financially material outside investor subscriptions/secondary acquisitions.
7. ONE principal scored claim: By end-2028, Citi will have completed legally operative SIX-platform digital depositary-receipt issues for at least TWO private-company issuers that were *not* Citi/Citi Ventures portfolio companies or affiliates at the issue decision, and identifiable unaffiliated end-investors will have supplied at least $50 million in aggregate net new purchase/subscription consideration across those two issues. Parent-level cross holdings or a Citi Wealth internal reshuffle of already owned stock fails; one issuer on a different unregulated venue cannot satisfy this SIX-specific claim.
8. Observability: O2 first named real transaction and legally regulated infrastructure; O1 targeted next private-company prospectuses, investor provenance, external net funded amounts and intermediary custody data. First-issue US private-company law/distribution limits are meaningful private residuals.
9. Call: SPECULATIVE LEAN that a broadly distributed private-securities receipt programme emerges through the incumbent SIX infrastructure, rather than remaining a one-off platform venture transaction.
10. Strongest alternative: private companies retain cap-table restrictions and conventional direct/secondary share sales; SPVs or conventional custody win; wealth clients lack demand; Citi opens a multi-network service but not SIX specifically; sufficient independent companies participate but subscribed amounts fall under $50m.
11. Evidence: Citi Issuer Services own June 11, 2026 first product and Kaleido receipt transaction [C1]; SIX own acknowledgement [C2]. Citi explicitly discusses future multichain interoperability, *not* continued SIX exclusivity. No issued 2028 client volume is implied by a launch press release.
12. Warrant/contradiction/private residual: Citi directly controls issuance + custody + wealth distribution and SIX provides credible compliant security-record infrastructure; that is a stronger distribution machine than a pure startup STO. Against this, late-stage private issuers face U.S. cap-table/shareholder thresholds and transfer controls, privacy, external pricing and secondary liquidity issues; debut Kaleido may reflect Citi's own investment relationship, not a repeatable client market.
13. Falsifier/trigger: independent issuer adoption remains zero; Citi publicly pivots to other networks or SPVs and does not use SIX for next non-affiliate; second unaffiliated issuer confirmation, legally operative receipts, audited externally funded proceeds and end-investor attestations.
14. Resolution: HIT only when at least two non-Citi-affiliated firms had separately consented to legally effective SIX-resident Citi receipt issues and unaffiliated investors' additional financed acquisition/subscription totals ≥$50m; purchased shares already owned internally or related-party experiments excluded. MISS on documented non-conversion after deadline or $50m failure if verified; genuine withheld investor amounts may generate EXPIRED UNRESOLVED without accuracy credit.
15. Burden/modules/token: Moderate, official bank/platform/client issuance primary corroboration; no specialist module. SIX regulated DLT is not the same as a public Ethereum, Stellar, Canton Global Synchronizer or their native token demand. No inferred ETH/SOL/CC/XLM capture absent separate actual rail and fee proof.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-062-v1 — Standard Chartered and LMAX turn XRP-Ledger RLUSD custody into significant repeat trading collateral

1. Forecast ID / version / method: PVR-062-v1, Institutional Architecture Forecasting v0.4 Lean Core.
2. Freeze / evidence cutoff: 12 October 2026; Standard Chartered XRPL RLUSD custody is *already live*, collateral launch has *not* been verified. No backdating.
3. Decision object, control and ancestry: Standard Chartered (regulated bank custody and collateral mirroring); LMAX Group's authorized venue/prime/collateral products; Ripple's RLUSD issuer/network distribution. Joint approvals required. This is a third-party commercial collateral branch, not a Ripple Prime deployment, and not necessarily a single unified procurement.
4. Task: F3 Maturity / Conversion, not F1 chain selection; XRPL RLUSD custody network was explicitly selected earlier.
5. Use, jurisdiction, horizon: Eligible institutional traders, Standard Chartered DIFC-regulated custody and relevant LMAX trading venues, legally recognized funded collateral; by 31 December 2028 23:59 New York time.
6. Primary resolution object: REPEAT externally funded RLUSD collateral accepted against actual trading obligations through Standard Chartered/LMAX arrangement.
7. ONE Principal Scored Claim: By the deadline, at least two non-affiliated, independently controlled LMAX institutional customers will have used RLUSD held on XRPL at Standard Chartered as legally eligible trading margin/collateral, with an aggregate of at least US$25 million *actually recognized against funded obligations* in each of at least two separate calendar month-end periods. The two month-ends must be at least 28 days apart; recycled intraday movement does not multiply credited collateral stock.
8. Observability / specificity: O1–O2; legal client IDs and month-end values may be commercially private. Bank/LMAX auditable, dated confirmation or independently verifiable deposit/pledge and liability records needed; mere XRPL circulating supply insufficient.
9. Call / strength: SPECULATIVE LEAN for meaningful external collateral conversion, NOT evidence of current scale.
10. Strongest alternative: eligible RLUSD never becomes accepted collateral in practice; service is restricted to one internal/test client; LMAX supports RLUSD on Ethereum or offchain ledger rather than specifically bank-custodied XRPL RLUSD; custody stays passive and trading collateral remains USD cash, Treasuries or USDC.
11. Evidence basis: Standard Chartered issuer-bank release 12 Oct 2026 [S1]; Ripple's corresponding account of same event (correlated first parties), Oct 12 Ledger (no edits), current Ripple audited report and inherited full-stack Master.
12. Warrant and counterpressure: Bank custody already live, LMAX formally agreed to pursue collateral mirroring, trading clients value retained bank custody. Critical pending documents/testing/approvals, jurisdiction and client onboarding. Mirroring's offchain accounting is a major token-use bypass: RLUSD balance exists on XRPL but adjustments can remain internal; XRP may only be tiny gas/reserve demand.
13. Falsifier / new evidence: Formal cancellation, rejection of XRPL collateral, adoption restricted to a different chain, no independent client, no actual margin accepted, or failure of two-month $25m threshold. Follow bank eligibility rulebook, venue legal docs and operating disclosures; reopen if architecture or approvals materially change.
14. Resolution: HIT only with reliable source proving client independence, XRPL RLUSD inventory, recognized legally operative collateral, both month-end aggregates and genuine funded trading obligations. MISS if contrary choice or unmet by deadline. EXPIRED UNRESOLVED if confidential clients/notional prevent verification despite suitable inquiry; do not grant a convenient partial hit for announcing LMAX eligibility.
15. Burden / specialist modules / token firewall: Moderate targeted bank/venue primary-source tracking; no specialist modules. XRPL network and RLUSD utility are supported by a hit, but bank custody success, RLUSD business revenue, and XRP persistent demand remain different propositions.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-063-v1 — The Clearing House/Quant moves from announced national network to repeat interbank tokenized deposits

1. ID/method: PVR-063-v1 / Institutional Architecture Forecasting v0.4 Lean Core.
2. First freeze/cutoff: 12 October 2026; TCH selection of Quant and H1 2027 participant availability are existing evidence, not fresh scored choices.
3. Decision control/ancestry: The Clearing House utility controls interbank network and operating/rulebook infrastructure; participating member banks independently decide to move liabilities and serve customers; Quant is selected interoperability/orchestration contractor. Inherited PVR-019 has the same upstream network ancestry but only availability as primary scored object.
4. Task: F3, bounded commercial bank-money adoption rather than a novel F1 vendor bet.
5. Use/horizon: U.S. regulated interbank tokenized-deposit clearing/settlement and commercial customer treasury/payments, by 31 December 2028.
6. Primary resolution object: genuine REPEATED bank-to-bank tokenized-deposit settlement through the TCH On-Chain Money Initiative, with Quant orchestration in service.
7. ONE scored claim: By end-2028, at least five distinct chartered deposit-taking institutions will originate or receive settled real customer-value tokenized-deposit transfers through the operational TCH On-Chain Money Initiative, with qualifying interbank transfers in at least three different calendar months and at least one disclosed outside-bank customer-use class (such as commercial treasury, supplier payments, or digital-asset settlement). A bank must actually issue/receive a legally recognized liability transfer; being an equity owner or listed supporter of TCH does not count.
8. Observability: O2 for operator/bank aggregate and named production; O1 for transaction data/private bank customers. Family/network specificity is directly contracted and already known; execution depth still unknown.
9. Call: LEAN for five-bank repeated adoption over two years; not a forecast of a particular dollar aggregate.
10. Strongest alternative: TCH offers connection but member banks use it only for pilots/bilateral demos; Citi/JPM tokenized money remains within proprietary books; Swift, RTP/CHIPS, conventional cash rails and stablecoin settlement retain customer demand; bank adoption below five.
11. Evidence: TCH 5 June bank-initiative launch [S3]; TCH 24 September Quant selection and H1 2027 window [S2]; inherited TCH PVR-019, Quant audited report, canonical Oct 12 Ledger read-only.
12. Warrant: TCH already operates significant US financial clearing rails and has documented numerous supportive banks, with Quant taking a specified technical role. Counterpressure: member banks do not have to put material real money on the new network; coordinated rulebooks, finality, treasury workflows and security reviews can delay expansion; TCH's daily legacy volume is NOT forecast onchain throughput.
13. Falsifier / trigger: first commercial participant disclosure, bank charter and settlement disclosures, transactions across months, product customer types; halt/reshape of utility or switch away from Quant; bank tally fails by 2028.
14. Resolution: HIT only if all five, repeat-three-month and external commercial-use requirements proved using bank/operator sources or robust regulated reporting. MISS if deadline unmet. EXPIRED UNRESOLVED for records not recoverable from reliable permitted evidence, not for mere failure to search. No credit for publicity by five equity-owner banks.
15. Burden/token separation: Moderate. No module activated. Quant software selection is already real, but no part of this forecast claims enterprise fiat revenue is forcibly converted to QNT; separate Fusion usage/staking/gas evidence would be required.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-064-v1 — MUFG commercializes external Japanese-government-bond repo on Canton

1. ID/method: PVR-064-v1 / v0.4 Lean Core.
2. Date / cutoff: 12 October 2026; August 13 MUFG pilot remains a PoC; Progmat securities estate separately migrated to Avalanche earlier, *not* a JGB repo production hit.
3. Object/controls/ancestry: MUFG Bank, MUFG Trust, MUFG Morgan Stanley Securities and independent external JGB repo counterparties; Digital Asset/Canton and Secured Finance supply architecture/protocol; Progmat is bridge to book-entry practices. Distinct Japan repo cluster from Euroclear international collateral PVR-060 and other Canton/DTCC forecasts.
4. Task: F3 commercial conversion of a known Canton/JGB programme.
5. Use/jurisdiction/horizon: Japanese-government-bond intraday/repo financing, Japan with possible international banks/dealers, by 31 Dec 2028.
6. Primary resolution object: financed, legally recognized Canton-orchestrated JGB repo with independent outside-MUFG principal and lifecycle settlement.
7. ONE Principal Scored Claim: By deadline, a live MUFG-related Canton-based JGB repo service will have handled at least ¥20 billion of cumulative executed, actually financed repo principal across at least two separate calendar months, including at least one legally independent, non-MUFG bank, dealer, asset manager or financing counterparty as principal, with binding opening- and closing-leg obligations and the corresponding JGB book-entry record legally reconciled. Real cash exchange and reuse of at least one position outside MUFG required; trial/sham transactions excluded.
8. Observability: O1–O2; bilateral notional and legal account book may be confidential. Verification via MUFG/partners/regulator/approved transaction reporting needed; Canton app count not enough.
9. Call: SPECULATIVE LEAN at meaningful commercial scale; no presumption PoC successfully crosses production controls.
10. Strongest alternative: conventional BOJ-NET/JGB book-entry and established repo clearing remain superior; sandbox stops at MUFG internal tests; token representation stays record-mirroring only; Canton runs within private synchronizers without public Global Synchronizer usage; pricing/regulatory/capital barriers impede full lifecycle.
11. Evidence: MUFG/Digital Asset Aug 13 primary release [S4]; Secured Finance role specification Aug 13 [S5]; Progmat completed Avalanche integration and separate securities migration [S6]; canonical Ledger, Canton asset audited report.
12. Warrant + limits: Named MUFG operating banks and dealers, real legal JGB book-entry update linkage, regulatory-supported PoC, dedicated Secured Finance repo protocol and credible cross-border repo analogues. But 2026 test participants belong to one financial group; no external repo is yet proven. Book-entry account ledger stays the authoritative JGB-rights system and Canton state may be orchestration/mirror. Distinguish Canton technology family, public GS traffic, and fee-paying CC.
13. Falsification/reopen: failed legal finality or JGB ledger reconciliation, project exits Canton, no outside counterparty, transaction only demo, amount or month count below threshold. Monitor regulatory rulebook, operating participant disclosures, independent counterparty names and official notional by period.
14. Resolution: HIT only with real financing, legal reconciliation, ≥¥20bn unique executed principal, ≥two months, ≥one outside MUFG principal. Count repo opening principal once, not both opening/closing or repeated mark-to-market as extra principal. MISS otherwise by 2028 subject to credible evidence. Confidential aggregate unresolved → EXPIRED UNRESOLVED, not invention.
15. Burden/specialist/token firewall: Elevated (Japanese-language legal/custody sources plus repo lifecycle), no module yet activated; use local primary retrieval when new evidence warrants. Successful Canton-family repo ≠ CC paid Global Synchronizer burn; separate synchronizer and payer needed. The parallel Progmat Avalanche securities migration ≠ AVAX directly financing JGB repo.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-065-v1 — R3/SIX private-Corda assets become independently funded Solana financial activity

1. ID / method: PVR-065-v1 / v0.4 Lean Core.
2. First issue/cutoff: 12 October 2026; R3/Solana collaboration announced May 2025, Corda Protocol yield system Dec 2025, and R3/SIX reports a built connector in 2026. No outside-capital migration/usage inferred from that alone.
3. Control and ancestry: R3 connectivity/enterprise Corda infrastructure; SIX project tech/market operator; *distinct independent licensed Corda network asset originators/issuers and financing or distribution users* control economic legal access. This is not a prediction that all R3 customers adopt the bridge or that SIX alone issues every asset.
4. Task: F3 private-origin securities to public network funded commercial conversion.
5. Use/jurisdiction/horizon: regulated securities and financial claims from permissioned Corda origination, later monetized/distributed/settled against onchain cash or used as collateral via public Solana, global relevant license jurisdictions, by 31 Dec 2028.
6. Primary resolution object: independently funded *economic use on public Solana* of genuine Corda-origin regulated securities claims, not an unfunded interoperability proof.
7. Principal Scored Claim: By end-2028, at least two legally unrelated, independently controlled regulated security issuers/originating Corda networks will have enabled assets originally legally recorded on Corda to be used in genuine funded distribution, DvP settlement, secured financing or collateral on public Solana, with a combined ≥US$25m of qualifying outside-funded executed transfers/financing across at least two different calendar months. The underlying Corda rights may remain there; valid legally enforceable corresponding Solana claims or commitments must be shown.
8. Observability: O1–O2; chain transfer telemetry can show flows but not legal beneficial interest and investor capital without original issuer/account documentation. Solana exact network is upstream R3 partner, not new first-chain selection.
9. Call: SPECULATIVE LEAN for commercialization; more conservative on double-originator breadth and capital volume.
10. Strongest alternative: Corda remains private legal state; Solana is only a technical confirmation channel; customers refuse collateral/compliance bridging; fungible proxies unsupported; access demand concentrates in a single R3/SIX demonstration; issuers select Canton, Ethereum, Avalanche or private APIs instead.
11. Evidence: R3/Solana May 2025 partnership [S7]; R3 Foundation Dec 2025 Solana RWA vault [S8]; R3's 2026 primary corporate social-media report referencing SIX connector [S9], lower-strength for live legal/financial state than signed primary transaction disclosure; controlling Solana audited report and Oct12 Ledger.
12. Warrant: direct R3 strategy, credible private installed-base and SIX participation in bridging architecture, deep Solana collateral/DeFi execution pool. Strong constraints: regulated asset rights may remain on Corda, bridge technical behavior is not legal issuance, two independent originators not yet verified funded. Provider aggregate claim of RWA value is *not* Solana volume.
13. Falsifier/update: licensed client issuer announcements, identified legally operative bridged asset, actual investor money/collateral agreement, Solana address and settlement records, chain substitution, security/legal/custody veto, failure to reach two issuers or ≥$25m by 2028.
14. Resolution: HIT only when both independent originator rights, actual qualified Solana onchain economic transaction(s), original legal asset claim, $25m non-double-counted executed value and two-month breadth substantiated. MISS if different architecture/below threshold. EXPIRED UNRESOLVED only for irreducibly private investor identity/capital; screenshot bridge demo never scores.
15. Burden/token firewall: Elevated because legal entitlements and public/private mapping complex; no module activated. SOL pays/sponsors chain fees but notional does not translate into proportional SOL purchased/staked. R3/Corda success may accrue to R3/issuers more than SOL.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-066-v1 — Chainlink CRE becomes repeated production signing middleware at three Swift-ledger banks

1. ID/method: PVR-066-v1 / v0.4 Lean Core.
2. Issue/cutoff: 12 October 2026; Chainlink announced a solution 28 September; 17 bank ledger first movers already had used Swift-ledger payment workflows. No three-bank CRE production use presumed.
3. Control/ancestry: Swift controls shared settlement-log infrastructure; banks independently select/authorize key handling and middleware; Chainlink supplies CRE orchestration/self-signing pathway. PVR-059 measures broad Swift outside-customer payment scale; PVR-044 measures DTCC/CRE collateral and belongs to a different client/technical system.
4. Task: F3 bank-specific installed production middleware, not F1 unknown Swift ledger selection.
5. Use/horizon: actual tokenized-deposit instructions and signer-controlled bank transactions across Swift ledger and bank-ledger ecosystems, by 31 Dec 2028.
6. Primary resolution object: Chainlink CRE actually orchestrates or authorizes real-value Swift shared-ledger operations for multiple independently controlled banks, beyond tests or software certification.
7. ONE scored claim: By the deadline, at least three separately chartered financial institutions will have operated Chainlink Runtime Environment (CRE) self-signing/orchestration as part of actual real-value Swift-blockchain-ledger tokenized-deposit transfers, with individually identifiable qualifying production use spanning at least three distinct calendar months overall and at least two banks participating in a common end-to-end transaction or settled workflow. Each bank's use must be attributable to CRE, not assumed from Swift participation.
8. Observability: O1–O2, institution procurement/security details private but participant/vendor joint attestations may identify the platform, months and real value; onchain CRE telemetry without verified bank attribution insufficient.
9. Call: SPECULATIVE LEAN on three-bank CRE adoption; credible solution fit but bank deployment unknown.
10. Strongest alternative: banks use native Swift SDK, bank-internal signing, other enterprise orchestration (including Quant or in-house API), direct Besu connectors, or delay production. Chainlink operates as optional integration and does not win multiple operational mandates.
11. Evidence: Chainlink 28 Sep CRE/Swift integration product announcement [S10]; Swift 28 Sep statement showing actual first cohort payment activity [S11]; existing canonical Ledger and Chainlink evidence; note Chainlink source directly describes its own intent, not a bank selection.
12. Warrant: self-custodied signing/key-control and interop are bank-relevant requirements; initial Swift cohort large; standardization could lower integration costs. Real competing vendor routes and installed bank IT path dependence matter; the 17 Swift banks cannot be counted as Chainlink adopters. Swift's ledger runs a permissioned Besu-compatible technology, NOT public Ethereum mainnet.
13. Falsifier / triggers: bank-specific technical contract or explicit alternative middleware choice, three CRE banks' operational attestations, first customer payments with CRE, technical/risk rejection, venue changes or insufficient attribution by 2028.
14. Resolution: HIT only with CRE identified in real bank signing/orchestration, three chartered bank users, multi-month activity, meaningful bank-to-bank workflow. MISS if below threshold, Swift succeeds via non-Chainlink middleware, or deadline passes without compliant evidence. EXPIRED UNRESOLVED only when secrecy prevents adjudication despite targeted effort; mere source announcement or unsupported marketing quote not enough.
15. Burden/token firewall: Moderate source triangulation bank/Swift/Chainlink; no specialist modules. Chainlink software/service revenue may eventually feed LINK Reserve according to separate rules, but Swift message count, CRE job count, and new outside LINK acquisition must not be equated without cash-to-LINK evidence.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-067-v1 — Canada's six-bank tokenized-deposit system chooses Hyperledger Fabric

1. Forecast ID / version / method: PVR-067-v1; v0.4 Lean Core with no activated specialist modules.
2. Freeze/evidence cutoff: 12 Oct 2026; prospective original call, no retroactive score/issuance date.
3. Decision object / controller / ancestry: Jointly governed initiative of BMO, CIBC, National Bank of Canada, RBC, Scotiabank and TD; final shared technology decision is collective, not six independent bank selections. The Bank of Canada's separate Samara project is precedent, *not* an ancestor selection for this new project.
4. Task: F1 exact technology/platform family (Hyperledger Fabric) for a still-unannounced core interbank ledger.
5. Use / jurisdiction / horizon: Canadian-dollar bank deposit transfers between participating regulated Canadian banks; by 31 Dec 2028.
6. Primary architecture slot: authoritative shared ledger recording interbank tokenized *commercial-bank deposit* obligations/transfers. Peripheral gateways, integration tools and bridge middleware do not resolve this slot.
7. ONE principal scored claim: The six-bank joint initiative will formally select and deploy Hyperledger Fabric as the authoritative/shared blockchain ledger for its first materially committed interbank tokenized-deposit transfer system by 31 Dec 2028, rather than using Fabric solely for a lab experiment or peripheral connector. Evidence of a binding technical decision and a bank-supported funded operational transfer is required; an official production architecture statement with a legally funded bank transfer is sufficient even without public transaction-level telemetry.
8. Observability/specificity: O1–O2; provider/ledger is a lower-public-visibility procurement decision. Exact choice is below Lean because there is no known target-specific Fabric procurement or contract.
9. Call: LIVE CONTENDER — directional high-risk Fabric bet, not Lean/Strong Lean. This is a forecast to test, not a claim that Fabric currently wins.
10. Strongest alternative: consortium employs a permissioned EVM/Besu shared ledger, Quant-managed infrastructure, Corda/Canton-family, another internally governed ledger, multiple linked bank ledgers, or conventional central-bank settlement. The March RBC/TD Samara tech choice may not carry over to these six banks or this different legal liability.
11. Evidence basis: six-bank 22 September primary announcement [CA-1]; Bank of Canada's March Samara real $100m bond and cash experiment with dual Hyperledger Fabric ledgers [CA-2]. Existing v3.7 portfolio contains Samara as a historical negative control, but no official six-bank Fabric F1 outcome.
12. Warrant / opposite case / unknown: RBC and TD have real experience operating regulated, permissioned Fabric asset+cash ledgers, supplying a plausible transferable technical/regulatory knowledge base. However, different governance and payment functions weaken direct portability; the six-bank announcement does not identify a vendor. No publicly recovered architecture shortlist. The strict F1 gate therefore caps strength at Live Contender.
13. Falsifier / next observable: consortium technical RFP/vendor award, bank architecture design, commercial legal settlement documentation, contracts/independent node stack; confirmed selection of another authoritative platform or no qualifying Fabric selection by deadline.
14. Resolution rule: HIT only on verified shared Fabric production-choice and genuine funded legal bank-liability transfer using that core ledger. MISS on an alternative architecture, abandonment, or deadline failure; unresolved only on documented irreducible evidence absence after proportionate searches. Peripheral or Samara-only Fabric usage fails. One coordinated shared selection, not six bank decisions.
15. Burden/modules/token firewall: Moderate; no specialist module. Hyperledger Fabric has no requisite public token. If the bank initiative succeeds, do not attribute that adoption to ETH, QNT, CC, HBAR or another coin without separate executed public-token mechanism.

Reader-facing impact: A Fabric choice could signal banks favoring governed/private banking infrastructure over a single public settlement rail; it could scale from bank-to-bank liquidity movements into programmable corporate payments. Both are *conditional scenarios*, not this record's scoreable prediction. A Fabric win need not benefit any cryptocurrency token.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-068-v1 — Standard Chartered issues real bank-deposit money on Arc

1. ID/version/method: PVR-068-v1; v0.4 Lean Core.
2. Freeze/cutoff: 12 Oct 2026, original prospective issue. Circle Arc Mainnet and Standard Chartered's founding-validator/integration relationship existed before this freeze.
3. Controller / ancestry: Standard Chartered or a separately named, suitably authorized Standard Chartered deposit-taking entity controls liability issuance and bank client eligibility; Circle controls Arc protocol and USDC (a distinct issuer). Related, but distinct from Standard Chartered's already-live Circle USDC mint/redeem service, Swift interbank tokenized deposits and XRPL/RLUSD custody.
4. Task: F1 exact public network, with a demanding bank-issued operating-use proof to distinguish economic commitment from access/validator marketing.
5. Use / jurisdiction / horizon: authorized regulated bank-deposit issuance and client transfer on Circle Arc Mainnet, through 31 Dec 2028; issuer jurisdiction may vary subject to bank/regulator approvals.
6. Primary architecture slot: ledger of legally enforceable *Standard Chartered commercial-bank deposit liabilities* used for external client money transfers; not Circle-issued USDC/USYC/RLUSD or a bank's role as validator/custodian alone.
7. ONE scored claim: By end-2028, a Standard Chartered deposit-taking entity will select Arc Mainnet as the ledger for a legally operative bank-issued deposit-token product, and at least two separately controlled non-affiliate institutional/corporate clients will complete externally meaningful funded transfers of those bank deposit claims on Arc in two different calendar months. The legal deposit issuer and Arc provenance must be shown.
8. Observability: O1–O2; public contracts can establish Arc ledger, but client/custody and legal money may be private. Exact Arc selection is presently not publicly established for this bank-issued product.
9. Call: LIVE CONTENDER (speculative, below Lean); not an announced Standard Chartered deposit-product network.
10. Alternative: the bank remains a Circle/USDC access gateway or Arc validator without issuing its own deposits there; internal bank infrastructure/Swift ledger, Canton, Ethereum rollups or other rails carry its bank-money products; legal deposit issuance fails regulatory or treasury sign-off.
11. Evidence: Circle's Aug 5 founding-validator/integration description and Sep 16 Arc Mainnet [ARC-1][ARC-2]; Standard Chartered's Jul 2 live Circle institutional USDC mint/redeem [ARC-3]; bank's Aug 19 Swift tokenized-deposit transfer [ARC-4]. These show adjacency and capability, not this selection.
12. Warrant & opposing evidence: Existing bank money/tokenization, real operational stablecoin access and Arc operator participation reduce integration friction. But bank deposits have different legal, supervisory, balance-sheet and redemption constraints from Circle-issued stablecoins; a validator partnership alone is weak direct evidence. Therefore Live Contender, not stronger.
13. Falsifier/triggers: regulated issuance terms, bank deposit register/lifecycle, named clients, payment ledger/transaction proof; explicit choice of another primary rail, Arc role limited to USDC access, or no qualifying Arc deposit token by 2028.
14. Resolution: HIT only if *bank's own regulated deposit liability* and Arc's actual public execution as recorded plus two unrelated outside-clients' funded transfers in two months are verified. Circle-issued stablecoin distribution or any validator status does not count. Alternative bank ledger, missed client proof or deadline fails.
15. Burden / token firewall: Moderate; no specialist modules. Arc public-network adoption would not automatically create demand for an ARC token: Arc currently charges USDC gas, and a native ARC token's economic mechanisms depend on future governance and issuance. Public coin benefit is unproven.

Reader-facing impact: If realized, a G-SIB would be using a public L1 as a bank-liability settlement venue rather than merely supporting third-party USDC custody. Potential expansion into intrabank cash pools, corporate treasury, DvP and bank-to-bank settlement is a conditional possible consequence—not a guaranteed adoption path or ARC-token demand.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-069-v1 — Stellar captures majority of actual Marketnode/CGS tokenized fund holdings

1. ID/version/method: PVR-069-v1; v0.4 Lean Core.
2. Freeze/cutoff: 12 Oct 2026; no retrospective promotion from announced compatibility.
3. Controller / ancestry: CGS International/CGS SG and the independent funds/managers decide asset entitlements, placements and eligibility; Marketnode decides Gateway technical distribution and operational route; beneficial investors select holdings. Distinct from BNY Investments' own previously named Stellar programme (PVR-034).
4. Task: F3 relative economic adoption of already announced multi-network possibilities, not first technology availability and not a new F1 single-chain procurement.
5. Use / horizon: CGS APAC and US Core Multifactor Strategy funds, live regulated outside-investor subscriptions/holdings through Marketnode Gateway, by 31 Dec 2028.
6. Primary maturity/scale object: funded attributable CGS beneficiary interests actually outstanding per public-chain ledger after netting double representations, not headline "supported chain" list.
7. ONE scored claim: In two distinct reporting month-ends in calendar 2028 at least 28 days apart, Stellar will hold MORE THAN 50% of all externally funded, outstanding onchain tokenized investor interests across CGS International's two named Marketnode-distributed multifactor strategy funds, including EVM, Solana, Stellar and XRP Ledger routes in the denominator, with ≥US$10 million aggregate verified real external subscribed tokenized interests at each month-end. Duplicate bridge wrappers and issuer treasury inventories do not count toward funded holdings.
8. Observability: O1–O2; definitive per-chain registered beneficial interests may be internal to regulated fund admin. Only externally verifiable issuer, registrar or audited operator reports suffice; raw explorer token balances could overstate beneficial ownership.
9. Call: LIVE CONTENDER (bold low-confidence chain-share winner), not a Lean exact first-network selection.
10. Alternative: distribution is genuinely diversified, with Solana or EVM dominating due to investor access/liquidity; XRPL takes the lead; tokens available at launch never attract material outside subscriptions; >50% Stellar never achieved.
11. Evidence: Marketnode April 14 CGS announcement explicitly describes EVM plus Solana/Stellar/XRPL launch support [CGS-1]; separate July 31 BNY Investments/Stellar route evidences one strong Marketnode–Stellar distribution relationship [CGS-2]; earlier July 2025 Marketnode Gateway multichain support [CGS-3]. Neither BNY nor general Gateway support proves CGS funded Stellar balances.
12. Warrant/competition: Marketnode's committed Stellar integration and existing BNY client path create a plausible network-local operating advantage for regulated funds; CGS investor demographics, custody/pricing/market-maker selection and actual chain distributions are unknown. No proof exists that it dominates non-Stellar routes. Confidence stays below Lean.
13. Falsifier/trigger: CGS first fund factsheets, fund registry, contract addresses, administrator reconciliation, per-chain beneficial balances; verified preference for Solana/EVM/XRPL or lack of external funded activity by deadline.
14. Resolution: HIT only if both month-end >50% majority tests, complete denominator, no counting duplication, ≥$10m funded holdings, and attributable CGS token register established; MISS otherwise. If chain distributions are inherently private despite reasonable retrieval, explicitly mark observation limits; do not treat unknown as HIT.
15. Burden/token: Moderate; no specialists. Stellar network issuance/distribution ≠ major XLM capture: fees and minimum balances remain small relative to asset principal; XLM investment repricing is separate.

Reader-facing impact: Stellar becoming the *preferred actual investor balance* network for an independent Asian investment-manager product would be more informative than another "Stellar supported" announcement. Potential follow-on distribution of funds across Asian capital markets is conditional; no forecast of $1bn AUM or proportionate XLM value.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-070-v1 — Twenty-one global financial institutions issue their first consortium dollar stablecoin on Ethereum Mainnet

1. Forecast ID / Version / Method Version: PVR-070-v1; Institutional Architecture Forecasting v0.4 Frozen Trial Lean Core; independent new F1 object, child specificity of family-level PVR-014, not independent evidence of a second consortium decision.
2. Freeze Date / Evidence Cutoff: First issued 12 October 2026; all public material examined through 12 October 2026. First Lean-or-better not earned.
3. Decision Object / Control Locus / Decision-Cluster ancestry: The announced 21-institution USD stablecoin venture, under future jointly governed operating company and regulators. One centralized issuance decision; founder banks are not counted as 21 independent architecture selections. Ancestry: 2025 ten-bank public-chain exploration → Sep 2026 21-member venture → existing PVR-014 public-family forecast.
4. Forecast Task: F1 exact first production public blockchain; independent test of a more specific choice than PVR-014, never a replacement for PVR-014.
5. Use Case / Jurisdiction / Horizon: USD fiat-backed stablecoin available to wholesale, institutional and possibly retail users across major jurisdictions; outcome by 31 December 2028.
6. Primary Resolution Object: First public L1/L2 ledger on which a legally issued, externally circulating venture dollar stablecoin is actually made available for real third-party redemption/transfer; not a later additional deployment or a testnet.
7. Principal Scored Claim: The venture will choose Ethereum Mainnet as the FIRST public network for its first externally usable USD stablecoin, with documented real circulation and third-party transfers by end-2028. An Ethereum L2 alone (including Base) does not count as Ethereum Mainnet; adding Ethereum only after a different chain fails.
8. Observability / Permitted Specificity: O1 exact-network before launch; chain attribution becomes O3 upon verifiable issuer statements, contracts and circulating tokens. A low-confidence exact-chain bet despite a stronger preexisting public-chain-family expectation.
9. Call / Forecast Label: LIVE CONTENDER — Bold exact-network selection; below Lean. Not a claim that the banks have selected Ethereum.
10. Strongest Alternative: Consortium initially launches on Solana, Base, Arc, another EVM network, a limited permissioned venue, a multichain simultaneous day-one issuance with no unique first ledger, or fails to issue.
11. Evidence Basis / Controlling Research: Consortium announcement commits to global reserve-backed issuance with public-chain history but names no exact chain [G21]. Existing official family-level PVR-014 remains separate. Source: https://www.santander.com/en/press-room/press-releases/2026/09/group-of-leading-international-financial-institutions-to-establish-stablecoin-enterprise
12. Load-Bearing Warrant / Opposition / Private Residual: Ethereum Mainnet supplies an established widely used stablecoin/regulated-finance environment and broad custody/tooling, potentially attractive for first legally conservative issuance; that is ANALYST INFERENCE, not consortium procurement evidence. A cheaper/faster chain or multichain first-day strategy is at least as live. No target-specific shortlist, contract or code recovered.
13. Falsifier / Next Observable: Legal venture documentation, first issuance terms, issuer contract addresses, chain-specific redemptions, public registry. Any earlier launch on another chain, exclusively private issuance, or multichain tied launch defeats this strict first-network bet.
14. Resolution Rule: HIT only when official/legal issuer terms and independently inspectable real funded balances establish Ethereum Mainnet as unique first live externally transferable USD issuance. MISS if another network precedes it, ties without unique first, or deadline passes; no retroactive redefinition to “EVM family” or “Ethereum ecosystem”. Document irreversible observability ceiling if official public evidence stays inadequate.
15. Burden / Specialist Modules / Token Firewall: Moderate; specialist modules off. Ethereum public network use does not prove meaningful ETH burn/staking demand, much less proportional ETH price appreciation. This forecast has the same issuer-decision ancestry as PVR-014 and must not be double-counted as independent accuracy.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-071-v1 — Goldman Sachs and BNY turn tokenized money-market fund shares into pledged collateral through Canton

1. Forecast ID / Version / Method Version: PVR-071-v1; forecasting v0.4 Lean Core; distinct funded collateral use case downstream of known GS DAP/BNY token mirror; correlated with broader Canton collateral ecosystem forecasts but separate exact counterparties and legal assets.
2. Freeze Date / Evidence Cutoff: First issued 12 October 2026; evidence cutoff 12 October 2026.
3. Decision Object / Control Locus / Decision-Cluster ancestry: BNY LiquidityDirect/BNY transfer agent and Goldman Sachs GS DAP technical operator, plus issuer/financing desks and one outside collateral taker. BNY remains official share-record authority under existing arrangement; Goldman uses Digital Asset technology. Neither automatically controls independent lender acceptance.
4. Forecast Task: F3 consequential collateral conversion with specified Canton execution rail; NOT a forecast of initial tokenization, already launched in 2025.
5. Use Case / Jurisdiction / Horizon: U.S.-domiciled institutionally held money-market shares, securities financing/credit collateral, by 31 December 2028.
6. Primary Resolution Object: Legally operative pledge/lien and funded loan/repo workflow over *the BNY/GS DAP initiative’s actual tokenized fund entitlement*, executed on Canton public Global Synchronizer (not merely Digital Asset/Canton-derived private applications).
7. Principal Scored Claim: By end-2028, a BNY/Goldman Sachs GS DAP-recorded money-market-fund entitlement will be used in at least two genuinely funded collateralized financing transactions with an independent nonaffiliate financing counterparty, totaling US$100 million or more notional, with the token/pledge state executed and verifiably synchronized on Canton Global Synchronizer. Mere mirror tokens, test pledge, and privately managed Canton-derived ledgers do not count.
8. Observability / Permitted Specificity: O1–O2, since legal pledge records and private synchronizer routing can be private. Public named institutional confirmation and legally meaningful confirmation of the GS role required.
9. Call / Forecast Label: LIVE CONTENDER — Bold funded-conversion/Canton-routing bet; below Lean.
10. Strongest Alternative: BNY mirror tokens remain read-only reference records; legally operative collateral is maintained on BNY books with conventional lien paperwork; a non-Canton private GS DAP deployment or other network serves first funded collateral.
11. Evidence Basis / Controlling Research: BNY/Goldman July 2025 primary launch confirms *mirrored share records*, with BNY still preserving official books, and expressly describes collateral as future possibility, not current legal capability [GS]. Goldman 2024 GS DAP strategic/technology ancestry establishes use of Digital Asset technology, not global public Canton use [GSS]. Sources: https://www.goldmansachs.com/pressroom/press-releases/2025/bny-goldman-sachs-launch-tokenized-money-market-funds-solution ; https://www.goldmansachs.com/pressroom/press-releases/2024/announcement-18-nov-2024 ; https://www.bny.com/corporate/global/en/solutions/platforms/liquidity-financing-solutions/liquidity-direct.html
12. Load-Bearing Warrant / Opposition / Private Residual: BNY already controls liquidity and collateral workflows, and GS DAP is built on Digital Asset technology; Canton ecosystem has live collateral experimentation. This makes a repeat financing pathway causally plausible. However the original mirror-token arrangement does not grant legal lien rights, Digital Asset technology does not entail Canton Global Synchronizer, and outside lender/regulatory sign-off is unobserved.
13. Falsifier / Next Observable: BNY collateral eligibility notices; issuer consent; named independent lender agreement; legal lien representation; actually funded repo/loan confirmations; synchronizer and traffic provenance. Official refusal to promote mirror to legal collateral, alternate network, or absence by deadline falsifies.
14. Resolution Rule: HIT only with two actual financing uses aggregating >=US$100m, independent taker, legal pledge, traceable Canton Global Synchronizer execution (not private Corda/Canton compatibility). Otherwise MISS at deadline; partial transition to other collateral venues does not satisfy the claim.
15. Burden / Specialist Modules / Token Firewall: High moderate research burden, modules off. Canton technology ≠ Global Synchronizer ≠ CC traffic burn ≠ CC outside purchase. Any CC benefit requires identifiable paid traffic, actual payer and sourcing; do not infer from repo notional.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-072-v1 — Wells Fargo connects its own tokenized deposits to other banks through the Quant-powered Clearing House network

1. Forecast ID / Version / Method Version: PVR-072-v1; forecasting v0.4 Lean Core; child of Wells Fargo independent technical routing strategy, linked ancestry to The Clearing House platform PVR-019 and five-bank adoption PVR-063, NOT independent proof of Quant chain or token use.
2. Freeze Date / Evidence Cutoff: First issued 12 October 2026, evidence cutoff 12 October 2026.
3. Decision Object / Control Locus / Decision-Cluster ancestry: Wells Fargo institutional payments engineering/product and The Clearing House shared utility, with outside counterparty bank. Wells Fargo publicly participates in TCH initiative; its proprietary blockchain was separately publicly disclosed Aug 2026. One bank routing choice, separate from operator adoption count.
4. Forecast Task: F3 first financially meaningful interbank interoperability from Wells Fargo proprietary bank-deposit system into TCH/Quant operated settlement; distinct from generic Wells Fargo launch or TCH standalone launch.
5. Use Case / Jurisdiction / Horizon: Corporate U.S. dollar / cross-border commercial-bank payment and programmable treasury; USA; by 31 December 2028.
6. Primary Resolution Object: First externally funded Wells Fargo-originating bank-liability payment path that uses its proprietary tokenized-deposit platform and The Clearing House shared on-chain money orchestration for clearing/settlement to an unrelated chartered bank.
7. Principal Scored Claim: By end-2028, Wells Fargo will execute production transfers of its legally issued tokenized bank deposits to a separate chartered bank through The Clearing House On-Chain Money Initiative, with Quant-provided orchestration in the operating path, on three separate calendar months. The transfers must represent actual funded client or bank obligations, not internal treasury test entries.
8. Observability / Permitted Specificity: O2 for named bank membership and platform announcements; O1 for exact transactional routing and vendor attribution. No claim that Wells Fargo chose public Ethereum, Arc, Canton or Fusion.
9. Call / Forecast Label: LIVE CONTENDER — bold interconnected bank-money route; below Lean on the banking interoperability outcome; Quant exact involvement is a declared operator stack, but its use in the specific Wells Fargo path is unverified.
10. Strongest Alternative: Wells Fargo expands its proprietary ledger and Swift connections while keeping TCH involvement limited to design or a different bank; TCH use occurs without linking Wells Fargo’s own tokenized-deposit balances; settlement remains conventional only.
11. Evidence Basis / Controlling Research: Wells Fargo Aug 4 announcement explicitly identifies proprietary blockchain, private custodial wallets and future interchain connectivity [WF]. June 5 TCH announcement explicitly quotes Wells Fargo as participant [TCH2]. September 24 TCH named Quant in orchestration role [TCH]. Sources: https://newsroom.wf.com/news-releases/news-details/2026/Wells-Fargo-to-Launch-Tokenized-Deposits-for-Corporate-and-Commercial-Clients/default.aspx ; https://www.theclearinghouse.org/payment-systems/Articles/2026/06/Major-Financial-Institutions-Unveil-Bank-Led-On-Chain-Money-Initiative ; https://www.theclearinghouse.org/payment-systems/Articles/2026/09/The-Clearing-House-Partners-with-Quant-to-Advance-the--On-Chain-Money-Initiative
12. Load-Bearing Warrant / Opposition / Private Residual: The same bank has an operating path under construction AND disclosed participation in a utility purposely designed to connect bank tokenized money. That is stronger than mere logo adjacency, but no production route from Wells private platform through Quant/TCH is yet established and regulatory/technical sequencing remains uncertain.
13. Falsifier / Next Observable: Dated Wells Fargo and TCH product notices, bank-to-bank settlement attestations, vendor reporting, three calendar months of paid client/bank value. A proprietary-only expansion or repeated Swift-ledger-only use defeats the strict TCH route.
14. Resolution Rule: HIT only on authentic Wells-issued bank-liability transfer to unrelated bank, contemporaneous TCH operating path with Quant layer, real value over three different months by end-2028. MISS otherwise. A TCH owner/partner announcement or five banks in PVR-063 without Wells-origin private-deposit path fails.
15. Burden / Specialist Modules / Token Firewall: Moderate; no specialists. The Clearing House using Quant infrastructure does not mean this uses Quant Fusion or buys/locks QNT. Bank currency principals do not flow to QNT mechanically.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-073-v1 — BNP Paribas moves its public-Ethereum money-market fund from an in-house test to €100 million in outside investor holdings

1. Forecast ID / Version / Method Version: PVR-073-v1; forecasting v0.4 Lean Core; bank/asset manager-specific F3 using preselected public Ethereum, not a surprise F1; no overlap with separate Allfunds private Luxembourgeois programme.
2. Freeze Date / Evidence Cutoff: First issued 12 October 2026, evidence cutoff 12 October 2026.
3. Decision Object / Control Locus / Decision-Cluster ancestry: BNP Paribas Asset Management fund issuer, Securities Services transfer agency/depositary and BNP Paribas CIB AssetFoundry technical platform. Outside investors elect subscriptions; French/Luxembourg legal eligibility is material.
4. Forecast Task: F3 external investor-funded commercial conversion of a currently one-off intragroup public-Ethereum money-market-fund issuance.
5. Use Case / Jurisdiction / Horizon: French/EU regulated tokenized money-market fund shares under BNP AssetFoundry on Ethereum Mainnet; deadline 31 December 2028.
6. Primary Resolution Object: Beneficial, subscribed outside-investor fund interests legally recorded on Ethereum Mainnet under BNP AssetFoundry, after netting issuer inventory/duplicate wrappers; external customer assets, not just a test share.
7. Principal Scored Claim: By end-2028, BNP Paribas will run a live public-Ethereum-based tokenized money-market-fund share class with at least €100 million of verified net beneficial fund interests owned by two or more separately controlled non-BNP institutional investors at two month-ends at least 28 days apart. Mere intragroup issuance, private Allfunds shares or nominal token supply fails.
8. Observability / Permitted Specificity: O2 for public chain and first instrument; O1–O2 for beneficial owner breadth, compliance and independent externally funded investor holdings.
9. Call / Forecast Label: LIVE CONTENDER — Bold funded-scale expansion; below Lean, because the first Ethereum program expressly described itself as one-off controlled intragroup experiment.
10. Strongest Alternative: BNP chooses its private Allfunds route for large production, uses a new Ethereum L2, keeps Ethereum Mainnet experimental, or tokenizes external funds without accumulating €100m/2 separate investor holders.
11. Evidence Basis / Controlling Research: BNP Feb 20, 2026 primary release defines one-off internal Ethereum issuance on permissioned-access tokens using BNP AssetFoundry, expressly distinguishing the prior private Luxembourg arrangement [BNP]. Oct 8 BNP update describes two successful fund issuances but does not verify external €100m Ethereum subscriptions [BNP2]. Sources: https://group.bnpparibas/en/press-release/bnp-paribas-explores-public-blockchain-infrastructure-for-money-market-fund-tokenisation ; https://securities.cib.bnpparibas/tokenised-funds-from-experimentation-to-production/
12. Load-Bearing Warrant / Opposition / Private Residual: Controlled public Ethereum tooling, the asset-manager issuer, operating transfer agent and asset servicing integration are available inside one bank; moving to customers is a realistic next step but requires investor, regulatory and custody adoption. Success on Allfunds or another network may be economically superior and would defeat this chain-specific bet.
13. Falsifier / Next Observable: Issuer audit/factsheets, fund administrator chain-specific register, two external investor legal-entity confirmations, dated month-end AUM reconciliation, chain contract registry. No qualifying amount or legal investor spread by deadline defeats.
14. Resolution Rule: HIT only if legally issued public Ethereum beneficial interests held by >=2 unrelated external institutional investors total >=€100m on TWO month-ends >=28 days apart by deadline. Allfunds private test, pilot-only balances, internal group funds, wrapper duplicates fail; alternative network is a MISS.
15. Burden / Specialist Modules / Token Firewall: Moderate; no specialist activation. This is Ethereum financial-asset distribution, not an ETH fee-burn, staking or investment-return forecast. Even €100m assets implies no €100m ETH demand.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-074-v1 — Bank of America chooses Swift's shared Besu-based ledger for its first external bank-deposit interoperability

1. ID / Version / Method: PVR-074-v1; Institutional Architecture Forecasting v0.4 Frozen Trial Lean Core.
2. Freeze / cutoff: Original issuance 13 October 2026; evidence available through 13 October 2026. Initial Lean-or-better lead-time start not earned.
3. Decision controller / ancestry: Bank of America controls its own bank-issued digital-deposit product, treasury client eligibility and integration choice; Swift controls the shared network. One Bank of America decision, not 17 or 30 independent Swift design-member decisions. Inherited Swift-operator scale PVR-059, Chainlink middleware PVR-066 and TCH vendor PVR-019 are correlated context, *not* the same bank-specific first-ledger outcome.
4. Task: F1 — exact shared-ledger selection for Bank of America's first bank-owned tokenized-deposit interbank transfer service; funded-transfer evidence is a condition of architecture-selection proof.
5. Use / jurisdiction / deadline: US-dollar deposit claims issued by Bank of America for eligible institutional/corporate customers, moving to a separately controlled recipient bank in international/interbank use; by 31 December 2028.
6. Primary resolution object: Authoritative transaction/instruction interoperability ledger recording Bank of America's own bank-money transfer commitment with another bank, specifically the Swift-operated permissioned Besu/EVM ledger. Do not mistake an Ethereum-family technical stack for the Ethereum public blockchain.
7. PRINCIPAL SCORED CLAIM: By the deadline, Bank of America will have issued legally effective bank-deposit tokens/claims for at least one external nonaffiliate customer and completed at least two real-money interbank/cross-border transfer operations on separate dates, connecting its Bank of America deposit obligation to a separately controlled bank through Swift's shared blockchain ledger as the primary cross-bank tokenized-deposit coordination/state route. No simulation or design participation counts.
8. Observability / specificity: O1–O2. Network participants have disclosed real Swift transactions; BofA's own product/implementation and contractual routing remain undisclosed. This is a consciously below-Lean exact-platform forecast; not a public procurement finding.
9. Call: LIVE CONTENDER — genuinely unknown bank-specific route, favored direction based on 2025 Swift design participation plus 2026 operational progress; not a confidence percentage.
10. Strongest alternative: Bank of America selects the Quant-powered The Clearing House initiative, proprietary/bilateral bank money, another regulated network, or no qualified external digital-deposit service in the period. Same bank can support both systems later; only the *first qualifying route* scores this F1.
11. Controlling evidence: Swift 29 Sep 2025 names Bank of America among banks shaping its ledger; Swift 9 Jul 2026 says 17 early banks were preparing to transact, not that BofA is among already transacting banks; Swift March 2026 describes Besu/EVM architecture and off-ledger final settlement. [B1] https://www.swift.com/about-us/media-centre/press-releases/swift-add-blockchain-based-ledger-its-infrastructure-stack-groundbreaking-move-accelerate-and-scale-benefits-digital-finance-across-more-200-countries-and-territories-worldwide ; [B2] https://www.swift.com/news-events/migrated-news/press-releases/swifts-blockchain-ledger-ready-use-17-banks-set-pioneer-tokenised-cross-border-payments-trusted-global-infrastructure ; [B3] https://www.swift.com/insights/newsletters/faster-payments-smarter-standards-and-swifts-blockchain-based-shared-ledger-road-ahead-global-finance ; TCH/Quant [B4] https://www.theclearinghouse.org/payment-systems/Articles/2026/09/The-Clearing-House-Partners-with-Quant-to-Advance-the--On-Chain-Money-Initiative .
12. Warrant / strongest opposition / private residual: Pre-existing Swift design investment lowers integration friction; Swift has operated actual transfers with other banks. But BofA may rationally prefer a US-regulated TCH shared utility for its dollar deposits, and cross-border payment finality may remain in ordinary off-chain rails. Bank-specific funding, token legal form, implementation approval and choice of utility remain private. This is materially speculative.
13. Falsifier / next proof: BofA product disclosure, legal token liability description, Swift and counterparty independently corroborated transaction dates, real external principal. First qualifying BofA route through another utility decisively defeats this *first-route* bet.
14. Resolution: HIT only if exact first-route and two separate real transactions with an independent recipient bank are proven by deadline. Being one of Swift's >30 advisers, customer access via Swift messaging, or public Ethereum activity is insufficient. Otherwise MISS when rival first route is confirmed; UNRESOLVED if the underlying first-route event/proof remains nonpublic at adjudication, explicitly excluded from accuracy numerator.
15. Burden / modules / token boundary: Moderate primary-source verification; conditional further research if BofA issues an announcement. No specialist activated. This predicts bank-money interoperability using permissioned Besu, not Ethereum Mainnet usage, ETH burn or LINK/Quant token demand. Potential business reach: corporate treasury and cross-bank liquidity, not a forecasted dollar volume.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-075-v1 — Deutsche Bank DAMA 2 attracts externally funded fund issuers and €250m legally tokenized assets

1. ID / Version / Method: PVR-075-v1; v0.4 Lean Core.
2. Freeze / cutoff: 13 October 2026 / 13 October 2026; no prior Lean-or-better issuance at this scored specificity.
3. Decision controller / ancestry: Two unrelated external asset managers/fund issuers independently authorize fund issuance; Deutsche Bank provides asset-servicing and platform design; Memento controls its ZK Chain infrastructure, Axelar provides interoperability. Two end-client adoption choices under one scored DAMA 2 platform conversion; do not count as two independent forecast records.
4. Task: F3 — from publicly described DAMA 2 architecture/demos to legally effective external fund-token adoption and meaningful holdings.
5. Use / jurisdiction / horizon: Regulated digital funds in EU/other permitted institutional jurisdictions; end-2028.
6. Primary resolution object: Legally effective registered investor fund interests with active issuance/servicing on DAMA 2's Memento ZK Chain based on ZKsync technology and Ethereum-connected architecture; Axelar bridging may be present but is not itself the scored slot.
7. PRINCIPAL SCORED CLAIM: By 31 Dec 2028, at least two unaffiliated non-Deutsche-Bank asset managers will issue legally operative fund interests serviced through DAMA 2/Memento ZK, with at least €250 million combined externally beneficially held subscribed interests at two consecutive month-ends, at least 28 days apart. Pilot/demo balances, internal bank-owned subscriptions and mirrored token representations without enforceable fund rights do not count.
8. Observability: O2 known architecture, O1 third-party issuer contracts/beneficially held balances. Hold precise network identity on Memento ZK, not on the broader term “Ethereum” alone.
9. Call: LIVE CONTENDER — bolder than ordinary platform launch; first outside customer plus second and substantial holdings.
10. Alternative: DAMA 2 persists as reference architecture or small pilot; DB earns custody business on unrelated networks; asset managers select their own Ethereum L2s, private ledgers, or another agent; regulatory acceptance is delayed.
11. Evidence: Deutsche Bank's 18 Jun 2025 official DAMA 2 release identifies Memento ZKsync ZK Chain, Axelar interoperability and prospective multichain funds; Memento platform demos describe issuance, servicing and privacy controls, not audited outside money; DB Sep 2026 custody release is a separate product and not evidence that DAMA 2 assets reached €250m. [D1] https://www.db.com/news/detail/20250618-dama-2-litepaper-institutional-blueprint-for-asset-tokenisation-and-servicing-on-ethereum-layer-2 ; [D2] https://cdn.mementoblockchain.com/dama2/index.html ; [D3] https://www.db.com/news/detail/20260916-deutsche-bank-to-launch-digital-asset-custody-solution-for-institutional-and-corporate-clients?language_id=1 .
12. Warrant / opposition / residual: DB contributes distribution, securities servicing, compliance and client access, while a permissioned privacy-preserving L2 can satisfy institutional requirements. Counterweight: tools and bank affiliation do not guarantee issuer migration, actual subscriptions, or security-law recognition across jurisdictions. Investor register authority, assets/AUM and post-trade compliance are private until issuer disclosure.
13. Falsifier / trigger: Fund prospectuses and administrator attestation, legal identifier of each independent issuer, contract/chain addresses when publishable, month-end external investor interests, fund factsheet AUM with jurisdiction and exact chain; two client pilots alone are insufficient.
14. Resolution: HIT if ≥2 unrelated outside fund issuers and ≥€250m aggregate qualifying investor-held fund claims exist at TWO month-ends ≥28 days apart on DAMA 2/Memento by deadline. Other Ethereum chains or off-platform servicing do not rescue. Unknown beneficial-holder balances stay unresolved, not presumptively met.
15. Burden / modules / token boundary: Moderate-to-high evidence burden due beneficial-ownership privacy; no specialist yet. It is an Ethereum-family L2 technology prediction; not proof that public Ethereum executes fund trades, that ETH burns proportionately or that AXL must capture equivalent fund AUM.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-076-v1 — HSBC's own bank-money tokens finance real outside collateral or securities transactions on Canton

1. ID / Version / Method: PVR-076-v1, v0.4 Lean Core.
2. Freeze / cutoff: 13 October 2026, contemporaneous public primary sources.
3. Decision controller / ancestry: HSBC Global Payments Solutions controls bank-deposit claims and client onboarding; separately controlled asset/collateral counterparties and potential Canton operators control the securities/financing use. HSBC already has a separate private TDS and joined Swift's live transactions. This record tests Canton settlement of external securities/collateral, not a second scoring of PVR-059 Swift cross-border payments or general Canton repo records.
4. Task: F3 — pilot/simulation to real bank-issued cash leg for externally executed on-Canton asset/financing settlement.
5. Use / jurisdiction / horizon: Regulated institutional asset trades or collateral/repo settlements in a legally permitted HSBC jurisdiction; end-2028.
6. Primary resolution object: Commercial-bank money/cash-settlement leg on Canton issued as an HSBC legal deposit liability, synchronized with a separately controlled legally operative tokenized securities/collateral claim.
7. PRINCIPAL SCORED CLAIM: By 31 Dec 2028, HSBC will have completed at least three executed real-value DvP / repo / collateral transactions across at least two separate calendar months in which HSBC-issued TDS/deposit tokens actually settle the money leg on Canton and at least one outside HSBC customer and one separately controlled asset/collateral counterparty are documented. A simulated deposit or an HSBC-only treasury transfer fails.
8. Observability: O2; HSBC and Canton explicitly confirm pilot and product family, but regulation, exact deposit-token contractual form, cash-leg finality and production counterparties remain private.
9. Call: LEAN — directionally supported conversion, NOT Strong Lean and not a probability; pilot is target-specific discriminatory signal, but legal/commercial completion remains a major open dependency.
10. Strongest alternative: HSBC's private TDS remains the actual cash book; Swift's ledger coordinates customer-bank money while final cash settlement remains off-ledger; a regulated third-party stablecoin or conventional payment leg services Canton transactions; Canton is never HSBC's production cash ledger.
11. Evidence: HSBC's April 13 US announcement establishes live private TDS across jurisdictions, HSBC product page confirms private HSBC blockchain; HSBC Aug 6 article explicitly describes a simulation on Canton; Canton April 13 independent ecosystem counterparty post calls the exercise a simulation, not live trading; HSBC and Standard Chartered August live Swift transaction makes competing architecture operationally real. [H1] https://www.about.us.hsbc.com/newsroom/press-releases/hsbc-expands-tokenized-deposit-service-to-the-united-states ; [H2] https://www.business.us.hsbc.com/en/products/tokenized-deposit-service ; [H3] https://www.business.hsbc.com/en-gb/insights/digital-currencies-an-institutional-payments-toolkit ; [H4] https://www.canton.network/news/hsbc-completes-tokenised-deposit-pilot-on-canton-network ; [H5] https://www.about.hsbc.com.hk/news-and-media/hsbc-and-standard-chartered-execute-first-live-tokenised-deposit-transaction-on-swifts-blockchain .
12. Warrant / opposition / residual: An actual target-specific Canton test improves this call versus prestige-logo inference; HSBC's live private TDS and other bank connections give feasible internal support. But simulated functionality is not legal finality, external funding, production controls or paid public Canton traffic. Strong real alternative: interoperability *above* multiple private networks rather than direct HSBC money issuance on Canton.
13. Falsifier / trigger: HSBC client and collateral-agent transaction confirmations, on-Canton provenance, bank cash-leg finality terms, outside counterparty identities, deal dates; a production claim that merely references Canton SDK/private synchronizers is inadequate if public Canton is the claimed route.
14. Resolution: HIT on ≥3 real distinct transactions over ≥2 calendar months satisfying legal cash leg, Canton and unrelated outside party requirements. Private-only HSBC book, mock settlement, or pure Swift transfers do not count. If confirmed first material collateral rollout chooses a different settlement network, forecast is defeated. Undisclosed activity remains unresolved rather than imagined.
15. Burden / modules / token boundary: Moderate-to-high legal/finality verification; no specialist activated. This predicts Canton technology and actual Canton settlement; Canton Coin capture additionally requires proof of public Global Synchronizer fees/burn, third-party acquisition and supply dynamics. Not a CC price forecast.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-077-v1 — UBS scales Chainlink Digital Transfer Agent across multiple unrelated fund distributors

1. ID / Version / Method: PVR-077-v1; v0.4 Lean Core.
2. Freeze / cutoff: 13 October 2026 / publicly available primary releases.
3. Decision controller / ancestry: UBS Asset Management and UBS Tokenize direct fund transfer agency, independently controlled distributors make integration/adoption decisions; Chainlink supplies DTA/CRE/possibly CCIP. Separate from PVR-066 banks adopting CRE to access Swift's new shared ledger; both create correlated LINK ecosystem narratives but different primary customer/workflow.
4. Task: F3 — one demonstrated subscription/redemption workflow to multiple recurring institutional distribution relationships at economic scale.
5. Use / jurisdiction / horizon: UBS-issued Ethereum uMINT or clearly identified successor regulated tokenized funds distributed to eligible institutional investors; by 31 Dec 2028.
6. Primary resolution object: Recurring Chainlink Digital Transfer Agent processing of legally valid fund subscriptions/redemptions, not total UBS funds AUM, chain token issuance counts or generic Chainlink interoperability availability.
7. PRINCIPAL SCORED CLAIM: By deadline, at least TWO additional unrelated, non-DigiFT institutional fund distributors or intermediaries will have completed production UBS tokenized-fund subscription/redemption orders through Chainlink's DTA/CRE and, across DigiFT plus those new distributors, at least $250 million cumulative principal-equivalent actual third-party subscription/redemption orders will have been completed over three distinct calendar months. No simulated volume or purely issuer-owned transfers.
8. Observability: O2 technical/proven product, O1–O2 volume attribution and participant names. Cross-chain is optional and cannot substitute for the scored transfer-agent operations.
9. Call: LIVE CONTENDER — broader adoption not yet verified; ambitious distributor/turnover thresholds.
10. Strongest alternative: DigiFT remains sole integrator, traditional fund services or other middleware handle later fund investors, or UBS uses DTA only for particular low-volume instruments; large uMINT fund stock but few DTA-processed orders.
11. Evidence: UBS November 4, 2025 press release confirms first *live* uMINT subscription/redemption with DigiFT using Chainlink DTA on Ethereum; UBS tokenization site describes current product family; Chainlink design description distinguishes CRE, DTA, CCIP and on-/off-chain settlement. [U1] https://www.ubs.com/global/en/media/display-page-ndp/en-20251104-chainlink.html ; [U2] https://www.ubs.com/global/en/investment-bank/tokenize.html ; [U3] https://chain.link/blog/digital-transfer-agent-ubs .
12. Warrant / opposition / private residual: UBS could leverage a tested standard to reduce integration cost for more distributors, which would be an institutional infrastructure achievement for Chainlink. Yet the demonstrated workflow alone establishes neither recurring customer economics nor token-fee capture. Investors, fund order sizes, distributor commercial decisions and CRE payments are not publicly characterized.
13. Falsifier / trigger: Two new named independent production intermediaries; issuer/TA order reconciliation or independent institution press records of settled volume across three months, DTA-specific receipts, not merely generic fund NAV/AUM.
14. Resolution: HIT only if both distributor-breadth and $250m cumulative DTA order-volume across ≥3 months established by deadline. More tokens minted, more uMINT AUM or Chainlink marketing cannot rescue a shortfall. Preserve uncertainty if no trustworthy attributable order-volume evidence is publishable.
15. Burden / modules / token boundary: Moderate-high due transaction privacy; no specialist activated. UBS success might improve Chainlink network importance, but not $250m LINK demand. Require CRE/CCIP fee and Chainlink Reserve economics separately for LINK causal capture.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-078-v1 — Santander participates in real sterling–dollar PvP cash settlement using two Fnality payment systems

1. ID / Version / Method: PVR-078-v1; v0.4 Lean Core.
2. Freeze / cutoff: 13 October 2026; contemporaneous public material.
3. Decision controller / ancestry: Banco Santander wholesale treasury/markets businesses plus separate UK and US Fnality payment-system legal operators and another nonaffiliate financial counterparty. One PvP inter-system conversion target; not a generic score for Fnality consortium membership or Santander's existing sterling usage.
4. Task: F3 — existing GBP real-money transfers → legally operative synchronized GBP/USD cross-currency settlement across distinct Fnality systems.
5. Use / jurisdiction / horizon: Wholesale FX/treasury liquidity and international institutional settlement, UK/US regulated jurisdictions, by Dec 2028.
6. Primary resolution object: Two-system central-bank-anchored tokenized cash PvP settlement in which a sterling Fnality obligation and dollar Fnality obligation are conditionally paired such that either both principal legs settle or neither settles. Mere GBP–GBP transfers or conventional FX payments fail.
7. PRINCIPAL SCORED CLAIM: By 31 Dec 2028, Banco Santander and at least one separately controlled bank will complete at least three externally funded GBP/USD principal-exchange settlements on distinct dates across two calendar months, with the two legs passing through the appropriately regulated Sterling Fnality Payment System and US-Dollar Fnality Payment System under an enforceable payment-versus-payment arrangement and at least $100m aggregate equivalent principal. No simulation or offsetting off-Fnality USD payout qualifies.
8. Observability: O2 for GBP; O1 for USD regulator/launch state and future cross-system PvP. Specific dual-Fnality wager is below Lean because USD regulatory clearance/production is not yet demonstrated.
9. Call: LIVE CONTENDER — material long shot with strong causal reason to watch, not base case disguised as certain.
10. Strongest alternative: US dollar Fnality remains non-operational or delayed; Santander's sterling Fnality use grows while dollar cash settles through conventional CHIPS/Fedwire, other tokenized deposits, Swift, Project Agorá-type systems or the 21-bank stablecoin.
11. Evidence: Santander 2025 Pillar 3 published Feb 2026 states bank already uses sterling Fnality for real-value transfers, with additional 2025 activity from Madrid and a planned 2026 USD service (planned is not commissioned). Fnality confirms Santander, Lloyds, UBS real sterling uncleared margin demonstration; Fnality's current USD platform page explicitly says discussions with US regulators are ongoing. [S1] https://www.santander.com/content/dam/santander-com/en/documentos/otra-informacion-relevante/2026/02/hr-2026-02-25-2025-pillar-3-disclosures-report-en.pdf ; [S2] https://fnality.com/news/santander-lloyds-ubs-settle-pilot-uncleared-margin-payment-using-sterling-fnality-payment-system ; [S3] https://fnality.com/payment-systems/us-dollar-payment-system ; [S4] https://fnality.com/news/earmarked-funds .
12. Warrant / opposition / private residual: Santander is a founding investor and operator/user of a real sterling digital settlement network; Fnality's strategy explicitly envisages separate interoperable currency systems. However US dollar licensure, finality alignment, interoperability rulebooks and buy-in from another US participant create substantial unresolved dependencies. This is not an extrapolation from one same-currency pilot to two-currency proof.
13. Falsifier / trigger: Fnality USD system authorization and go-live; name of independent US/UK transaction counterparty; publicly attested matched PvP executed dates and value; any cross-border transaction settling USD on a different platform fails this exact two-system bet.
14. Resolution: HIT only for ≥3 qualifying principal PvP events, ≥2 calendar months, aggregate ≥$100m, with real final GBP and USD Fnality legs and unrelated other bank. A GBP-only payment, planned USD service, live sandbox, legal collateral pledge or fiat-bank payout does not qualify. Outcome remains unresolved if private banks decline to publish data even if architecture could operate.
15. Burden / modules / token boundary: Moderate-high legal/settlement verification; no specialist activated. Fnality private wholesale infrastructure success has no automatic public token capture. It is not a Canton/Ethereum/Solana payment-volume credit or a crypto token price prediction.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-079-v1 — Citi converts Solana trade-finance exploration to outside-corporate financed bills

1. ID / Version / Method: PVR-079-v1; v0.4 Frozen Trial, first official issue 13 October 2026.
2. Freeze / evidence cutoff: 13 October 2026; no favorable backdating. First Lean-or-better issuance not earned.
3. Decision controller / ancestry: Citigroup trade-finance services and participating corporate issuers/financing parties; Citi controls its own offerings, but cannot unilaterally confer enforceable title or compel independent corporate participation. Distinct from Citi/SIX private-share PVR-061 and R3/SIX Solana PVR-065.
4. Forecast task: F3 commercial conversion of the specifically announced Citi/PwC/Solana exploration, not unknown selection of Solana (already publicly discussed).
5. Use / jurisdiction / horizon: Legally enforceable digital bills of exchange or closely equivalent transferable trade-receivable instruments for corporate trade finance, in an eligible jurisdiction; by 31 December 2028.
6. Primary resolution object: On-Solana legally consequential trade-finance instrument ownership/endorsement or transferable payment undertaking with actual financing, not a reference hash or test record. The adjudicated function is trade-credit issuance, funding and servicing.
7. PRINCIPAL SCORED CLAIM: Citi's operational trade-finance business will finance, arrange or service at least $100 million cumulative principal in legally enforceable Solana-recorded electronic bills or equivalent transferable receivables involving at least two separately controlled non-Citi corporate issuers, with at least three distinct real funded transactions across two calendar months by end-2028. Funding must be external to a demonstration balance and the legal operative claim must require the Solana record.
8. Observability / specificity: O1–O2 for legal documentation and funded transaction notional; exact chain clear only if records/source corroborate; the bank may disclose no deal-by-deal statistics.
9. Forecast call: LIVE CONTENDER — bold funded-scale conversion, below Lean. No quantitative probability asserted.
10. Leading alternative: Citi deploys digital trade instruments using private Corda/Besu, trade-finance consortia, traditional electronic documents or proprietary banking records while Solana stays experimental. PvP/stablecoin settlement alone is not a hit.
11. Controlling evidence: Citi's 2026 Supply Chain Financing report explicitly describes exploration with PwC and Solana of a tokenized bill of exchange; its Feb 2026 essay discusses the legal issues of digital bills. Primary: https://www.citigroup.com/global/insights/supply-chain-financing-2026 ; https://www.citigroup.com/global/insights/digital-bill-trade-finance-new-frontier ; corroborating institutional context https://solana.com/solutions/financial-institutions .
12. Warrant, rival, private residual: Citi has trade-finance customers and jurisdictional legal capabilities, while Solana offers compliance-aware issuance and stablecoin DvP. But trade-document title, bank credit authority, confidentiality and actual customer preference may select another stack. No Citi production selection or funding is proven by the existing exploration.
13. Falsifiers / proof triggers: Primary Citi deal disclosures, buyer/issuer confirmation, legal terms, token contract/instrument identifiers, principal funded and repaid, dates and chain of authoritative state. Proving merely Citi's commercial-paper transaction elsewhere or a Solana demo is insufficient.
14. Resolution: HIT only for all amount, outside-issuer, financed-transaction and time tests on Solana by deadline. MISS if the verified commercial conversion is exclusively elsewhere or the full test fails by deadline; UNRESOLVED if qualifying private transaction documentation is inaccessible, with evidence limitation recorded.
15. Burden / module / token interpretation: Medium-high transaction/legal verification; optional targeted evidence research only if a concrete deal emerges; specialist modules default off. Network adoption is not proportional SOL burn; actual gas and security balances must be measured separately.

Reader explanation: Citi already explored turning trade paperwork into digital instruments. Our bet is that independent companies will actually receive working-capital financing through Solana. If it scales, Solana could move from fund tokens and stablecoins to trade-credit infrastructure. This is potential significance, not an asserted trillion-dollar projection.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-080-v1 — U.S. Bank's USBDC becomes an external-client Stellar payment rail

1. ID / Version / Method: PVR-080-v1; v0.4 Frozen Trial; first official issue 13 October 2026.
2. Freeze / evidence cutoff: 13 October 2026; historical September 9 live pilot is NOT predicted anew.
3. Decision controller / ancestry: U.S. Bank as issuer, Digital Asset Platform operator and business risk/treasury approver; nonaffiliated corporate customer approval separate. Existing canonical XLM-USBANK-USBDC-01 is underlying history; this is a future economic-scale target.
4. Task: F3, from an intra-group USBDC pilot to recurring outside customer payment production.
5. Use / jurisdiction / horizon: U.S.-dollar bank-issued stablecoin for U.S. Bank's legally distinct corporate/institutional clients, cross-border or cross-entity treasury settlement, by end-2028.
6. Primary resolution object: Actual movement and redemption/settlement of USBDC on public Stellar as a bank obligation to qualifying outside clients, not Stellar support inside a middleware product.
7. PRINCIPAL SCORED CLAIM: U.S. Bank facilitates at least $100 million aggregate genuinely funded USBDC transfers on public Stellar, attributable to at least two non-U.S.-Bank-controlled corporate/institutional customers, over at least three distinct calendar months by end-2028; at least one transfer must cross independent beneficial-account control. The September 2026 North America-to-Europe bank-group-only pilot is excluded.
8. Observability: O1–O2: bank may publicly attest volumes, client names may be private; onchain gross transfers cannot by themselves prove distinct owners or funded end uses.
9. Call: LIVE CONTENDER — genuine third-party bank money, not another pilot; no quantified odds.
10. Rival: U.S. Bank keeps USBDC intragroup, chooses an internal ledger, moves corporate customers through existing wire/ACH or unrelated public stablecoin, or lacks approvals for scale.
11. Evidence: U.S. Bank bank-primary September 9 release confirms a live cross-border pilot on Stellar between its own North American and European entities, not repeat customer production: https://ir.usbank.com/news-events/news/news-details/2026/U-S--Bank-Launches-USBDC-Stablecoin/default.aspx . Canonical Ledger XLM-USBANK-USBDC-01 explicitly states that recurring clients and material XLM demand are not proven.
12. Warrant / countercase / residual: An issuer-operated bank platform already integrated with compliance/risk reduces conversion friction. But U.S. Bank may prefer controlled intra-group use or avoid opening bank liabilities to new clients on a public ledger. Legal eligibility, customer launch plans and true customer balances remain opaque.
13. Falsifier / next proof: Bank customer terms, issuances/redemptions and volume attestation, dates, independent beneficial counterparty; exclude internal mint/burn cycles, one wallet's self-transfers and market-maker recycling.
14. Resolution: HIT only if distinct customers, attributed volume, repeated months and public Stellar USBDC are all proven; otherwise MISS at cutoff if threshold demonstrably not met, with UNRESOLVED for inaccessible client-level facts explicitly maintained outside success numerator.
15. Burden / token firewall: Medium-high outside-client attribution. Even $100m bank money does not imply $100m XLM purchases; incremental XLM gas/reserves may remain immaterial.

Reader explanation: U.S. Bank has already moved its own bank coin between its divisions on Stellar. We predict it starts moving substantial *customers'* money there, which would be a much bigger validation of the public network.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-081-v1 — Kbank selects public XRPL for its first real customer stablecoin remittance path

1. ID / Version / Method: PVR-081-v1; v0.4 Frozen Trial; first official issue 13 October 2026.
2. Freeze / evidence cutoff: 13 October 2026; custody vendor choice is an inherited known fact, not a scored hit.
3. Decision controller / ancestry: South Korea's Kbank determines its product, liability, regulated intermediary and routing; Ripple supplies custody software, which is multichain. Not an automatic selection by Ripple. Distinct from PVR-040/041/046 Ripple-controlled functional outcomes and PVR-062 Standard Chartered collateral.
4. Task: F1 exact public-network choice for first Kbank-directed external corporate or customer stablecoin remittance service where Kbank has settlement-network control.
5. Use / jurisdiction / deadline: A Kbank-authorized, legally permitted stablecoin remittance/cross-border customer offering in Korea or an authorized corridor; by 31 December 2028.
6. Primary resolution slot: Actual settlement ledger for economically consequential customer stablecoin value, specifically the public XRP Ledger (XRPL), not custody wallet software or a fee/quote recorded elsewhere.
7. PRINCIPAL SCORED CLAIM: Kbank's first externally available bank-directed stablecoin cross-border remittance product that executes at least $10 million cumulative genuinely funded third-party customer payment value across two calendar months will use public XRPL as the authoritative onchain settlement leg for those customer transfers by end-2028; an EVM-based or private-ledger primary settlement route would defeat this exact-chain call.
8. Observability: O1 (private product procurement, legal permission and custody routing); exact ledger is an explicitly risky forecast based on weak public chain-specific data.
9. Call: LIVE CONTENDER — bold lower-than-Lean choice, not a statement that Kbank has selected XRPL.
10. Leading alternative: Ripple Custody's multichain tools run an EVM stablecoin (or other network) while Kbank retains conventional settlement or a Korean bank-private scheme. Kbank can be a strong Ripple customer with no public XRPL volume.
11. Evidence: Kbank/Ripple press release April 29–30 2026 confirms multichain Ripple Custody wallet infrastructure and the bank's interest in stablecoin cross-border remittances, not XRPL selection: https://ripple.com/ripple-press/ripple-partners-with-kbank-to-deploy-scalable-digital-asset-wallet-infrastructure-through-ripple-custody/ . Ripple Custody advertises multichain support: https://ripple.com/products/custody/ . Canonical research preserves Ripple ≠ XRPL ≠ XRP.
12. Warrant / opposition / private residual: Ripple integration reduces onboarding friction and native XRPL can support issued stablecoin transfers. The stronger opposing fact is that custody vendors are chain-agnostic and Korean policy constraints may favor other operators. There is no corroborated Kbank XRPL payment procurement.
13. Reopen / falsifier: Kbank regulatory product filing, remittance terms, first real independent customer transaction, contract/ledger IDs, asset issuer, beneficial sender/receiver, customer volume, dates. Proof of custody of XRP or RLUSD is insufficient.
14. Resolution: HIT only if the first qualifying service passes $10m/two-month outside-client threshold with XRPL in the primary slot. MISS for a first qualifying production service on EVM, private or conventional rails, or if no qualifying XRPL first service by deadline. No rescue by Ripple-as-vendor or secondary XRPL ledger use.
15. Burden / token boundary: High for confidential bank customer transaction attribution; modules default off. An XRPL win supports XRP's public network narrative but stablecoin value can settle without XRP as principal; transaction fees alone are economically weak.

Reader explanation: Kbank already chose Ripple custody technology. We are making the much less obvious bet that when Kbank actually moves customers' stablecoin payments, it chooses the public XRP Ledger, rather than Ethereum-family networks or a private bank system.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-082-v1 — A new regulated credit investor finances PACT loans directly through Aptos

1. ID / Version / Method: PVR-082-v1; v0.4 Frozen Trial; issued 13 October 2026.
2. Freeze / cutoff: 13 October 2026; pre-issue PACT represented loan balance is baseline, not a prospective hit.
3. Decision controller / ancestry: A new independently controlled regulated bank, institutional credit fund or licensed warehouse lender, together with PACT borrower/servicer and custodian. PACT and BitGo do not unilaterally make the outside lender's investment decision. Separate from Archax additional manager PVR-036.
4. Task: F3 external new credit investor / economically active credit financing, not merely asset tokenization or a new logo.
5. Use / jurisdiction / horizon: Institutional private-credit origination or warehouse financing involving enforceable real borrowers and licensed eligible creditors; by 31 December 2028.
6. Primary resolution object: New outside-funded outstanding drawn loan principal on Aptos PACT with operational onchain loan lifecycle and legally documented investor claims.
7. PRINCIPAL SCORED CLAIM: A specifically named independently controlled regulated bank, credit fund or licensed warehouse lender not already identified as an operating PACT financing lender before this forecast will supply at least $75 million in incremental, genuinely externally funded outstanding drawn principal administered through Aptos PACT, verified on two monthly dates at least 28 days apart before end-2028, with identifiable loan-level legal rights, custody and servicing. Previously represented/synthetic principal cannot qualify.
8. Observability: O1–O2 outside lender and beneficial funding sources; provider aggregate loan notional does not establish marginal cash funding.
9. Call: LIVE CONTENDER — bold funded-credit conversion, not measured probability.
10. Leading alternative: PACT remains concentrated in existing lender/borrower cohort, additional credit is merely represented onchain, or institutional lenders fund privately/on Ethereum without Aptos as operational source of truth.
11. Evidence: Canonical APT-PACT-REAL-WORLD-CREDIT-01: ~$568m represented RWA credit, with strong caveat represented notional ≠ protocol loan liquidity/throughput. Aptos/PACT operator materials describe BitGo custody and institutional credit rails: https://aptosnetwork.com/currents/pact-enters-its-next-chapter ; https://aptosnetwork.com/currents/ushering-in-the-future-of-on-chain-credit .
12. Warrant / opposition / private residual: Existing asset/originator and custody capabilities provide integration starting points, but lender due diligence, borrower risk, asset provenance, legal enforceability and loss performance remain substantial inhibitors. Public promotional aggregate figures cannot be treated as independently funded deposits.
13. Falsifier / proof: New named regulated lending entity, tranche legal terms, funded cash draw, outstanding loan principal, borrower agreement, Aptos loan-NFT/servicing evidence, two month-ends. Protocol TVL alone, tokenization of old receivables or promised allocation fail.
14. Resolution: HIT only with *new named* independent regulated capital owner plus >=$75m actual funded outstanding principal and two dated balance tests through Aptos PACT; elsewhere and under-threshold outcomes fail. Unobservable lender funding flagged UNRESOLVED, not credited.
15. Burden / token boundary: High legal/accounting source recovery; no specialist autoactivated. Increased Aptos credit importance is not proportional APT burn and PACT token benefits are a separate object.

Reader explanation: Aptos already tracks substantial real-world credit through PACT. We predict a new regulated financial institution will actually put major new lending capital to work on those rails, making Aptos more than a digital loan-record system.

Dated historical updates

No separately dated formal update is displayed for this record. Historical issue-state is preserved; no new resolution is claimed.

Historical issue-state record · current outcome not adjudicated

Immutable original forecast

PVR-083-v1 — WOO X selects Hyperliquid as its execution engine for outside-market perpetuals

1. ID / Version / Method: PVR-083-v1; v0.4 Frozen Trial; prospective issue 13 October 2026.
2. Freeze / cutoff: 13 October 2026. WOO X/Payward existing spot/custody partnership, historical WOO derivatives and Payward's separately announced HIP-3 plan are NOT this call's success.
3. Decision controller / ancestry: WOO X and its jurisdictionally eligible operating affiliate for product and customer flow; independent from Payward/Bitnomial's own intended U.S. HIP-3 deployment (IFC-074) and Ripple Prime's already-live Hyperliquid access (IFC-075). Payward may provide enabling routing but cannot count as WOO X's independent procurement by itself.
4. Task: F1 new named outside-operator execution backend selection for a qualifying WOO X non-crypto perpetual market.
5. Use / region / deadline: A legally offered perpetual derivative referencing an equity index, commodity, foreign-exchange rate or other non-crypto benchmark offered by WOO X or appropriately authorized affiliate in a permitted jurisdiction by end-2028. MiCA-aligned EU spot registration does not itself authorize this derivative.
6. Primary resolution slot: Actual order matching and position management on public Hyperliquid / HIP-3 HyperCore, rather than WOO X's own CEX matching, indirect price feed, derivative on the HYPE token, or permission to access a Payward website.
7. PRINCIPAL SCORED CLAIM: By 31 December 2028 a WOO X-controlled customer-facing non-crypto perpetual product will route eligible client orders for at least $50 million cumulative genuine executed notional over two calendar months into a specific Hyperliquid HIP-3 order book whose matched trades and positions are recorded on HyperCore, with corroboration that WOO X clients have the corresponding legal/beneficial exposures. Merely listing HYPE-PERP, integrating Payward custody or quoting Hyperliquid market data does not qualify.
8. Observability: O1 for internal routing; O2 for chain trades and product terms. Exact WOO X choice has not been announced. High dilution of inference from chain/ecosystem association.
9. Call: WEAK SIGNAL / BOLD DIRECTIONAL — below Live Contender; unusually speculative but grounded in specific independent infrastructure relationships. No probability implied.
10. Leading alternative: WOO X continues proprietary/perhaps Payward centralized matching; HIP-3 regulatory, custody, margin or operational risks prohibit the product; Payward uses Hyperliquid only in its own U.S. derivatives business.
11. Evidence: Payward 29 Sep 2026 confirms WOO X EU uses Payward for custody/spot infrastructure (not derivatives): https://www.payward.com/press-release/payward-services-powers-woo . Payward 16 Sep 2026 separately proposes U.S. HIP-3 on Hyperliquid under Bitnomial/NinjaTrader, regulator pending: https://www.payward.com/press-release/payward-hyperliquid-onchain-perpetual-futures . Hyperliquid HIP-3 specification defines actual deployer, market and order-book mechanics: https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals . WOO X previously explored onchain derivative liquidity via a separate Perpetual Protocol arrangement: https://woox.io/blog/woo-network-partners-with-perpetual-protocol-to-expand-support-for-on-chain-derivatives-trading .
12. Warrant / strongest countercase / private residual: Two concrete propagation edges exist (WOO X↔Payward; Payward↔proposed Hyperliquid backend) and WOO X already operates derivatives; these edges do not establish a WOO X HIP-3 plan. Their convergence is a low-confidence analytical hypothesis, defeated by centralized matching and distinct regulatory perimeters. HIP-3 builder concentration and compliance are serious counterevidence.
13. Falsifiers / proof triggers: WOO X specific published legal product terms, jurisdictional derivative authorization, Hyperliquid HIP-3 deployer / market IDs, WOO X routing attribution, independent customer eligible accounts, onchain trades and two-month notional calculation. A Payward-only product fails WOO X attribution.
14. Resolution: HIT only for exact independent-operator choice + verifiable onchain matching, customer beneficial exposure, product legality and $50m/two-month threshold. A noncrypto derivatives launch exclusively on WOO's conventional matching stack is a scored MISS; unresolved routing must remain UNRESOLVED and not a hit.
15. Burden / token transmission: High legal/execution/attribution verification. If a real HIP-3 deployer emerges, HYPE operational staking/collateral and qualifying protocol fee capture might benefit HYPE, but *the WOO X trading-notional dollar amount is not HYPE purchase demand*. Deployer may rent/buy stake, aggregate, or leverage existing inventory; fee splits require actual telemetry.