XRP Ledger's GL1 Review: CertiK Verified Only 2 of 10 Principles
Key Takeaways
- •CertiK independently verified only two of the GL1 toolkit's ten principles for XRPL, covering Architecture and Resiliency, while the Foundation self-attested the remaining eight without publishing the findings or the software version reviewed.
- •The attestation is explicitly not a certification, approval, or endorsement by GL1, any central bank, regulator, or participating institution, and GL1's backers, including HSBC, Kinexys by J.P. Morgan, MUFG Bank, Societe Generale-FORGE, and Standard Chartered, have not approved XRPL.
- •XRPL's Permission Delegation amendment went live on mainnet on October 8, allowing an account to delegate up to ten specific permissions so routine signing can run on limited keys while the master key stays offline.
- •XRPL issuers retain controls such as single-holder, deep, and global freezes plus clawback, which must be enabled before a token circulates and cannot coexist with the permanent No Freeze flag.
- •In Brazil, Ripple and depository CSD BR use XRPL to mirror records of BTG Pactual fund shares as Multi-Purpose Tokens, though CSD BR's register and Brazilian law remain the official record of ownership.

The XRP Ledger Foundation announced on November 18 that the XRP Ledger (XRPL) has become the first public, permissionless layer-1 blockchain to have two principles of the GL1 Market Infrastructure Toolkit independently verified, citing a CertiK attestation report dated November 13. The scope of that review was narrow: CertiK examined only two of the framework's ten principles, and the public release discloses none of its findings.
Two principles verified, eight self-assessed
The Foundation completed a self-attestation against all ten principles of GL1's Market Infrastructure Toolkit. Its answers cover governance, legal basis, settlement finality, operational and cyber resilience, access and participation, and data and privacy. CertiK reviewed only the responses and evidence filed under Architecture and Resiliency — a split that GL1's toolkit website shows as well.
What CertiK actually found is not disclosed. The release publishes no findings, quotes no one from CertiK, and omits the XRPL software version that was under review. Anyone seeking more than the headline has to request the report.
The harder part sits inside the framework itself. GL1's toolkit builds on the CPMI-IOSCO Principles for Financial Market Infrastructures — the international standard used to assess payment systems, central securities depositories and central counterparties — along with the Digital Asset Securities Control Principles and the Global Blockchain Business Council's risk mitigation framework, and many of its controls assume a single operator runs the network. XRPL has none. Where a control did not fit, the Foundation explained how protocol design, open-source governance, the amendment process and issuer compliance tools handle the same risk instead.
A bank's risk team is therefore not reading a checklist but a translation — and it must judge whether each substitute does the work of the control it replaces.
XRPL is also not the only name on GL1's list. Just one other entry carries a CertiK verification label, and it runs a permissioned network, which is why the Foundation's “first” claim leans so heavily on the words “public, permissionless.” GL1 thanks the organizations listed on its toolkit page for “self-attestations and/or feedback” and does not mark the status of the unlabeled entries.
Who backs GL1, and what they didn't sign
The Monetary Authority of Singapore (MAS) convened the original GL1 initiative with global banks and policymakers. On November 4, HSBC, Kinexys by J.P. Morgan, MUFG Bank, Societe Generale-FORGE and Standard Chartered turned it into an industry-led non-profit based in Singapore. The working group behind the toolkit includes the Bank of England, the Banque de France and MAS.
None of them has approved XRPL. The Foundation's release says so directly: the attestation is not a certification, approval or endorsement by GL1, any central bank, regulator or participating institution, and it is not a finding that XRPL meets the standards the toolkit draws on. It tells institutions to run their own assessments.
Foundation Executive Director Brett Mollin pitched the exercise as an answer to institutional fatigue. Institutions, he said, don't need “another white paper” arguing that public ledgers can carry tokenized assets; they need evidence their compliance teams can map. That map, however, ends at the network: follow one payment and it becomes clear where the bank's own work begins.
Who can move the bank's token?
Picture a bank sending an issuer-backed dollar token to an approved counterparty. Before anything reaches the ledger, several questions need answers: What does the token represent? What can the holder redeem? Who inside the bank may sign?
XRPL now gives the bank finer control over that last question. Permission Delegation went live on mainnet on October 8 through the PermissionDelegationV1_1 amendment, replacing an earlier version that never reached mainnet after a bug surfaced in testing. An account can hand a delegate up to ten specific permissions, so routine signing runs on limited keys while the master key stays offline. Delegates cannot change keys or grant themselves extra powers, and the protocol enforces each permission. The bank decides who holds the permissions, how it guards the keys and what happens when an employee leaves. Coindoo's look at XRPL's new wallet controls walks through the setup.
In the ledger doesn't mean paid
The bank submits. A success message comes back. Nothing has settled yet.
XRPL's finality documentation separates that early response from the result recorded in a validated ledger, and validated ledgers hold failures too. Some failed transactions still pay a fee and land in the record, so an operations system that spots a transaction in a ledger and stops checking could credit a customer for money that never moved. The bank's software therefore has to read the final result code and the balance changes the transaction actually made.
Partial payments add a trap: the delivered amount can fall short of the amount field, and only the delivered figure counts. Dropped connections cause the nastier problem, because the bank cannot tell whether the payment failed, succeeded or is still pending. XRPL's submission guidance tells applications to give every transaction a last valid ledger, so a lost instruction expires at a known point, and to confirm the original's fate before sending a replacement. Skip that check and the bank can pay twice.
The issuer keeps a hand on the balance
The payment validates. Can the recipient move those tokens next week? That depends on the issuer, not the network.
Under XRPL's freeze rules, an issuer can freeze a single holder's trust line, which blocks that holder from sending the tokens anywhere except back to the issuer. A deep freeze also stops receiving and trading, and a global freeze hits every holder of everything the issuer has issued. Issuers who want to give all of this up can set No Freeze, a permanent flag that only the master key can sign.
Clawback works on a stricter clock: an issuer has to switch it on before its account holds any trust lines, offers, escrows or similar objects, so it cannot be bolted onto a token already in circulation. Clawback and No Freeze cannot coexist, and neither tool touches XRP. None of this rewrites history — a clawback is a fresh transaction — but it does change what the bank's customer actually holds. Those settings sit on the issuer's account, where anyone can query them, and they reveal more about one token's risk than a network-wide attestation does.
Brazil shows the issuer side at work. In a September 29 announcement, Ripple and depository CSD BR said XRPL now mirrors records of BTG Pactual fund shares as Multi-Purpose Tokens. CSD BR's systems remain the official record. The ledger lets authorized participants audit that the two match, and only Brazilian corporate and banking clients that clear KYC and anti-money-laundering checks can join. CSD BR also keeps the power to freeze holdings or claw them back when a regulator or court orders it. Whatever the ledger shows, the depository's register and Brazilian law decide ownership. Coindoo's report on XRPL's entry into Brazil's fund system has the project background.
An attestation of a network that won't sit still
XRPL changes through amendments. One takes effect after it holds support from more than 80% of trusted validators — meaning those on the default Unique Node List — for two straight weeks. Those changes come often: Permission Delegation arrived on October 8, and within weeks validators enabled fixCleanup3_4_0, which closed a gap that let a delegated burn permission create new tokens.
The Foundation says it intends to refresh its assessment as the toolkit evolves and new amendments activate. Today's readers face a narrower problem: because the release does not name the software version CertiK reviewed, a risk team cannot tell which of this autumn's changes the attestation covers. That is the first question to ask. The rest can be watched directly: whether the full CertiK report, available today only on request, is ever published; whether GL1 starts marking the status of the unlabeled entries on its list; whether any of the eight self-assessed principles pick up an independent verification label; and which amendments validators enable next.