Financial Integrity for Permissionless Networks - FINAL

Redundant with selected · 29

• claimFinancial institutions can and should transact on permissionless networks todayc 0.95 · sim 0.89

  Existing law already permits regulated institutions to operate on permissionless networks, and the case for engaging now is affirmative rather than merely permissive.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• claimPermissioned blockchains rely on a designated gatekeeperc 0.90 · sim 0.83

  Permissioned networks are governed by a central authority or consortium that decides who may validate, access, use, or build on the network. This structural gatekeeping is what fundamentally distinguishes them from permissionless systems.

  overlapped with: Permissionless networks are compatible with financial integrity

• claimExisting compliance programs can extend to permissionless networksc 0.90 · sim 0.89

  Financial institutions can adapt their existing financial integrity programs to comply with relevant laws while participating on permissionless networks, rather than needing a wholly new framework.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• mechanismThe operative standard is material assistance or facilitationc 0.85 · sim 0.86

  Liability turns on whether a party materially assisted sanctioned conduct, sometimes described informally as making that conduct easier. This framing is what allows compliance to be evaluated in terms of contribution rather than absolute prevention.

  overlapped with: Sanctions compliance is not about wholesale elimination of risk

• mechanismControls live at the application layer, not the base networkc 0.85 · sim 0.87

  Permissionless networks can serve highly regulated environments by implementing compliance controls at the application layer on top of the permissionless architecture, leaving the base layer open.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• claimInadvertent protocol-level contact with sanctioned parties isn't what sanctions laws targetc 0.85 · sim 0.87

  Unknowing interactions with validators or other network participants who happen to be sanctioned are not the activity sanctions laws were written to address. The institution never selected, contracted with, or dealt with those operators.

  overlapped with: Sanctions compliance is not about wholesale elimination of risk

• implicationA nine-point risk-management framework operationalizes compliance on public chainsc 0.85 · sim 0.86

  The paper offers a nine-point framework as a concrete compliance reference showing how permissionless networks map onto existing financial integrity obligations.

  overlapped with: Permissionless networks are compatible with financial integrity

• claimThe real novelty is shared financial infrastructure, not the underlying techc 0.80 · sim 0.83

  Distributed data structures, cryptographic verification, and consensus all predate blockchains. The genuinely new contribution is shared financial infrastructure that incumbents and new entrants can access on equal terms.

  overlapped with: Permissionless networks are compatible with financial integrity

• implicationProgram-based analysis extends to permissionless settlementc 0.80 · sim 0.85

  Because compliance obligations run through the institution's own program, the same analysis applies when transactions settle on a permissionless network as when they settle anywhere else.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• claimOFAC endorses a risk-based approach to compliance programsc 0.80 · sim 0.85

  OFAC's Framework for OFAC Compliance Commitments makes clear that sanctions compliance programs should employ a risk-based approach. The intensity of controls varies depending on the profile of the business, not a single fixed standard.

  overlapped with: Sanctions compliance is not about wholesale elimination of risk

• implicationRegulated firms have a viable path onto permissionless railsc 0.80 · sim 0.87

  Together, the layered-controls model and the shift in supervisory posture mean regulated institutions now have a workable route to participate on permissionless networks without abandoning their compliance obligations.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• claimThe underlying network doesn't change what an institution must know about its customerc 0.80 · sim 0.86

  Regardless of whether the ledger is permissioned or permissionless, the institution still ties customer identities to wallet addresses and performs the same KYC. The architecture of the network below doesn't alter the obligation above.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• contextBSA and sanctions law require risk-based programs, not perfectionc 0.80 · sim 0.86

  The BSA and sanctions regime demands reasonably designed, risk-based programs covering the customers, counterparties, and assets within an institution's control — a standard permissionless activity can meet.

  overlapped with: Sanctions compliance is not about wholesale elimination of risk

• mechanismSecurity rests on cryptography combined with economic incentivesc 0.75 · sim 0.85

  Rather than trusted intermediaries, permissionless networks secure themselves through a mix of cryptographic guarantees and economic incentive design.

  overlapped with: Permissionless networks are compatible with financial integrity

