LogoLogo
LogoLogo
  • Intro
    • Welcome
    • The Benefits of BSV Blockchain
    • What Can I Do?
    • Overview of GitHub repositories
    • Quick Start
  • Protocol
    • Introduction
    • BSV Blockchain
      • Blocks
      • Transactions
      • Proof of Work
      • Capabilities
      • Economic Model of Governance
      • Digital Asset Recovery
    • Network Policies
      • High-Level Architecture
      • Mining
      • Standard and Local Policies
      • Consensus Rules
      • Local Policies
    • Node Operations
      • Node Software
      • Bitcoin Server Network (BSN)
      • ChainTracker
      • Transaction Validation
      • UTXO Storage
      • Mempool
      • Block Assembler
      • Block Validation
      • Mining Software
      • Pruning transactions
      • Responsibilities of a Node
    • SPV Wallets, Overlays and SPV Processes
      • Simplified Payment Verification (SPV)
      • Instant Payments
      • Integrity Checks
      • SPV Wallets & Overlays
    • Transaction Lifecycle
      • Transaction Inputs and Outputs
      • Script
      • Transaction Flow
      • Constructing a transaction
      • Sequence Number and Time Locking
      • Transaction Templates
      • Transaction Processing
      • Opcodes used in Script
    • Privacy
      • Keys and Identity
      • Private vs Anonymous
      • Digital Signatures
      • Privacy on the Public Blockchain
  • Network Access Rules
    • Rules
      • Table of Contents
      • Background to the Rules
      • PART I - MASTER RULES
      • PART II - GENERAL RULES
      • PART III - ENFORCEMENT RULES
      • PART IV - DISPUTE RESOLUTION RULES
      • PART V - INTERPRETIVE RULES
    • FAQs
      • Miners
      • Professionals
      • Users
  • Important Concepts
    • High Level
      • Web3
      • Timestamping
      • SPV
      • UTXO vs Account Based
      • Linked Keys
      • Smart Contracts
    • Details
      • Hash Functions
      • Merkle Trees
      • Sighash Flags
      • Script
      • SPV
        • Deep Dive
        • Payments Flow
        • Data Models
        • Broadcasting
  • Network Topology
    • Mandala Upgrade
    • Nodes
      • SV Node
        • Architecture
        • System Requirements
        • Installation
          • SV Node
            • Configuration
            • AWS Volumes Setup
            • DDOS Mitigation
            • Docker
            • Genesis Settings
            • GetMiningCandidate
            • GKE
            • Network Environments
              • Regtest
              • STN
              • Testnet
        • Alert System
          • Alert Messages
          • Running the Alert System
            • Startup Script
          • Webhooks
        • RPC Interface
          • RPC Methods
        • Frequently Asked Questions
          • Blocks
          • Initial Block Download
          • Transactions
          • Log File Warnings
          • Safe Mode
          • Bug Bounty
        • Chronicle Release
      • Teranode
    • Overlay Services
      • Overlay Example
    • SPV Wallet
      • Quickstart
      • Key Concepts
      • AWS Deployment
        • Installation
        • Manage & Maintain
        • Update
        • Delete
      • Components
        • SPV Wallet Server
        • Storage
        • Web Admin
        • Block Headers Service
        • Web App & API
      • Who is it for?
      • Functionality & Roadmap
      • Contribute
      • Developers Guide
        • SPV Wallet
          • Authentication
          • Configuration
          • Notification
        • Go Client
          • Authentication
        • JS Client
          • Authentication
        • Admin
        • Keygen
        • Block Headers Service
          • Authentication
          • Configuration
      • Additional Components
  • paymail
    • Overview
    • BRFC Specifications
      • Specification Documents
      • BRFC ID Assignment
    • Service Discovery
      • Host Discovery
      • Capability Discovery
    • Public Key Infrastructure
    • Payment Addressing
      • Basic Address Resolution
      • Sender Validation
      • Receiver Approvals
      • PayTo Protocol Prefix
    • Verify Public Key Owner
    • Recommendations
  • Guides
    • Local Blockchain Stack
      • Mockchain Stack
    • Business Use Cases
      • Creating a Tranche of Event Tickets
    • SDKs
      • Concepts
        • BEEF
        • Fees
        • SPV
        • Transactions
        • Op Codes
        • Script Templates
        • Signatures
        • Verification
      • TypeScript
        • Node, CommonJS
        • React
        • Low Level
          • Verification
          • ECDH
          • Numbers & Points
          • Signatures
          • 42
          • ECDSA
          • Hmacs
          • Keys
          • Scripts
        • Examples
          • Creating a Simple Transaction
          • Verifying a BEEF Structure
          • Creating Transactions with Inputs, Outputs and Templates
          • Creating the R-puzzle Script Template
          • Message Encryption and Decryption
          • Message Signing
          • Building a Custom Transaction Broadcast Client
          • Verifying Spends with Script Intrepreter
          • BIP32 Key Derivation with HD Wallets
          • Using Type 42 Key Derivation for Bitcoin Wallet Management
          • Creating a Custom Transaction Fee Model
          • Building a Pulse Block Headers Client
          • Using ECIES Encryption
      • Go
        • Examples
          • Simple Tx
          • Keys
          • Encryption
          • Broadcasting
          • Inscribing
          • Data Markers
          • Linked Keys
          • ECIES
          • Fees
          • HD Keys
          • Headers
          • Secure Messages
          • Merkle Path Verification
      • Python
        • Examples
          • Simple Tx
          • Verifying BEEF
          • Complex Tx
          • Script Templates
          • Encryption
          • Message Signing
          • Building A Custom Broadcaster
          • HD Wallets
          • Linked Keys
          • Fees
          • Merkle Path Verification
          • ECIES
  • BSV Academy
    • Getting Started
    • BSV Basics: Protocol and Design
      • Introduction
        • Bit-Coin
      • The BSV Ledger
        • The Ledger
        • Triple Entry Accounting
        • Example
      • Coins and Transactions
        • Coins
        • Transactions
        • Transaction Fees
      • Theory
      • Conclusion
    • BSV Enterprise
      • Introduction
      • About BSV Blockchain
        • Introduction
        • Safe, Instant Transactions at a Predictably Low Cost
          • Reliably Low Fees
          • Comparison to Legacy Transaction Systems
          • Payment Channels
        • Scalability to Accommodate Global Demand
          • Big Blocks Show Big Potential
        • A Plan for Regulatory Acceptance
          • Ready-made Compliance
          • The Open BSV License
        • Protocol Stability
          • Building Foundations on a Bedrock of Stone
      • Technical Details
        • The Network
          • The Small World Network
          • Robust In Its Unstructured Simplicity
        • The Bitcoin SV Node Client
          • Teranode - The Future of BSV
        • The Protocol - Simple, Robust and Unbounded
          • What is the BSV Protocol?
        • Proof of Work
          • The Algorithm
          • Efficiency of Proof of Work
        • Privacy and Identity
        • Permissions and Privacy
      • Resources and Tools
        • The Technical Standards Comittee
          • TSC Principles
          • Standard Development Process
          • Status of Current and In-progress Standards
        • The Working Blockchain
          • Pruning to Create a Working Blockchain
          • Building a Working Blockchain from a List of Block Headers
          • A World View Backed by Proof of Work
    • Hash Functions
      • What are Hash Functions?
        • The Differences Between Hashing and Encryption
        • The Three Important Properties of Hash Functions
        • The Hash Functions Found in BSV
      • Base58 and Base58Check
        • What is Base58 and Why Does Bitcoin use it?
        • What is Base58 and How Does BSV use it?
      • SHA256
        • BSV Transactions and SHA-256
        • BSV Blocks and SHA-256
        • Proof-of-Work and HASH-256
      • Walkthrough Implementation of SHA-256 in Golang
        • Overview of SHA-256
        • SHA-256 Input and Processing
        • SHA-256 Compression
        • SHA-256 Final Value Construction and Output
      • RIPEMD-160
        • BSV Addresses & WIFs
      • Walkthrough Implementation of RIPEMD-160 in Golang
        • Overview of RIPEMD-160
        • RIPEMD-160 Input and Processing
        • RIPEMD-160 Compression
        • RIPEMD-160 Final Value Construction and Output
      • Doubla Hashing and BSV's Security
        • Why is Double Hashing Used in BSV
        • Hash Functions and BSV's Security Model
    • Merkle Trees
      • The Merkle Tree
        • What is a Merkle Tree?
        • Why use a Merkle Tree?
        • Merkle Trees in Action
      • Merkles Trees in BSV
        • The Data Elements
        • Transaction Merkle Trees
        • Transaction Merkle Trees in Action
      • Merkle Trees and the Block Header
        • What is the Block Header
        • The Hash Puzzle
        • Proof-of-Work in Action
      • Merkle trees and Verifying Proof of Work
        • Broadcasting the Block
        • The Coinbase Transaction
        • Data Integrity of the Block
        • Saving Disk Space
      • Standarised Merkle Proof
        • What is a Merkle Proof?
        • The BSV Unified Merkle Path (BUMP) Standard
        • Simple and Composite Proofs
      • Merkle Trees and Simplified Payment Verification
        • SPV
        • Offline Payments
    • Digital Signatures
      • What are Digital Signatures
        • Background
        • Introduction
        • Digital Signatures Protocol
        • Properties of Digital Signatures
      • ECDSA Prerequisites
        • Disclaimer
        • Modular Arithmetic
        • Groups, Rings and Finite Fields
        • Discrete Logarithm Problem
        • Elliptic Curve Cryptography (ECC)
        • Discrete Logarithm Problem with Elliptic Curves
      • ECDSA
        • Introduction
        • ECDSA
        • Further Discussion
      • BSV and Digital Signatures
        • Introduction
        • BSV Transaction
        • ECDSA (secp256k1) for BSV Transaction
        • Summary
        • Signed Messages
        • Miner Identification and Digital Signatures
    • BSV Theory
      • Abstract
        • Peer-to-Peer Cash
        • Digital Signatures and Trusted Third Parties
        • Peer-to-Peer Network
        • Timechain and Proof-of-Work
        • CPU Power
        • Cooperation in the Network
        • Network Structure
        • Messaging Between Nodes
      • Introduction
        • Commerce on the Internet
        • Non Reversible Transactions
        • Privacy in Commerce
        • The Paradigm of Fraud Acceptance
        • What is Needed...
        • Protecting Sellers From Fraud
        • Proposed Solution
        • Security and Honesty
      • Transactions
        • Electronic Coins
        • Spending a Coin
        • Payee Verification
        • Existing Solutions
        • First Seen Rule
        • Broadcasting Transactions
        • Achieving Consensus
        • Proof of Acceptance
      • Timestamp Server
        • Timestamped Hashes
        • A Chain of Timestamped Hashes
      • Proof of Work
        • Hashcash
        • Scanning Random Space
        • Nonce
        • Immutable Work
        • Chain Effort
        • One CPU, One Vote
        • The Majority Decision
        • The Honest Chain
        • Attacking the Longest Chain
        • Controlling the Block Discovery Rate
      • Network
        • Running the Network
        • The Longest Chain
        • Simultaneous Blocks
        • Breaking the Tie
        • Missed Messages
      • Incentive
        • The Coinbase Transaction
        • Coin Distribution
        • Mining Analogy
        • Transaction Fees
        • The End of Inflation
        • Encouraging Honesty
        • The Attacker's Dilemma
      • Reclaiming Disk Space
        • Spent Transactions
        • The Merkle Tree
        • Compacting Blocks
        • Block Headers
      • Simplified Payment Verification
        • Full Network Nodes
        • Merkle Branches
        • Transaction Acceptance
        • Verification During Attack Situations
        • Maintaining an Attack
        • Invalid Block Relay System
        • Businesses Running Nodes
      • Combining and Splitting Value
        • Dynamically Sized Coins
        • Inputs and Outputs
        • A Typical Example
        • Fan Out
      • Privacy
        • Traditional Models
        • Privacy in Bitcoin
        • Public Records
        • Stock Exchange Comparison
        • Key Re-Use
        • Privacy - Assessment 2
        • Linking Inputs
        • Linking the Owner
      • Calculations
        • Attacking the Chain
        • Things the Attacker Cannot Achieve
        • The Only Thing an Attacker Can Achieve
        • The Binomial Random Walk
        • The Gambler's Ruin
        • Exponential Odds
        • Waiting For Confirmation
        • Attack Via Proof of Work
        • Vanishing Probabilities
      • Conclusion
        • Conclusion Explained
    • Introduction to Bitcoin Script
      • Chapter 1: About Bitcoin Script
        • 01 - Introduction
        • 02 - FORTH: A Precursor to Bitcoin Script
        • 03 - From FORTH to Bitcoin Script
        • 04 - Bitcoin's Transaction Protocol
        • 05 - Transaction Breakdown
        • 06 - nLockTime
        • 07 - The Script Evaluator
      • Chapter 2: Basic Script Syntax
        • 01 - Introduction
        • 02 - Rules Around Data and Scripting Grammar
        • 03 - The Stacks
      • Chapter 3: The Opcodes
        • 01 - Introduction
        • 02 - Constant Value and PUSHDATA Opcodes
        • 03 - IF Loops
        • 04 - OP_NOP, OP_VERIFY and its Derivatives
        • 05 - OP_RETURN
        • 06 - Stack Operations
        • 07 - Data transformation
        • 08 - Stack Data Queries
        • 09 - Bitwise transformations and Arithmetic
        • 10 - Cryptographic Functions
        • 11 - Disabled and Removed Opcodes
      • Chapter 4: Simple Scripts
        • 01 - Introduction
        • 01 - Pay to Public Key (P2PK)
        • 02 - Pay to Hash Puzzle
        • 03 - Pay to Public Key Hash (P2PKH)
        • 04 - Pay to MultiSig (P2MS)
        • 05 - Pay to MultiSignature Hash (P2MSH)
        • 06 - R-Puzzles
      • Chapter 5: OP_PUSH_TX
        • 01 - Turing Machines
        • 02 - Elliptic Curve Signatures in Bitcoin
        • 03 - OP_PUSH_TX
        • 04 - Signing and Checking the Pre-Image
        • 05 - nVersion
        • 06 - hashPrevouts
        • 07 - hashSequence
        • 08 - Outpoint
        • 09 - scriptLen and scriptPubKey
        • 10 - value
        • 11 - nSequence
        • 12 - hashOutputs
        • 13 - nLocktime
        • 14 - SIGHASH flags
      • Chapter 6: Conclusion
        • Conclusion
    • BSV Infrastructure
      • The Instructions
        • The Whitepaper
        • Steps to Run the Network
        • Step 1
        • Step 2
        • Step 3
        • Step 4
        • Step 5
        • Step 6
      • Rules and their Enforcement
        • Introduction
        • Consensus Rules
        • Block Consensus Rules
        • Transaction Consensus Rules
        • Script Language Rules
        • Standard Local Policies
      • Transactions, Payment Channels and Mempools
      • Block Assembly
      • The Small World Network
        • The Decentralisation of Power
        • Incentive Driven Behaviour
        • Lightspeed Propagation of Transactions
        • Ensuring Rapid Receipt and Propagation of New Blocks
        • Hardware Developments to Meet User Demand
        • Novel Service Delivery Methods
        • MinerID
      • Conclusion
  • Research and Development
    • BRCs
    • Technical Standards
  • Support & Contribution
    • Join Our Discord
    • GitHub
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Network Access Rules
  2. Rules

