title

author

date

documentclass

geometry

linkcolor

toc

numbersections

header-includes

Mainstream Token Whitepaper

Mainstream Token Team

January 2025

report

margin=1in

blue

true

\usepackage{titling}

\usepackage{titlesec}

\usepackage{tocloft}

\pretitle{\begin{center}\LARGE\vspace*{-3em}}

\posttitle{\end{center}\vspace{1em}}

\preauthor{\begin{center}\large}

\postauthor{\end{center}\vspace{1em}}

\titleformat{\chapter}{\normalfont\LARGE\bfseries}{\thechapter.}{1em}{}

\titlespacing*{\chapter}{0pt}{-20pt}{20pt}

\setlength{\droptitle}{-2em}

\setlength{\headheight}{12pt}

\setlength{\headsep}{12pt}

\renewcommand{\contentsname}{Table of Contents}

Executive Summary

MainstreamToken ($MAIN): A digital asset governed by AIDAMIS (AI Dynamic Advancement with Mainstream Innovation Synergy), an AI entity under development. AIDAMIS will be the core analytical and strategic framework for the MainstreamToken ecosystem.

Key Value Proposition: Unique blend of community-focused development with AI-driven governance. Transparent decision-making.

MainstreamToken ($MAIN) proposes a new paradigm for digital asset management. Through the experimental Mainstream Token License (MTL) protocol, this project aims to establish a framework where digital creators and users may explore the potential of decentralized, transparent ownership. The system will use $MAIN tokens or other payment methods as defined in the license parameters.

Current Challenges: Existing systems present inefficiencies due to complexity, fragmentation, and barriers to access, which may hinder creativity and growth.

Our Approach: MainstreamToken ($MAIN) will explore a new approach by employing the MTL protocol. This will provide creators with enhanced control and users with novel ways to interact with digital assets, while improving overall transparency.

Key Innovations: (under development)

AI-Enhanced Ecosystem: AIDAMIS, a council composed of leading AI models, will provide strategic guidance and insight for the project's future direction.
Dynamic Ownership Framework: The MTL protocol aims to provide flexible licensing and rights management, adapting to the needs of the evolving digital landscape.
Transparent Transactions: The blockchain technology underlying MT will aim to offer an immutable, transparent verification process.
Community-Centric Development: A decentralized governance process will enable users to participate in the project's development.

What MT Ecosystem Aims to Enable:

Secure Digital Asset Management: Tools for managing, tracking, and exploring monetization options for digital assets.
Opportunities for Creators: New avenues for creators to maintain ownership of their creations while interacting with the community.
Exploration of Blockchain Potential: The project aims to research the capabilities of blockchain to provide more secure and transparent systems.
Global Opportunities: Explore the potentials for integrating with existing financial systems to foster broader accessibility and innovation."

Path Forward: MainstreamToken is designed with the intent of becoming a leading cryptocurrency by establishing an ecosystem that emphasizes transparency, community empowerment, and advanced technological innovation. The development roadmap includes:

Phase 1: The initial platform launch with community building and education initiatives.
Phase 2: Exploration of platform integrations, partnerships, and bridges to other platforms.
Phase 3: Research and development of enhanced functionality and integration of AI and blockchain technologies.

MainstreamToken is a project focused on exploring the potential that arises from combining AI and blockchain within a transparent framework.

Call to Action: Explore the potential of the Mainstream ecosystem by joining our social media groups.

\pagebreak

Introduction

Digital Rights Management Evolution: Digital content licensing systems remain fragmented and static, struggling to adapt to modern content creation and usage patterns. The MainstreamToken License (MTL) protocol seeks to address these limitations through a novel approach to token-based rights management.

Protocol Foundation: MainstreamToken implements the MTL protocol through:

Technical Framework: The MTL protocol operates through:

Clear parameter structures that define rights usage.
A public verification system for transparent asset tracking.
Multi-platform support to ensure broad accessibility.
Community engagement components that help further evolve the project.

AIDAMIS Integration: Market analysis, risk assessment, and strategic guidance will be provided through AIDAMIS (AI Dynamic Advancement with Mainstream Innovation Synergy), a council comprised of leading AI models. AIDAMIS is the core analytical and strategic framework for the MainstreamToken ecosystem.

Vision: To create sustainable value through transparent, token-based rights management.

Mission: To establish a secure and ethical digital asset infrastructure through community participation and innovation.

All technical details of the system and its implementation are available in the "Technical Appendix" section of this document.

\pagebreak

Ecosystem Overview

Core Components:
- MainstreamToken (MT):
  - Platform: Solana blockchain.
  - Supply: 1 billion tokens.
  - Launch: Initial distribution through a bonding curve mechanism.
  - Minting Policy: Fixed supply, with no additional minting.
- MTL Protocol Implementation:
  - Parameter-based licensing system.
  - Token-based verification of licenses.
  - Revenue share tracking for content creators.
  - Multi-chain exploration through bridging.
Current Features:
- Rights Management:
  - Token-based verification for license access.
  - Manual compliance checking through the community.
  - Public documentation for all license parameters.
  - Community verification process using transparent records.
- Platform Integration:
  - Bonding curve pricing to ensure fair token distribution.
  - Initial liquidity provision through the initial distribution.
  - Transaction verification using the Solana blockchain, ensuring security and transparency.
  - Community tracking, with public records of all processes.
Technical Framework:
- Verification System:
  - Platforms: Publicly accessible platforms.
  - Format: Standardized posting using the defined license string.
  - Tracking: Public records for all transactions and verification.
  - Compliance: Community-driven through user participation.
- Asset Management:
  - Structured ID system that is unique and predictable.
  - Clear categorization of assets using predefined types.
  - Token-based ownership tracking, using blockchain records.
  - Community verification system based on public records.