• mechanismSanctions controls should be proportionate to what the institution actually controlsc 0.75 · sim 0.86

  An institution can implement geolocation and IP controls on its customer-facing services, screen counterparties it deals with, document a legal analysis of network-fee and validator interactions, and maintain an OFAC-designation escalation protocol. What it cannot do is police the whole network, and its controls should reflect that.

  overlapped with: Sanctions compliance is not about wholesale elimination of risk

• implicationPermissionless networks can meet highly regulated environments' needsc 0.75 · sim 0.89

  With appropriate control layering, permissionless networks can be implemented in ways that fully satisfy the requirements of highly regulated financial environments. Regulation is not a reason to exclude them from the stack.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• contextRegulated institutions are adopting blockchain but splitting on which kindc 0.70 · sim 0.84

  Regulated financial institutions are rapidly building products on blockchain infrastructure, but many are opting for permissioned versions and treating open permissionless networks as off-limits.

  overlapped with: Permissionless networks are compatible with financial integrity

• claimOFAC targets systemic evasion, not isolated activityc 0.70 · sim 0.83

  In the designation space, OFAC has typically focused on enablement of ongoing, systemic sanctions evasion rather than launching surprise actions against limited activity.

  overlapped with: Sanctions compliance is not about wholesale elimination of risk

• claimPermissionless networks offer benefits beyond compliance parityc 0.70 · sim 0.88

  Beyond meeting regulatory requirements, permissionless blockchains offer financial institutions operational, regulatory, and commercial benefits that their current databases and tooling do not readily provide.

  overlapped with: Permissionless networks are compatible with financial integrity

• claimPermissionless blockchains are more operationally resilient than closed databasesc 0.65 · sim 0.85

  Compared to traditional closed financial databases, permissionless blockchains offer higher operational resilience. This is a concrete operational advantage rather than an abstract one.

  overlapped with: Permissionless networks are compatible with financial integrity

• contextWhat makes a network permissionlessc 0.60 · sim 0.86

  Permissionless networks run autonomously under rules no single actor can change, and are open to anyone on identical terms.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• contextCredible neutrality as an organizing propertyc 0.60 · sim 0.84

  The paper introduces credible neutrality — the property that a network does not and cannot favor particular participants — as a key concept for evaluating permissionless infrastructure.

  overlapped with: Permissionless networks are compatible with financial integrity

• contextThe internet's layered evolution as the reference modelc 0.60 · sim 0.82

  This layered approach mirrors the way the internet evolved — an open, permissionless substrate with regulated, controlled services built on top.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• contextLayering controls on open infrastructure is not newc 0.60 · sim 0.90

  Financial services already adapted to the internet by layering compliance controls on top of open infrastructure. Doing the same on permissionless networks follows a well-worn pattern.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• caveatTreating the network as infrastructure doesn't erase compliance obligationsc 0.55 · sim 0.85

  The infrastructure framing recalibrates how institutions think about protocol-layer contact; it does not eliminate their duty to screen counterparties or respond to identifiable exposures to designated persons.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• contextThe thesis generalizes across permissionless networksc 0.40 · sim 0.82

  The analysis is not specific to one chain; it applies with equal force to any permissionless network sharing the features described.

  overlapped with: Permissionless networks are compatible with financial integrity

• contextInstitutional hesitation persists despite the infrastructure analogyc 0.40 · sim 0.89

  Even accepting that permissionless networks are shared infrastructure, financial institutions remain reluctant to engage — a gap between the correct legal framing and current risk posture.

  overlapped with: Permissionless networks should be treated as shared infrastructure, like the internet or phone system

• contextFinancial institutions have used closed ledgers for decadesc 0.40 · sim 0.84

  Banks have long operated on ledgers kept as databases, just closed ones. Permissionless blockchains are a shift in openness, not a shift into unfamiliar recordkeeping.

  overlapped with: Permissionless networks are compatible with financial integrity

• contextRoadmap: distinguishing permissionless from permissioned systemsc 0.30 · sim 0.83

  Section I of the paper will explain how permissionless networks operate and how they differ from permissioned systems, framing the rest of the analysis.

  overlapped with: Permissionless networks are compatible with financial integrity

