View source on GitHub →

ICN Legal Considerations

This document outlines legal questions that communities using ICN may need to consider. This is not legal advice - communities should consult qualified attorneys in their jurisdiction.

Overview

ICN provides infrastructure for mutual credit systems. The legal treatment of such systems varies by jurisdiction and depends on specific implementation details. This document helps communities identify questions to ask their legal counsel.

1. Are Mutual Credits "Money"?

The Question

Regulators in various jurisdictions have rules about who can issue "money" or "payment instruments." Communities need to understand whether their mutual credit system falls under these regulations.

Key Distinctions

Generally NOT money:

  • Credits redeemable only within a closed community
  • No conversion to government currency (USD, EUR, etc.)
  • Used for time exchange or mutual aid
  • Members know each other and have ongoing relationships

May be regulated as money:

  • Open to the general public
  • Convertible to government currency
  • Large transaction volumes
  • Used for general commerce

By Jurisdiction

United States:

  • Most timebanks are NOT considered money transmission
  • IRS typically treats timebank hours as service barter
  • State-level money transmitter laws vary
  • Key case: Most timebanks operate without money transmitter licenses

European Union:

  • Similar to US - internal exchange systems generally exempt
  • PSD2 (Payment Services Directive) has exemptions for limited networks
  • LETS (Local Exchange Trading Systems) typically unregulated

United Kingdom:

  • FCA (Financial Conduct Authority) guidance on community currencies
  • Timebanks generally exempt from e-money regulations
  • Bristol Pound precedent (was regulated, but unusual due to £ convertibility)

Questions for Your Lawyer

  1. Does our mutual credit system require a money transmitter license in our state/country?
  2. Are we operating a "closed loop" system that qualifies for exemptions?
  3. What activities would cause us to need registration (e.g., allowing currency conversion)?

ICN Design Implications

ICN is designed for closed-loop mutual credit:

  • No built-in currency conversion
  • Cooperative membership controls who participates
  • Credits have no value outside the community
  • This design helps stay within exemptions

2. Tax Reporting

The Question

When members exchange services, are there tax obligations? How should the cooperative report transactions?

General Principles (US-focused)

IRS Barter Exchange Rules:

  • Technically, barter transactions are taxable events
  • Fair market value of services received is income
  • In practice, most small timebanks are not audited

Timebank Exception (IRS informal guidance):

  • Hour-for-hour exchanges at equal value may not be taxable
  • If you give 1 hour and receive 1 hour, net value is $0
  • This applies to equal-rate timebanks
  • Variable-rate systems (plumber hour ≠ babysitter hour) are more complex

Record Keeping:

  • IRS requires records of all barter transactions
  • Report on Form 1099-B if operating as a barter exchange
  • Individual members report on Schedule C or Schedule 1

Cooperative Responsibilities

  1. As a barter exchange: May need to file Form 1099-B for members with >$1 transaction volume
  2. As a nonprofit: Different reporting requirements (Form 990)
  3. Record retention: Keep transaction records for 7+ years

Export for Tax Reporting

ICN provides CSV export for compliance:

icnctl ledger export --coop-id my-coop --format csv --year 2024 -o transactions-2024.csv

Output includes:

  • Transaction ID
  • Date
  • Parties (DIDs or member names if available)
  • Amount
  • Description
  • Running balances

Questions for Your Accountant

  1. Do we need to file as a barter exchange with the IRS?
  2. Are our member-to-member transactions taxable events?
  3. What records do we need to maintain and for how long?
  4. Should members report timebank income on their personal taxes?

3. Data Protection

GDPR (European Union)

If any members are EU residents, GDPR applies.

Data Controller: The cooperative is the data controller Lawful Basis: Legitimate interest (cooperative operation) or consent Data Processed:

  • DIDs (pseudonymous identifiers)
  • Transaction history
  • Membership records

GDPR Rights to Support:

  1. Right to Access: Export member's data
  2. Right to Erasure: Delete member data (with limitations)
  3. Right to Portability: Export in machine-readable format
  4. Right to Rectification: Correct inaccurate data

ICN Implementation:

  • DIDs are pseudonymous (not directly identifying)
  • Ledger entries are immutable (historical integrity)
  • Deletion: Remove from membership, redact personal details
  • Export: icnctl member export --did did:icn:...

Ledger Immutability vs. Erasure:

  • Ledger entries cannot be deleted (double-entry integrity)
  • Approach: Redact identifying information, keep transaction structure
  • Document this limitation in privacy policy

CCPA (California)

Similar to GDPR but narrower. Applies if:

  • Annual revenue >$25M, OR
  • Data on 50,000+ California residents, OR
  • 50%+ revenue from selling personal data

Most cooperative timebanks won't meet these thresholds.

Privacy Best Practices

  1. Minimize data collection: Only collect what's necessary
  2. Document processing: Maintain a data processing record
  3. Secure storage: ICN uses encryption at rest and in transit
  4. Access controls: Limit who can view member data
  5. Retention policy: Define how long to keep inactive member data

Privacy Policy Template

Include in your cooperative's privacy policy:

DATA WE COLLECT:
- Decentralized Identifier (DID) - pseudonymous ID
- Transaction history within the cooperative
- Membership information you provide

HOW WE USE DATA:
- Operate the mutual credit ledger
- Verify membership and balances
- Generate reports for the cooperative