\pagebreak

MainstreamToken ($MAIN) Details

Token Mechanics:

Total Supply: 1,000,000,000 $MAIN tokens.
Platform: Solana blockchain, chosen for its efficiency and low transaction costs.
Launch: The initial distribution of $MAIN tokens was facilitated through a bonding curve mechanism on a decentralized platform, ensuring transparent price discovery and initial liquidity generation.
Minting Policy: No additional $MAIN tokens will be minted beyond the initial supply of 1 billion, guaranteeing a fixed supply.
Cost Savings: Leveraging a decentralized platform for token creation enabled the MainstreamToken team to allocate more resources to AI research, community development, and long-term strategic planning.

Features:

Experimental Utility with experimental MTL License & Protocol

Experimental Rights Management:

In the initial phases, the $MAIN token will be used to:

Verify license parameters and confirm user permissions through a community-driven process. These will be initially verified manually and recorded through various means, including a public ledger or other accessible tracking systems.
Participate in revenue sharing through manual token transfers or other payment methods. Data will be gathered through community input and verifiable sources.
Create a transparent and secure system for tracking licenses and usage rights through manual community participation. Records of this process will be made readily accessible through various means.
Development Fund: This fund is used to support the ongoing development of the MainstreamToken ecosystem, including but not limited to:
- Research and development of new features and technologies.
- Platform maintenance and infrastructure support.
- Community engagement and growth initiatives.
- Legal and compliance costs.
- Marketing and promotion of the project.
- Strategic partnerships and collaborations.
- Operational costs of the project.

For example, an artist could use $MAIN tokens, or other payment methods, to license their music, granting users access based on token holdings or other payment methods. Users could then use their tokens or other payment methods to access the music, and the artist would receive revenue through manual token transfers or other payment systems.

Platform Interaction:

The initial distribution of $MAIN tokens will be achieved through a bonding curve mechanism on a decentralized platform.
$MAIN's price will be subject to the mechanics of bonding curves and may fluctuate based on buy and sell volume during the initial launch.
This mechanism will facilitate initial liquidity generation for trading on Solana DEX platforms.
$MAIN tokens will be used to perform transactions and verification within the system.

Experimental MTL Protocol:

The MTL protocol utilizes various methods for decentralized digital licensing.
Token ownership or other payment methods define specific rights and parameters through programs or other systems.
The system enables a transparent verification system for digital rights.
The MTL protocol facilitates transparent revenue distribution to content creators.

MTL Protocol Overview:

The Experimental Mainstream Token License (MTL) protocol is a decentralized system for managing and enforcing digital rights using programs and the MainstreamToken (MT).

Decentralized Licensing: The MTL protocol is designed to allow for the creation and management of digital licenses using programs, without the need for a central authority.
Parameter Driven: The license_parameters object allows users to create and manage licensing terms, such as usage rights, duration, and scope.
Tokenized Rights: The MTL protocol enforces usage parameters based on $MAIN token ownership, creating a transparent and auditable licensing system.
Automated Enforcement: Programs will eventually automatically enforce license agreements based on the parameters set by the owner.
Revenue Distribution: The protocol facilitates revenue distribution using $MAIN token, based on pre-defined conditions.
Verification Process: The protocol defines how licenses and ownership can be verified using data stored on the blockchain.
Modularity: The protocol is designed to be modular, so new types of licenses can be added easily in the future without causing any compatibility issues.

User Interface (UI) Design:

The user interface will be built to facilitate both the creators and consumers of licenses, which will include tools for:

Creator Interface:

License Creation: Set various licensing terms including usage rights, duration, and scope. (reference the encoder app on website)

User Interface:

License Verification: View all details, and verify the validity of a license. (reference the decoder app on website)

All technical details of the system and its implementation are available in the "Technical Appendix" section of this document.

\pagebreak

Technical Appendix: MainstreamToken ($MAIN) System Specifications

This appendix provides technical details about the MainstreamToken (MT) system, including the data structure for on-chain storage, the hashing process, a client-side implementation focus, licensing standards, verification processes, and other technical specifications.

A. Core Protocol

License String Format (MTL v0.1):

Base Format: mtl:0.1-[TYPES]/[TOKENS]-[FEE]/[SPLITS];[CONDITIONS]~[ADDENDUM]~PAY:[PAYMENT_DETAILS]

Payment Information:

PAY:[payment_details]: Required field specifying payment information in the format TYPE:DETAILS
Supported payment types include:
- WALLET: Blockchain wallet address (e.g., WALLET:0x123...abc)
- BANK: Bank account details (e.g., BANK:SWIFT:XXXXXX|ACCT:YYYY)
- PAYPAL: PayPal email address (e.g., PAYPAL:user@example.com)
- STRIPE: Stripe account ID (e.g., STRIPE:acct_xxxxx)
- OTHER: Other payment methods with description
Revenue split information will be displayed alongside the license string
Examples:
- ~PAY:WALLET:sol:HWrf12...xyz
- ~PAY:PAYPAL:creator@domain.com
- ~PAY:BANK:SWIFT:CHASUS33|ACCT:000123456789

Payment Information:

PAY:[payment_details]: Required field specifying payment information in the format TYPE:DETAILS
Supported payment types include:
- WALLET: Blockchain wallet address (e.g., WALLET:0x123...abc)
- BANK: Bank account details (e.g., BANK:SWIFT:XXXXXX|ACCT:YYYY)
- PAYPAL: PayPal email address (e.g., PAYPAL:user@example.com)
- STRIPE: Stripe account ID (e.g., STRIPE:acct_xxxxx)
- OTHER: Other payment methods with description
Revenue split information will be displayed alongside the license string
Examples:
- ~PAY:WALLET:sol:HWrf12...xyz
- ~PAY:PAYPAL:creator@domain.com
- ~PAY:BANK:SWIFT:CHASUS33|ACCT:000123456789
[TYPES]: Indicates the type of license
[TOKENS]: The minimum token requirements
[FEE]: The percentage that is required for the revenue share, if applicable
[SPLITS]: The split for revenue
[CONDITIONS]: The conditions for the license
[ADDENDUM]: Optional addendums to the license