Below top-k · 53

• claimPermissioned networks are not credibly neutralc 0.90

  Because the rules ultimately rest on off-chain agreements controlled by a gatekeeper, permissioned networks cannot offer credible neutrality. Participants, users, and builders are left exposed to the discretion of that authority.

• claimAnyone can join as a validator at any timec 0.85

  Open validator participation is a defining property: there can be no implicit or explicit restrictions on who operates a node.

• mechanismRules depend on off-chain cooperation rather than on-chain incentivesc 0.85

  Unlike permissionless networks whose rules are enforced by transparent economic incentives, permissioned networks depend on the gatekeeper's ongoing cooperation and on contractual agreements. This dependence is especially fragile in consortium arrangements where members must continuously coordinate.

• claim24/7 global market access deepens liquidity for everyonec 0.85

  Because permissionless networks run continuously and openly, assets can be sold, financed, or posted as collateral at any hour against a worldwide counterparty pool. This deeper, more continuous access benefits the system as a whole, not just individual users.

• claimOpen protocols level the playing field for smaller institutionsc 0.85

  Because the networks are identical for everyone, a smaller institution can interoperate with the tokenized assets, payment rails, and liquidity that larger institutions have already deployed. No bilateral negotiation or approval process is required.

• claimLedgers are effectively immutablec 0.80

  Once written, the history of the ledger cannot be altered by any single entity, which is what fixed the original double-spend problem.

• claimIdentity on the network is purely cryptographicc 0.80

  The network knows a user only by a key pair the user alone controls, and any transaction bearing a valid signature is eligible for processing.

• implicationPermissioned networks are inherently censorablec 0.80

  Because a single entity or privileged group controls participation, permissioned systems can exclude, block, or reverse activity at will. Censorability is not a bug of the design but a direct consequence of it.

• claimOn-chain traceability lets exposure be measured with precision unavailable in traditional paymentsc 0.80

  Blockchains allow institutions to distinguish direct exposure — assets arriving immediately from a designated wallet — from indirect, multi-hop exposure attenuated by intervening legitimate transactions. This precision is not available in conventional payment rails.

• implicationTransparency narrows the opacity risk premiumc 0.80

  When exposures are visible on-chain, investors demand a smaller risk premium for opacity. Fewer hidden, correlated exposures also mean less systemic risk accumulating beyond supervisors' sight.

• implicationWaiting for new law is unnecessary and cedes the fieldc 0.80

  Because current statutes, regulator statements, and standard risk programs already accommodate permissionless activity, institutions that delay engagement are choosing to sit out, not being kept out.

• mechanismImmutability comes from replication plus cryptographyc 0.75

  Copies of the ledger are replicated across independent nodes and secured with advanced cryptography, so no one party can rewrite history.

• implicationCounterparty and coordination risks reappear in permissioned systemsc 0.75

  Because enforcement lives in contracts and human cooperation, permissioned networks reintroduce the very counterparty and coordination risks that decentralized systems were designed to eliminate.

• evidenceFDIC and Federal Reserve rolled back crypto pre-approval regimesc 0.75

  In 2025 the FDIC and Federal Reserve rescinded their prior-notification and non-objection requirements for crypto-asset activities, returning them to the ordinary supervisory process.

• evidenceExisting BSA tools already cover the plausible risksc 0.75

  Institutions can flag inbound exposure to designated addresses, decline or quarantine assets, freeze accounts pending review, file SARs, and report to OFAC — all within their existing BSA programs. No new regime is needed to handle these cases.

• claimContinuous infrastructure improves systemic resiliencec 0.75

  Deep, always-on liquidity across many assets can mitigate market stress because collateral can move within minutes to where it is needed. A seller is never locked out of the market simply because of the clock.

• evidenceOCC has expressly blessed node operation and validator activityc 0.75

  The OCC has stated that banks may run nodes, validate transactions, pay network fees, and hold the crypto needed to do so — removing a foundational legal ambiguity.

