Profit Distribution & Rewards
Mintly introduces a direct profit-sharing mechanism designed to align platform monetization with community incentives.
The 50% Profit Distribution Model
Mintly distributes 50% of Mintly launchpad profits to token holders.
This is intended to:
make platform revenue capture more transparent to the community
create a durable reason to hold Mintly tokens
connect usage and adoption to token holder rewards over time
Monthly Claim Period
Rewards are claimable on a monthly schedule.
Claim period: between the 15th and 17th of each month
During active claim periods, the platform enables claim actions
Claim eligibility and reward availability are determined on-chain
Reward Read + Claim Flow (Conceptual)
The reward system is driven by on-chain functions that the platform can call to:
read how much reward is currently available for a specific wallet (displayed to users)
check whether the current claim period is active (controls claim button state)
execute the claim transaction (users receive their reward according to contract logic)
At a contract-method level, the intended flow maps to:
getAvailableReward(account): returns the available reward amount for the connected walletisCurrentClaimActive(): returns whether the current monthly claim period is activeclaimReward(): executes the claim for the caller when eligible
Reward Contract (Base)
The claim experience is executed on Base and targets the deployed reward contract:
rewardContractAddress:0xd31f89B9c726ede1Df6149aAc544FeFFD42473C0
In the Mintly UI, the value returned from getAvailableReward(account) is converted and displayed to users in ETH.
Payout Denomination (User Facing)
In the Mintly reward UX, available rewards are displayed in ETH and claims are executed on the Base network.
Users may be prompted to switch to Base before claiming to ensure the wallet and contract network match.
Important Notes
Reward amounts and claim availability depend on contract state, wallet eligibility, and the active claim window.
Any accounting that defines “profits” and reward allocation should be validated against the final contract implementation and documentation.
Last updated