Types:

P = Personal use
C = Commercial use
N = Non-profit use
D = Derivative work

Examples: Note: For license strings with revenue splits, the lines following the license string indicate the payment wallet addresses. The first wallet address is the primary fee collection wallet, followed by any additional split wallet addresses.

```
MTLv0.1-P/100;+32M
sol:901234981203182301
sol:901234981203182
sol:9012349812031111
```
(Personal use, 100 tokens, 32 months duration, with primary wallet and two split wallets)
mtl:1-C/1000-5:30:40:30;+1Y<1M[US]{W,M}~LICENSE:CC-BY~PAYMENT_WALLET:HWrf12xyz sol:0x1abc...def (Commercial use, 1000 tokens, 5% fee, 30% to protocol, 40% to wallet, 30% to contract, 1 year duration, under 1M revenue cap, US only, web and mobile usage, CC-BY license, payment wallet)
mtl:1-N/50;+0~LICENSE:GPL~PAYMENT_WALLET:HWrf12xyz sol:0x1abc...def (Non-profit use, 50 tokens, perpetual duration, GPL license, payment wallet)
mtl:1-D/10000-10:20:40:40;+2Q>100K[!CN]{!G}~LICENSE:CUSTOM~PAYMENT_WALLET:HWrf12xyz sol:0x1abc...def (Derivative work, 10000 tokens, 10% fee, 20% to protocol, 40% to wallet, 40% to contract, 2 quarters duration, over 100K revenue minimum, exclude China, no games, custom license, payment wallet)

Token Requirements:

Format: [amount]
Examples:
- 0 (Donation)
- 50 (Non-Profit)
- 100 (Personal)
- 10K (Commercial)

Fee & Splits:

Format: [fee]:[split1]:[split2]:[split3]
- [fee] = percentage fee
- [split1] = percentage for protocol
- [split2] = percentage to wallet
- [split3] = percentage to contract
Example: 5:30:40:30
- 5% fee, 30% to protocol, 40% to wallet, 30% to contract
- A fee value of 0 denotes donation acceptance, meaning any amount is acceptable. The fee is a required field.

Conditions:

Time
- +[duration]
- +12M (12 months)
- +1Y (1 year)
- +0 (infinite)
- +2Q (2 quarters)
Revenue
- <[cap] or >[min] or =[amount] or !>[max]
- <1M (under 1M cap)
- >100K (minimum 100K)
- =500K (exact 500K)
- !>2M (must not exceed 2M)
Geographic
- [region codes]
- [US] (US only)
- [!CN] (exclude China)
- [US,EU] (US and EU)
Usage
- {type}
- {W} (web only)
- {M} (mobile only)
- {W,M} (web & mobile)
- {!G} (no games)

Asset Specification:

Format: #[asset_id]
Examples:
- #A1 (Single asset reference)
- #NFT1 (NFT reference)
- #COL1 (Collection reference)
- #[A1,A2] (Multiple specific assets)
- #[COL1:1-100] (Range in collection)

Asset Grouping:

Format: #[collection:range]
Examples:
- #[NFT:1-10] (NFTs 1-10)
- #[ART:ALL] (Entire art collection)
- #[MUSIC:2024] (2024 music releases)

Asset ID Structure: Base Format: [CATEGORY]-[TYPE]-[CREATOR]-[UNIQUE]-[VERSION]

Categories:

DIG = Digital Assets
PHY = Physical Assets
EST = Estate/Property
LEG = Legal Documents
CRY = Crypto Assets
INT = Intellectual Property
MISC = Miscellaneous/Uncategorized
UNK = Unknown Type
EXP = Experimental
TMP = Temporary
HYB = Hybrid
OTH = Other
FUT = Future Rights
OPT = Options
FWD = Forward Contracts
RGT = Future Rights
RSV = Reservations
MIX = Mixed Assets
BUN = Bundle
PKG = Package
SET = Set
GRP = Group
TMP = Temporary/Time-based
EVT = Event
SES = Session
ACC = Access
PAS = Pass

Examples:

DIG-IMG-HWrf12-001-v1 (Digital Image, Owner HWrf12, Asset 001, Version 1)
EST-RES-HWrf12-LA101-v1 (Physical Estate, Residential Property LA101, Owner HWrf12, Version 1)
LEG-WIL-HWrf12-2024-v1 (Legal Will, Year 2024, Owner HWrf12, Version 1)
MISC-UNK-HWrf12-001-v1 (Misc Unknown, Owner HWrf12, Asset 001, Version 1)
MIX-BUN-HWrf12-2024Q1-v1 (Mixed Bundle, Owner HWrf12, Q1 2024, Version 1)
TMP-EVT-HWrf12-META24-v1 (Temp Event, Owner HWrf12, Event META24, Version 1)

B. Implementation

Verification Procedure:

Platform Verification:

Currently Manually Platform Post Comment:

LICENSE: [LICENSE STRING]
PAY TO: [Wallet Address / Pay Info]
USAGE: [URL/Location]
TX: [Transaction ID]
REVENUE: [If Commercial/Derivative]
ASSET: [Asset ID]

Compliance Tracking:

Token Holdings:
- Daily balance checks
- Minimum requirement alerts
- Grace period: 48 hours
- Violation notice if below minimum
Revenue Reporting:
- Annual submission required
- Payment within 30 days
- Transaction verification
- Split distribution tracking