PART V - INTERPRETIVE RULES

Part V - Interpretive Rules

  1. Principles of interpretation The following principles of interpretation apply to the Rules:

    • (a) references to parties are to the Association and Nodes, and not to any third parties;

    • (b) references to a person will include a natural person, corporate, or unincorporated body (whether or not such body has a separate legal personality);

    • (c) references to a company will include any company, corporation, or other body corporate, wherever and however incorporated or established;

    • (d) a reference to any of a Node’s obligations under the Rules will include an obligation not to procure, permit, or suffer that thing to be done;

    • (e) a reference to writing or written excludes fax but includes being recorded by any means and, includes email and messages in any human-readable format or representing words in any visible form sent through the Network;

    • (f) a reference to signing includes an electronic signature, but only where signed through a secure operating system or platform which, in the Association’s reasonable opinion: (i) allows the signature to be uniquely linked to the signatory and capable of identifying them; and (ii) provides a link to the signed data in such a way that any subsequent change in the data is detectable;

    • (g) any reference to a legal term for any action, remedy, method of judicial proceeding, legal document, legal status, court, official, or any legal concept or thing will, in respect of any jurisdiction other than England and Wales, be deemed to include a reference to that which most nearly approximates to the legal term in that jurisdiction which is equivalent to that in England and Wales;

    • (h) unless the context otherwise requires, words in the singular will include the plural, and words in the plural will include the singular;

    • (i) unless the context otherwise requires, the words ‘or’ and ‘and’ will be interpreted such that ‘A or B’ means ‘A or B or both,’ ‘either A or B’ means ‘A or B, but not both,’ and ‘A and B’ means ‘both A and B’; and

    • (j) any words following the terms including, include, in particular, for example, or any similar expression will be interpreted as illustrative and will not limit the sense of the words preceding those terms.

  2. Glossary

