Documentation Portal
Project Home
  • Core Documentation
    • Overview
    • Whitepaper
      • Abstract
      • I. Introduction
      • II. Protocol
        • II.I Operation
          • II.I.I Generation of M
          • II.I.II Protocol Fees
          • II.I.III Cancel and Freeze
          • II.I.IV Retrieving Free Collateral
          • II.I.V The Earn Mechanism
          • II.I.VI Removing a Permissioned Actor
          • II.I.VII Example Interactions and Flows
        • II.II Governance Controlled Protocol Actors
        • II.III Governance Controlled Protocol Parameters
      • III. Governance
        • III.I Inputs
        • III.II Operation
          • III.II.I Epochs
          • III.II.II Proposals
            • III.II.II.I Standard Proposals
            • III.II.II.II POWER Threshold Proposals
            • III.II.II.III ZERO Threshold Proposals
            • III.II.II.IV Proposal Matrix
          • III.II.III Checkpoints and Voting
          • III.II.IV Proposing
          • III.II.V Inflation Mechanics
          • III.II.VI Dutch Auction
          • III.II.VII Delegation
          • III.II.VIII ZERO Claiming of Residual Value
        • III.III Governance Controlled TTG Parameters
        • III.IV Immutable TTG Parameters
        • III.V Immutable POWER Parameters
        • III.VI Immutable ZERO Parameters
      • IV. The M0 Economy
        • IV.I Minters
        • IV.II Validators
        • IV.III Earners
      • V. Off-Chain Ecosystem
        • V.I Guidance
        • V.II Off-Chain Actors and Components
    • Adopted Guidance
      • Adopted Guidance v1.30
        • 1. Description of the Adopted Guidance
          • 1.1. Purpose of the Adopted Guidance
          • 1.2. Change Process for the Adopted Guidance
        • 2. Ecosystem Description
          • 2.1. Actors
          • 2.2. Mandatory Contracts
          • 2.3. Duty of Transparency
          • 2.4. Core Operational Flows
            • 2.4.1. Update Collateral Process
            • 2.4.2. Minting M
            • 2.4.3. Retrieval of Collateral
          • 2.5. High-Risk Jurisdictions
        • 3. Eligible Collateral
          • 3.1. Criteria for Eligible Collateral
          • 3.2. Valuation Policy for Eligible Collateral
          • 3.3. Collateral Storage
          • 3.4. Approved Jurisdictions
            • 3.4.1. Bankruptcy Remoteness
            • 3.4.2. Non-Petition and Non-Seizure Provisions
            • 3.4.3. Priority of Payments and Subordination
            • 3.4.4. Regulatory Compliance
            • 3.4.5. Legal and Regulatory Framework
            • 3.4.6. Political Stability
            • 3.4.7. Dispute Resolution
            • 3.4.8. Asset Segregation
            • 3.4.9. Limited Recourse
            • 3.4.10. Investor Protection
            • 3.4.11. Operational Infrastructure
            • 3.4.12. Custody Relationship
            • 3.4.13. Audit
        • 4. SPV Operators
          • 4.1. Contact Information of Currently Approved SPV Operators
          • 4.2. Eligibility Criteria for Approved SPV Operators
          • 4.3. Obligations of SPV Operators
            • 4.3.1. Obligations in the Normal Course of Business
            • 4.3.2. Obligations Outside of the Normal Course of Business
              • 4.3.2.1. Amicable Wind Down Process
              • 4.3.2.2. Non-Amicable Wind Down Process
              • 4.3.2.3. Minter Insolvency
              • 4.3.2.4. Unauthorized Termination of Minter – SPV Operator Agreement
            • 4.3.3. Operational Obligations of SPV Operators
              • 4.3.3.1. Co-signature of the SPV for significant payments
              • 4.3.3.2. Cooperation with Validators
              • 4.3.3.3. Maintenance of Administrative Buffer
              • 4.3.3.4. No Wire Back Instructions
          • 4.4. Guidelines for Submission of Approval Requests
        • 5. Validators
          • 5.1. Contact Information of Currently Permissioned Validators
          • 5.2. Eligibility Criteria for Permissioned Validators
          • 5.3. Obligations of Validators
          • 5.4. Guidelines for Submission of Permissioning Requests
        • 6. BD Minters and Minters
          • 6.1. Contact Information of Currently Permissioned Minters
          • 6.2. Eligibility Criteria for Permissioned Minters
          • 6.3. Obligations of Minters
          • 6.4. BD Minter and Minter Compliance Requirements
          • 6.5. Guidelines for Submission of Permissioning Requests
        • Adopted Guidance PDF Version
      • Adopted Guidance v1.20 (deprecated)
        • Adopted Guidance PDF Version
    • Glossary
    • Disclosures
    • Whitepaper PDF Version
  • Technical Documentation
    • Protocol Technical Specification
      • Main Invariants
      • Variables
        • Protocol Variables Controlled by TTG
        • Protocol Variables And Definitions
        • Protocol Variables Used For Interest Accruals
      • Protocol And M Token Actors And Actions
        • Protocol Core Functions
          • Minter Gateway
            • updateCollateral
            • proposeMint
            • mintM
            • cancelMint
            • freezeMinter
            • burnM
            • proposeRetrieval
            • activateMinter
            • deactivateMinter
          • M Token
            • startEarning
            • stopEarning
            • transfer
          • Interest Calculations And Indices
            • MinterGateway.updateIndex
            • MinterGateway.currentIndex
            • MToken.updateIndex
            • MToken.currentIndex
            • activeOwedM
          • Interest Rate Models
            • Stable Earner Interest Rate Model Contract
            • Minter Interest Rate Model Contract
    • TTG Technical Specification
      • Main Invariants
      • Core Architecture
        • 1. Registrar
          • Registrar Variables and Getters
          • Registrar Core Functions
        • 2. TTG Governors
          • Matrix Of TTG Proposals
          • 2.1 Standard Governor
            • Variables And Getters
            • Governor Proposal State Transitions
            • Core Functions
            • Core Governance Proposals
          • 2.2 Emergency Governor
            • Emergency Governor Variables And Getters
            • Governor Proposal State Transitions
            • Core functions
              • propose(targets[], values[], callDatas[], description): proposalId
              • castVote(proposalId, support): weight
              • castVotes(proposalIds[], supports): weight
              • execute(targets[], values[], callDatas[], description): proposalId
              • setThresholdRatio(newThresholdRatio)
              • getProposal(proposalId)
              • state(proposalId)
            • Core Governance Proposals
          • 2.3 ZERO Governor
            • Variables And Getters
            • Core Functions
            • Core Governance Proposals
        • 3. POWER Token
          • Variables And Getters
          • POWER Token Core Functions
        • 4. ZERO Token
          • ZERO Token Core Functions
        • 5. Distribution Vault
          • Variables And Getters
          • Core Functions
    • Source Code Reference
      • Protocol
        • Protocol Contracts
          • Core Protocol Contracts
            • MToken
            • MinterGateway
          • Abstract Protocol Contracts
            • ContinuousIndexing
          • Protocol Interfaces
            • IContinuousIndexing
            • IMToken
            • IMinterGateway
            • IRateModel
            • ITTGRegistrar
          • Libs
            • ContinuousIndexingMath
            • TTGRegistrarReader
          • Rate Models
            • Contracts
              • EarnerRateModel
              • MinterRateModel
            • Interfaces
              • IEarnerRateModel
              • IMinterRateModel
      • TTG
        • TTG Contracts
          • Core TTG Contracts
            • DistributionVault
            • Registrar
            • Governors
              • EmergencyGovernor
              • StandardGovernor
              • ZeroGovernor
            • Tokens
              • PowerBootstrapToken
              • PowerToken
              • ZeroToken
          • Abstract TTG Contracts
            • ERC5805
            • Governors
              • BatchGovernor
              • ThresholdGovernor
            • Tokens
              • EpochBasedInflationaryVoteToken
              • EpochBasedVoteToken
            • Interfaces
              • IBatchGovernor
              • IERC5805
              • IERC6372
              • IEpochBasedInflationaryVoteToken
              • IEpochBasedVoteToken
              • IGovernor
              • IThresholdGovernor
          • Deployers
            • EmergencyGovernorDeployer
            • PowerTokenDeployer
            • StandardGovernorDeployer
          • TTG Interfaces
            • IDistributionVault
            • IRegistrar
            • Deployers
              • IDeployer
              • IEmergencyGovernorDeployer
              • IPowerTokenDeployer
              • IStandardGovernorDeployer
            • Governors
              • IEmergencyGovernor
              • IStandardGovernor
              • IZeroGovernor
            • Tokens
              • IPowerBootstrapToken
              • IPowerToken
              • IZeroToken
          • Libs
            • PureEpochs
      • Common
        • Contracts
          • Main
            • ContractHelper
            • ERC20Extended
            • ERC3009
            • ERC712Extended
            • StatefulERC712
          • Interfaces
            • IERC1271
            • IERC20
            • IERC20Extended
            • IERC3009
            • IERC712
            • IERC712Extended
            • IStatefulERC712
          • Libs
            • SignatureChecker
            • UIntMath
    • 🏁Audits
    • 🔛Deployments