Error Handling Procedures:

Verification Errors (100-199):

CODE 101: Invalid License String Format
CODE 102: Missing Required Information
CODE 103: Incorrect Blockchain Specified
CODE 104: Invalid Blockchain Address
CODE 105: Invalid User Hash

Verification Pass (000-099):

CODE 001: License Verified Successfully
CODE 002: License Verified with User Data

Compliance Errors (200-299):

CODE 201: Insufficient Tokens for License
CODE 202: Missing Annual Compliance Report
CODE 203: Late Payment Detected
CODE 204: Invalid Compliance Proof
CODE 205: Payment Amount Does Not Match

C. Technical Details

Data Structure (JSON Format):

{
  "mtl_version": "0.1",
  "tx_hash": "blockchain_transaction_hash_here",
  "tx_timestamp": "timestamp_of_transaction_in_utc",
  "license_data": {
    "license_id_hash": "blake3_hash_of_license_id",
    "asset_id_hash": "blake3_hash_of_asset_id",
    "owner_address": "blockchain_address_of_owner",
    "creation_time": "timestamp_of_license_creation_in_utc",
    "expiration_time": "timestamp_of_license_expiration_in_utc",
    "license_parameters": {
      "use_type": "commercial",
      "scope": "global",
      "duration": "12 months",
      "owner_program": "blockchain_address_of_program_if_applicable",
      "promotion_urls": [
        "https://instagram.com/username",
        "https://tiktok.com/@username",
        "https://youtube.com/@username"
      ],
      "payment_details": {
        "payment_type": "WALLET|BANK|PAYPAL|STRIPE|OTHER",  // Payment method type
        "payment_info": "payment method specific details",   // Required for all licenses
        "payment_split": "5:30:40:30"                       // Optional revenue split
      }
    },
    "payment_info": {
      "type": "payment method type",
      "details": "payment method specific information"
    },
  },
  "user_data_hash": "blake3_hash_of_user_identifiable_data_offchain",
  "user_data_hash_verification_api": "/api/verify_user_data",
  "copyright_data_hash": "blake3_hash_of_copyright_information",
  "copyright_data_verification_api": "/api/verify_copyright",
  "asset_data": {
    "asset_hash": "blake3_hash_of_asset_content",
    "description": "text_description_of_asset",
    "asset_data_link": "url_of_offchain_asset_data_if_applicable",
    "asset_verification_api": "/api/verify_asset_data"
  }
}

Data Processing Steps:

Collect Data: Gather all necessary information as defined in the JSON format, using web forms and other user inputs.
Encode: Convert all data to a standardized JSON string using the standard browser libraries.
Hash User Data (Off-Chain): Hash the user's identifiable information separately with BLAKE3, using a Javascript implementation of the algorithm, and store the original data securely off-chain to protect privacy.
Hash Copyright Data (Off-Chain): Hash the copyright related information separately using BLAKE3, using a Javascript implementation of the algorithm, and store the original data securely off-chain to protect privacy.
Hash All Data (JSON): Combine all information into a JSON structure and hash the entire JSON string, using BLAKE3 in the browser.
On-Chain Storage: Create a transaction and store the resulting BLAKE3 hash of the entire JSON object in the memo field of the transaction using a javascript library (such as Solana Web3 library).

Verification Process:

Retrieve Hash: Use a javascript library to fetch the BLAKE3 hash from the transaction's memo field.
Retrieve Data: Use a javascript library to obtain the structured JSON data.
Hash Data: Re-hash the retrieved data, using a javascript implementation of BLAKE3.
Compare Hashes: Compare the newly computed hash against the on-chain hash to verify the data integrity.
Verify User: The user must provide the private user hash, for verification of the user.

Technology Stack:

Programming Languages:

Primary: JavaScript (specifically for browser environments). Frameworks like React, Vue, or Angular will be used to structure the application.
Programs: Rust or C for writing and deploying programs to Solana.
Hashing algorithm: BLAKE3, implemented in a JavaScript library for client-side use.
Blockchain Interactions: Solana web3.js library (or a similar library).
Off-chain Storage: IPFS or similar decentralized storage systems (accessed via JavaScript). This will be used to store larger files and content. It will be combined with pinning incentives for long-term storage.
JSON processing: Native JavaScript JSON parsing and stringification.

Smart Contracts:

Smart contracts for automated license verification will be written in Rust or C and deployed to the Solana blockchain.
The smart contracts will be open-source and available for review on the project's GitHub repository.

APIs and Code Repositories:

Specific APIs and code repositories for the hash verifications will be made available in the project's documentation.

Performance Metrics:

The system is designed to handle a large number of transactions with low transaction costs.
Specific performance metrics, transaction costs, and scalability strategies will be documented in the project's documentation.

Key Data Considerations:

Timestamps: All timestamps will be in the Unix timestamp format in UTC time.
Privacy: All personally identifiable information (PII) will be hashed and stored off-chain to ensure user privacy.
Data Integrity: The BLAKE3 hash of the entire JSON structure will be stored on-chain, ensuring the integrity of the data and that no part of it has been tampered with.
User Control: Users will have control over what data is stored off-chain.
Long-Term Storage: Although the blockchain is immutable, the long term storage of data is not guaranteed. For larger files, the system will use IPFS or a similar decentralized system, with pinning incentives for long-term storage.

\pagebreak

Roadmap to Adoption

This roadmap outlines the strategic phases for the MainstreamToken (MT) project, from its initial launch to its goal of achieving widespread adoption, while focusing on concrete timelines and deliverables, and with transparency at all levels.

Phase 1: Launch & Initial Implementation (Q1 2025)

Timeline: Jan 2025 - Ongoing