The following definitions apply to the Rules:

Term
Definition

Affiliate:

any entity that directly or indirectly Controls, is Controlled by, or is under common Control with, another entity;

Applicable Laws:

in respect of any Node:

(a) any laws, legislation, regulation, by-law, or subordinate legislation;

(b) any rule or principle of the common law or equity;

(c) any binding order, judgment, or decree of any court, or arbitrator or tribunal, having jurisdiction or contractual authority over that Node or the Association (as applicable) or any of that Node’s or the Association’s assets, resources, or business (as applicable); or

(e) any direction, policy, decision, rule, or order that is binding on that Node or the Association and that is made or given by any governmental, regulatory, or supervisory authority;

in each case as amended, extended, or re-enacted and which:

(i) has the force of law in any part of the world where that Node or the Association (as the case may be) is located or does business or conducts any Relevant Activity; and

(ii) are binding on that Node or the Association (as applicable) or either of that Node’s or the Association’s assets (as applicable) in any part of the world;

Association and we, our, or us:

each has the meaning set out in recital A of the Background to the Rules;

Bitcoin Protocol:

the protocol implementation of the Bitcoin White Paper as set out at: https://protocol.bsvblockchain.org/;

Bitcoin White Paper:

has the meaning set out in recital A of the Background to the Rules;

