Revenue and Fees

●Draft

Status: Draft
Version: 0.1.0
Last Updated: 2026-05-16
Owner: Axodus Treasury

---

Purpose

Revenue and fees are treasury inflows or routing mechanisms that may support ecosystem sustainability when implemented and reported correctly.

Scope

This document defines revenue sources, fee types, routing categories, revenue records, validation requirements, and risks. It must not be interpreted as a guarantee of revenue, liquidity, price support, or treasury yield.

Revenue Sources

• Business services, including consulting, development services, DAO service requests, BBA campaigns, and partner programs.
• Marketplace activity, including platform fees, course sales, service sales, royalties, or commissions when policy defines them.
• Academy activity, including paid courses, certifications, or partner training programs.
• Trading activity, including realized internal strategy revenue or implemented strategy access products.
• Tokenomics flows, including mint reporting, burn reporting, and future fee reporting only if contracts support them.
• DaaS or DeFi services when approved.
• Grants, sponsorships, or partner contributions.

Fee Types

Potential fee types include marketplace fees, operational fees, service fees, subscription fees, royalties, commissions, and performance fees. Token-level treasury, liquidity, or burn fees are not defined in the current $Neurons tokenomics model. Performance fees are compliance-sensitive and require product, legal, governance, and policy review before public use.

Revenue Routing

Revenue may be routed to treasury reserves, operating budgets, reward budgets, liquidity support, creator or tutor settlement, partner shares, token burn if supported by contract, or governance-allocated budgets.

Revenue Flow Record

A revenue flow record should include source, product or service, public-safe counterparty reference, asset, gross amount, fees, net amount, destination, routing category, settlement status, refund or chargeback status, reporting period, governance reference, and notes.

Historical Tokenomics Fee References

Older planning material referenced burn, liquidity, and treasury fee concepts. Those concepts are superseded for the current $Neurons documentation unless a future contract and governance record reintroduce them. They must not be described as active token mechanics.

Risk Considerations

Revenue risk includes overestimated revenue, fee opacity, settlement confusion, refunds or chargebacks, token fee mismatch, and compliance sensitivity around performance-based fees.