Fee Sharing

Partners can easily integrate with Velora Protocol using the Velora API and control the fee structure of their integration, deciding whether to charge a swap fee or participate in surplus sharing.

♻ Fee Sharing Overview

Partner Fee = Yes
Partner Fee = No

Surplus Sharing = Yes

Not possible, fallbacks to Partner Fees = Yes and Surplus Sharing = No

Surplus: 50% to Partner or User 50% to Velora DAO

Surplus Sharing = No

Swap Fees: Market: 85% to Partner, 15% to Velora DAO

Delta: 100% to Partner

Surplus: Market: 100% to Velora DAO Delta: 50% to Velora DAO 50% to User

Swap Fee

Partners can charge a fee on the swaps they facilitate if they choose to. By default, Velora DAO collects 15% of this fee.

Surplus

As described above, Velora DAO keeps surplus by default. If the Partner decides not to charge a Swap fee, they can opt-in to keep 50% of the surplus to be used as best suited to the Partner's interest or to direct it to the user.

Our fee structure allows Partners to charge no extra fee. In that case, Velora DAO takes no added fees.

Revenue Sharing on Velora (when integrated into another dApp)

If you'd like to discuss how to harness Velora for your dAPP best, please reach out through our Contact Form.

What are the Velora DAO fees used for?

All fees collected by the Velora DAO are used to grow further and perpetuate the Velora Protocol. DAO members and proposals decide the specific initiatives, and it is up to governance and community participants to decide where to direct these fees.

Fee Claimer

Partners can choose to have their Partner fees, including Swap Fees and Surplus, redirected to a Fee Claimer contract, from where they can be claimed at will or sent directly to their wallet of choice using the isDirectFeeTransfer parameter.

For those Partners who chose Fee Claimer, fees can be claimed through the Velora Fee Claimer UI, using the wallet passed on the API call as partneraddress. The complete list of Fee Claimer addresses can be found in the Smart Contracts - Fee Claimer section.

For more information about API parameters setup, please refer to the Velora API Developers Documentation.

Last updated

Was this helpful?