search

      Speakers

      All speakers
      Prof. Bob Wardrop

      Prof. Bob Wardrop

      Founder & Chief Executive Officer of RegGenome

      Cambridge University & RegGenome

      View LinkedIn profile
      View the agenda

      Robert (Bob) Wardrop is Founder and CEO of RegGenome, a regulatory data infrastructure company. RegGenome turns complex global regulation into structured data that retains the meaning and context of each requirement and stays traceable to its original source, supporting policy, supervision, risk and compliance.

      Bob was Management Practice Professor of Finance at Cambridge Judge Business School, and founding Director of the Cambridge Centre for Alternative Finance until 2020. His research studied innovation at the intersection of technological change and the global financial system, and in 2021 he received the CJBS Research Impact Award for his work applying AI to regulatory information in the field of computational regulation.

      That research led to the founding of RegGenome, which has its origins at the University of Cambridge and is a founding member of the Regulatory Genome Project, an ongoing public-private initiative standardising how regulation is structured. RegGenome data and models are used by 100 regulatory organisations, and by three of the world's 29 globally systemically important banks.

      Bob has held several advisory board roles with regulatory authorities and corporate directorships over the course of his professional career. He holds an MBA from the Booth School of Business at the University of Chicago, an MSc from the London School of Economics, and a PhD from the University of Cambridge.

      Speaking At

      • 1:30–3:00pmTue 17 NovPublic-Private RoundtableRoundtable Room 3Invite-Only

        Global Frameworks, Interoperability & Shared Best Practices

        Programmable Compliance: Which Rules Travel with the Money, and How?

        Public-Private RoundtableRoundtable Room 3Invite-Only

        About this session

        As money becomes programmable, across central bank digital currencies, tokenized deposits, and stablecoins, a real question is emerging about where compliance should live: embedded directly in the asset as a rule that travels with it, layered on top through richer messaging and real-time screening, or enforced separately by whichever party touches the transaction last.

        Players are all building credible but different answers in parallel, and none has converged on how these should interoperate across jurisdictions with different compliance regimes. The stakes are rising on every front — real-time cross-border settlement, tokenized securities, and increasingly, autonomous agents initiating transactions on their own — all of which need a compliance check at the moment value moves, not after. What would each of these approaches to programmable compliance actually need to interoperate, and which rules win when they conflict across borders?

        Discussion questions:

        1\.         Should compliance logic live in the asset itself, in the messaging/settlement layer, or in a separate real-time screening service, and does the answer change depending on whether it's a CBDC, a tokenized deposit, or a stablecoin?

        2\.         When a transaction crosses borders, whose compliance rule actually governs — sender's jurisdiction, receiver's, or the rail's — and what happens when they conflict?

        3\.         Retrofitting compliance onto existing settlement infrastructure and building it in from scratch are both live strategies right now — what would each need to prove to become the default, and is convergence between them actually possible?

        4\.         As more transactions — including those initiated by autonomous agents — require a compliance check the moment value moves, what are the minimum interoperability standards needed for rules to actually travel with money across rails?