Fees and Protocol Revenue
CICADA Finance monetizes its onchain asset management platform through a multi-layered revenue framework designed to scale with managed assets and actual performance. Fees and revenues are generated across the full asset lifecycle—onboarding, issuance, liquidity operation, settlement, and distribution—while emphasizing transparency and long-term alignment.
Note: Fee items and parameters may differ by asset category and are disclosed on the relevant product pages and/or governance-controlled parameter registries, where applicable.
Protocol-Level Revenues
Asset Management Fees
CICADA Finance may charge management and operational fees for maintaining asset products and their lifecycle processes, including monitoring, settlement coordination, reporting, and protocol operations. Fee basis and timing are asset-specific and disclosed per product.
Protocol Transaction Fees
CICADA Finance may charge fees for protocol functions that enable issuance, conversion (where applicable), liquidity routing, redemption workflows, and cross-chain operations. Users may also incur third-party costs (e.g., DEX aggregators, bridges, custodians), which should be disclosed at the interface level.
Yield Settlement & Distribution Fees
In addition to basic management fees, CICADA Finance may charge fees related to automated yield settlement and distribution only when underlying assets generate real yields and complete allocation. This creates structural alignment:
CICADA Finance does not profit in advance if assets do not generate yields
Avoids “charge first, perform later” dynamics
Strengthens long-term alignment between the platform, asset providers, and capital-side users
This is a revenue model centered on realised performance, not expectations.
Product-Level Revenues
CICADA Finance provides asset-side services to support professional originators entering onchain markets with durable product structures and long-term operational support. Revenue may be generated from:
Asset issuance & listing services: structure design, token model planning, protocol onboarding, and market-readiness support
Launchpad & structured product services: yield layering, risk isolation, and product combination designs tailored to different capital preferences
These services reflect higher professional value and product complexity and are distinct from basic protocol usage fees.
Advanced Service Revenues
As CICADA Finance expands managed asset types and operational depth, the platform may offer advanced services such as:
cross-chain asset management and liquidity efficiency solutions
composite yield and allocation frameworks under risk-control and compliance constraints
customized onchain asset management solutions for institutions, enterprises, or family offices
These services tend to be longer-term and higher-touch, supporting recurring revenue in mature phases.
Market, Integration, and Ecosystem Revenues
CICADA Finance may generate additional revenues from:
Market and trading access: listing-related services and Marketplace enablement (where applicable)
Integrations and partnerships: technical integration, interoperability support, and ecosystem collaboration programs
Launchpad enablement: launch-related service fees, and where a financing/credit structure exists, disclosure of any platform fees and applicable external costs
Transparency
CICADA Finance aims to ensure fee and revenue transparency through:
clear asset-level fee schedules and definitions
indication of whether displayed yields are gross or net of fees
separation of protocol-owned onchain assets vs custodied offchain assets and strategy capital
disclosure of third-party dependencies that may introduce additional costs
Scalability
CICADA Finance’s revenue model scales because the underlying framework is reusable across scenarios:
Multi-chain by design: the chain is an execution environment, not a business boundary
Paradigm replicability: CICADA Finance standardizes the asset management process while adapting token structures to each asset
Compliance compatibility: compliance is treated as configurable parameters, enabling jurisdiction-specific onboarding and disclosure without breaking core protocol logic
Last updated