Bitcoin, Bitcoin SV, or BSV:

has the meaning set out in recital A of the Background to the Rules;

Block Reward:

has the meaning set out in clause I.3.2 of the Rules;

Block Subsidy:

has the meaning set out in clause I.3.2 of the Rules;

Business Day:

a day other than a Saturday, Sunday, or public holiday in England or Switzerland;

Change Notice:

has the meaning set out in clause II.5.2 of the Rules;

Control:

the beneficial ownership of more than 50% of the issued share capital of a company or the legal or de-facto power to direct or cause the direction of the affairs of a company or entity, and ‘Controls’ and ‘Controlled’ will be interpreted accordingly;

Data Protection Laws:

(a) any laws, legislation, regulation, by-law, or subordinate legislation;

(b) any binding order, judgment or decree of any court or arbitrator or tribunal having jurisdiction or contractual authority any party’s assets, resources, or business (as applicable); or

(c) any direction, policy, decision, rule, or order that is binding on any party and that is made or given by any governmental, regulatory, or supervisory authority;

in each case which relates to the processing of Personal Data and as amended, extended or re-enacted, including the Privacy and Electronic Communications Regulations 2003 (as amended by SI 2011 no. 6), the Data Protection Act 2018 and Regulation 2016/679 of 27 April 2016 of the European Parliament and of the Council on the protection of individuals with regard to the processing of personal data and on the free movement of such data as each is amended in accordance with the Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019 (as amended by SI 2020 no. 1586) and incorporated into UK law under the UK European Union (Withdrawal) Act 2018 and which:

