Supervision, issuance and the room where those conversations have to happen together
Reserve quality, redemption rights and travel-rule implementation cannot be designed in one room while the banks and networks that will carry the instruments sit in another. Supervision of digital money is now a joint production problem.
The last cycle of digital-asset policy was organised as a sequence of warnings: investor protection, market integrity, financial-crime risk. Those warnings were not wrong. They were incomplete as a map of what stablecoins have become. Once an instrument is used to pay a supplier, pre-fund a treasury, or settle a cross-border invoice, the supervisor is no longer looking only at a speculative token. They are looking at a payments activity that sits beside banking, e-money and securities settlement — and that borrows legal concepts from all three without fitting neatly into any of them.
That is why isolated consultation papers keep missing the operating reality. An issuer can write a white paper about reserves. A bank can write a memo about deposit substitution. A payment network can write a spec about on-chain messaging. If those documents never meet, the public gets a market in which the legal claim, the cash, and the transfer instruction live in different regimes. Responsible adoption is the work of aligning those regimes before scale makes the gaps expensive.
Three files that only resolve together
Issuance is the first file. Who may create a claim on a dollar, a euro, or a local currency; what must sit behind it; how often that backing is attested; and who is liable if the attestation is wrong. Different jurisdictions are answering this with licensing regimes that look like e-money, bank deposits, or a new category. The design choice matters because it determines whether the instrument is a direct claim on an issuer, a claim on a trust, or something less clear in insolvency.
The second file is the banking perimeter. Even a fully reserved token still depends on banks to hold cash and government securities, to process redemptions, and to connect to existing payment systems. If those banks treat the activity as reputationally radioactive, issuance migrates to weaker institutions. If they treat it as a product line without operational controls, the next outage becomes a systemic story. Supervisors of issuers and supervisors of banks therefore need a shared picture of concentration, liquidity and operational risk.
The third file is transfer. Travel-rule data, sanctions screening, and consumer disclosures have to travel with the payment. Always-on settlement is a capability of the rail; it is not a waiver of financial-crime obligations. Where compliance cannot keep up with block times, two failure modes appear: either the rail is throttled back into the same delays as correspondent banking, or activity leaks into channels that no serious institution can touch. Neither outcome is a policy success.
Dialogue is not a substitute for standards
Industry events often advertise “dialogue between regulators and innovators” as if conversation itself were the deliverable. Conversation is the minimum. The deliverable is a shared description of the instrument: what a holder actually owns, how they get out, who they call when something fails, and which rulebook applies when two jurisdictions disagree. Without that, “responsible innovation” is a tone of voice.
GSCS was established so that those descriptions can be argued in a room that includes the people who will have to live with them. Central banks assessing monetary and settlement implications; regulators writing licensing and conduct rules; commercial and digital banks integrating the rails; issuers operating the instruments; payment networks connecting them to commerce. The interdependence is not a branding taxonomy. It is the reason a summit series exists rather than a product conference.
Africa Edition, as the first chapter, will not resolve global rulebooks. It can do something more useful: put corridor-level evidence — remittance costs, correspondent constraints, inclusion goals — next to the supervisory questions that will otherwise be answered in the abstract. Later editions in other regions will inherit that method. The alternative is a familiar split: policy discussed in Basel, products demoed in Las Vegas, and the public asked to trust an instrument that was never examined as infrastructure.
What GSCS will not do
This platform will not present empty partner logos, illustrative speakers, or unsourced market-size claims as institutional proof. It will not treat every stablecoin design as equivalent. It will not describe Africa as a pilot for a brand conceived elsewhere. Confirmed partners, speakers and research will be named when they exist. Until then, the work is to hold a precise conversation: which designs, under which rules, can carry value across borders without asking the public to subsidise the risk.
That is a narrower mission than “shaping the future of digital money” as a slogan. It is also the only mission that matches the size of the market that now exists. Instruments that already move trillions of dollars in adjusted on-chain volume, and that already sit above $300 billion in supply, do not need another round of vision statements. They need the people who issue, supervise, bank and accept them to sit in the same programme — and to leave with obligations, not only impressions.
Sources
DefiLlama, August 2026 (circulating stablecoin supply).
Talos, August 2026 (adjusted on-chain transfer volume).
World Bank Remittance Prices Worldwide, Q3 2025 (corridor cost context for why issuance, banking and transfer rules cannot be separated from real-economy payments).