• mechanismValidation happens through independent verification and rebroadcastc 0.70

  Participants verify that each transaction satisfies the network's cryptographic and consensus rules, then broadcast updates so other nodes can independently confirm and apply them to the ledger.

• mechanismA consensus mechanism binds all participants to one ledger statec 0.70

  An algorithmic set of rules — the consensus mechanism — is how all participants agree on the latest state of the ledger.

• caveatPermissioned approval to join would break the definitionc 0.70

  If joining the network requires someone's approval, it is no longer a permissionless blockchain in any meaningful sense.

• claimTrust surface shifts from code and incentives to contracts and peoplec 0.70

  In permissioned systems, participants must trust the gatekeeper's willingness and ability to enforce contractual agreements and resolve disputes. This relocates the trust surface from transparent protocol rules to opaque legal and institutional processes.

• implicationDetection and deterrence, not perfect blocking, is the goalc 0.70

  Programs are expected to adequately detect suspicious activity so that potentially illicit actors can be investigated and ultimately deterred. The regime accepts that some bad activity will occur; the question is whether the system surfaces it.

• implicationCrypto activity is being normalized into standard bank supervisionc 0.70

  By folding crypto-asset activities back into ordinary supervision, regulators are treating them as a normal line of business to be conducted in a safe and sound manner under existing law.

• mechanismProtocol fees reach validators through rules that apply identically to every userc 0.70

  A validator fee is not a chosen commercial dealing; it flows through neutral protocol rules that apply the same way to every user of the network. That structural symmetry undercuts the notion of a targeted transaction with the validator.

• implicationDirect exposure should be treated more seriously than attenuated exposurec 0.70

  Because on-chain provenance can be measured, direct receipts from a designated wallet warrant a stronger compliance response than multi-hop flows that pass through legitimate intermediaries.

• evidenceBIS Project Tourbillon shows regulators reaching the same conclusionc 0.70

  The BIS Innovation Hub's Project Tourbillon CBDC prototype built payer anonymity into the payment system while preserving disclosure needed for illicit-finance controls. This is the regulator's own confirmation that privacy and compliance can coexist.

• mechanismNo geographic anchor expands the addressable marketc 0.70

  The protocol treats a payment across the ocean the same as one across the street, so the infrastructure has no geographic anchor. This expands the total addressable market for investable assets and services built on top of it.

• implicationOpen protocols unravel platform-style incumbency advantagesc 0.70

  By making the same rails available to all participants, open protocols dissolve the kind of gatekeeping advantages that closed tech platforms typically accumulate.

• mechanismCustomer-layer KYC applies unchanged, tied to wallet addressesc 0.70

  CIP, CDD, and EDD obligations apply exactly as they do in traditional banking, with each customer's wallet addresses linked to their verified identity file.

• mechanismWallet and counterparty screening uses SDN lists plus analyticsc 0.70

  Deposits and withdrawals are screened against the OFAC SDN List, and blockchain analytics are used to separate sanctioned or illicit flows from legitimate counterparties.

• evidenceSecurities, investment, and derivatives regulators aligned with banking regulatorsc 0.65

  Banking regulators are not alone: securities, investment management, and derivatives regulators have each addressed how the firms they supervise may hold and trade crypto assets, signaling cross-agency convergence.

• mechanismPermissionless access removes the need for approval to integratec 0.65

  Interoperating with existing on-chain liquidity does not require waiting for someone else's approval process to clear. Access is a property of the protocol, not a privilege granted by an incumbent.

• claimThe transaction record is fully transparentc 0.60

  Anyone can store their own copy of the ledger or use third-party APIs and websites to inspect it.

• caveat'Facilitation' is described informally, not by bright-line rulec 0.60

  The material-assistance standard is often articulated informally as making sanctioned conduct easier. That informality leaves meaningful ambiguity about where the line falls in novel contexts like permissionless networks.

• implicationFewer crises requiring official interventionc 0.60

  With continuous liquidity and transparent exposures, authorities may face fewer occasions on which crisis management requires their direct involvement.