DATA RETENTION:
- Active member data: Retained while membership active
- Transaction history: Retained permanently for ledger integrity
- Inactive members: [Define your policy]

YOUR RIGHTS:
- Access your data: Request a copy of your records
- Correct data: Request corrections to personal information
- Restrict processing: Limit how we use your data
- Data portability: Export your data in standard format
- Deletion: Request removal (ledger entries redacted, not deleted)

4. Liability

The Question

What happens if something goes wrong? Who is responsible?

Potential Liability Areas

Technical Failures:

  • Data loss (backup failures)
  • Incorrect balances (software bugs)
  • Security breaches (compromised keys)

Economic Failures:

  • Member defaults (can't or won't repay negative balance)
  • Disputes between members
  • Fraud within the system

Governance Failures:

  • Decisions that harm members
  • Discrimination in membership
  • Misuse of cooperative funds

Mitigation Strategies

  1. Terms of Service: Clear agreement members accept

    • Limitation of liability clauses
    • Dispute resolution procedures
    • Member responsibilities

  2. Insurance: Consider:

    • Directors & Officers (D&O) insurance
    • Cyber liability insurance
    • General liability insurance

  3. Corporate Structure: Operate as:

    • Incorporated cooperative (limited liability)
    • LLC or similar structure
    • NOT as unincorporated association (personal liability)

  4. Technical Safeguards:

    • Regular backups (ICN supports encrypted backups)
    • Security audits
    • Incident response plan

Limitation of Liability Language

Example clause (customize with legal counsel):

LIMITATION OF LIABILITY

The Cooperative provides the ICN platform "as is" without warranties
of any kind. To the maximum extent permitted by law:

1. The Cooperative is not liable for indirect, incidental, or
   consequential damages arising from use of the system.

2. The Cooperative's total liability shall not exceed the value of
   credits in dispute.

3. The Cooperative is not responsible for losses due to member
   default, security breaches beyond our reasonable control, or
   technical failures despite reasonable precautions.

Members agree to resolve disputes through the cooperative's internal
dispute resolution process before seeking external remedies.

Dispute Resolution

ICN includes dispute primitives:

# File a dispute
icnctl dispute file --counterparty did:icn:other --amount 5 --description "Services not rendered"

# View disputes
icnctl dispute list

# Resolve (requires mediator role)
icnctl dispute resolve --id DISPUTE-001 --resolution partial_payment --amount 2.5

Build your dispute resolution process around these tools.

5. Corporate Structure

Options for Cooperatives

Worker Cooperative:

  • Members are workers in a business
  • Democratic control (one member, one vote)
  • Profit sharing
  • Subject to employment law

Consumer Cooperative:

  • Members are customers/users
  • Democratic control
  • Surplus returned as patronage dividends
  • Common for timebanks

Multi-Stakeholder Cooperative:

  • Multiple member classes (workers, consumers, investors)
  • More complex governance
  • Flexible for different community needs

Nonprofit Organization:

  • 501(c)(3) or 501(c)(4) in US
  • Can still operate mutual credit
  • Tax-exempt status
  • Restrictions on political activity

Incorporation Benefits

  1. Limited Liability: Members not personally liable for cooperative debts
  2. Legal Personhood: Can enter contracts, own property
  3. Perpetual Existence: Survives member changes
  4. Credibility: Recognized legal structure

Jurisdiction Considerations

Some states/countries have better cooperative law:

  • California: Worker cooperative statute
  • Colorado: Strong cooperative law
  • Wisconsin: Cooperative finance options
  • Quebec: Well-developed cooperative sector
  • UK: Co-operative and Community Benefit Societies Act

6. Intellectual Property

Open Source Licenses

ICN is dual-licensed under MIT and Apache-2.0:

  • Can be used for any purpose
  • No warranty provided
  • Must include license and copyright notice
  • Apache-2.0 includes patent grant

Derivative Works

If your cooperative modifies ICN:

  • Your modifications can be kept private
  • If distributed, must include original license
  • No requirement to contribute back (but encouraged)

Cooperative's Own IP

Your cooperative may create:

  • Custom governance contracts
  • UI customizations
  • Documentation

Consider how you want to license these:

  • Open source (contribute to ecosystem)
  • Proprietary (keep competitive advantage)
  • Creative Commons (for documentation)

7. Compliance Checklist

Before Launch

  • Choose corporate structure and incorporate
  • Draft Terms of Service with legal counsel
  • Create privacy policy
  • Define dispute resolution process
  • Consult accountant on tax reporting
  • Check money transmitter regulations in your jurisdiction
  • Set up backup and security procedures

Ongoing

  • Regular backups (weekly minimum)
  • Annual tax reporting (if required)
  • Privacy policy updates as needed
  • D&O insurance renewal
  • Member data access requests
  • Dispute resolution tracking

Record Keeping

Maintain records of:

  • All transactions (7+ years)
  • Membership changes
  • Governance decisions
  • Dispute resolutions
  • Data access requests

ICN stores transaction history automatically. Export regularly for off-system backup.

8. Resources

Legal

Tax

Privacy

Cooperative Development

Disclaimer

This document provides general information about legal considerations for mutual credit systems. It is not legal advice. Laws vary by jurisdiction and change over time. Communities should consult qualified legal and financial professionals in their jurisdiction before launching or operating a mutual credit system.

The ICN project and its contributors are not responsible for legal compliance of individual cooperative implementations.

Last updated: 2025-01-17

← Back to Docs