It’s slower than we all think it’s gonna be .. Banks not ready

NOV 2/4 Popcorn please

I bought XRP for retirement. At this point, the most realistic roadmap is transferring it to my heirs and letting them be disappointed too. 💀🚀📉

XRP isn’t a cryptocurrency. It’s a support group for people who mistake patience for a retirement strategy. 🚀📉💀

If I wasn’t on a GLP-1 - total cake binge day - instead I had butter noodles with salmon #faceplant

XRPN is the Nasdaq ticker for Armada Acquisition Corp. II Class A ordinary shares (the security shown in your screenshot). It is a Cayman Islands SPAC that just completed its merger with Evernorth, an XRP-focused digital asset treasury company. Trading under XRPN began (or resumed post-merger) around October 12, 2026, after the deal closed on October 9. The screenshot matches exactly: • Full name: Armada Acquisition Corp II CL A • Identifier G0R38G104 (the CUSIP; the ISIN is KYG0R38G1040, which starts with “KY” for Cayman Islands) • Price around $17.09 (the prior close; the stock has been trading in the mid-teens recently after earlier volatility) Fidelity (and many brokers) often displays the official long-form legal/security name plus the ISIN or CUSIP for foreign-incorporated companies, SPACs, or newly listed/restructured securities rather than (or alongside) just the short ticker. Data feeds and display systems frequently lag a day or two after a SPAC business combination and ticker-related corporate actions, so the full Armada description appears until everything fully updates to the post-merger Evernorth entity. In short, you are looking at the correct security for XRPN—it is not a different stock. The display is normal for this type of Cayman SPAC share, especially on the first post-merger trading day.

Core pacs payment instruction messages (especially pacs.008 and pacs.009) became the required digital format on 22 November 2025. This was the end of the SWIFT CBPR+ (Cross-Border Payments and Reporting Plus) coexistence period between legacy MT messages and ISO 20022 MX messages for payment instructions. From that date: • MT103 → pacs.008 (FI to FI Customer Credit Transfer) • MT202 / MT202 COV / MT205 → pacs.009 (and variants) • Related returns and status messages also shifted to pacs.004 / pacs.002 ISO 20022 is now the exclusive standard for these in-scope cross-border payment instructions on the SWIFT network. Contingency MT-to-MX conversion services still exist for some cases but incur charges and stricter validation. Adoption reached roughly 97–98% of payment instructions shortly after the deadline. Swift delayed the structured/hybrid postal address requirement (and the broader payments portion of Standards Release 2026) primarily because large parts of the industry were not ready. Key Reasons • Uneven readiness across the industry: As the original 14 November 2026 deadline approached, progress was inconsistent in every region. Readiness data (around April 2026) showed roughly 61% of payments still carried fully unstructured debtor addresses and ~63% unstructured creditor addresses. Surveys indicated nearly half of banks were not on track, and about 20% of the largest banks called the deadline unrealistic. • Formal community requests for more time: Several banking communities and domestic payment market infrastructures asked Swift (and their local infrastructures, which had aligned deadlines) for additional preparation time. • Data-quality and systems challenge: The 2025 MT-to-MX migration for core payment instructions was largely achieved with translation layers. Structured addresses, however, require clean, structured data captured at origination (in core banking, onboarding, and corporate systems). There was no practical network-level contingency to fix unstructured addresses after the fact—non-compliant messages would simply be rejected (NAK’d). • Coordination with market infrastructures: Swift consulted with banks, central banks, and payment market infrastructures and agreed to a controlled extension to avoid widespread rejections and operational disruption. This also led aligned infrastructures (e.g., Bank of England RTGS/CHAPS) to defer their own related releases. What Was Delayed On 27 August 2026, Swift deferred all payments-related changes in Standards Release 2026 (not only the address rule). SR 2025 remains in effect until a future release. Non-payments elements (e.g., certain securities and trade changes) were decoupled and moved on a separate track (later set around June 2027). Swift is consulting stakeholders on the optimal new timing and approach and has indicated it will provide an update by December 2026 at the latest. The underlying requirement (minimum structured town name + country, preferably fully structured or hybrid) has not been dropped—only the enforcement date has been postponed. In short, the delay was a pragmatic response to industry readiness gaps rather than a change in the strategic goal of richer, structured data for better straight-through processing, screening, and interoperability. Sit your ass down nobody is ready

Did the boat get stuck in a mud Pitt ? @evernorthxrp Asking for a friend ?