Risks, Disclaimers & FAQ

This whitepaper contains forward-looking statements and design goals. Actual outcomes depend on contract deployments, security audits, market adoption, and operational execution.

Smart Contract and Security Risk

Smart contracts underpin claiming and reward accounting. Risks include:

• vulnerabilities in contract logic

• unexpected behavior due to edge cases in accounting

• operational errors during deployment or parameter configuration

Mitigation includes security audits, test coverage, and carefully managed deployments.

Economic and Market Risk

Token utility and profit-sharing depend on:

• sustained launch activity and fee revenue

• token market conditions and holder behavior

• the ability of the platform to attract users and collections

If platform revenue underperforms, reward distribution size may be smaller than expected.

Operational Risk

The claim period is managed by the reward contract and app logic. Risk factors include:

• incorrect configuration of the claim window

• user wallet/network mismatches

• UI/UX issues that confuse users during claim windows

Regulatory and Legal Considerations

Profit-sharing token mechanics can be subject to regulatory interpretation depending on jurisdiction. This document does not provide legal advice. Token holders should consult qualified legal professionals if needed.

FAQ

What counts as "profits"?

"Profits" and distribution accounting are defined by the final reward contract implementation and its accounting logic. Users should rely on on-chain data and contract documentation for exact definitions.

When can I claim?

The claim period is intended to be set between the 15th and 17th of each month. Claims should only be available during active periods as indicated by on-chain contract state.

Is the reward shown in ETH?

The intended user experience is to display available rewards in ETH (on the claim environment), matching the expected payout denomination.

Where are claims executed?

The Mintly reward experience is designed around Base. Users should switch to Base before claiming to ensure network compatibility.

What if the claim period is not active?

The claim UI should be hidden or disabled when the claim period is not active to prevent failed transactions.