Powered by GitBook

M0 Project

  • Home
  • Research

Legal

  • Terms & Conditions
  • Privacy Policy

Copyright 2025 M0 Foundation

On this page
  1. Core Documentation
  2. Adopted Guidance
  3. Adopted Guidance v1.30
  4. 6. BD Minters and Minters

6.4. BD Minter and Minter Compliance Requirements

Each Minter and its affiliates, such as the BD Minter, must have written policies, procedures, and internal controls designed to ensure compliance with the applicable laws within the jurisdiction in which they operate. Additionally, Minters need to have anti-money laundering procedures that are reasonably designed to prevent the Minter from facilitating money laundering and terrorist financing including know-your-customer policies, maintaining highly useful records for law enforcement and regulators and identifying and reporting suspicious activity, as appropriate. These controls must be designed to comply with the obligations of the Minter’s jurisdiction of incorporation or with the international standards recommended by the Financial Action Task Force, as specified below. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

Minters need to maintain anti-money laundering and counter terrorist financing (AML/CFT) programs that are reasonably designed to manage and mitigate the Minter’s risks related to money laundering and terrorist financing. The nature and extent of the AML/CFT program depends upon a number of factors, including the nature, scale and complexity of the Minter’s operations, the diversity of its operations, including geographical diversity, its customer base, product and activity profile, and the degree of risk associated with each area of its operations, among other factors. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