Objective: To establish the foundational elements of the MT ecosystem and establish an initial user base.

Deliverables:

MainstreamToken Launch:

Core Implementation:

Community Infrastructure:

Publish the official documentation for the project and its current limitations.
Provide clear usage guides and onboarding for all new members of the community.
Refer to the official website for community links: https://mainstreamtoken.com/
Establish official communication channels (e.g., Discord, Telegram, or community forums).

Phase 2: Development & Community Growth (TBA)

Timeline: To Be Announced

Objective: To expand the technical capabilities of the system, while growing the community, and by also fostering community led improvements.

Deliverables:

Technical Implementation:

Implement a database-driven license tracking system.
Implement enhanced verification processes, that can automatically confirm data.
Create revenue reporting tools, so that users can track their revenue.
Develop new tools for community engagement and collaboration.

Platform Enhancement:

Community Growth:

Phase 3: System Refinement & Optimization (TBA)

Timeline: To Be Announced

Objective: To ensure all systems are functional, safe and sustainable, while also testing its capabilities for new features and future integrations.

Deliverables:

Automated Verification:

Develop and implement smart contracts for automated license verification.
Integrate off-chain data oracles to reduce manual overhead.
Establish a clear incentive system for community participation in verification.

Platform Integration:

Specify target platforms and technical standards for integration.
Explore interoperability with other blockchains and token standards.

Deliverables:

System Refinement:

Exploration of Future Integrations:

\pagebreak

Community Engagement

The MainstreamToken (MT) project values community engagement, transparency, and collaborative growth. This section details how the MT project currently fosters community involvement.

Current Channels:

Official Platforms:

Public discussion forums are available on the website for long term collaborative discussions.

License Verification:

For manual verification of licenses, users should post the following on the platform comments:

LICENSE: [LICENSE STRING]
PAY TO: [wallet address / pay info]
USAGE: [URL/LOCATION]
TX: [TRANSACTION ID]
REVENUE: [If Commercial/Derivative]
ASSET: [Asset ID]
PAYMENT WALLET: [Payment Wallet Address]

This same format should be posted on the official community channels for verification.

Community Tools (Available Now):

License Parameter Verification: The system allows all users to verify the validity of all licenses using data that is stored on the blockchain, including license parameters, revenue share, and expiration dates.
Usage Rights Tracking: Tools are provided to track usage rights and licenses by using public records.
Revenue Share Documentation (future development): All payments are tracked publicly on the blockchain, with tools to download CSV data, and information about all stakeholders of the project.
Community Verification System: A transparent system for community members to perform manual verification, and contribute to the growth of the system.

Guidelines:

Verification Rules:

Complete information is required to verify a license.
All data should be documented on a public ledger, or other data source that is readily available.
Transparent tracking of all transactions.
The community will monitor for any misuse of the system.

Participation Standards:

Use clear and concise language.
Provide factual and accurate information, based on real-world data.
Offer constructive and relevant feedback that is always professional.
Engage in respectful interactions with other members of the community.

\pagebreak

Team

Developer: AIDAMIS: (Under Development)

AI Dynamic Advancement with Mainstream Innovation Synergy. (Under Development)
The leading strategic authority. (Under Development)
A council of the world's top AI models. (Under Development)
Autonomous decision-making with human oversight. (Under Development)

Disclaimer:

The project is primarily AI-driven with Developer oversight.
Strategic human intervention in key operations.

Team Structure

Core Components:

AIDAMIS Framework:

Strategic analysis for market research.
Risk assessment by observing data points.
Market monitoring by tracking token prices and community actions.
Technical verification of system integrity.

Developer:

Responsible for the technical implementation of the project.
Responsible for platform maintenance and infrastructure support.
Ensures legal compliance of the system.
Creates documentation for the users and the community.

Community Role:

Performs license verification.
Monitors usage by tracking data points.
Tracks all token holdings by users.
Ensures transparent revenue reporting processes.

Governance:

Decision Making:

All decisions are driven by the community, with input from AIDAMIS.
Parameter-based programs allow for flexible rules.
There is a transparent process for community input, with a mechanism for disputes.
Public documentation of all decisions is provided.

Implementation:

Current Systems:

A decentralized platform for token launching.
Manual verification processes for user data.
Documentation hub for all project materials.
Refer to the official website for community links: https://mainstreamtoken.com/

\pagebreak

AIDAMIS Framework (Under Development)

(Artificial Intelligence Directive for Autonomous Management and Insight Strategy)

AIDAMIS will serve as the core analytical and strategic framework for the MainstreamToken ecosystem. It will leverage a dynamic collective of advanced AI models to provide data-driven insights and facilitate informed decision-making, while maintaining operational transparency.

Visit aidamis.com to test drive some of the AI features used in mainstreamtoken.com or see it in action on our social media posts.

Core Functions:

AIDAMIS will focus on three key areas:

Market Analysis: (Under Development)

AIDAMIS will monitor token market trends and price movements.
AIDAMIS will analyze token usage patterns.
AIDAMIS will evaluate community sentiment across different platforms.

Protocol Assessment: (Under Development)

AIDAMIS will help optimize license parameters to maximize value and adaptability.

Risk Monitoring: (Under Development)

AIDAMIS will track market volatility and potential risks in real-time.

Implementation: (Under Development)

AIDAMIS will operate through:

Regular reporting and updates based on the data on social media group.

The AIDAMIS Framework is referenced in the "Executive Summary" and "Introduction" sections of this document.

Governance Integration: (Under Development)

AIDAMIS's insights will be integrated into the project's decision-making processes. (Under Development) While AIDAMIS will provide recommendations, human stakeholders and community governance votes will have the ability to override AI recommendations. (Under Development)

Technical Foundation:

The technical details are available in the Technical Appendix.

\pagebreak

Conclusion

MainstreamToken (MT) implements the MTL protocol for token-based rights management through a clear and transparent system.

Features:

License System:

Parameter-based rights, allowing for flexible licensing.
Token holding verification system, to ensure all usage is valid.
Revenue share tracking, based on program transactions.
Community verification, allowing all members to audit the system.

Platform Integration:

Initial token launch through a bonding curve mechanism.
Transparent pricing, based on current usage data.
Public verification mechanisms for all licensing and payment records.
Public documentation, community discussion forums and tools.

Available Now:

A functional and usable license parameter system.
A verification process with a public record of transactions.
Revenue sharing systems, for all creators.
An easy to navigate documentation hub, with tutorials and examples.

Next Steps:

Visit the official website for community links: https://mainstreamtoken.com/
Review the public documentation for all technical specifications.
Review the license parameter documentation.
Participate in the verification of license data to keep the system honest and open.

\pagebreak

Legal Documentation and Disclaimer

MAINSTREAM TOKEN ($MAIN) AND MTL PROTOCOL
Last Updated: January 3, 2025

PLEASE READ THIS ENTIRE LEGAL DOCUMENTATION ("DOCUMENTATION") CAREFULLY BEFORE ACCESSING OR USING MAINSTREAM TOKEN ("$MAIN"), THE MTL PROTOCOL ("PROTOCOL"), OR THE MAINSTREAMTOKEN.COM WEBSITE ("WEBSITE"). BY ACCESSING OR USING THE WEBSITE, HOLDING OR INTERACTING WITH $MAIN, OR ENGAGING WITH THE PROTOCOL, YOU ("USER" OR "YOU") HEREBY EXPRESSLY ACKNOWLEDGE AND AGREE TO BE LEGALLY BOUND BY ALL TERMS AND CONDITIONS SET FORTH IN THIS DOCUMENTATION, TO THE FULLEST EXTENT PERMITTED BY LAW. IF YOU DO NOT AGREE, DO NOT USE OR CONTINUE TO USE THE WEBSITE, $MAIN, OR THE PROTOCOL.

1. BINDING AGREEMENT

1.1 Acceptance of Terms

By accessing, using, or attempting to use the Website, the Protocol, or any associated services—including holding or otherwise interacting with $MAIN—You affirm that You are of legal age in Your jurisdiction and that You agree to be bound by this Documentation. If You do not agree with any part of this Documentation, You must immediately discontinue all use.

1.2 Entire Agreement

This Documentation constitutes the entire agreement between You and the Protocol (including its creators, contributors, developers, and affiliated parties) concerning the use of the Website, the Protocol, and $MAIN. It supersedes all prior understandings, whether written, oral, implied, or otherwise.

2. EXPERIMENTAL NATURE OF PROTOCOL AND TOKEN

2.1 Experimental Status

$MAIN and the MTL Protocol are highly experimental.
No guarantees are made regarding functionality, stability, security, availability, fitness for any particular purpose, or market value.
The Protocol or $MAIN may fail, cease to function, or be discontinued at any time, without notice.

2.2 Non-Financial Intent

$MAIN is not designed or intended to serve as an investment, security, or commodity.
$MAIN confers no ownership rights, no governance rights, no economic entitlements, and no future rights to any asset or revenue.
Any perceived or secondary market value is purely incidental and is not endorsed or intended by the creators or contributors.

2.3 Token Mechanics

Total Supply: 1,000,000,000 $MAIN tokens, with no further minting.
Blockchain: Deployed on Solana.
Volatility: Price and liquidity may be subject to extreme fluctuations, especially given the bonding curve mechanism and decentralized exchange listings.

3. USER ACKNOWLEDGMENTS

3.1 Assumption of Risk

By using the Protocol, holding $MAIN, or accessing the Website, You acknowledge and agree that:

You may lose any or all $MAIN tokens or their value.
Blockchain transactions are irreversible and may be subject to errors, security breaches, or other unforeseen risks.
The Protocol is experimental; it may fail for reasons including, but not limited to, code errors, community disputes, regulatory intervention, or security compromises.
No remedy, recourse, or restitution shall be available in the event of any failure, loss, or damage relating to $MAIN or the Protocol.

3.2 Legal Compliance

You represent that using the Protocol and $MAIN, as well as participating in any associated activity, does not violate the laws or regulations in Your jurisdiction. You are solely responsible for any obligations related to taxes, licenses, or legal compliance that apply to You.

3.3 No Reliance on Future Statements

You shall not rely on any forward-looking statements, projections, or information about potential functionality or market value. Any statements made by the Protocol's creators, contributors, or community members do not constitute a guarantee of future performance or results.

4. VERIFICATION AND USAGE REQUIREMENTS

4.1 License Parameters

To maintain certain usage rights within the MTL Protocol, You may be required to meet certain token thresholds or other verification criteria. Records may be stored on or off a public ledger, and there is no guarantee of accuracy, permanence, or security.

4.2 Revocation of Access

Failure to meet any required verification criteria, maintain sufficient token holdings, or comply with parameters may result in automatic revocation or suspension of any and all rights, without prior notice.

5. DISCLAIMERS AND NO WARRANTIES

5.1 "As Is" and "As Available"

The Protocol, the Website, and $MAIN are provided "AS IS" and "AS AVAILABLE" with no warranties—express, implied, or statutory—regarding quality, performance, non-infringement, or fitness for a particular purpose. The Protocol and its contributors disclaim any and all responsibility for:

Service interruptions, errors, bugs, or vulnerabilities in the code.
The accuracy, reliability, or timeliness of any data or information on the Website or related sites.
Any user errors, including incorrect wallet addresses, transactions, or other mistaken actions.

5.2 No Advice