(i) has the force of law in any part of the world where any party (as the case may be) is located or does business or conduct any Relevant Activity; and

(ii) is binding on any party (as applicable) or any party’s assets (as applicable) in any part of the world;

Decision:

any order, judgment, decree, direction, or requirement of any kind issued by a court or a competent tribunal, including any tribunal of arbitration or adjudication;

Direct Decision:

has the meaning set out in clause III.4.2 of the Rules;

Direct Decision Event:

has the meaning set out in clause III.4.1 of the Rules;

Directive:

has the meaning set out in clause III.1.1 of the Rules;

Directive Event:

has the meaning set out in clause III.1.2 of the Rules;

Enforcement Event:

has the meaning set out in clause III.3.1 of the Rules;

Indirect Decision:

has the meaning set out in clause III.5.2 of the Rules;

Indirect Decision Event:

has the meaning set out in clause III.5.1 of the Rules;

Intellectual Property Rights:

patents, utility models, rights to inventions, copyright, and neighbouring and related rights, moral rights, trademarks, and service marks, business names, and domain names, rights in get-up and trade dress, goodwill, and the right to sue for passing off or unfair competition, rights in designs, rights in computer software, database rights, rights to use, and protect the confidentiality of, confidential information (including know-how and trade secrets), and all other intellectual property rights, in each case whether registered or unregistered and including all applications and rights to apply for, and be granted, renewals, or extensions of, and rights to claim priority from, such rights, and all similar or equivalent rights or forms of protection which subsist or will subsist now or in the future in any part of the world;