As part of its AML/CFT program, Minters need to obtain and verify the customer identification information as required by the laws of the jurisdiction within which it operates. Minters must also implement policies and procedures to collect additional information to verify the customer’s identity at the beginning of the customer relationship to demonstrate that the Minter can form a reasonable belief of the identity of its customer. Minters must also implement policies and procedures to conduct due diligence about its customer sufficient for the Minter to establish a customer’s risk profile and conduct ongoing monitoring. Such additional, non-core identity information, could include, for example an IP address with an associated time stamp; geo-location data; device identifiers; digital asset wallet addresses; and transaction hashes. Minters may simplify the extent of these due diligence measures where the risk associated with the customer relationship or activities is lower. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

Minters need to implement policies and procedures that assist with identifying customers’ unusual or suspicious movements of funds or transactions indicative of potential involvement in illicit activity. These policies and procedures should ensure that the Minter can timely identify, investigate, and report customers’ unusual or suspicious activity in compliance with the requirements and timeframes imposed by the jurisdictions within which they operate. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

Minters need to designate a person with the responsibility to ensure compliance with the AML/CFT program and oversee day-to-day operations concerning such compliance. This person must be empowered with sufficient authority and autonomy to implement the Minter’s AML/CFT program including access to sufficient resources as needed to mitigate the Minter’s risks of money laundering and terrorist financing. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

Minters need to develop procedures to test the effectiveness of the AML/CFT program commensurate with the Minter’s level of AML risk exposure. The party designated to test the AML/CFT program must be independent, qualified, unbiased and free from any conflicting business interests that may influence the outcome of the compliance program test. The Minter’s policies should include provisions for tracking and remediating weaknesses identified as part of these independent reviews. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

BD Minters need to implement a training program to ensure that all employees at the BD Minter, or independent contractors or third party service providers involved in the BD Minter’s and/or Minter’s operations, understand their obligations under the AML/CFT program. Such training should include senior management and the board of directors or other similar governing bodies of the BD Minter and Minter. The training program should be designed to provide appropriately detailed information to employees based on their level of responsibility regarding the AML/CFT program.

BD Minters and Minters need to, at all times, comply with all economic or financial sanctions or trade embargoes imposed, administered or enforced by the United States (including those administered by OFAC and the U.S. Department of State), the EU, and any other government authority with jurisdiction over the BD Minter and Minter. The Minter needs to maintain effective measures to ensure compliance with, and awareness of, its sanctions-related obligations. This includes implementing measures to conduct appropriate due diligence on customers’ underlying transactions and the parties involved by screening such parties against OFAC’s SDN list and EU sanctions and monitoring virtual asset wallet addresses against such lists. Additionally, these measures will monitor the jurisdictions within which its customers are domiciled to prevent the Minter from facilitating transactions on behalf of persons residing in any country, region or territory, or government thereof, that is the subject or target of comprehensive sanctions. These obligations can be fulfilled by the BD Minter on behalf and for the Minter.

Previous6.3. Obligations of MintersNext6.5. Guidelines for Submission of Permissioning Requests

Last updated 7 months ago