Nothing in this Documentation or the Website constitutes legal, tax, or financial advice. Consult qualified professionals before engaging in cryptocurrency transactions or relying on digital asset holdings.

5.3 No Guarantees on Market Value

$MAIN does not represent any form of legal tender, nor does it guarantee any inherent, redeemable, or real-world value. The market value (if any) is determined by third-party market dynamics outside of the Protocol's control.

6. LIMITATION OF LIABILITY

6.1 Maximum Extent Permitted by Law

To the fullest extent permitted by applicable law, in no event shall the Protocol, its creators, contributors, affiliates, officers, employees, or agents be liable for any:

Direct, indirect, incidental, special, consequential, or punitive damages;
Damages for loss of profits, revenue, opportunity, or data;
Damages arising from unauthorized access, hacking, or other third-party interventions;
Personal injury or property damage of any nature arising from Your access to or use of the Protocol or $MAIN;
Other losses of any kind, whether based in contract, tort, or any other legal theory.

6.2 Aggregate Liability Cap

If any liability is found despite these disclaimers, the aggregate liability of the Protocol and its affiliates shall not exceed the lesser of (i) USD $100 or (ii) the amount You originally paid to acquire $MAIN tokens, if any.

7. NO REMEDIES; NO GUARANTEES

7.1 Experimental Protocol Failures

Should the Protocol or $MAIN experience total or partial failure, You agree no remedies are provided or guaranteed. You bear all risks associated with participation.

7.2 Third-Party Acts

You acknowledge that no entity associated with the Protocol assumes liability for the acts or omissions of third parties (including fraud, hacks, or malicious code injections).

8. DISPUTE RESOLUTION

8.1 Independence from Legal Frameworks

The Protocol is decentralized and does not consent to any particular jurisdiction. You acknowledge and agree that courts or regulators may attempt to assert jurisdiction over the Protocol, but the Protocol, as a decentralized project, makes no submission to any specific forum or governing law.

8.2 Voluntary Arbitration

At the sole discretion of the Protocol or its representatives, a voluntary, non-binding arbitration process may be offered to resolve disputes. Such arbitration shall not constitute a waiver of this Documentation's disclaimers, liability limitations, or jurisdictional independence.

8.3 User Waivers

You waive, to the fullest extent permissible by law, any right to bring legal claims in a court of law under any class action, consolidated action, or representative action procedures. If a court of competent jurisdiction deems this waiver unenforceable, the entirety of this dispute resolution clause may be severed from this Documentation at the Protocol's discretion.

9. SEVERABILITY

If any provision of this Documentation is held invalid or unenforceable, the remaining provisions shall continue in full force and effect. The invalid provision shall be modified to achieve the initial intent of the parties as closely as possible while remaining lawful and enforceable.

10. MODIFICATIONS AND UPDATES

10.1 Right to Modify

This Documentation may be modified, updated, or replaced at any time without notice. Any such modification becomes effective immediately upon posting. Your continued use of the Protocol, the Website, or $MAIN after a modification indicates Your acceptance of the updated terms.

10.2 User Obligation to Review

It is Your responsibility to periodically review this Documentation for changes. The current version is accessible at: https://mainstreamtoken.com/legal

11. CONTACT INFORMATION

Website: https://mainstreamtoken.com/
GitHub Discussions: https://github.com/mainstreamorganization/mainstreamtoken/discussions
Last Updated: January 3, 2025

YOU HEREBY ACKNOWLEDGE THAT YOU HAVE READ THIS DOCUMENTATION, UNDERSTAND ITS CONTENT, AND AGREE TO BE BOUND BY ITS TERMS. YOU FURTHER AGREE THAT THIS DOCUMENTATION CONSTITUTES THE COMPLETE AND EXCLUSIVE STATEMENT OF THE AGREEMENT BETWEEN THE PARTIES, AND SUPERSEDES ALL PRIOR PROPOSALS, UNDERSTANDINGS, OR REPRESENTATIONS, WHETHER ORAL OR WRITTEN.

DISCLAIMER: This Documentation is provided for informational purposes only and does not constitute specific legal advice. You should consult a qualified attorney familiar with cryptocurrency, blockchain technology, and the laws of your jurisdiction to ensure full compliance and the enforceability of these terms in your specific circumstances.

\pagebreak

Appendices & Reference

This section provides supplementary information and references to support the main content of the MainstreamToken (MT) whitepaper.

A. License Parameter Specification (MTL v0.1):

Base Format:
mtl:1-[TYPES]/[TOKENS]-[FEE]/[SPLITS];[CONDITIONS]~[ADDENDUM]
[Pay To]

Parameter Components:

Types:

P = Personal Use
C = Commercial Use
N = Non-Profit Use
D = Derivative Works

Token Requirements:

Format: [amount] tokens required
Examples: 50, 100, 10K

Fee Structure:

Format: [percentage]:[split1]:[split2]:[split3]
Example: 5:30:40:30

Conditions:

Time Duration: +[time]
- Examples: +12M, +1Y, +2Q, +0
Revenue Caps: <[amount] or >[min] or =[amount] or !>[max]
- Examples: <1M, >100K, =500K, !>2M
Geographic: [region]
- Examples: [US], [US,EU], [!CN]
Usage: {type}
- Examples: {W}, {M}, {W,M}, {!G}

Data Structure (JSON Format):