• evidenceFinCEN and OFAC enforce against systemic failures, not isolated slipsc 0.60

  Enforcement patterns from FinCEN and OFAC target knowable, systemic compliance failures, which is compatible with the kind of program an institution can actually run on a public chain.

• caveatConsortium governance amplifies the cooperation problemc 0.55

  When the gatekeeper is a consortium rather than a single firm, sustaining agreement among members is especially difficult. Governance drift or member conflict can degrade the network's rules over time.

• implicationOpen networks push institutions to evolvec 0.55

  Openness benefits not only end users but also the institutions themselves, which must evolve to meet market demand. This dynamic pushes the broader financial system forward.

• contextThe framework separates transaction-layer duties from broader controlsc 0.55

  The nine-point framework organizes compliance by layer — starting with transaction-layer controls that mirror what institutions already do — making the mapping to existing programs explicit.

• caveatComposability may still require permission at the application layerc 0.50

  While the base layer is open, applications built on top can impose their own permissioning on how they interoperate.

• contextAML programs must meet statutory minimum standardsc 0.50

  Under 31 U.S.C. § 5318(h), regulated entities must maintain internal policies and controls, designate a compliance officer, train employees, and provide for an independent audit. These four pillars define the baseline of any AML program.

• contextSecondary sanctions extend U.S. reach to non-U.S. actors abroadc 0.50

  Secondary sanctions expose non-U.S. persons to designation or other consequences for specified activity conducted outside the U.S. with certain jurisdictions or entities. They function as a lever to deter foreign actors from dealing with places like North Korea or Iran.

• exampleSAR and CTR filings are core reporting obligationsc 0.50

  Banks and non-bank MSBs must file Suspicious Activity Reports for qualifying suspicious transactions and Currency Transaction Reports for cash payments over $10,000. These filings are the concrete artifacts through which detection obligations are discharged.

• exampleGarantex and Grinex designations illustrate the patternc 0.50

  In August 2025 OFAC re-designated Garantex and designated its successor Grinex for processing over $100 million in transactions linked to ransomware actors and cybercriminals since 2019, along with three executives and six associated companies.

• contextThe concern is broader than geography because a sanctioned validator can operate anywherec 0.50

  Framing the problem as a jurisdictional one misses the point: a designated person can run a validator from anywhere, so location-based screening does not resolve the underlying question of protocol-mediated contact.

• mechanismThird-party risk management extends to node and staking providersc 0.50

  Node-as-a-service and staking providers are third parties that institutions engage with, and standard third-party risk management applies. This brings familiar vendor oversight frameworks to a novel infrastructure layer.

• contextFederal banking agencies have issued their own supporting guidancec 0.50

  The federal banking agencies have collectively issued guidance framing how supervised institutions can engage with crypto assets and public networks under existing prudential standards.

• contextThe PATRIOT Act layered on customer identification and due diligencec 0.45

  The 2001 USA PATRIOT Act added customer-identification requirements and special due-diligence obligations for specified relationships, expanding the AML compliance perimeter beyond the original BSA baseline.

• exampleOFAC escalation protocol as a good-faith response mechanismc 0.45

  When OFAC designates wallet addresses or individuals with associated wallets, a pre-defined escalation protocol lets the institution demonstrate a prompt, good-faith response. This is a concrete way to operationalize sanctions compliance on a permissionless network.

• exampleInternet analogy for open commercial infrastructurec 0.40

  The paper draws a parallel to the internet, noting that its commercial success followed from a deliberate policy choice to keep the underlying network open rather than permissioned.

• evidenceEnforcement statistics show restrained penalty usec 0.40

  Of the enforcement actions referenced, only 12 were deemed egregious, resulting in $3.1 million in penalties — a signal that severe sanctions are reserved for the worst cases.

• contextSanctions serve national security and foreign policy endsc 0.35

  The stated purpose of the secondary sanctions regime is to advance U.S. national security and foreign policy by deterring engagement with adversarial jurisdictions. This framing shapes how aggressively the rules are enforced.

• contextRecords must be retained for five yearsc 0.30

  Copies of reports and supporting documents must be maintained for five years to support later investigation. Recordkeeping duration is itself a substantive part of the compliance obligation.