Malicious Code:

code, files, scripts, agents, or programmes intended to do harm to the Network, the Association, other Nodes, or third parties (or made with reckless indifference as to whether they may cause such harm), and whether effected by means of automatic devices, scripts, algorithms, or any similar manual processes;

Message:

has the meaning set out in clause I.5.2(d) of the Rules;

Network:

(a) the Bitcoin blockchain (and any test blockchains) containing block height #556767 with the hash

‘000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b’ and that contains the longest persistent chain of blocks which are valid under the Rules; or

(b) all relevant communication channels between peers;

Network Activities:

has the meaning set out in recital D of the Background to the Rules;

Network Database:

the distributed ledger relating to the Network;

Node:

has the meaning set out in recital D of the Background to the Rules, but does not include the Association;

Node Software:

any software made available in the Repository on the Repository or elsewhere under the Node Software Licence, any prior version of that software, and any software derived from the same;

Node Software Licence:

has the meaning set out in recital G of the Background to the Rules;

Personal Data:

has the meaning given to it under Data Protection Laws;

Purpose:

has the meaning set out in clause III.6.3 of the Rules;

Relevant Activity:

has the meaning set out in clause I.2.2 of the Rules;

Repository:

the Association’s Github repository made available at https://github.com/bitcoin-sv/bitcoin-sv/, or such other code repository as the Association may specify for the purposes of the Rules;

Rules:

has the meaning set out in clause I.1 of the Rules, as varied from time to time in accordance with clause II.5 of the Rules;

Sanctions Authority:

Switzerland, the United Nations, the European Union (or any of its member states), the United Kingdom, and in each case their respective sanctions, governmental, judicial, or regulatory institutions, agencies, departments, and authorities, including the Swiss State Secretariat for Economic Affairs, the Swiss Federal Council, the United Nations Security Council, His Majesty’s Treasury, the United Kingdom’s Office of Financial Sanctions Implementation, and the United Kingdom’s Department of International Trade;

Sanctions List:

any of the lists issued or maintained by a Sanctions Authority designating or identifying persons that are subject to Sanctions, in each case as from time to time amended, supplemented, or substituted;

Sanctions Restricted Person:

a natural person or legal entity that is: (a) listed on any Sanctions List; (b) resident, domiciled, or located in, or incorporated, or organised under the laws of, a country or territory that is the target of any Sanctions; (c) a government of any country or territory that is the target of any Sanctions, or an agency or instrumentality of such a government; (d) otherwise identified by a Sanctions Authority as being subject to Sanctions; or (e) is at least 50% owned (whether legally or beneficially) and/or Controlled by any person or entity which falls into the foregoing categories or is acting or purporting to act on behalf of any such person or entity;

Sanctions:

any economic, financial, or trade sanctions laws, regulations, embargoes, or restrictive measures administered, enacted, or enforced by any Sanctions Authority, including any such law or regulation enacted, promulgated, or issued by any Sanctions Authority after the date of the Rules and including any enabling legislation, executive order, or regulation promulgated under or based under the authorities of any of the foregoing by any Sanctions Authority;

Step:

has the meaning set out in clause III.6.2 of the Rules;

Suspended Node:

has the meaning set out in clause I.9 of the Rules;

Swiss Rules:

has the meaning set out in clause IV.1.1 of the Rules;

Unilateral Contract:

has the meaning set out in recital B of the Background to the Rules;

Website:

the Association’s website at bsvblockchain.org/network-access-rules or such other website or online portal as the Association may specify for the purposes of the Rules.

PreviousPART IV - DISPUTE RESOLUTION RULESNextFAQs

Last updated 12 months ago

Was this helpful?