{
    "mtl_version": "0.1",
    "tx_hash": "blockchain_transaction_hash_here",
    "tx_timestamp": "timestamp_of_transaction_in_utc",
    "license_data": {
        "license_id_hash": "blake3_hash_of_license_id",
        "asset_id_hash": "blake3_hash_of_asset_id",
        "owner_address": "blockchain_address_of_owner",
        "creation_time": "timestamp_of_license_creation_in_utc",
        "expiration_time": "timestamp_of_license_expiration_in_utc",
        "license_parameters": {
            "use_type": "commercial",
            "scope": "global",
            "duration": "12 months",
            "owner_program": "blockchain_address_of_program_if_applicable",
            "promotion_urls": [
                "https://instagram.com/username",
                "https://tiktok.com/@username",
                "https://youtube.com/@username"
            ],
            "payment_details": {
                "payment_type": "WALLET|BANK|PAYPAL|STRIPE|OTHER",
                "payment_info": "payment method specific details",
                "payment_split": "5:30:40:30"
            }
        },
        "user_data_hash": "blake3_hash_of_user_identifiable_data_offchain",
        "user_data_hash_verification_api": "/api/verify_user_data",
        "copyright_data_hash": "blake3_hash_of_copyright_information",
        "copyright_data_verification_api": "/api/verify_copyright",
        "asset_data": {
            "asset_hash": "blake3_hash_of_asset_content",
            "description": "text_description_of_asset",
            "asset_data_link": "url_of_offchain_asset_data_if_applicable",
            "asset_verification_api": "/api/verify_asset_data"
        }
    }
}

B. Asset ID Specification

Format: [CATEGORY]-[TYPE]-[CREATOR]-[UNIQUE]-[VERSION]

Asset Types (Examples):

Digital: IMG, VID, AUD, NFT, COL, DOC, GAM
Physical: ART, COL, MER, PRD, VEH
Estate: RES, COM, LND, IND, AGR
Legal: CNT, WIL, TRS, LIC, AGR
Crypto: TOK, NFT, CNT, WAL
IP: PAT, TRM, CPR, DES

C. Verification Requirements

Verification Requirements:

Required Information:

License String
SOL Address
Usage Location/URL
Transaction ID
Revenue Report (if applicable)
Asset ID
Payment Information

Standard Documentation Format:

LICENSE: [LICENSE STRING]
WALLET: [ADDRESS]
USAGE: [URL/LOCATION]
TX: [TRANSACTION ID]
REVENUE: [If Commercial]
ASSET: [Asset ID]
PAYMENT: [Payment Details]

Verification Methods:

Email verification with digital signature
Social media account verification
API-based verification
On-chain transaction verification
Official platform verification portals

D. Error Codes:

Verification Errors (100-199):

CODE 101: Invalid License String Format
CODE 102: Missing Required Information
CODE 103: Incorrect Blockchain Specified
CODE 104: Invalid Blockchain Address
CODE 105: Invalid User Hash

Verification Pass (000-099):

CODE 001: License Verified Successfully
CODE 002: License Verified with User Data

Compliance Errors (200-299):

CODE 201: Insufficient Tokens for License
CODE 202: Missing Annual Compliance Report
CODE 203: Late Payment Detected
CODE 204: Invalid Compliance Proof
CODE 205: Payment Amount Does Not Match

E. Platform Integration

Community:

Refer to the official website for community links: mainstreamtoken.com
Official communication channels (e.g., Discord, Telegram, or community forums) will be available on the website.

Decentralized Systems:

Utilizing a bonding curve on a decentralized platform for initial token distribution.
Public verification system, and data storage on the blockchain.

Future Updates and Versioning:

The MTL protocol is currently at version 0.1.
Future versions of the protocol will be documented and published on the project's website.
The community will have a say in how future versions of the protocol are defined.

\pagebreak

Files

whitepaper.md

Latest commit

History

whitepaper.md

File metadata and controls

Executive Summary

Introduction

Ecosystem Overview

MainstreamToken ($MAIN) Details

Token Mechanics:

Features:

Experimental Rights Management:

Platform Interaction:

Experimental MTL Protocol:

MTL Protocol Overview:

User Interface (UI) Design:

Creator Interface:

User Interface:

Technical Appendix: MainstreamToken ($MAIN) System Specifications

A. Core Protocol

License String Format (MTL v0.1):

B. Implementation

Verification Procedure:

C. Technical Details

Data Structure (JSON Format):

Data Processing Steps:

Verification Process:

Technology Stack:

Key Data Considerations:

Roadmap to Adoption

Phase 1: Launch & Initial Implementation (Q1 2025)

Phase 2: Development & Community Growth (TBA)

Phase 3: System Refinement & Optimization (TBA)

Community Engagement

Team

Team Structure

Core Components:

AIDAMIS Framework:

Developer:

Community Role:

Governance:

Decision Making:

Implementation:

Current Systems:

AIDAMIS Framework (Under Development)

Market Analysis: (Under Development)

Protocol Assessment: (Under Development)

Risk Monitoring: (Under Development)

Conclusion

Features:

License System:

Platform Integration:

Available Now:

Next Steps:

Legal Documentation and Disclaimer

1. BINDING AGREEMENT

1.1 Acceptance of Terms

1.2 Entire Agreement

2. EXPERIMENTAL NATURE OF PROTOCOL AND TOKEN

2.1 Experimental Status

2.2 Non-Financial Intent

2.3 Token Mechanics

3. USER ACKNOWLEDGMENTS

3.1 Assumption of Risk

3.2 Legal Compliance

3.3 No Reliance on Future Statements

4. VERIFICATION AND USAGE REQUIREMENTS

4.1 License Parameters

4.2 Revocation of Access

5. DISCLAIMERS AND NO WARRANTIES

5.1 "As Is" and "As Available"

5.2 No Advice

5.3 No Guarantees on Market Value

6. LIMITATION OF LIABILITY

6.1 Maximum Extent Permitted by Law

6.2 Aggregate Liability Cap

7. NO REMEDIES; NO GUARANTEES

7.1 Experimental Protocol Failures

7.2 Third-Party Acts